CVE-2026-53173: Linux Kernel Ethos-U Out-of-Bounds Write Privilege Escalation
A memory safety flaw in the Linux kernel's Arm Ethos-U NPU driver allows a local attacker to write data beyond the boundaries of an allocated buffer. The vulnerability exists in the command stream parsing loop, which fails to validate the buffer bounds after incrementing an index for 64-bit command words. An attacker with local access can craft a malicious command buffer via ioctl to trigger an out-of-bounds heap write, potentially corrupting kernel memory or escalating privileges.
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-787
- 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 OOB write in ethosu_gem_cmdstream_copy_and_validate() The command stream parsing loop increments the index variable a second time when a 64-bit command word is encountered (bit 14 set), but does not re-check the loop bound before writing the second word: for (i = 0; i < size / 4; i++) { bocmds[i] = cmds[0]; if (cmd & 0x4000) { i++; bocmds[i] = cmds[1]; /* unchecked */ } } The buffer bocmds is backed by a DMA allocation of exactly size bytes from drm_gem_dma_create(ddev, size), giving valid indices [0, size/4-1]. When i == size/4 - 1 on entry to an iteration and bit 14 of cmds[0] is set, bocmds[size/4-1] is written in bounds, i is then incremented to size/4, and bocmds[size/4] writes four bytes past the end of the allocation. Userspace controls both the buffer contents and the size argument via the ioctl, making this a userspace-triggerable heap out-of-bounds write. Fix by checking the incremented index against the buffer bound before the second write and returning -EINVAL if the buffer is too small to contain the extended command.
2 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-53173 is an out-of-bounds (OOB) write vulnerability in accel/ethosu within the Linux kernel. The ethosu_gem_cmdstream_copy_and_validate() function parses command streams into a DMA-allocated buffer (bocmds) of exactly size bytes, providing valid indices from 0 to size/4−1. The parsing loop iterates i from 0 to size/4−1, and when bit 14 is set in a command word (indicating a 64-bit command), the index i is incremented and a second write is performed without re-checking the loop bound. When i equals size/4−1 at loop entry and bit 14 is set, the second write at bocmds[i] (after incrementing to size/4) exceeds the allocation by four bytes. Both buffer contents and size are user-controlled via ioctl, making this a direct userspace-triggerable heap overflow.
Business impact
This vulnerability enables local privilege escalation on systems running vulnerable Linux kernels with the Ethos-U accelerator driver. An unprivileged local user can corrupt kernel heap memory, potentially gaining root access or causing denial of service. The impact is elevated because the vulnerability affects security-critical kernel memory management and can be reliably triggered. For organizations running GPU-accelerated or ML-accelerated workloads on Linux systems, this represents a significant privilege escalation risk that could undermine kernel isolation guarantees.
Affected systems
The Linux kernel versions containing this vulnerability are those with the accel/ethosu driver. Affected platforms include systems using Arm Ethos-U neural processing units. Verify your kernel version against the vendor advisory to determine exact patch boundaries. Typically, systems running recent kernel versions (5.10+) without the specific patch are at risk.
Exploitability
Exploitability is straightforward from the local context. An unprivileged local user with access to the Ethos-U device (/dev/ethosu or similar) can trigger the vulnerability by issuing a specially crafted ioctl with a command buffer where the final command word has bit 14 set. No elevated privileges, user interaction, or complex environment setup is required beyond local system access. The vulnerability is not exposed remotely unless the system permits unprivileged local code execution.
Remediation
Apply the Linux kernel patch that adds bounds checking for the incremented index before the second write in ethosu_gem_cmdstream_copy_and_validate(). The fix verifies that i+1 remains within bounds when a 64-bit command is detected and returns -EINVAL if the buffer is too small. Consult your Linux distribution's security advisory or the upstream kernel repository for the specific patch version addressing this issue.
Patch guidance
Check your current kernel version against the Linux kernel security advisory for CVE-2026-53173. Most distributions (Red Hat, Debian, Ubuntu, SUSE, etc.) will backport the bounds-checking fix to their supported kernel branches. Update to the patched kernel version recommended by your distribution, typically available through standard package management (yum, apt, zypper). After patching, verify the fix is present by confirming the bounds check in the accel/ethosu driver code or monitoring kernel changelogs.
Detection guidance
Monitor kernel logs for failed ioctl calls with -EINVAL returns on the Ethos-U device. Detection tools should focus on: (1) unauthorized access attempts to /dev/ethosu or equivalent device nodes by unprivileged users; (2) command stream parsing errors in kernel logs; (3) heap corruption detectors (if available) that identify out-of-bounds writes in DMA-allocated memory. Kernel Address Sanitizer (KASAN) or similar runtime checkers will catch exploitation attempts if enabled. Network-based detection is not applicable as the vulnerability is local only.
Why prioritize this
This vulnerability merits immediate attention due to its HIGH CVSS score (7.8) reflecting local privilege escalation capability, CWE-787 (out-of-bounds write) classification, and reliable exploitability by unprivileged users. The kernel is a critical attack surface, and heap corruption leading to privilege escalation is a fundamental security failure. Organizations should prioritize patching systems that expose Ethos-U devices to untrusted local users.
Risk score, explained
The CVSS 3.1 score of 7.8 (HIGH) reflects: Attack Vector Local (narrow exposure surface but still significant), Attack Complexity Low (straightforward trigger), Privilege Required Low (unprivileged user sufficient), User Interaction None (automatic), Scope Unchanged, and high impact on Confidentiality, Integrity, and Availability. The score appropriately captures the severity of a local heap overflow in kernel memory leading to privilege escalation. The absence of a KEV entry indicates this was not yet publicly exploited at the time of advisory publication, but the technical tractability and local access model suggest risk.
Frequently asked questions
Can this vulnerability be exploited remotely?
No. The vulnerability requires local system access and direct interaction with the Ethos-U device ioctl interface. It is not remotely exploitable unless the system already permits unauthenticated remote code execution.
Which systems are most at risk?
Systems running Linux with Arm Ethos-U NPU hardware (typically embedded, edge, or specialized ML accelerator setups) and kernel versions without the patch are at highest risk. Desktop and server systems without Ethos-U hardware are not affected.
What is the recommended timeline for patching?
Given the HIGH severity and local privilege escalation vector, patches should be applied within 1-2 weeks of availability. Prioritize systems allowing untrusted local users or running multi-tenant workloads on shared hardware.
Does this affect only the accel/ethosu driver or broader kernel components?
The vulnerability is specific to the accel/ethosu driver's command stream parser. Other kernel subsystems and drivers are not directly affected by this issue.
This analysis is based on the published CVE details and Linux kernel security advisories as of the publication date. Specific patch versions, affected kernel releases, and mitigation steps may vary by Linux distribution and should be verified against your vendor's official security advisory. No exploit code is provided. Organizations should conduct internal testing and validation before deploying patches in production environments. Source: NVD (public-domain), retrieved 2026-08-03. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2026-10883HIGHType Confusion in Chrome ANGLE Graphics Library
- CVE-2026-10897HIGHCritical Chrome GPU Sandbox Escape Vulnerability
- CVE-2026-10907HIGHChrome ANGLE Out-of-Bounds Write – Remote Code Execution Risk
- CVE-2026-10941HIGHSkia Out-of-Bounds Memory Vulnerability in Chrome – Urgent Patch Required
- CVE-2026-11091HIGHCritical Chrome Memory Corruption Vulnerability in Dawn Graphics Engine
- CVE-2026-11173HIGHChrome V8 Out-of-Bounds Write Sandbox Escape – Patch Guidance
- CVE-2026-12019HIGHChrome Heap Overflow & Sandbox Escape (Linux, ChromeOS)
- CVE-2026-13033HIGHCritical Out-of-Bounds Memory Vulnerability in Chrome InterestGroups