Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
7.8
CVE-2023-52455: Linux kernel can block display mapping with zero-size IOVA
CVE-2023-52455 · published 2 years ago
Summary
The Linux kernel may reserve a memory region for the display even when the firmware reports a size of zero. This creates a corrupted internal table, preventing the display driver from working correctly. Update the kernel to skip zero-length reservations and apply any available firmware updates.
What to do
- Update debian linux to version 6.6.15-1.
- Update linux kernel to version 6.7.2.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| Debian:13 | debian | linux |
< 6.6.15-1 Fix: upgrade to 6.6.15-1
|
| Debian:14 | debian | linux |
< 6.6.15-1 Fix: upgrade to 6.6.15-1
|
| – | linux | linux_kernel |
>= 6.3.0, < 6.6.14 >= 6.7.0, < 6.7.2 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* |
| Linux | linux | kernel |
>= 6.7.0, < 6.7.2 Fix: upgrade to 6.7.2
|
Original advisory text
iommu: Don't reserve 0-length IOVA region
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.
References
- https://security-tracker.debian.org/tracker/CVE-2023-52455 Vendor Advisory
- https://git.kernel.org/stable/c/5e23e283910c9f30248732ae0770bcb0c9438abf URL
- https://git.kernel.org/stable/c/98b8a550da83cc392a14298c4b3eaaf0332ae6ad URL
- https://git.kernel.org/stable/c/bb57f6705960bebeb832142ce9abf43220c3eab1 URL
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/52xxx/CVE-2023-52455... Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2023-52455 Vendor Advisory
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git Product
Internet-facing
60 days
Internal
At next upgrade
- Not known to be exploited
- Needs hands-on effort to exploit
- Gives an attacker partial control
Severity
7.8
High
Timeline
Published23 Feb 2024
Updated4 Nov 2026
First seen15 Sep 2026
Track software like this
Free during beta