CVE-2025-38427

System interruption via stale framebuffer address

Published Jul 25, 2025 · Updated May 23, 2026

Invalid I/O-memory access in affected Linux kernel releases allows local users to interrupt the system through a relocated PCI framebuffer. drivers/video/screen_info_pci.c copies the framebuffer resource before PCI bridge relocation, leaving screen_info with a stale CPU address instead of applying the bridge-window offset. The condition requires firmware to relocate a PCI host bridge during boot, and the published assessment limits impact to availability.

CVSS severity5.5
Medium
EPSS probability0.16%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Invalid I/O-memory access in affected Linux kernel releases allows local users to interrupt the system through a relocated PCI framebuffer. drivers/video/screen_info_pci.c copies the framebuffer resource before PCI bridge relocation, leaving screen_info with a stale CPU address instead of applying the bridge-window offset. The condition requires firmware to relocate a PCI host bridge during boot, and the published assessment limits impact to availability.

The record

CVE
CVE-2025-38427
Published
Jul 25, 2025
Updated
May 23, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
CWE-401, T1499
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Jul 25, 2025CVE publishedPublication date reported by the CVE source.
  2. May 23, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=6.6.45 <6.6.95
  2. Affected versionversion=6.9
  3. Affected versionversion=78aa89d1dfba1e3cf4a2e053afa3b4c4ec622371 <2f29b5c231011b94007d2c8a6d793992f2275db1
  4. Affected versionversion=78aa89d1dfba1e3cf4a2e053afa3b4c4ec622371 <5c70e3ad85d2890d8af375333699429de26327f2
  5. Affected versionversion=78aa89d1dfba1e3cf4a2e053afa3b4c4ec622371 <aeda386d86d79269a08f470dbdc53d13a91e51fa
  6. Affected versionversion=a168da3182f8727b338509cb413147aa29012d6f <cc3cc41ed67054a03134bea42408c720eec0fa04

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=6.6.45 <6.6.95; version=6.9; version=78aa89d1dfba1e3cf4a2e053afa3b4c4ec622371 <2f29b5c231011b94007d2c8a6d793992f2275db1; version=78aa89d1dfba1e3cf4a2e053afa3b4c4ec622371 <5c70e3ad85d2890d8af375333699429de26327f2; version=78aa89d1dfba1e3cf4a2e053afa3b4c4ec622371 <aeda386d86d79269a08f470dbdc53d13a91e51fa; version=a168da3182f8727b338509cb413147aa29012d6f <cc3cc41ed67054a03134bea42408c720eec0fa04

Published CVSS scores

5.5UbuntuCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-401Missing Release of Memory after Effective Lifetime
T1499Endpoint Denial of Service

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo