During a SRAM mapping attempt within the EthosU acceleration driver, a failure is not correctly detected; as a result, the driver leaves the SRAM size field non‑zero and reports success. Subsequent job requests then proceed under the assumption that SRAM is available and access the region whose base address is 0x0. This mismatch can cause the kernel to read or write to an unmapped or unintended memory region, potentially corrupting kernel data structures or triggering a crash. The primary consequence identified in the description is a loss of availability rather than privilege escalation.

Based on the description, it is inferred that any Linux kernel that includes the unpatched EthosU driver code may be affected. Systems that include the driver and have EthosU hardware are likely at risk, while environments that do not include the driver or have disabled it are not affected.

The EPSS score is 0.00189 and the CVE is not listed in CISA’s KEV catalog, indicating no publicly reported exploits at present. With a CVSS score of 5.5, the vulnerability is rated medium. Exhaustive exploitation requires the attacker to be able to submit jobs to the EthosU driver, which generally implies local or partially privileged access. It is inferred that by submitting a crafted job, one could trigger the mapping failure path and cause the driver to believe SRAM is present, leading to a null‑pointer or invalid memory access that most likely results in a kernel panic. The vulnerability does not provide a standalone privilege‑escalation path, so its impact is primarily denial of service rather than systemic takeover. Given the lack of exploitation data, the risk can be considered moderate until further evidence emerges.