Kernel memory leak via s3fb probe errors
Published Aug 15, 2026 · Updated Aug 15, 2026
Memory leak in the s3fb driver in affected Linux kernel releases allows attackers to retain kernel memory through device-probe error paths. The s3_pci_probe() function allocates a modelist with fb_videomode_to_modelist() but omits fb_destroy_modelist() on later error paths. Reachability requires the s3fb driver and a probe failure after allocation; published sources do not establish attacker control or system-level exhaustion.
Summary
What happened
Memory leak in the s3fb driver in affected Linux kernel releases allows attackers to retain kernel memory through device-probe error paths. The s3_pci_probe() function allocates a modelist with fb_videomode_to_modelist() but omits fb_destroy_modelist() on later error paths. Reachability requires the s3fb driver and a probe failure after allocation; published sources do not establish attacker control or system-level exhaustion.
The record
- CVE
- CVE-2026-72270
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Aug 15, 2026CVE publishedPublication date reported by the CVE source.
- Aug 15, 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=3.0
- Affected versionversion=86c0f043a737dadf034a4e6f29aefb074f4a1146 <0d0fa8425b29657b3d3e5bb36f50a50e57c8101f
- Affected versionversion=86c0f043a737dadf034a4e6f29aefb074f4a1146 <25b354f74b028a3f91b12e6b446256965744c477
- Affected versionversion=86c0f043a737dadf034a4e6f29aefb074f4a1146 <37f4b8bd9e3835a7d4da26baf80b497e478d3123
- Affected versionversion=86c0f043a737dadf034a4e6f29aefb074f4a1146 <3b0ed04bc852887a9164e1bbf521652e8ef3eb92
- Affected versionversion=86c0f043a737dadf034a4e6f29aefb074f4a1146 <56964e8039150a14462005458b25f19d6cad8f4a
- Affected versionversion=86c0f043a737dadf034a4e6f29aefb074f4a1146 <ad54698255a4b988cae1ad908c158c1d4128887c
- Affected versionversion=86c0f043a737dadf034a4e6f29aefb074f4a1146 <ef6c5e4607483259a0daf6584e9e34ef643a655d
- Affected versionversion=86c0f043a737dadf034a4e6f29aefb074f4a1146 <fc90ec978a3cef6f6d8c6074bee538998c7c9837
What conditions does exploitation require?
What is affected?
Published CVSS scores
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