CVE-2026-53171

What it actually does

This flaw is an integer arithmetic validation bug in the Linux kernel Arm Ethos-U accelerator driver. The driver calculates DMA region usage from untrusted or attacker-influenced command stream values using signed additions, multiplications, and offset additions. Underflow or overflow can cause the calculated DMA length to wrap and appear smaller than the real region accessed. Because that derived size is later used to validate command stream accesses against GEM buffer sizes, a malicious command stream may bypass bounds checks and cause out-of-bounds DMA-related access or memory corruption within the kernel driver context. Impact is primarily relevant on systems with the affected Ethos-U accelerator driver present and reachable by an attacker able to submit jobs to the device.

Why it matters to the business

On affected Linux systems that expose the Ethos-U accelerator interface, a local or device-adjacent workload with access to the accelerator could potentially trigger kernel memory corruption, causing crashes, instability, or privilege escalation. The risk is lower for general-purpose Linux systems that do not include or enable this accelerator driver. There is no current evidence of public exploitation, ransomware use, or CISA KEV listing, and the EPSS score is low, but kernel memory corruption flaws should still be remediated during normal kernel update cycles for systems using the impacted hardware path.

How an attack unfolds

An attacker first needs the ability to interact with the Ethos-U accelerator driver, typically by running code on the system or in a workload that can open the accelerator device node and submit command streams. The attacker crafts command stream DMA descriptors with values that cause signed stride additions, intermediate multiplications, or offset additions in dma_length() to underflow or overflow. The wrapped result causes the driver to record an artificially small region_size[] value. The job validation logic then compares this incorrect size against the GEM buffer size and may accept a command stream that should have been rejected. If accepted, the hardware or driver path may access memory outside the intended buffer, potentially leading to kernel memory corruption, denial of service, information exposure, or privilege escalation depending on surrounding memory layout and exploit reliability.

How to fix it

Update to a Linux kernel version that includes the upstream fix for CVE-2026-53171. The fix validates signed additions, uses overflow-safe arithmetic helpers for multiplications and offset calculations, and propagates dma_length() errors to the caller so invalid command streams are rejected. If no vendor kernel package is available yet, track the distribution, embedded Linux vendor, or device manufacturer advisory for a backported fix. As a temporary mitigation, disable or unload the Ethos-U accelerator driver where it is not required, restrict access to the accelerator device node to trusted users and services only, and avoid exposing the device into containers or untrusted workloads.

How to confirm the fix worked

Confirm the running kernel includes the vendor fix or an upstream/backported patch for the Ethos-U dma_length() arithmetic checks. Validate kernel package versions against the operating system or device vendor advisory once fixed builds are published. On systems where the driver is not needed, confirm the Ethos-U driver is not loaded and the related device node is absent or inaccessible to untrusted users. Security teams can also review kernel configuration, loaded modules, and device permissions to verify that only trusted processes can submit jobs to the accelerator.

Typical attack path

1. Gain local code execution or workload-level access on a Linux system with the affected Ethos-U accelerator driver enabled and accessible.
2. Open or otherwise interact with the accelerator device interface used to submit Ethos-U jobs.
3. Prepare a malicious command stream containing DMA region parameters, strides, sizes, and offsets selected to trigger arithmetic underflow or overflow in dma_length().
4. Submit the malicious job so the driver computes an incorrect, wrapped DMA region length.
5. Rely on the under-reported region_size[] value to bypass command stream bounds validation against the GEM buffer size.
6. Trigger out-of-bounds access or memory corruption during job processing, potentially causing a kernel crash or enabling further exploitation.

How to detect it

There are no known public exploit indicators or unique network signatures for this issue. Detection should focus on host-level evidence from systems with the Ethos-U driver enabled. Review kernel logs for crashes, warnings, oops traces, DMA faults, IOMMU faults, or accelerator job failures involving the Ethos-U driver. Examine audit logs, EDR telemetry, and device access records for unexpected processes opening accelerator device nodes or submitting jobs, especially from containers, low-privileged users, or applications that should not use NPU acceleration. If a crash occurred, preserve vmcore/kdump data and inspect stack traces for accel/ethosu, ethosu_job, dma_length, GEM buffer validation, IOMMU, or DMA mapping paths. Because exploitation may manifest only as memory corruption or denial of service, absence of a clear IOC does not prove absence of exploitation.

What your security team should do

• Inventory Linux systems and embedded devices that include Arm Ethos-U accelerator support or the accel/ethosu kernel driver.
• Prioritize patching systems where untrusted users, containers, edge workloads, or third-party applications can access the accelerator device.
• Restrict permissions on accelerator device nodes so only trusted service accounts can submit jobs.
• Disable or remove the Ethos-U driver on systems that do not require NPU acceleration.
• Monitor vendor advisories for exact fixed kernel package versions and deploy them through standard kernel update processes.
• Treat unexplained kernel crashes or memory corruption on systems using Ethos-U acceleration as potentially suspicious until patched.
• Do not prioritize as an internet-facing emergency unless the accelerator device is exposed to untrusted code paths; current public exploit maturity is none and EPSS is low.