Local service interruption via accept-queue memory leak
Published Dec 2, 2024 · Updated May 23, 2026
Memory leak in Linux kernel virtio/vsock allows local users to exhaust memory by racing connection receipt with socket destruction. After accept_queue is flushed but before SOCK_DONE is set, virtio_transport_recv_listen() can create a child socket that vsock_enqueue_accept() retains without later removal. The race requires local access to exercise virtio/vsock during listener teardown, and repeated wins can deplete kernel memory and interrupt service.
Summary
What happened
Memory leak in Linux kernel virtio/vsock allows local users to exhaust memory by racing connection receipt with socket destruction. After accept_queue is flushed but before SOCK_DONE is set, virtio_transport_recv_listen() can create a child socket that vsock_enqueue_accept() retains without later removal. The race requires local access to exercise virtio/vsock during listener teardown, and repeated wins can deplete kernel memory and interrupt service.
The record
- CVE
- CVE-2024-53119
- Published
- Dec 2, 2024
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-401, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 2, 2024CVE publishedPublication date reported by the CVE source.
- May 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=2e7dd95046203bd05e8f4dc06ee53cace70a8e3c
- Affected versionversion=3fe356d58efae54dade9ec94ea7c919ed20cf4db <2415345042245de7601dcc6eafdbe3a3dcc9e379
- Affected versionversion=3fe356d58efae54dade9ec94ea7c919ed20cf4db <4310902c766e371359e6c6311056ae80b5beeac9
- Affected versionversion=3fe356d58efae54dade9ec94ea7c919ed20cf4db <897617a413e0bf1c6380e3b34b2f28f450508549
- Affected versionversion=3fe356d58efae54dade9ec94ea7c919ed20cf4db <946c7600fa2207cc8d3fbc86a518ec56f98a5813
- Affected versionversion=3fe356d58efae54dade9ec94ea7c919ed20cf4db <d7b0ff5a866724c3ad21f2628c22a63336deec3f
- Affected versionversion=3fe356d58efae54dade9ec94ea7c919ed20cf4db <e26fa236758e8baa61a82cfd9fd4388d2e8d6a4c
- Affected versionversion=5.10
- Affected versionversion=5.9.13 <5.10
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