What is CVE-2026-53170?

CVE-2026-53170 is a High severity Linux kernel vulnerability with a CVSS score of 8.8 out of 10, affecting Linux kernel versions from 6.19 onward and patched in 7.0.13 and 7.1. CVE-2026-53170 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2026-53170?

CVE-2026-53170 has a CVSS score of 8.8 out of 10, rated High severity. The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H.

Is there a patch available for CVE-2026-53170?

Yes, CVE-2026-53170 has been patched. Fixed versions include 7.0.13 and 7.1. If you are running Linux kernel 6.19 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2026-53170 actively exploited?

CVE-2026-53170 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

CVE-2026-53170

High

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.

Package Linux Kernel

Published 2026-06-25

Last modified 2026-07-06

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

8.8

out of 10

High

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Vector string

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Weakness type

CWE-908

CVE-2026-53170 is classified as CWE-908

See CWE-908 on MITRE CWE for full details on this weakness type.

Affected versions

Linux kernel versions 6.19 and later are affected. Fixed in 7.0.13, 7.1 and their respective stable series.

Affected from

≥ 6.19

Fixed in

✓ 7.0.13 7.0.x ✓ 7.1

References

2 total

Kernel Git
https://git.kernel.org/stable/c/d9d021218162b6c4fe0bdf42b2b340f1aae23a12

Patch
Kernel Git
https://git.kernel.org/stable/c/fb25c76a820ca8a547aa478bfb503da0a11494ab

Patch

Details

CVE ID CVE-2026-53170

Severity High

CVSS score 8.8 / 10

CVSS version 3.1

Published 2026-06-25

Modified 2026-07-06

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-53170?

CVE-2026-53170 is a High severity Linux kernel vulnerability with a CVSS score of 8.8 out of 10 . It affects Linux kernel versions from 6.19 onward and has been patched in 7.0.13 and 7.1. CVE-2026-53170 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-53170?

CVE-2026-53170 has a CVSS score of 8.8 out of 10, rated High severity (CVSS 3.1). The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H.
Is there a patch available for CVE-2026-53170?

Yes. CVE-2026-53170 has been patched. Fixed versions include 7.0.13 and 7.1. If you are running Linux kernel 6.19 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2026-53170 actively exploited?

No. CVE-2026-53170 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.