CVE-2026-97912: Linux kernel · accel: ethosu: Ensure SRAM size is 0 on mapping failure
Affects Linux kernelSource CVE Database V5
Not known to be exploited : upgrade to f5376d7e0fb703876199d3b6f9f97e128fa2f8a4 or e5576641b79ecd36acaf91fec4a5333b1ad19c57 when convenient.
Data as of 26 Oct 2026, 14:05 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in f5376d7e0fb703876199d3b6f9f97e128fa2f8a4, e5576641b79ecd36acaf91fec4a5333b1ad19c57
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 f5376d7e0fb703876199d3b6f9f97e128fa2f8a4 or e5576641b79ecd36acaf91fec4a5333b1ad19c57.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
This vulnerability has been fixed in the Linux kernel by commits f5376d7e0fb703876199d3b6f9f97e128fa2f8a4 and e5576641b79ecd36acaf91fec4a5333b1ad19c57. Users should update to a Linux kernel version that includes these fixes to ensure the SRAM size is correctly handled on mapping failure.
Description
A vulnerability in the Linux kernel's ethosu accelerator driver was fixed by ensuring the SRAM size is set to zero on mapping failure. Previously, if SRAM mapping failed, the SRAM size remained non-zero, causing the probe to succeed incorrectly. This allowed jobs to access SRAM memory that was actually unmapped and pointed to physical address 0x0.