GHSA-FF22-8XJR-7629

Vulnerability from github – Published: 2026-10-28 12:31 – Updated: 2026-10-28 12:31
VLAI
Details

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)

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-99151"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-10-28T11:17:35Z",
    "severity": null
  },
  "details": "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": "GHSA-ff22-8xjr-7629",
  "modified": "2026-10-28T12:31:05Z",
  "published": "2026-10-28T12:31:05Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99151"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/4c8b5e5b9776ad08138d79b14238c5742b32911b"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/55a67aa89342545b89f469dea6f29bfb6fac6f3d"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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…

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…