CVE-2023-52455 iommu: Don't reserve 0-length IOVA region
A Linux kernel IOMMU bug causes display driver failures and potential denial of service when firmware provides zero-length IOVA regions.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2023-52455?
CVE-2023-52455 is a high-severity vulnerability in Linux kernel, published on 23 Feb 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Official 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.
Which versions are affected by CVE-2023-52455?
It affects 1 product.
Products include Linux kernel.
How do I fix CVE-2023-52455?
Apply the vendor's patch.
Is CVE-2023-52455 being exploited?
There is no known exploitation of CVE-2023-52455 in the wild and no public exploit code.
Other vulnerabilities in Linux kernel
Sources
Also known as BELL-CVE-2023-52455, DEBIAN-CVE-2023-52455, GHSA-vqv4-92gw-6c3g, UBUNTU-CVE-2023-52455.