Local denial of service via unbalanced socket references
Published Oct 21, 2022 · Updated Apr 23, 2025
Memory leak in Linux Kernel vsock_connect allows local users to consume kernel memory through repeated connection requests. A pending connect_work makes scheduling return without adding another timeout, yet vsock_connect still calls sock_hold, leaving two holds for one sock_put. Reaching the leak requires nonblocking connects around a signal-interrupted blocking connect; each sequence leaves a socket reference unreleased.
Summary
What happened
Memory leak in Linux Kernel vsock_connect allows local users to consume kernel memory through repeated connection requests. A pending connect_work makes scheduling return without adding another timeout, yet vsock_connect still calls sock_hold, leaving two holds for one sock_put. Reaching the leak requires nonblocking connects around a signal-interrupted blocking connect; each sequence leaves a socket reference unreleased.
The record
- CVE
- CVE-2022-3629
- Published
- Oct 21, 2022
- Updated
- Apr 23, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-401, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 21, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 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=n/a
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