System crash via UDP socket destruction race
Published May 21, 2024 · Updated Aug 5, 2026
Race condition in Linux kernel UDP handling allows local users to crash the system by racing socket destruction against close(). The udp_abort() path can proceed after udp_destroy_sock() or udpv6_destroy_sock() releases the socket lock, rehashing a socket as close() destroys it and leaving a dangling UDP hash node. Exploitation requires concurrent close() and netlink SOCK_DESTROY operations plus CAP_NET_ADMIN in the socket's network namespace; successful triggering causes a kernel panic.
Summary
What happened
Race condition in Linux kernel UDP handling allows local users to crash the system by racing socket destruction against close(). The udp_abort() path can proceed after udp_destroy_sock() or udpv6_destroy_sock() releases the socket lock, rehashing a socket as close() destroys it and leaving a dangling UDP hash node. Exploitation requires concurrent close() and netlink SOCK_DESTROY operations plus CAP_NET_ADMIN in the socket's network namespace; successful triggering causes a kernel panic.
The record
- CVE
- CVE-2021-47248
- Published
- May 21, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-362, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 21, 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=4.9
- Affected versionversion=5d77dca82839ef016a93ad7acd7058b14d967752 <2f73448041bd0682d4b552cfd314ace66107f1ad
- Affected versionversion=5d77dca82839ef016a93ad7acd7058b14d967752 <5a88477c1c85e4baa51e91f2d40f2166235daa56
- Affected versionversion=5d77dca82839ef016a93ad7acd7058b14d967752 <65310b0aff86980a011c7c7bfa487a333d4ca241
- Affected versionversion=5d77dca82839ef016a93ad7acd7058b14d967752 <8729ec8a2238152a4afc212a331a6cd2c61aeeac
- Affected versionversion=5d77dca82839ef016a93ad7acd7058b14d967752 <a0882f68f54f7a8b6308261acee9bd4faab5a69e
- Affected versionversion=5d77dca82839ef016a93ad7acd7058b14d967752 <a8b897c7bcd47f4147d066e22cc01d1026d7640e
- Affected versionversion=5d77dca82839ef016a93ad7acd7058b14d967752 <e3c36c773aed0fef8b1d3d555b43393ec564400f
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