CPU hang via non-yielding socket-map teardown
Published Oct 21, 2024 · Updated May 23, 2026
Resource exhaustion in affected Linux kernel releases allows local users to cause a CPU soft lockup by destroying a large socket map. sock_hash_free() traverses every bucket during map teardown without a scheduling point, so a large bucket array monopolizes the CPU instead of yielding. Exploitation requires local low-privileged access and control of a large BPF socket-hash map; the bounded consequence is a CPU hang and service interruption.
Summary
What happened
Resource exhaustion in affected Linux kernel releases allows local users to cause a CPU soft lockup by destroying a large socket map. sock_hash_free() traverses every bucket during map teardown without a scheduling point, so a large bucket array monopolizes the CPU instead of yielding. Exploitation requires local low-privileged access and control of a large BPF socket-hash map; the bounded consequence is a CPU hang and service interruption.
The record
- CVE
- CVE-2024-47710
- Published
- Oct 21, 2024
- Updated
- May 23, 2026
- Vendor
- Siemens
- Product
- SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 21, 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=0 <V3.2
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