CVE-2026-97911 Linux CVE debrief

Who should care

Defenders responsible for Linux kernel-based systems, especially those executing untrusted userspace applications, should assess exposure and prioritize patching. This includes operators managing Linux kernel deployments, vulnerability management teams, and security teams responsible for ensuring system security and integrity.

Why it matters

Defenders should care about CVE-2026-97911 because it affects the Linux kernel's accel: ethosu driver, potentially allowing userspace to access stale SRAM base addresses. This could lead to information disclosure or unintended behavior in systems using this driver. The vulnerability requires verification of patch application and system configuration to mitigate.

• Potential information disclosure due to stale SRAM base address usage
• Unintended behavior in systems using the accel: ethosu driver
• Need for verification of patch application and system configuration

Technical summary

The Linux kernel's accel: ethosu driver is vulnerable to a situation where userspace can set the job SRAM size to 0 and still have SRAM accesses in the command stream. This can lead to the use of a stale base address from a prior job, potentially causing unintended behavior or information disclosure. The vulnerability requires verification of patch application and system configuration to mitigate. The issue arises from the lack of checking the region size against the job's SRAM size, which can lead to security concerns.

Defensive priority

Defenders should prioritize verifying and applying patches for this vulnerability, especially in systems where untrusted userspace applications are executed.

Recommended defensive actions

• Verify and apply patches for this vulnerability
• Review and update Linux kernel versions to ensure the fix is included
• Monitor systems for unusual behavior related to the accel: ethosu driver
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its CVSS score and vector. However, the corpus does not establish versions, exploitation, impact, or remediation beyond the provided information.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.