Kernel panic via shared command-count race
Published Sep 25, 2026 · Updated Sep 25, 2026
Race condition in Linux 6.14 allows local users with AMD XDNA device access to trigger a kernel panic through a shared command buffer. The __counted_by annotation on amdxdna_cmd_chain.data trusts command_count in shared AMDXDNA_BO_SHARE memory, so a concurrent zero value makes the generated bounds check fail. Access to the AMD XDNA shared command buffer is required, and successful exploitation interrupts the host by panicking its kernel.
Summary
What happened
Race condition in Linux 6.14 allows local users with AMD XDNA device access to trigger a kernel panic through a shared command buffer. The __counted_by annotation on amdxdna_cmd_chain.data trusts command_count in shared AMDXDNA_BO_SHARE memory, so a concurrent zero value makes the generated bounds check fail. Access to the AMD XDNA shared command buffer is required, and successful exploitation interrupts the host by panicking its kernel.
The record
- CVE
- CVE-2026-98146
- Published
- Sep 25, 2026
- Updated
- Sep 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 25, 2026CVE publishedPublication date reported by the CVE source.
- Sep 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.14
- Affected versionversion=aac243092b707bb3018e951d470cc1a9bcbaba6c <52f3e086760a9a3e02a46a10b57caffd73b1c204
- Affected versionversion=aac243092b707bb3018e951d470cc1a9bcbaba6c <93fa3e925b15b0ded0a549fe7f12bfbb1c4e171a
- Affected versionversion=aac243092b707bb3018e951d470cc1a9bcbaba6c <b3709d354545e70388177500761f92d906c4dfd6
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started