Service interruption via tridentfb probe memory leak
Published Aug 15, 2026 · Updated Aug 15, 2026
Memory leak in the tridentfb PCI probe in Linux allows local users to exhaust kernel memory through repeated probe failures. trident_pci_probe() allocates modelist entries with fb_videomode_to_modelist(), but subsequent error branches return without calling fb_destroy_modelist(). Exploitation requires local low-privilege access and a supported PCI or AGP Trident graphics card; repeated failures can interrupt the system by depleting memory.
Summary
What happened
Memory leak in the tridentfb PCI probe in Linux allows local users to exhaust kernel memory through repeated probe failures. trident_pci_probe() allocates modelist entries with fb_videomode_to_modelist(), but subsequent error branches return without calling fb_destroy_modelist(). Exploitation requires local low-privilege access and a supported PCI or AGP Trident graphics card; repeated failures can interrupt the system by depleting memory.
The record
- CVE
- CVE-2026-72264
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-772, T1499.004
- Attack vector
- local
- Privileges
- authenticated
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=4.4
- Affected versionversion=6a5e3bd0c8bc1025bb5092f54d5aea38216c665e <089d149ccd7c3ac3d5e14ac65e558dcd9ec27583
- Affected versionversion=6a5e3bd0c8bc1025bb5092f54d5aea38216c665e <2efd9797331a559b93ab888f451838f87bd6dfa3
- Affected versionversion=6a5e3bd0c8bc1025bb5092f54d5aea38216c665e <4ebe2c3a7db6332aab3655f8c552ca387c1dc199
- Affected versionversion=6a5e3bd0c8bc1025bb5092f54d5aea38216c665e <5bdb6f11ad0398b11a3ae4d9104035f9dc628cdc
- Affected versionversion=6a5e3bd0c8bc1025bb5092f54d5aea38216c665e <7a35ec619d9af8ee128320975c1252b8ad65f1e8
- Affected versionversion=6a5e3bd0c8bc1025bb5092f54d5aea38216c665e <868432039a3fd7c2c0d515e48f33d5e43391666c
- Affected versionversion=6a5e3bd0c8bc1025bb5092f54d5aea38216c665e <8d16e5bc78478176621cac0f4c381136d3c92c5f
- Affected versionversion=6a5e3bd0c8bc1025bb5092f54d5aea38216c665e <de9cf16e39c0378716e9764fc0fbb6d4b45a1ee1
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
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