Kernel faults via socket lifetime race
Published Oct 23, 2026 · Updated Oct 23, 2026
Use-after-free in Linux SMC smc_getname() allows local users to trigger kernel faults via getsockname() during socket teardown. The callback dereferences smc->clcsock without clcsock_release_lock while link-group termination releases the CLC socket, causing a stale or NULL pointer access. Triggering requires an SMC socket and concurrent teardown; the published demonstration uses test-only timing instrumentation and does not establish privilege escalation.
Summary
What happened
Use-after-free in Linux SMC smc_getname() allows local users to trigger kernel faults via getsockname() during socket teardown. The callback dereferences smc->clcsock without clcsock_release_lock while link-group termination releases the CLC socket, causing a stale or NULL pointer access. Triggering requires an SMC socket and concurrent teardown; the published demonstration uses test-only timing instrumentation and does not establish privilege escalation.
The record
- CVE
- CVE-2026-99032
- Published
- Oct 23, 2026
- Updated
- Oct 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 23, 2026CVE publishedPublication date reported by the CVE source.
- Oct 23, 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=0b6153d04c96a1d4b6284692386aa21d04d7956c
- Affected versionversion=4.19.299 <4.20
- Affected versionversion=5.1
- Affected versionversion=b03faa1fafc8018295401dc558bdc76362d860a4 <1512e3714b3946bda75a160a34f22a51710daa43
- Affected versionversion=b03faa1fafc8018295401dc558bdc76362d860a4 <64a6b36b0e1855288080bc5f89769f27d6dc03c8
- Affected versionversion=b03faa1fafc8018295401dc558bdc76362d860a4 <6a1833f0d7dc037c8e876b9178ba69d5d107c086
- Affected versionversion=b03faa1fafc8018295401dc558bdc76362d860a4 <c223da71abfaea2ebb1c7208ae9ebf15038f9388
- Affected versionversion=b03faa1fafc8018295401dc558bdc76362d860a4 <e607017a553d2a48e428ec8b8ffb06bf3bb92ce9
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us