HIGH Introduced in 6.19
ethosu Precision OOB
CVE-2026-98143
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
KernelScan AI7.8HIGH
01Description
In the Linux kernel, the following vulnerability has been resolved: accel: ethosu: Don't read the U65 rounding mode as a storage mode Bits 15:14 of NPU_SET_{IFM,OFM}_PRECISION select the activation storage mode on U85 only. On U65 the same field holds the rounding mode, and the command stream parser has read it as a storage mode since the driver was added. That went unnoticed while unknown values fell through the switch, but now that they are rejected, every U65 command stream that asks for natural rounding (2) fails CMDSTREAM_BO_CREATE with -EINVAL. Mesa emits it for average pooling, concatenation, split, unpack, strided slice, LUT and argmax, which is 72 failures of the Teflon test suite on an i.MX93. Truncating rounding (1) is misread as well: it picks the two-tile address path and computes a bogus feature map size from tile bases the command stream never set. Read the field as a storage mode only on the hardware where it is one.
02KernelScan AI Analysis
Risk summary
A local user with access to an Arm Ethos-U NPU device can submit a command stream that triggers incorrect buffer size computation, causing the DMA engine to read or write outside allocated memory. Because the NPU lacks an MMU and can access any system memory, this can lead to arbitrary memory corruption, information disclosure, or denial of service. The bug requires specific hardware (Ethos-U65 NPU, e.g. on i.MX93 platforms).
Vulnerability analysis
The driver for the Arm Ethos-U NPU misuses a command-stream setting on U65 hardware. On that hardware, the setting controls rounding, but the driver interprets it as a memory-layout mode. When certain rounding values are requested, the driver calculates buffer sizes using data that was never supplied, producing incorrect dimensions. Because the NPU lacks an MMU and can directly access any system memory, the flawed size check allows the hardware to read or write outside the intended buffers. The corrected driver now interprets that setting as a layout mode only on the hardware where it actually is one, and ignores it otherwise. Any local user who can submit workloads to the accelerator device can reach the bug, which typically includes unprivileged users accessing the device through standard graphics and machine-learning libraries.
Lifecycle
03Fix Versions
| Branch | Introduced | Fixed in | Patch commit |
|---|---|---|---|
| 7.2 | 6.19 | 7.2.7 | 6b08adbda8ea |
| mainline | 6.19 | 7.3 | db9deec5a345 |