Local use-after-free via stale modelist pointers
Published Jul 19, 2026 · Updated Jul 19, 2026
Use-after-free in Linux Kernel fbdev before 6.6.144, 6.12.95, 6.18.38, or 7.1.3 allows local users to trigger stale kernel-memory reads. The store_modes() handler frees the old framebuffer modelist without clearing the console or framebuffer mode pointers, and later fbcon or sysfs paths dereference the stale pointers. Triggering the reads requires replacing the modelist, then reaching fbcon_mode_deleted() for an unmapped console or reading the mode sysfs attribute; the published record reports a read use-after-free, not privilege escalation.
Summary
What happened
Use-after-free in Linux Kernel fbdev before 6.6.144, 6.12.95, 6.18.38, or 7.1.3 allows local users to trigger stale kernel-memory reads. The store_modes() handler frees the old framebuffer modelist without clearing the console or framebuffer mode pointers, and later fbcon or sysfs paths dereference the stale pointers. Triggering the reads requires replacing the modelist, then reaching fbcon_mode_deleted() for an unmapped console or reading the mode sysfs attribute; the published record reports a read use-after-free, not privilege escalation.
The record
- CVE
- CVE-2026-63826
- Published
- Jul 19, 2026
- Updated
- Jul 19, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jul 19, 2026CVE publishedPublication date reported by the CVE source.
- Jul 19, 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.
- Affected versionversion=0 <6.12.95
- Affected versionversion=0 <6.18.38
- Affected versionversion=0 <6.6.144
- Affected versionversion=0 <7.1.3
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0d35f9f194a858567a21017d69318a51e3a822b9
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2c1c805c65fb7dc7524e20376d6987721e73a0b1
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5267eab88fa4c684459504b8be577ad64953b9a6
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <70f1e000b88cfa8ca3fd7f4d082647fc089a7769
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c6765f39ed27014ff877b00a2efa494233404e17
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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.
Weakness, pattern, technique
No sourced classifications are available.
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