Answer in brief
CVE-2026-97912 records a Unknown severity vulnerability in accel: ethosu: Ensure SRAM size is 0 on mapping failure. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=5a5e9c0228e613f0ef2a58b9782d7c0ea8f1e58b <e5576641b79ecd36acaf91fec4a5333b1ad19c57 || >=5a5e9c0228e613f0ef2a58b9782d7c0ea8f1e58b <f5376d7e0fb703876199d3b6f9f97e128fa2f8a4 | e5576641b79ecd36acaf91fec4a5333b1ad19c57, f5376d7e0fb703876199d3b6f9f97e128fa2f8a4 |
| Linux/Linuxgeneric | 6.19 | Not reported |
Published upstream
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 25, 2026
In the Linux kernel, the following vulnerability has been resolved: accel: ethosu: Ensure SRAM size is 0 on mapping failure On a mapping failure of the SRAM, the SRAM size is left as non-zero. The probe will succeed as the error return is not checked since having SRAM is not a hard requirement. The non-zero size allows jobs to access SRAM which is left pointing to physical base address 0x0.
Quoted source text, attributed separately from HOL analysis.