CVE-2023-52455
Last modified
CVE-2023-52455 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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. EPSS estimates a 0.24% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 6.3.0, < 6.6.14 |
| Linux | Linux Kernel | >= 6.7.0, < 6.7.2 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2023-52455?
How severe is CVE-2023-52455?
How do I fix CVE-2023-52455?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2023
- CVE-2023-5245FileUtil.extract() enumerates all zip file entries and extra…9.8
- CVE-2023-52450In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-52451In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-52452In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-52453In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-52454In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-52456In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-52457In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-52458In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-52459In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-5246Authentication Bypass by Capture-replay in SICK Flexi Soft G…8.8
- CVE-2023-52460In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2023-52455?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
