CPU soft lockup via zero retire timeout
Published Jun 3, 2020 · Updated Aug 5, 2024
Denial of service in the Linux kernel before 5.4.7 allows local users with CAP_NET_RAW to cause a CPU soft lockup through TPACKET_V3. If __ethtool_get_link_ksettings() fails, prb_calc_retire_blk_tmo() leaves the timeout at zero and repeatedly schedules retire_blk_timer at the current jiffy, driving softirq CPU use to 100%. Triggering the failure path requires CAP_NET_RAW; successful exploitation hangs a CPU in softirq processing without reading or changing data.
Summary
What happened
Denial of service in the Linux kernel before 5.4.7 allows local users with CAP_NET_RAW to cause a CPU soft lockup through TPACKET_V3. If __ethtool_get_link_ksettings() fails, prb_calc_retire_blk_tmo() leaves the timeout at zero and repeatedly schedules retire_blk_timer at the current jiffy, driving softirq CPU use to 100%. Triggering the failure path requires CAP_NET_RAW; successful exploitation hangs a CPU in softirq processing without reading or changing data.
The record
- CVE
- CVE-2019-20812
- Published
- Jun 3, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-400, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 3, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 2024Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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