VulnerabilityPublished 25 Jul 2025Updated 5 Nov 2026

CVE-2025-38427: Linux kernel · video: screen_info: Relocate framebuffers behind PCI bridges

Affects Linux kernelSource CVE Database V5

Compare

Not known to be exploited · fixed in cc3cc41ed67054a03134bea42408c720eec0fa04 : update Linux kernel when convenient.

Data as of 5 Nov 2026, 21:20 UTC

Severity

Medium

Rated Medium by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-05.

Patch

Available – fixed in cc3cc41ed67054a03134bea42408c720eec0fa04, aeda386d86d79269a08f470dbdc53d13a91e51fa, 6.6.95 +2

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected >=6.6.45 <6.6.95	Fixed in cc3cc41ed67054a03134bea42408c720eec0fa04 aeda386d86d79269a08f470dbdc53d13a91e51fa 6.6.95 5c70e3ad85d2890d8af375333699429de26327f2 2f29b5c231011b94007d2c8a6d793992f2275db1
LinuxLinux	Affected =6.9	Fixed in–

AI-suggested

This vulnerability has been fixed in Linux kernel versions 6.6.95 and 6.9, as well as specific commits identified in the established facts. Users and administrators should update to these fixed versions to remediate the issue. No additional mitigation actions are indicated.

Description

A vulnerability in the Linux kernel's video subsystem related to the handling of framebuffer memory behind PCI bridges has been resolved. The issue involved incorrect addressing of framebuffer memory due to relocation offsets applied by PCI host bridges, which could cause invalid access to I/O memory. The fix ensures that the screen_info framebuffer addresses are updated to reflect these relocations properly.

Impact

The vulnerability could cause invalid access to I/O memory due to mismatched framebuffer addresses, potentially leading to system instability or crashes related to graphics device memory handling. No evidence of exploitation in the wild is reported. The impact is primarily on the correctness and stability of framebuffer memory access in affected Linux kernel versions.

Summary

CVE-2025-38427 addresses a flaw in the Linux kernel where framebuffer memory addresses stored in screen_info did not account for PCI host-bridge window offsets. During boot, firmware may relocate PCI graphics device framebuffer addresses by applying an offset, but the kernel's screen_info structure retained the original CPU address seen at boot (offset zero), leading to invalid I/O memory access. The patch applies the PCI host-bridge window offsets to the framebuffer addresses in screen_info, aligning them with the relocated PCI resource addresses. This fix prevents invalid memory accesses by synchronizing screen_info with the actual PCI resource mappings.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Nov 2026, 21:20 UTC

Technical details

References

Community reviews

Related threats