Kernel memory exhaustion via unpurged TIPC buffers
Published May 1, 2025 · Updated Aug 5, 2026
A memory leak in TIPC in Linux 4.11 and affected later branches allows remote attackers to exhaust kernel memory via TIPC traffic. When backlog overload makes tipc_link_xmit return -ENOBUFS, net/tipc/link.c leaves the skb list unpurged and permanently orphans buffers. An unauthenticated peer reaching a configured TIPC UDP or Ethernet bearer can force allocation failures, OOM pressure, and lost TIPC connectivity.
Summary
What happened
A memory leak in TIPC in Linux 4.11 and affected later branches allows remote attackers to exhaust kernel memory via TIPC traffic. When backlog overload makes tipc_link_xmit return -ENOBUFS, net/tipc/link.c leaves the skb list unpurged and permanently orphans buffers. An unauthenticated peer reaching a configured TIPC UDP or Ethernet bearer can force allocation failures, OOM pressure, and lost TIPC connectivity.
The record
- CVE
- CVE-2025-37757
- Published
- May 1, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-401, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 1, 2025CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=365ad353c2564bba8835290061308ba825166b3a <09c2dcda2c551bba30710c33f6ac678ae7395389
- Affected versionversion=365ad353c2564bba8835290061308ba825166b3a <24e6280cdd7f8d01fc6b9b365fb800c2fb7ea9bb
- Affected versionversion=365ad353c2564bba8835290061308ba825166b3a <69ae94725f4fc9e75219d2d69022029c5b24bc9a
- Affected versionversion=365ad353c2564bba8835290061308ba825166b3a <7c5957f7905b4aede9d7a559d271438f3ca9e852
- Affected versionversion=365ad353c2564bba8835290061308ba825166b3a <84895f5ce3829d9fc030e5ec2d8729da4c0c9d08
- Affected versionversion=365ad353c2564bba8835290061308ba825166b3a <a40cbfbb8f95c325430f017883da669b2aa927d4
- Affected versionversion=365ad353c2564bba8835290061308ba825166b3a <d0e02d3d27a0b4dcb13f954f537ca1dd8f282dcf
- Affected versionversion=365ad353c2564bba8835290061308ba825166b3a <d4d40e437adb376be16b3a12dd5c63f0fa768247
- Affected versionversion=365ad353c2564bba8835290061308ba825166b3a <ed06675d3b8cd37120b447646d53f7cd3e6fcd63
- Affected versionversion=4.11
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