Kernel-memory exhaustion via stale KCM send cursor
Published Dec 24, 2025 · Updated Dec 24, 2025
Memory leak in the Linux kernel KCM send path allows local users to exhaust kernel memory through crafted socket send errors. The kcm_sendmsg() error path leaves last_skb pointing to an obsolete buffer after a partial copy, so a later send corrupts the head frag_list and leaks the allocated buffer. Low-privileged local access and KCM socket use are required; repeated triggering consumes kernel memory and can interrupt service.
Summary
What happened
Memory leak in the Linux kernel KCM send path allows local users to exhaust kernel memory through crafted socket send errors. The kcm_sendmsg() error path leaves last_skb pointing to an obsolete buffer after a partial copy, so a later send corrupts the head frag_list and leaks the allocated buffer. Low-privileged local access and KCM socket use are required; repeated triggering consumes kernel memory and can interrupt service.
The record
- CVE
- CVE-2023-54112
- Published
- Dec 24, 2025
- Updated
- Dec 24, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 24, 2025CVE publishedPublication date reported by the CVE source.
- Dec 24, 2025Record 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.6
- Affected versionversion=ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 <16989de75497574b5fafd174c0c233d5a86858b7
- Affected versionversion=ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 <33db24ad811b3576a0c2f8862506763f2be925b0
- Affected versionversion=ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 <479c71cda14b3c3a6515773faa39055333eaa2b7
- Affected versionversion=ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 <5e5554389397e98fafb9efe395d8b4830dd5f042
- Affected versionversion=ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 <8dc7eb757b1652b82725f32e0c89a1e9f6c0e13b
- Affected versionversion=ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 <97275339c34cfbccd65e87bc38fd910ae66c48ba
- Affected versionversion=ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 <af8085e0fc3207ecbf8b9e7a635c790e36d058c6
- Affected versionversion=ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 <c821a88bd720b0046433173185fd841a100d44ad
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