# CVE-2025-38427: video: screen_info: Relocate framebuffers behind PCI bridges

Status: published. Published: 2025-07-25. Updated: 2026-11-05.

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

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Linux / Linux: ≥ a168da3182f8727b338509cb413147aa29012d6f; < cc3cc41ed67054a03134bea42408c720eec0fa04 (affected, git); ≥ 78aa89d1dfba1e3cf4a2e053afa3b4c4ec622371; < 5c70e3ad85d2890d8af375333699429de26327f2 (affected, git); ≥ 78aa89d1dfba1e3cf4a2e053afa3b4c4ec622371; < aeda386d86d79269a08f470dbdc53d13a91e51fa (affected, git); ≥ 78aa89d1dfba1e3cf4a2e053afa3b4c4ec622371; < 2f29b5c231011b94007d2c8a6d793992f2275db1 (affected, git); ≥ 6.6.45; < 6.6.95 (affected, semver). Source: CNA: Linux
- Linux / Linux: 6.9 (affected); ≥ 0; < 6.9 (unaffected, semver); ≥ 6.6.95; ≤ 6.6.* (unaffected, semver); ≥ 6.12.35; ≤ 6.12.* (unaffected, semver); ≥ 6.15.4; ≤ 6.15.* (unaffected, semver); ≥ 6.16; ≤ * (unaffected, original_commit_for_fix). Source: CNA: Linux

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: 0.19% as of 2026-11-05; percentile 8.58%

- SSVC: exploitation none; automatable no; technical impact partial; source ADP: CISA-ADP

- Weaknesses: Not reported

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://git.kernel.org/stable/c/cc3cc41ed67054a03134bea42408c720eec0fa04 (CNA: Linux)

- https://git.kernel.org/stable/c/5c70e3ad85d2890d8af375333699429de26327f2 (CNA: Linux)

- https://git.kernel.org/stable/c/aeda386d86d79269a08f470dbdc53d13a91e51fa (CNA: Linux)

- https://git.kernel.org/stable/c/2f29b5c231011b94007d2c8a6d793992f2275db1 (CNA: Linux)

## Provenance

- CNA: Linux: https://www.cve.org/CVERecord?id=CVE-2025-38427; retrieved 2026-11-05; source updated 2026-11-05

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2025-38427; retrieved 2026-11-05; source updated Not reported

Revision: 45015ad172a72c5dfde203beb92516fa3418608efe41b50f47716d255ceb4ad8

Canonical: https://y2.dev/cve/CVE-2025-38427

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.