Local system crash via double policy release
Published Jul 27, 2022 · Updated May 5, 2025
A reference-counting error in Linux kernel 5.18.14 and earlier allows local users to crash the system through XFRM policy handling. When xfrm_expand_policies returns an error after releasing pols[0], xfrm_bundle_lookup retains num_pols as 1 and releases the same policy again. Low-privileged local access is required, and the reported consequence is a system crash rather than data disclosure or modification.
Summary
What happened
A reference-counting error in Linux kernel 5.18.14 and earlier allows local users to crash the system through XFRM policy handling. When xfrm_expand_policies returns an error after releasing pols[0], xfrm_bundle_lookup retains num_pols as 1 and releases the same policy again. Low-privileged local access is required, and the reported consequence is a system crash rather than data disclosure or modification.
The record
- CVE
- CVE-2022-36879
- Published
- Jul 27, 2022
- Updated
- May 5, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 27, 2022CVE publishedPublication date reported by the CVE source.
- May 5, 2025Record 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