Answer in brief
CVE-2026-97911 records a High severity (CVSS 7.8) vulnerability in accel: ethosu: Ensure SRAM region size matches job. 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.
CVSS is 7.8. 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 | >=9cff90774872ed6613b7571ce018b5b455d86890 <50c27d412fedc95b8d54d477af47451a382e8cdd || >=9cff90774872ed6613b7571ce018b5b455d86890 <2b39d680c9e0fb4d625f2916980977622e84248c | 50c27d412fedc95b8d54d477af47451a382e8cdd, 2b39d680c9e0fb4d625f2916980977622e84248c |
| Linux/Linuxgeneric | 7.2 | 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 region size matches job It is possible for userspace to set the job SRAM size to 0, but then still have SRAM accesses in the command stream. When the job SRAM size is 0, setting the region base register is skipped and a stale base address from a prior job is used. Check the region size against the job's SRAM size instead of just the size of the SRAM. The job's SRAM size was already checked against the total SRAM size.
Quoted source text, attributed separately from HOL analysis.