What is CVE-2026-53164?

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

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

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

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

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

Is CVE-2026-53164 actively exploited?

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

CVE-2026-53164

Medium

In the Linux kernel, the following vulnerability has been resolved: iommu/dma: Do not try to iommu_map a 0 length region in swiotlb iommu_dma_iova_link_swiotlb() processes a mapping that is unaligned in three parts, the head, middle and trailer. If the middle is empty because there are no aligned pages it will call down to iommu_map() with a 0 size which the iommupt implementation will fail as illegal. It then tries to do an error unwind and starts from the wrong spot corrupting the mapping so the eventual destruction triggers a WARN_ON. Check for 0 length and avoid mapping and use offset not 0 as the starting point to unlink. This is frequently triggered by using some kinds of thunderbolt NVMe drives that trigger forced SWIOTLB for unaligned memory. NVMe seems to pass in oddly aligned buffers for the passthrough commands from smartctl that hit this condition.

Package Linux Kernel

Published 2026-06-25

Last modified 2026-07-07

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

5.5

out of 10

Medium

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

High

Vector string

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

Affected versions

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

Affected from

≥ 6.16

Fixed in

✓ 6.18.36 6.18.x ✓ 7.0.13 7.0.x ✓ 7.1

References

3 total

Kernel Git
https://git.kernel.org/stable/c/6ec91df8aff77e2e8fe3179c1f3fc15b43a40ba3

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

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

Patch

Details

CVE ID CVE-2026-53164

Severity Medium

CVSS score 5.5 / 10

CVSS version 3.1

Published 2026-06-25

Modified 2026-07-07

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-53164?

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

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

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

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