CVE-2026-53172: Linux Kernel NPU Buffer Overflow – High Severity Privilege Escalation Risk
A flaw in the Linux kernel's NPU (Neural Processing Unit) command stream parser allows a local attacker to corrupt kernel memory by sending specially crafted input. The vulnerability exists because the code incorrectly validates region indices for input feature map (IFM) regions, permitting values up to 127 when only 0–7 are valid. This mismatch enables an attacker to write data far beyond the intended memory buffer, potentially causing system instability, privilege escalation, or information disclosure.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 7.8 HIGH · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weaknesses (CWE)
- CWE-125
- Affected products
- 7 configuration(s)
- Published / Modified
- 2026-06-25 / 2026-07-06
NVD description (verbatim)
In the Linux kernel, the following vulnerability has been resolved: accel/ethosu: fix IFM region index out-of-bounds in command stream parser NPU_SET_IFM_REGION extracts the region index with param & 0x7f, giving a maximum value of 127. However region_size[] and output_region[] in struct ethosu_validated_cmdstream_info are both sized to NPU_BASEP_REGION_MAX (8), giving valid indices [0..7]. Every other region assignment in the same switch uses param & 0x7: NPU_SET_OFM_REGION: st.ofm.region = param & 0x7; NPU_SET_IFM2_REGION: st.ifm2.region = param & 0x7; NPU_SET_WEIGHT_REGION: st.weight[0].region = param & 0x7; NPU_SET_SCALE_REGION: st.scale[0].region = param & 0x7; The 0x7f mask on IFM is inconsistent and appears to be a typo. feat_matrix_length() and calc_sizes() use the region index directly as an array subscript into the kzalloc'd info struct: info->region_size[fm->region] = max(...); A userspace caller supplying NPU_SET_IFM_REGION with param > 7 causes a write up to 127*8 = 1016 bytes past the start of region_size[], corrupting adjacent kernel heap data. Fix by applying the same & 0x7 mask used by all other region assignments.
2 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-53172 is a heap buffer out-of-bounds write vulnerability in the accel/ethosu subsystem of the Linux kernel. The NPU_SET_IFM_REGION command handler extracts a region index using (param & 0x7f), yielding indices 0–127. However, the region_size[] and output_region[] arrays in struct ethosu_validated_cmdstream_info are sized to NPU_BASEP_REGION_MAX (8 elements), supporting only indices 0–7. Every other region assignment in the same switch statement correctly uses (param & 0x7), indicating the 0x7f mask is a typo. When feat_matrix_length() or calc_sizes() use this unchecked index as an array subscript, an out-of-bounds write up to 1016 bytes past region_size[] corrupts adjacent kernel heap metadata and data structures.
Business impact
This vulnerability allows any unprivileged local user with access to the NPU device to crash the kernel, leak sensitive kernel memory, or potentially escalate privileges. Systems relying on NPU hardware acceleration (increasingly common in edge AI applications, automotive platforms, and embedded systems) face elevated risk of denial of service or privilege escalation attacks. Organizations deploying Arm-based edge or IoT infrastructure should assess exposure and prioritize patching.
Affected systems
The Linux kernel accel/ethosu driver is affected. This impacts systems with Arm Ethos-U NPU hardware or software emulation support enabled. Typically found in edge computing platforms, automotive SoCs, embedded Linux deployments, and AI inference appliances. Desktop and server deployments with this subsystem built-in or as a module are also at risk if the NPU device is accessible to unprivileged users.
Exploitability
Exploitability is moderate to high. The attack requires local access and the ability to interact with the NPU device (e.g., /dev/ethosu or equivalent), which may be restricted by file permissions or SELinux policy. However, once access is obtained, no special privileges or user interaction is required; a malicious process can immediately craft and submit the malformed command. The vulnerability is straightforward to trigger and does not require specialized knowledge of the NPU instruction set—only crafting a single command with an out-of-range region index.
Remediation
Apply the upstream Linux kernel patch that corrects the NPU_SET_IFM_REGION mask from (param & 0x7f) to (param & 0x7), aligning it with other region assignment operations. Verify the patch against the official Linux kernel repository or your distribution's security advisory. Alternatively, disable the accel/ethosu driver if NPU acceleration is not required.
Patch guidance
Locate and apply the kernel patch from the Linux kernel repository that fixes the mask in the accel/ethosu command stream parser. Check your Linux distribution's security advisories for backported fixes to stable kernels you are running. If you maintain a custom kernel, manually apply the one-line change to switch the mask constant from 0x7f to 0x7. Recompile and reboot. Verify the fix by confirming the corrected mask is present in the running kernel image.
Detection guidance
Monitor for unexpected kernel crashes, particularly on systems with NPU drivers loaded. Enable kernel address space layout randomization (ASLR) and heap corruption detection (if available) to surface exploitation attempts. Audit device permissions for /dev/ethosu or equivalent; restrict access to trusted users. Consider kernel hardening options such as CONFIG_HARDENED_USERCOPY and CONFIG_DEBUG_LIST. System call tracing (auditd, strace) can identify processes attempting to interact with the NPU device or command stream parser, but will not definitively prove exploitation attempt without additional heap instrumentation.
Why prioritize this
This vulnerability merits HIGH priority because it permits local privilege escalation and denial of service with minimal user interaction. It affects a growing category of edge AI and embedded systems. The fix is simple and low-risk, making rapid patching feasible. Until patched, restrict NPU device access via filesystem permissions or disable the subsystem if not in use.
Risk score, explained
CVSS 3.1 score of 7.8 (HIGH) reflects: local attack vector (AV:L), low attack complexity (AC:L), low privilege requirement (PR:L), no user interaction (UI:N), and impact on confidentiality, integrity, and availability (C:H/I:H/A:H). The vulnerability permits arbitrary kernel memory corruption, justifying the high severity despite requiring local access.
Frequently asked questions
Who can exploit this vulnerability?
Any user with local access to the system and permission to interact with the NPU device (typically the root user or members of a dedicated device group). In systems where the NPU device is world-readable or accessible to unprivileged users, any local attacker qualifies.
What is the real-world impact if this is exploited?
An attacker could crash the kernel (denial of service), read sensitive kernel memory (information disclosure), or manipulate kernel structures to escalate privileges. On production edge AI or automotive systems, this could disrupt critical inference services or enable further compromise.
How do I know if my system is vulnerable?
Check if your kernel version includes the fix (verify against your distribution's advisory). Confirm whether accel/ethosu is compiled into the kernel or loaded as a module (lsmod | grep ethosu). If it is present and your kernel version predates the patch, you are vulnerable.
What if I don't use NPU acceleration?
If you do not require NPU hardware support, disable the accel/ethosu driver at compile time (CONFIG_ETHOSU=n) or prevent the module from loading (blacklist or rmmod). This eliminates the attack surface entirely.
This analysis is provided for informational purposes and does not constitute legal advice or a guarantee of protection. While we have structured this summary on the basis of ground-truth CVE data, you must verify patch availability and applicability against your specific kernel version and distribution. No exploit proof-of-concept code has been included. Organizations should conduct their own testing in non-production environments before applying patches to critical systems. SEC.co and its analysts accept no liability for system outages, data loss, or other damages resulting from patching or failure to patch. Source: NVD (public-domain), retrieved 2026-08-03. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2026-10889HIGHCritical ANGLE Sandbox Escape in Google Chrome – Patch to 149.0.7827.53
- CVE-2026-10927HIGHChrome Sandbox Escape via Dawn Out-of-Bounds Read
- CVE-2026-10941HIGHSkia Out-of-Bounds Memory Vulnerability in Chrome – Urgent Patch Required
- CVE-2026-11015HIGHCritical Chrome WebGPU Out-of-Bounds Read Vulnerability
- CVE-2026-11077HIGHChrome Dawn Graphics Vulnerability – Sandbox Escape Risk
- CVE-2026-11091HIGHCritical Chrome Memory Corruption Vulnerability in Dawn Graphics Engine
- CVE-2026-11111HIGHChrome Out-of-Bounds Read in ANGLE Graphics Engine — Patch Guidance
- CVE-2026-11191HIGHOut-of-Bounds Memory Access in Chrome ANGLE Library