Local service interruption via vsock list corruption
Published Jul 16, 2024 · Updated Aug 5, 2026
List corruption in Linux kernel vsock allows local users to interrupt service by retrying a connection after a pending signal. When vsock_stream_connect wakes with a pending signal after reaching TCP_ESTABLISHED, it resets socket state without removing the socket from the connected table, so a successful retry inserts the same socket twice. Exploitation requires local low-privileged access and control of the interrupted connection attempt; the double insertion corrupts the kernel's connected-socket list.
Summary
What happened
List corruption in Linux kernel vsock allows local users to interrupt service by retrying a connection after a pending signal. When vsock_stream_connect wakes with a pending signal after reaching TCP_ESTABLISHED, it resets socket state without removing the socket from the connected table, so a successful retry inserts the same socket twice. Exploitation requires local low-privileged access and control of the interrupted connection attempt; the double insertion corrupts the kernel's connected-socket list.
The record
- CVE
- CVE-2022-48786
- Published
- Jul 16, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 16, 2024CVE 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=3.9
- Affected versionversion=d021c344051af91f42c5ba9fdedc176740cbd238 <0bb88f3f7e8d506f3efe46d694964117e20efbfc
- Affected versionversion=d021c344051af91f42c5ba9fdedc176740cbd238 <2910bcb9f67551a45397735e47b6d456eb8cd549
- Affected versionversion=d021c344051af91f42c5ba9fdedc176740cbd238 <5f326fe2aef411a6575628f92bd861463ea91df7
- Affected versionversion=d021c344051af91f42c5ba9fdedc176740cbd238 <787468ee7a435777521d33399d012fd591ae2f94
- Affected versionversion=d021c344051af91f42c5ba9fdedc176740cbd238 <87cd1bbd6677411e17369cd4b7389ab1e1fdba44
- Affected versionversion=d021c344051af91f42c5ba9fdedc176740cbd238 <addd62a8cb6fa90aa322365c62487da61f6baab8
- Affected versionversion=d021c344051af91f42c5ba9fdedc176740cbd238 <b9208492fcaecff8f43915529ae34b3bcb03877c
- Affected versionversion=d021c344051af91f42c5ba9fdedc176740cbd238 <e3b3939fd137aab6d00d54bee0ee9244b286a608
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