Kernel memory corruption via empty RT queue
Published Mar 27, 2023 · Updated Aug 2, 2024
Type confusion in the Linux kernel RT scheduler allows local users to corrupt kernel memory through an empty real-time run queue. pick_next_rt_entity() applies list_entry() to an empty scheduler queue, receives its list_head rather than NULL, and treats it as a sched_rt_entity. A local low-privileged process must reach the high-complexity scheduler state; successful corruption affects kernel-level confidentiality, integrity, and availability.
Summary
What happened
Type confusion in the Linux kernel RT scheduler allows local users to corrupt kernel memory through an empty real-time run queue. pick_next_rt_entity() applies list_entry() to an empty scheduler queue, receives its list_head rather than NULL, and treats it as a sched_rt_entity. A local low-privileged process must reach the high-complexity scheduler state; successful corruption affects kernel-level confidentiality, integrity, and availability.
The record
- CVE
- CVE-2023-1077
- Published
- Mar 27, 2023
- Updated
- Aug 2, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-843, T1068
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Mar 27, 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=unknown
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.
Weakness, pattern, technique
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