System crash via repeated RTRS client free
Published Apr 13, 2022 · Updated Aug 3, 2024
A double free in the Linux kernel RTRS client before 5.16.12 allows local users to crash the system during error handling. The alloc_clt error path directly frees the client object after put_device invokes rtrs_clt_dev_release, which already frees the same allocation. Exploitation requires low-privileged local access and an RTRS client allocation failure, with a system crash as the documented consequence.
Summary
What happened
A double free in the Linux kernel RTRS client before 5.16.12 allows local users to crash the system during error handling. The alloc_clt error path directly frees the client object after put_device invokes rtrs_clt_dev_release, which already frees the same allocation. Exploitation requires low-privileged local access and an RTRS client allocation failure, with a system crash as the documented consequence.
The record
- CVE
- CVE-2022-29156
- Published
- Apr 13, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-415, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 13, 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?
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.
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