Local system crash via incomplete XFRM flush
Published Jun 7, 2021 · Updated Aug 5, 2024
Use-after-free in the Linux kernel XFRM subsystem before 5.0.19 allows local users to crash the system during network namespace teardown. xfrm_state_flush treats IPSEC_PROTO_ANY as matching only three IPsec protocols, so IPPROTO_ROUTING entries remain in net->xfrm.state_all when a network namespace exits. Low-privileged local access is required, and the stale XFRM state reaches xfrm_state_fini during cleanup, causing a kernel panic and system reboot.
Summary
What happened
Use-after-free in the Linux kernel XFRM subsystem before 5.0.19 allows local users to crash the system during network namespace teardown. xfrm_state_flush treats IPSEC_PROTO_ANY as matching only three IPsec protocols, so IPPROTO_ROUTING entries remain in net->xfrm.state_all when a network namespace exits. Low-privileged local access is required, and the stale XFRM state reaches xfrm_state_fini during cleanup, causing a kernel panic and system reboot.
The record
- CVE
- CVE-2019-25045
- Published
- Jun 7, 2021
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 7, 2021CVE 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
- syzkaller C reproducer for xfrm_state_fini panicproof of concept · demonstrated
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