Kernel memory corruption via premature cache identifier assignment
Published Oct 17, 2022 · Updated Apr 15, 2025
Use-after-free in the Linux kernel NFP driver before 6.0 allows local users to corrupt kernel memory through failed area setup. area_cache_get assigns cache->id before area_init or area acquisition succeeds, so a failure leaves a zero-refcount area eligible for release and later reuse. Reachability requires the Netronome Flow Processor driver and local low-privileged access; public sources identify no reliable trigger or demonstrated code execution.
Summary
What happened
Use-after-free in the Linux kernel NFP driver before 6.0 allows local users to corrupt kernel memory through failed area setup. area_cache_get assigns cache->id before area_init or area acquisition succeeds, so a failure leaves a zero-refcount area eligible for release and later reuse. Reachability requires the Netronome Flow Processor driver and local low-privileged access; public sources identify no reliable trigger or demonstrated code execution.
The record
- CVE
- CVE-2022-3545
- Published
- Oct 17, 2022
- Updated
- Apr 15, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-119, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 17, 2022CVE publishedPublication date reported by the CVE source.
- Apr 15, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=n/a
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
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