Local kernel crash via ROSE timer race
Published Jul 6, 2022 · Updated Aug 3, 2024
Use-after-free in the Linux kernel before 5.19-rc5 allows local users to crash the system through an active ROSE interface. ROSE timer teardown uses del_timer without retaining the socket, so a running expiry handler can call bh_lock_sock after rose_release frees that socket. An unprivileged local user must activate a ROSE interface and race close, bind, and connect calls; successful triggering interrupts the entire host.
Summary
What happened
Use-after-free in the Linux kernel before 5.19-rc5 allows local users to crash the system through an active ROSE interface. ROSE timer teardown uses del_timer without retaining the socket, so a running expiry handler can call bh_lock_sock after rose_release frees that socket. An unprivileged local user must activate a ROSE interface and race close, bind, and connect calls; successful triggering interrupts the entire host.
The record
- CVE
- CVE-2022-2318
- Published
- Jul 6, 2022
- Updated
- Aug 3, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-416, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 6, 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=Linux Kernel version prior to kernel 5.19 rc5
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.
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