ZeroDay Findings
Sign inSign up

Findings

CVE-2025-71305

In the Linux kernel, the following vulnerability has been resolved: drm/display/dp_mst: Add protection against 0 vcpi When releasing a timeslot there is a slight chanc…

Published May 27, 2026 · updated Oct 14, 2026 · linux linux kernel

In the Linux kernel, the following vulnerability has been resolved: drm/display/dp_mst: Add protection against 0 vcpi 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. Otherwise it leads to [515.287237] xe 0000:03:00.0: [drm:drm_dp_mst_get_port_malloc [drm_display_helper]] port ffff888126ce9000 (3) [515.287267] -----------[ cut here ]----------- [515.287268] UBSAN: shift-out-of-bounds in ../drivers/gpu/drm/display/drm_dp_mst_topology.c:4575:36 [515.287271] shift exponent -1 is negative [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) [515.287279] Tainted: [S]=CPU_OUT_OF_SPEC, [U]=USER [515.287279] Hardware name: ASUS System Product Name/PRIME Z790-P WIFI, BIOS 1645 03/15/2024 [515.287281] Workqueue: drm_dp_mst_wq drm_dp_delayed_destroy_work [drm_display_helper] [515.287303] Call Trace: [515.287304] [515.287306] dump_stack_lvl+0xc1/0xf0 [515.287313] dump_stack+0x10/0x20 [515.287316] __ubsan_handle_shift_out_of_bounds+0x133/0x2e0 [515.287324] ? drm_atomic_get_private_obj_state+0x186/0x1d0 [515.287333] drm_dp_atomic_release_time_slots.cold+0x17/0x3d [drm_display_helper] [515.287355] mst_connector_atomic_check+0x159/0x180 [xe] [515.287546] drm_atomic_helper_check_modeset+0x4d9/0xfa0 [515.287550] ? __ww_mutex_lock.constprop.0+0x6f/0x1a60 [515.287562] intel_atomic_check+0x119/0x2b80 [xe] [515.287740] ? find_held_lock+0x31/0x90 [515.287747] ? lock_release+0xce/0x2a0 [515.287754] drm_atomic_check_only+0x6a2/0xb40 [515.287758] ? drm_atomic_add_affected_connectors+0x12b/0x140 [515.287765] drm_atomic_commit+0x6e/0xf0 [515.287766] ? _pfx__drm_printfn_

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. May 27, 2026 · NIST NVD

    Detected

    In the Linux kernel, the following vulnerability has been resolved: drm/display/dp_mst: Add protection against 0 vcpi 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)

  2. Oct 14, 2026 · NIST NVD

    Updated

    In the Linux kernel, the following vulnerability has been resolved: drm/display/dp_mst: Add protection against 0 vcpi 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)

Affected

  • cpe linux/linux kernelversion unspecified

Sources

  • CVE.orgVulnerability recordCVE-2025-71305

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2025-71305

    30-day exploitation probability 0.2%

    first.org
  • NIST NVDVulnerability recordCVE-2025-71305

    In the Linux kernel, the following vulnerability has been resolved: drm/display/dp_mst: Add protection against 0 vcpi 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 pla

    nvd.nist.gov

References