Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2023-52455iommu: Don't reserve 0-length IOVA region

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.

Timeline

  1. ID reserved

    By Linux

  2. · 3 days later

    Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2023-52455, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.24% · top 85% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected a5bf3cfce8cb77d9d24613ab52d520896f83dd48 – < 98b8a550da83cc392a14298c4b3eaaf0332ae6ad
    • affected a5bf3cfce8cb77d9d24613ab52d520896f83dd48 – < 5e23e283910c9f30248732ae0770bcb0c9438abf
    • affected a5bf3cfce8cb77d9d24613ab52d520896f83dd48 – < bb57f6705960bebeb832142ce9abf43220c3eab1
  • Linux · Linux

    • affected 6.3
    • unaffected < 6.3
    • unaffected 6.6.14 – ≤ 6.6.*
    • unaffected 6.7.2 – ≤ 6.7.*
    • unaffected 6.8 – ≤ *

References

References3

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-52455 badge
[![CVE-2023-52455](https://cveledger.app/badge/CVE-2023-52455.svg)](https://cveledger.app/cve/CVE-2023-52455)

Record last updated .