GHSA-VH8J-7R6V-H2X4

Vulnerability from github – Published: 2026-11-20 06:32 – Updated: 2026-11-20 06:32
VLAI
Details

In the Linux kernel, the following vulnerability has been resolved:

drm/amdgpu: Clamp the ATIF backlight curve to its 99 points

amdgpu_atif_query_backlight_caps() stores the firmware's number_of_points as data_points but copies only the 99 points that luminance_data[] holds. number_of_points is a u8, so a firmware table that claims more makes the custom curve code in amdgpu_dm index past the array, and dm_query_extended_brightness_caps() copy past the end of the data_points[] buffer it fills

Clamp the count to ATIF_QBTC_MAX_DATA_POINTS and warn, since a table that claims more is a firmware bug

(cherry picked from commit af8a1c2b7d3de4960e10f94e8ba2fc0ccd168072)

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-99623"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-11-20T06:17:55Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: Clamp the ATIF backlight curve to its 99 points\n\namdgpu_atif_query_backlight_caps() stores the firmware\u0027s number_of_points\nas data_points but copies only the 99 points that luminance_data[] holds.\nnumber_of_points is a u8, so a firmware table that claims more makes the\ncustom curve code in amdgpu_dm index past the array, and\ndm_query_extended_brightness_caps() copy past the end of the\ndata_points[] buffer it fills\n\nClamp the count to ATIF_QBTC_MAX_DATA_POINTS and warn, since a table\nthat claims more is a firmware bug\n\n(cherry picked from commit af8a1c2b7d3de4960e10f94e8ba2fc0ccd168072)",
  "id": "GHSA-vh8j-7r6v-h2x4",
  "modified": "2026-11-20T06:32:04Z",
  "published": "2026-11-20T06:32:04Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99623"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/7ba7655701c5cad5bfa043d464d1e24873e24aab"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/d00442ef393bd725288514cabc2be4b5472195f4"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/e36430fda69a3b6087bf57ab52f549deca531f3a"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

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.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    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.