System crash via duplicate rpmsg_probe cleanup
Published Jun 26, 2022 · Updated Aug 3, 2024
Double free in the Linux kernel before 5.18.4 allows local users to crash the system through a virtio RPMSG device probe failure. In rpmsg_probe, failure of rpmsg_ns_register_device invokes virtio_rpmsg_release_device to free vch, then the error path calls kfree on the same allocation again. A local low-privileged user must trigger the registration-error path; the documented consequence is a system crash, with no confidentiality or integrity impact.
Summary
What happened
Double free in the Linux kernel before 5.18.4 allows local users to crash the system through a virtio RPMSG device probe failure. In rpmsg_probe, failure of rpmsg_ns_register_device invokes virtio_rpmsg_release_device to free vch, then the error path calls kfree on the same allocation again. A local low-privileged user must trigger the registration-error path; the documented consequence is a system crash, with no confidentiality or integrity impact.
The record
- CVE
- CVE-2022-34495
- Published
- Jun 26, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-415, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 26, 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