<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 13:03:17 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-71305 — drm/display/dp_mst: Add protection against 0 vcpi</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-71305</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/display/dp_mst: Add protection against 0 vcpi&lt;/p&gt;
&lt;p&gt;When releasing a timeslot there is a slight chance we may end up
with the wrong payload mask due to overflow if the delayed_destroy_work
ends up coming into play after a DP 2.1 monitor gets disconnected
which causes vcpi to become 0 then we try to make the payload =
~BIT(vcpi - 1) which is a negative shift. VCPI id should never
really be 0 hence skip changing the payload mask if VCPI is 0.&lt;/p&gt;
&lt;p&gt;Otherwise it leads to
&amp;lt;7&amp;gt; [515.287237] xe 0000:03:00.0: [drm:drm_dp_mst_get_port_malloc
[drm_display_helper]] port ffff888126ce9000 (3)
&amp;lt;4&amp;gt; [515.287267] -----------[ cut here ]-----------
&amp;lt;3&amp;gt; [515.287268] UBSAN: shift-out-of-bounds in
../drivers/gpu/drm/display/drm_dp_mst_topology.c:4575:36
&amp;lt;3&amp;gt; [515.287271] shift exponent -1 is negative
&amp;lt;4&amp;gt; [515.287275] CPU: 7 UID: 0 PID: 3108 Comm: kworker/u64:33 Tainted: G
S U 6.17.0-rc6-lgci-xe-xe-3795-3e79699fa1b216e92+ #1 PREEMPT(voluntary)
&amp;lt;4&amp;gt; [515.287279] Tainted: [S]=CPU_OUT_OF_SPEC, [U]=USER
&amp;lt;4&amp;gt; [515.287279] Hardware name: ASUS System Product Name/PRIME Z790-P
WIFI, BIOS 1645 03/15/2024
&amp;lt;4&amp;gt; [515.287281] Workqueue: drm_dp_mst_wq drm_dp_delayed_destroy_work
[drm_display_helper]
&amp;lt;4&amp;gt; [515.287303] Call Trace:
&amp;lt;4&amp;gt; [515.287304] &amp;lt;TASK&amp;gt;
&amp;lt;4&amp;gt; [515.287306] dump_stack_lvl+0xc1/0xf0
&amp;lt;4&amp;gt; [515.287313] dump_stack+0x10/0x20
&amp;lt;4&amp;gt; [515.287316] __ubsan_handle_shift_out_of_bounds+0x133/0x2e0
&amp;lt;4&amp;gt; [515.287324] ? drm_atomic_get_private_obj_state+0x186/0x…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/display/dp_mst: Add protection against 0 vcpi&lt;/p&gt;
&lt;p&gt;When releasing a timeslot there is a slight chance we may end up
with the wrong payload mask due to overflow if the delayed_destroy_work
ends up coming into play after a DP 2.1 monitor gets disconnected
which causes vcpi to become 0 then we try to make the payload =
~BIT(vcpi - 1) which is a negative shift. VCPI id should never
really be 0 hence skip changing the payload mask if VCPI is 0.&lt;/p&gt;
&lt;p&gt;Otherwise it leads to
&amp;lt;7&amp;gt; [515.287237] xe 0000:03:00.0: [drm:drm_dp_mst_get_port_malloc
[drm_display_helper]] port ffff888126ce9000 (3)
&amp;lt;4&amp;gt; [515.287267] -----------[ cut here ]-----------
&amp;lt;3&amp;gt; [515.287268] UBSAN: shift-out-of-bounds in
../drivers/gpu/drm/display/drm_dp_mst_topology.c:4575:36
&amp;lt;3&amp;gt; [515.287271] shift exponent -1 is negative
&amp;lt;4&amp;gt; [515.287275] CPU: 7 UID: 0 PID: 3108 Comm: kworker/u64:33 Tainted: G
S U 6.17.0-rc6-lgci-xe-xe-3795-3e79699fa1b216e92+ #1 PREEMPT(voluntary)
&amp;lt;4&amp;gt; [515.287279] Tainted: [S]=CPU_OUT_OF_SPEC, [U]=USER
&amp;lt;4&amp;gt; [515.287279] Hardware name: ASUS System Product Name/PRIME Z790-P
WIFI, BIOS 1645 03/15/2024
&amp;lt;4&amp;gt; [515.287281] Workqueue: drm_dp_mst_wq drm_dp_delayed_destroy_work
[drm_display_helper]
&amp;lt;4&amp;gt; [515.287303] Call Trace:
&amp;lt;4&amp;gt; [515.287304] &amp;lt;TASK&amp;gt;
&amp;lt;4&amp;gt; [515.287306] dump_stack_lvl+0xc1/0xf0
&amp;lt;4&amp;gt; [515.287313] dump_stack+0x10/0x20
&amp;lt;4&amp;gt; [515.287316] __ubsan_handle_shift_out_of_bounds+0x133/0x2e0
&amp;lt;4&amp;gt; [515.287324] ? drm_atomic_get_private_obj_state+0x186/0x…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-71305</guid>
    </item>
  </channel>
</rss>
