Kernel crash via unlocked ROSE neighbour reference
Published Aug 31, 2022 · Updated Aug 2, 2024
Use-after-free in the Linux Kernel ROSE networking driver allows local users to crash the kernel by racing route deletion with connection setup. rose_connect increments rose_neigh->use without rose_neigh_list_lock, while rose_del_node can observe zero use and free the same neighbour. Low-privileged local access plus the AF_ROSE driver is required; the published proof demonstrates a use-after-free and kernel crash.
Summary
What happened
Use-after-free in the Linux Kernel ROSE networking driver allows local users to crash the kernel by racing route deletion with connection setup. rose_connect increments rose_neigh->use without rose_neigh_list_lock, while rose_del_node can observe zero use and free the same neighbour. Low-privileged local access plus the AF_ROSE driver is required; the published proof demonstrates a use-after-free and kernel crash.
The record
- CVE
- CVE-2022-1247
- Published
- Aug 31, 2022
- Updated
- Aug 2, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-366, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 31, 2022CVE publishedPublication date reported by the CVE source.
- Aug 2, 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=Not-Known
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