CVE-2023-52455
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Record status
- Modified
Affected
- Linux Kernel < 6.6.14
- Linux Kernel < 6.7.2
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2023-52455.md and follow it. Check whether this project is affected by CVE-2023-52455. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/5e23e283910c9f30248732ae0770bcb0c9438abf
- https://git.kernel.org/stable/c/98b8a550da83cc392a14298c4b3eaaf0332ae6ad
- https://git.kernel.org/stable/c/bb57f6705960bebeb832142ce9abf43220c3eab1
- https://git.kernel.org/stable/c/5e23e283910c9f30248732ae0770bcb0c9438abf
- https://git.kernel.org/stable/c/98b8a550da83cc392a14298c4b3eaaf0332ae6ad
- https://git.kernel.org/stable/c/bb57f6705960bebeb832142ce9abf43220c3eab1
References
- https://git.kernel.org/stable/c/5e23e283910c9f30248732ae0770bcb0c9438abf
- https://git.kernel.org/stable/c/98b8a550da83cc392a14298c4b3eaaf0332ae6ad
- https://git.kernel.org/stable/c/bb57f6705960bebeb832142ce9abf43220c3eab1
- https://git.kernel.org/stable/c/5e23e283910c9f30248732ae0770bcb0c9438abf
- https://git.kernel.org/stable/c/98b8a550da83cc392a14298c4b3eaaf0332ae6ad
- https://git.kernel.org/stable/c/bb57f6705960bebeb832142ce9abf43220c3eab1