VulnerabilityPublished 28 Oct 2026

CVE-2026-99151: Linux kernel · drm/amd/display: Fix NULL sink dereference in USB4 bandwidth functions

Affects Linux kernelSource CVE Database V5

Not known to be exploited : upgrade to 55a67aa89342545b89f469dea6f29bfb6fac6f3d or 4c8b5e5b9776ad08138d79b14238c5742b32911b when convenient.

Data as of 28 Oct 2026, 10:58 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Patch: Available – fixed in 55a67aa89342545b89f469dea6f29bfb6fac6f3d, 4c8b5e5b9776ad08138d79b14238c5742b32911b, 7.2.13

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Linux to 55a67aa89342545b89f469dea6f29bfb6fac6f3d or 4c8b5e5b9776ad08138d79b14238c5742b32911b; Linux to 7.2.13.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 8fa813b7fd1eccbed13e126166cf764f1f11a7d3, < 55a67aa89342545b89f469dea6f29bfb6fac6f3d	Fixed in 55a67aa89342545b89f469dea6f29bfb6fac6f3d
LinuxLinux	Affected ≥ 0b1eebd359685dd681f6e0df5540a5bb985a27bf, < 4c8b5e5b9776ad08138d79b14238c5742b32911b	Fixed in 4c8b5e5b9776ad08138d79b14238c5742b32911b
LinuxLinux	Affected >=7.2.9 <7.2.13	Fixed in 7.2.13

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix NULL sink dereference in USB4 bandwidth functions allocate_usb4_bandwidth_for_stream() and allocate_usb4_bandwidth() both use ASSERT(stream->sink) before dereferencing stream->sink->link. ASSERT is compiled out in production builds, so a NULL stream->sink causes a NULL pointer dereference. link_set_dpms_off() already guards two earlier accesses to stream->sink with explicit NULL checks, confirming that stream->sink can legitimately be NULL. The subsequent call to deallocate_usb4_bandwidth() had no equivalent guard. Replace the ASSERT() calls with proper NULL checks that return false early, and add a matching stream->sink guard at the call site in link_set_dpms_off() consistent with the surrounding pattern. v2: Keep the existing ASSERT() calls for diagnostics (to report unexpected NULL sink), and add explicit NULL checks that return false before dereferencing stream->sink. Also add a matching stream->sink guard at the deallocation call site in link_set_dpms_off(). (Alex) (cherry picked from commit 98029a0ce61feb52c563f65349dd9b25f672e355)

References

Community reviews

Loading reviews…