Linux Kernel up to 7.0.12 accel ethosu_job.c cmd_state_init sentinel uninitialized pointer

Summaryinfo

A vulnerability marked as critical has been reported in Linux Kernel up to 7.0.12. The affected element is the function cmd_state_init of the file ethosu_job.c of the component accel. Performing a manipulation of the argument sentinel results in uninitialized pointer. This vulnerability is reported as CVE-2026-53170. The attack may be carried out on the physical device. No exploit exists. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability classified as critical has been found in Linux Kernel up to 7.0.12. This affects the function cmd_state_init of the file ethosu_job.c of the component accel. The manipulation of the argument sentinel with an unknown input leads to a uninitialized pointer vulnerability. CWE is classifying the issue as CWE-824. The product accesses or uses a pointer that has not been initialized. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: accel/ethosu: reject DMA commands with uninitialized length cmd_state_init() initializes the command state with memset(0xff), leaving dma->len at U64_MAX to signal missing setup. The only setter is NPU_SET_DMA0_LEN; if userspace omits this command and issues NPU_OP_DMA_START, dma->len remains U64_MAX. In dma_length(), a positive stride added to U64_MAX wraps to a small value. With size0 == 1, check_mul_overflow() does not trigger and dma_length() returns 0 instead of U64_MAX. The caller's U64_MAX check then passes, region_size[] stays 0, and the bounds check in ethosu_job.c is bypassed, allowing hardware to execute DMA with stale physical addresses. Fix by checking for U64_MAX at the start of dma_length() before any arithmetic, consistent with the sentinel value used throughout the driver to detect uninitialized fields.

The advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2026-53170 since 06/09/2026. The exploitability is told to be difficult. An attack has to be approached locally. Technical details are known, but no exploit is available.

Upgrading to version 7.0.13 eliminates this vulnerability. Applying the patch fb25c76a820ca8a547aa478bfb503da0a11494ab/d9d021218162b6c4fe0bdf42b2b340f1aae23a12 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 7.0.0
• 7.0.1
• 7.0.2
• 7.0.3
• 7.0.4
• 7.0.5
• 7.0.6
• 7.0.7
• 7.0.8
• 7.0.9
• 7.0.10
• 7.0.11
• 7.0.12

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion