CVE-2023-52455

iommu: Don't reserve 0-length IOVA region

HIGH
7.8
CVSS Score
Published: February 23, 2024 at 02:46 PM UTC
Updated: June 17, 2026 at 06:42 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: iommu: Don't reserve 0-length IOVA region When the bootloader/firmware doesn't setup the framebuffers, their address and size are 0 in "iommu-addresses" property. If IOVA region is reserved with 0 length, then it ends up corrupting the IOVA rbtree with an entry which has pfn_hi < pfn_lo. If we intend to use display driver in kernel without framebuffer then it's causing the display IOMMU mappings to fail as entire valid IOVA space is reserved when address and length are passed as 0. An ideal solution would be firmware removing the "iommu-addresses" property and corresponding "memory-region" if display is not present. But the kernel should be able to handle this by checking for size of IOVA region and skipping the IOVA reservation if size is 0. Also, add a warning if firmware is requesting 0-length IOVA region reservation.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.3 ≤ v < 6.6.146.3 ≤ v < 6.7.26.3 ≤ v < 6.86.3.0 ≤ v < 6.6.146.7.0 ≤ v < 6.7.26.3a5bf3cfce8cb77d9d24613ab52d520896f83dd48
Vendor states this is fixed in 5e23e283910c9f30248732ae0770bcb0c9438abf (fixed)
Vendor states this is fixed in 98b8a550da83cc392a14298c4b3eaaf0332ae6ad (fixed)
Vendor states this is fixed in bb57f6705960bebeb832142ce9abf43220c3eab1 (fixed)
Vendor states this is fixed in 6.3 (unaffected)
Vendor states this is fixed in 6.6.14 (unaffected)
Vendor states this is fixed in 6.7.2 (unaffected)
Vendor states this is fixed in 6.8 (unaffected)

References (3)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/5e23e283910c9f30248732ae0770bcb0c9438abf
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/98b8a550da83cc392a14298c4b3eaaf0332ae6ad
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/bb57f6705960bebeb832142ce9abf43220c3eab1

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card