Root-only kernel memory corruption via kobject path race
Published Oct 14, 2023 · Updated Aug 2, 2024
An out-of-bounds write in Linux kernel lib/kobject.c before 6.2.3 allows local users with root access to corrupt kernel memory. A race can lengthen a kobject name after kobject_get_path allocates the path buffer, so fill_kobj_path subtracts the longer length and copies before the buffer boundary. Reaching the write requires root privileges and concurrent device activity; published evidence demonstrates invalid kernel memory access but no privilege-boundary bypass.
Summary
What happened
An out-of-bounds write in Linux kernel lib/kobject.c before 6.2.3 allows local users with root access to corrupt kernel memory. A race can lengthen a kobject name after kobject_get_path allocates the path buffer, so fill_kobj_path subtracts the longer length and copies before the buffer boundary. Reaching the write requires root privileges and concurrent device activity; published evidence demonstrates invalid kernel memory access but no privilege-boundary bypass.
The record
- CVE
- CVE-2023-45863
- Published
- Oct 14, 2023
- Updated
- Aug 2, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Oct 14, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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