CVE-2025-38427video: screen_info: Relocate framebuffers behind PCI bridges
- 5.5MediumCVSS base score
- 0.19%Exploitation in 30 daysEPSS · top 91% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: video: screen_info: Relocate framebuffers behind PCI bridges Apply PCI host-bridge window offsets to screen_info framebuffers. Fixes invalid access to I/O memory. Resources behind a PCI host bridge can be relocated by a certain offset in the kernel's CPU address range used for I/O. The framebuffer memory range stored in screen_info refers to the CPU addresses as seen during boot (where the offset is 0). During boot up, firmware may assign a different memory offset to the PCI host bridge and thereby relocating the framebuffer address of the PCI graphics device as seen by the kernel. The information in screen_info must be updated as well. The helper pcibios_bus_to_resource() performs the relocation of the screen_info's framebuffer resource (given in PCI bus addresses). The result matches the I/O-memory resource of the PCI graphics device (given in CPU addresses). As before, we store away the information necessary to later update the information in screen_info itself. Commit 78aa89d1dfba ("firmware/sysfb: Update screen_info for relocated EFI framebuffers") added the code for updating screen_info. It is based on similar functionality that pre-existed in efifb. Efifb uses a pointer to the PCI resource, while the newer code does a memcpy of the region. Hence efifb sees any updates to the PCI resource and avoids the issue. v3: - Only use struct pci_bus_region for PCI bus addresses (Bjorn) - Clarify address semantics in commit messages and comments (Bjorn) v2: - Fixed tags (Takashi, Ivan) - Updated information on efifb
Timeline
ID reserved
By Linux
- 3 months later
· 3 months later
Published
- 16 months later
· 16 months 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
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.19% · top 91% of all CVEs (16 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected a168da3182f8727b338509cb413147aa29012d6f – < cc3cc41ed67054a03134bea42408c720eec0fa04
- affected 78aa89d1dfba1e3cf4a2e053afa3b4c4ec622371 – < 5c70e3ad85d2890d8af375333699429de26327f2
- affected 78aa89d1dfba1e3cf4a2e053afa3b4c4ec622371 – < aeda386d86d79269a08f470dbdc53d13a91e51fa
- affected 78aa89d1dfba1e3cf4a2e053afa3b4c4ec622371 – < 2f29b5c231011b94007d2c8a6d793992f2275db1
- affected 6.6.45 – < 6.6.95
- affected 6.9
- unaffected < 6.9
- unaffected 6.6.95 – ≤ 6.6.*
- unaffected 6.12.35 – ≤ 6.12.*
- unaffected 6.15.4 – ≤ 6.15.*
- unaffected 6.16 – ≤ *
References
References4
- https://git.kernel.org/stable/c/cc3cc41ed67054a03134bea42408c720eec0fa04 (opens in a new tab)
- https://git.kernel.org/stable/c/5c70e3ad85d2890d8af375333699429de26327f2 (opens in a new tab)
- https://git.kernel.org/stable/c/aeda386d86d79269a08f470dbdc53d13a91e51fa (opens in a new tab)
- https://git.kernel.org/stable/c/2f29b5c231011b94007d2c8a6d793992f2275db1 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-22658 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-38427)Record last updated .