Process crash via unchecked CPU-set allocation
Published Aug 22, 2023 · Updated Oct 3, 2024
Null pointer dereference in Open MPI hwloc 2.1.0 through 2.9.2 allows local users to crash a process during CPU binding. Linux binding routines pass the unchecked result of CPU_ALLOC to CPU_ZERO_S, dereferencing a null glibc CPU-set pointer after allocation failure. Triggering the crash requires local access to an affected binding operation and an allocation failure; no data disclosure or modification is reported.
Summary
What happened
Null pointer dereference in Open MPI hwloc 2.1.0 through 2.9.2 allows local users to crash a process during CPU binding. Linux binding routines pass the unchecked result of CPU_ALLOC to CPU_ZERO_S, dereferencing a null glibc CPU-set pointer after allocation failure. Triggering the crash requires local access to an affected binding operation and an allocation failure; no data disclosure or modification is reported.
The record
- CVE
- CVE-2022-47022
- Published
- Aug 22, 2023
- Updated
- Oct 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 22, 2023CVE publishedPublication date reported by the CVE source.
- Oct 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
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