Linux Kernel: Out-of-Bounds Access (CVE-2026-97493)
Published Last modified Sources: HKCERT, Ubuntu, Debian LTS, Debian, Red Hat, EUVD, CVE.org, Msrc Update Guide, BSI
What is affected, what to do
A flaw was found in the Linux kernel's AMD GPU (amdgpu) driver. The driver fails to validate the size of Video BIOS (VBIOS) tables, allowing the calculated entry count to exceed the bounds of an internal array.
Update Linux Kernel to version 6.1.191, Linux Kernel to version 6.6.160, Linux Kernel to version 6.12.114.
- Affected
- Linux Kernel
lt 4.2..6.1.191 - Linux Kernel
lt 6.2..6.6.160 - Linux Kernel
lt 6.7..6.12.114 - Linux Kernel
lt 6.13..6.18.53 - Linux Kernel
lt 6.19..7.2
- Linux Kernel
- Fixed in
- Linux Kernel
6.1.191 - Linux Kernel
6.6.160 - Linux Kernel
6.12.114 - Linux Kernel
6.18.53 - Linux Kernel
7.2
- Linux Kernel
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
6.3
XIEM Effective CVSS
Highest available CVSS rating from NVD and vendor data.
Source: Vendor (CNA), CVSS v3
6.3
CVSS v3
Severity Medium on the scale from 0 to 10.
Source: HKCERT, Ubuntu, Debian LTS, Debian, Red Hat, EUVD, CVE.org, Msrc Update Guide, BSI
0.2 %
EPSS score
Low — model estimates < 1% exploitation likelihood.
Source: FIRST EPSS, percentile 7.0
Show all metrics
- Severity
- Medium
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 58.07 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 6.3 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 6.3
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 0.2 %
- Low — model estimates < 1% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 7.0
- Low — this CVE sits in the lower 10% of all CVEs scored today.
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
A flaw was found in the Linux kernel's AMD GPU (amdgpu) driver. The driver fails to validate the size of Video BIOS (VBIOS) tables, allowing the calculated entry count to exceed the bounds of an internal array. A local attacker or compromised firmware image could exploit this flaw to trigger an out-of-bounds memory write, leading to memory corruption, system instability, or a Denial of Service (DoS).
Source: HKCERT (CC BY 3.0 HK) · HKCERT rating: medium, Ubuntu Security Notices, Debian LTS Advisories, Debian Security Advisories, redhat_csaf, ENISA EUVD, NVD (NIST), Microsoft Security Update Guide, cvelistv5, BSI WID Portal, BSI CSAF
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| Linux | Linux |
|
|
Vendors and products
Affected operating systems
| Linux | debian | linux | trixie |
| Linux | ubuntu | linux | resolute |
| Linux | debian | linux-6.12 | bookworm |
| Linux | ubuntu | linux-aws | resolute |
| Linux | ubuntu | linux-aws-7.0 | noble |
| Linux | ubuntu | linux-azure | resolute |
| Linux | ubuntu | linux-azure-fde | resolute |
| Linux | ubuntu | linux-azure-fde-7.0 | noble |
| Linux | ubuntu | linux-gcp | resolute |
| Linux | ubuntu | linux-gcp-7.0 | noble |
| Linux | ubuntu | linux-gke | resolute |
| Linux | ubuntu | linux-hwe-7.0 | noble |
| Linux | ubuntu | linux-ibm | resolute |
| Linux | ubuntu | linux-oem-7.0 | resolute |
| Linux | ubuntu | linux-oracle | resolute |
| Linux | ubuntu | linux-oracle-7.0 | noble |
| Linux | ubuntu | linux-realtime | resolute |
References & sources
- git.kernel.orgstable/c/f8f0985375c3b977757fd73e2b691ff1bf1ea7b9euvd
- git.kernel.orgstable/c/a99cd231cd924b7160fecb9fb3a94b801522323beuvd
- git.kernel.orgstable/c/0786b38af822fcd153d565cc85be7dbd9fed4d25euvd
- git.kernel.orgstable/c/6db45123306c7167c6867ca3d24924bd7960d947euvd
- git.kernel.orgstable/c/b12abff6a52d96c4114d7668f790b18f9201c17ceuvd
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
Record modifiedLinux
Show 2 original changes
Individual changes of this event as published by NVD Type Action Before After Affected versions (publisher) added —Affected value modified. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/97xxx/CVE-2026-97493.json">CVE-2026-97493</a>Reference added —https://git.kernel.org/stable/c/b12abff6a52d96c4114d7668f790b18f9201c17cSource identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Record modifiedLinux
Show 3 original changes
Individual changes of this event as published by NVD Type Action Before After Affected versions (publisher) added —Affected value modified. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/97xxx/CVE-2026-97493.json">CVE-2026-97493</a>Reference added —https://git.kernel.org/stable/c/0786b38af822fcd153d565cc85be7dbd9fed4d25Reference added —https://git.kernel.org/stable/c/6db45123306c7167c6867ca3d24924bd7960d947Source identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Record modifiedLinux
1 individual change: Affected versions (publisher)
Show the original change
Individual changes of this event as published by NVD Type Action Before After Affected versions (publisher) added —Affected value modified. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/97xxx/CVE-2026-97493.json">CVE-2026-97493</a>Source identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
ReceivedLinux
Description added or changed
Show 4 original changes
Individual changes of this event as published by NVD Type Action Before After Description added —In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Bound GPIO I2C table entry count from VBIOS Reject undersized tables and cap the derived entry count to AMDGPU_MAX_I2C_BUS so we do not overrun adev->i2c_bus[] or walk an absurd number of entries on corrupt size fields.Affected versions (publisher) added —New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/97xxx/CVE-2026-97493.json">CVE-2026-97493</a>Reference added —https://git.kernel.org/stable/c/a99cd231cd924b7160fecb9fb3a94b801522323bReference added —https://git.kernel.org/stable/c/f8f0985375c3b977757fd73e2b691ff1bf1ea7b9Source identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-97493"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-97493.svg?lang=en" alt="CVE-2026-97493 – NEOSEC Intel" height="20"></a>