# drm/amdgpu: fix buffer overflow during vBIOS update CVE record · `CVE-2026-97425` - **Identifiers:** `CVE-2026-97425` - **State:** Confirmed - **Severity:** No CVSS score - **Critical:** No - **CNA:** Linux - **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md) - **Published:** 24 Sept 2026 - **Updated:** 30 Oct 2026 - **Reviewed by a person:** No Published by the CVE Program (CNA: Linux) at 24 Sept 2026, 16:03 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. ## Affected products, as the CNA wrote them - Vendor: Linux. Product: Linux. - affected: `8424f2ccb3c0dd43369288a47d15c980136c3bd5 to before bce28deb42b9e8d368648a002ffe3a6124c482aa` (git) - affected: `8424f2ccb3c0dd43369288a47d15c980136c3bd5 to before 4a1b0a4c5acbe96368d71157b264dcd917ba6c9e` (git) - affected: `8424f2ccb3c0dd43369288a47d15c980136c3bd5 to before c7b2af01ee2ecfb8f2289dc83524d8fb1ec72992` (git) - affected: `8424f2ccb3c0dd43369288a47d15c980136c3bd5 to before 29fef371331e87311822000535f491ffc3d7a64f` (git) - affected: `8424f2ccb3c0dd43369288a47d15c980136c3bd5 to before 6229898d46c0cbc238a6fe9f11c1ea12cf8bb9c5` (git) - Other versions: unaffected - Vendor: Linux. Product: Linux. - affected: `5.19` - unaffected: `before 5.19` (semver) - unaffected: `6.1.191 to 6.1.*, inclusive` (semver) - unaffected: `6.6.158 to 6.6.*, inclusive` (semver) - unaffected: `6.12.111 to 6.12.*, inclusive` (semver) - unaffected: `6.18.53 to 6.18.*, inclusive` (semver) - unaffected: `7.2 to *, inclusive` (original_commit_for_fix) - Other versions: affected ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > The Linux kernel amdgpu driver is affected from version 5.19 until the fix, which is listed in stable releases 6.1.191, 6.6.158, 6.12.111 and 6.18.53. The source gives few details: it describes a buffer overflow during vBIOS update but does not say who can trigger it or what an attacker could achieve. Upgrade to a fixed kernel version listed above. Written 12 Nov 2026. ## Not analysed yet We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter. ## Severity and exploitation No source has published a CVSS score for this record yet. - **CISA KEV:** Not listed. - **EPSS:** 0.0019, the 8th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline This record came from the full history of the CVE Program, published 24 Sept 2026. New records show when each source confirmed them. ## Sources - [CVE List: CVE-2026-97425](https://www.cve.org/CVERecord?id=CVE-2026-97425) - [NVD: CVE-2026-97425](https://nvd.nist.gov/vuln/detail/CVE-2026-97425) ### References from the CNA - - - - - Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description. ## Check whether this affects you This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run. - With the agentprime MCP server (), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: - As JSON: - Everything that needs attention now: --- The web page: . Everything for agents: .