CVE-2026-97495: drm/amdkfd: Check bounds on allocate_doorbell
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- Fixed version: Linux Linux 1f087bb8cf9e8797633da35c85435e557ef74d06, 3d2ddfc9b361b0d38c3ff4804ce42503e4bc97de, 7e06636260a2d95e3fa181bc337d0eeb812b7a41; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1.
Low priority for now. Upgrade to Linux Linux 1f087bb8cf9e8797633da35c85435e557ef74d06, 3d2ddfc9b361b0d38c3ff4804ce42503e4bc97de, 7e06636260a2d95e3fa181bc337d0eeb812b7a41; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Check bounds on allocate_doorbell allocated_doorbell has an option to set the doorbell id to a specific value (used by CRIU). This value was not bounds checked. Check to confirm it's less than KFD_MAX_NUM_OF_QUEUES_PER_PROCESS.
- Published
- Sep 24, 2026
- Updated
- Oct 3, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.18affected
- 5bb6a8fa75fcfda93592bee0a4910420ceab15f3 and later · before 7e06636260a2d95e3fa181bc337d0eeb812b7a41affected · git
- 5bb6a8fa75fcfda93592bee0a4910420ceab15f3 and later · before 3d2ddfc9b361b0d38c3ff4804ce42503e4bc97deaffected · git
- 5bb6a8fa75fcfda93592bee0a4910420ceab15f3 and later · before e0cecd04a4fc4c75e375b91cf53eab5ba2e4ab7faffected · git
- 5bb6a8fa75fcfda93592bee0a4910420ceab15f3 and later · before c2c89118c27cbd3adace62c5df19d15b0e96ade1affected · git
- 5bb6a8fa75fcfda93592bee0a4910420ceab15f3 and later · before 1f087bb8cf9e8797633da35c85435e557ef74d06affected · git
- before 5.18not affected · semver
- 6.1.189 and later · up to and including 6.1.*not affected · semver
- 6.6.158 and later · up to and including 6.6.*not affected · semver
- 6.12.111 and later · up to and including 6.12.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-97493Sep 24, 2026 · drm/amdgpu: Bound GPIO I2C table entry count from VBIOS0Monitor
- ← EarlierCVE-2026-97494Sep 24, 2026 · drm/amdgpu: validate and share PSP fw_pri_buf copies via psp_copy_fw0Monitor
- Later →CVE-2026-97496Sep 24, 2026 · drm/amdkfd: Fix OOB memory exposure in get_wave_state()28Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1f087bb8cf9e8797633da35c85435e557ef74d06 | Vendor (CNA) |
| Linux Linux | 3d2ddfc9b361b0d38c3ff4804ce42503e4bc97de | Vendor (CNA) |
| Linux Linux | 7e06636260a2d95e3fa181bc337d0eeb812b7a41 | Vendor (CNA) |
| Linux Linux | c2c89118c27cbd3adace62c5df19d15b0e96ade1 | Vendor (CNA) |
| Linux Linux | e0cecd04a4fc4c75e375b91cf53eab5ba2e4ab7f | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.158.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.