Service interruption via ring-allocation resource leak
Published May 1, 2026 · Updated May 1, 2026
Resource leak in the Linux Kernel ftgmac100 Ethernet driver allows local users to interrupt service during interface opening. ftgmac100_alloc_rings() returns directly when an intermediate allocation fails, leaving previously allocated descriptor rings, socket-buffer arrays, or scratch memory unreleased. Reachability requires the ftgmac100 driver and an allocation failure during device opening; each reachable failure consumes unreclaimed kernel memory and reduces availability.
Summary
What happened
Resource leak in the Linux Kernel ftgmac100 Ethernet driver allows local users to interrupt service during interface opening. ftgmac100_alloc_rings() returns directly when an intermediate allocation fails, leaving previously allocated descriptor rings, socket-buffer arrays, or scratch memory unreleased. Reachability requires the ftgmac100 driver and an allocation failure during device opening; each reachable failure consumes unreclaimed kernel memory and reduces availability.
The record
- CVE
- CVE-2026-31737
- Published
- May 1, 2026
- Updated
- May 1, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- May 1, 2026CVE publishedPublication date reported by the CVE source.
- May 1, 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.12
- Affected versionversion=d72e01a0430f8a1ae7adb3cbf0b2e73fcd99252e <184b3a500d60ea48d1b176103cff1706c456edf3
- Affected versionversion=d72e01a0430f8a1ae7adb3cbf0b2e73fcd99252e <78da43320d9d6ed788147fb085184e4fc801f057
- Affected versionversion=d72e01a0430f8a1ae7adb3cbf0b2e73fcd99252e <82f86111f0704ab2ded11a2033bc6cf0be3e09ea
- Affected versionversion=d72e01a0430f8a1ae7adb3cbf0b2e73fcd99252e <8351d18989c8642fc53e2e12d94e42314a39b078
- Affected versionversion=d72e01a0430f8a1ae7adb3cbf0b2e73fcd99252e <8a71911fc7eeea930153322bc1efc065db8cd97e
- Affected versionversion=d72e01a0430f8a1ae7adb3cbf0b2e73fcd99252e <a7e1bf392acf11dc4209820fef75758f6e42bd65
- Affected versionversion=d72e01a0430f8a1ae7adb3cbf0b2e73fcd99252e <c0fd0fe745f5e8c568d898cd1513d0083e46204a
- Affected versionversion=d72e01a0430f8a1ae7adb3cbf0b2e73fcd99252e <d45230081f19c280096241353c26b0de457de795
What conditions does exploitation require?
What is affected?
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