Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-68238drm/amdgpu: Release VFCT ACPI table reference

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Release VFCT ACPI table reference amdgpu_acpi_vfct_bios() fetches the VFCT table with acpi_get_table() but never releases it. acpi_get_table() takes a reference on the table (incrementing its validation_count and mapping it on the 0->1 transition); without a paired acpi_put_table() the mapping is leaked on every call, whether or not a matching VBIOS image is found. Route all exit paths after the table is acquired through a common acpi_put_table(). The VBIOS image is copied out with kmemdup() before the table is released, so it remains valid for the caller. (cherry picked from commit ca5988682b4cba4cd125a0fa99b2de1239164ae4)

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected d38ceaf99ed015f2a0b9af3499791bd3a3daae21 – < 1c19e02a689661a9687d689dcc5995d3be538262
    • affected d38ceaf99ed015f2a0b9af3499791bd3a3daae21 – < 1748043b5114ce5ee5ee874d5f821a158d70631c
    • affected d38ceaf99ed015f2a0b9af3499791bd3a3daae21 – < 50a75929c0c5e8ab29a3ac49dc92489873d9d261
    • affected d38ceaf99ed015f2a0b9af3499791bd3a3daae21 – < 312278b3091912fa56a6a587609f17dcb33465c2
    • affected d38ceaf99ed015f2a0b9af3499791bd3a3daae21 – < 9b7de3ee5d2c5ee2a706e5f7ca0126f4fbea4da8
    • affected d38ceaf99ed015f2a0b9af3499791bd3a3daae21 – < 65bff26617607c1331283232016c0e89088c5b78
  • Linux · Linux

    • affected 4.2
    • unaffected < 4.2
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.42 – ≤ 6.18.*
    • unaffected 7.1.6 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-68238 badge
[![CVE-2026-68238](https://cveledger.app/badge/CVE-2026-68238.svg)](https://cveledger.app/cve/CVE-2026-68238)

Record last updated .