CVE-2026-98144: Linux kernel · accel/amdxdna: put the chained BO when its mapping fails
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in eb90cb257e0792ac11f0347254bad3fc72417db6 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:47 UTC
Rated Low by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in eb90cb257e0792ac11f0347254bad3fc72417db6, 7e33ba3a1d48c2d20ed270dec9d2d08332585c8e, 6.19
Exploitation evidence
Disclosed: evidence found.
CVE published 25 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade Linux kernel to eb90cb257e0792ac11f0347254bad3fc72417db6, 7e33ba3a1d48c2d20ed270dec9d2d08332585c8e or 6.19.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix for this vulnerability is available and has been incorporated in Linux kernel version 6.19 and specific commits (eb90cb257e0792ac11f0347254bad3fc72417db6, 7e33ba3a1d48c2d20ed270dec9d2d08332585c8e). Users should upgrade to these versions or later to remediate the issue.
Description
A reference leak vulnerability in the Linux kernel's amdxdna accelerator driver was fixed. The flaw occurs when the mapping of a chained buffer object (BO) fails in the amdxdna_cmd_set_error() function, causing a reference to not be properly released. This can happen when userspace closes a handle after submission and imports a dma-buf with an exporter that does not implement vmap on the same id, leading to an unmappable object. The issue affects specific Linux kernel versions and has been resolved in version 6.19 and certain commits.