Local system crash via qdisc replacement race
Published Mar 23, 2023 · Updated Aug 2, 2024
Use-after-free in qdisc_graft in Linux Kernel before 6.1-rc2 allows local users to crash the system through concurrent qdisc changes. The function releases the old queueing discipline through notify_and_destroy while dev->qdisc still points to it, starting an RCU grace period before replacing the visible pointer. A low-privileged local user must win the race through rtnetlink traffic-control operations; the grounded consequence is a kernel crash.
Summary
What happened
Use-after-free in qdisc_graft in Linux Kernel before 6.1-rc2 allows local users to crash the system through concurrent qdisc changes. The function releases the old queueing discipline through notify_and_destroy while dev->qdisc still points to it, starting an RCU grace period before replacing the visible pointer. A low-privileged local user must win the race through rtnetlink traffic-control operations; the grounded consequence is a kernel crash.
The record
- CVE
- CVE-2023-0590
- Published
- Mar 23, 2023
- Updated
- Aug 2, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-416, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 23, 2023CVE 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=Linux kernel 6.1-rc2
What conditions does exploitation require?
What is affected?
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