CVE-2026-97911: accel: ethosu: Ensure SRAM region size matches job
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.
Affected Software
Event History
Frequently Asked Questions
What is required to trigger the issue?
Userspace must submit a job with its SRAM size set to 0 while including SRAM accesses in the command stream. This can cause the device to use a stale SRAM base address left by a prior job.
How can I check whether the fix is present?
Check whether the kernel source includes the change identified by either referenced stable commit: 50c27d412fedc95b8d54d477af47451a382e8cdd or 2b39d680c9e0fb4d625f2916980977622e84248c. The corrected logic validates the SRAM region size against the job's SRAM size.