Kernel memory disclosure or corruption via XFRM race
Published Aug 31, 2022 · Updated Aug 3, 2024
Race condition in the Linux kernel XFRM subsystem before 6.0-rc3 allows local users to read kernel heap memory or corrupt it. The PF_KEY registration path calls xfrm_probe_algs concurrently, so unsynchronized updates to algorithm availability lists permit out-of-bounds reads and writes. A local low-privileged user must race concurrent PF_KEY registration requests; success exposes kernel data or corrupts kernel memory.
Summary
What happened
Race condition in the Linux kernel XFRM subsystem before 6.0-rc3 allows local users to read kernel heap memory or corrupt it. The PF_KEY registration path calls xfrm_probe_algs concurrently, so unsynchronized updates to algorithm availability lists permit out-of-bounds reads and writes. A local low-privileged user must race concurrent PF_KEY registration requests; success exposes kernel data or corrupts kernel memory.
The record
- CVE
- CVE-2022-3028
- Published
- Aug 31, 2022
- Updated
- Aug 3, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 31, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Fixed in kernel 6.0-rc3
What conditions does exploitation require?
What is affected?
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
No sourced classifications are available.
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