FKIE_CVE-2026-99151
Vulnerability from fkie_nvd - Published: 2026-10-28 11:17 - Updated: 2026-10-28 11:17
Severity
Summary
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
Impacted products
| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/gpu/drm/amd/display/dc/link/link_dpms.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "4c8b5e5b9776ad08138d79b14238c5742b32911b",
"status": "affected",
"version": "0b1eebd359685dd681f6e0df5540a5bb985a27bf",
"versionType": "git"
},
{
"lessThan": "55a67aa89342545b89f469dea6f29bfb6fac6f3d",
"status": "affected",
"version": "8fa813b7fd1eccbed13e126166cf764f1f11a7d3",
"versionType": "git"
}
]
},
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/gpu/drm/amd/display/dc/link/link_dpms.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "7.2.13",
"status": "affected",
"version": "7.2.9",
"versionType": "semver"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/display: Fix NULL sink dereference in USB4 bandwidth functions\n\nallocate_usb4_bandwidth_for_stream() and allocate_usb4_bandwidth() both\nuse ASSERT(stream-\u003esink) before dereferencing stream-\u003esink-\u003elink. ASSERT\nis compiled out in production builds, so a NULL stream-\u003esink causes a\nNULL pointer dereference.\n\nlink_set_dpms_off() already guards two earlier accesses to stream-\u003esink\nwith explicit NULL checks, confirming that stream-\u003esink can legitimately\nbe NULL. The subsequent call to deallocate_usb4_bandwidth() had no\nequivalent guard.\n\nReplace the ASSERT() calls with proper NULL checks that return false\nearly, and add a matching stream-\u003esink guard at the call site in\nlink_set_dpms_off() consistent with the surrounding pattern.\n\nv2: Keep the existing ASSERT() calls for diagnostics (to report\n unexpected NULL sink), and add explicit NULL checks that return false\n before dereferencing stream-\u003esink. Also add a matching stream-\u003esink\n guard at the deallocation call site in link_set_dpms_off(). (Alex)\n\n(cherry picked from commit 98029a0ce61feb52c563f65349dd9b25f672e355)"
}
],
"id": "CVE-2026-99151",
"lastModified": "2026-10-28T11:17:35.207",
"metrics": {},
"published": "2026-10-28T11:17:35.207",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/4c8b5e5b9776ad08138d79b14238c5742b32911b"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/55a67aa89342545b89f469dea6f29bfb6fac6f3d"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.
Loading…