Local privilege escalation via unchecked waitid pointer
Published Nov 2, 2021 · Updated Aug 5, 2024
Improper input validation in Linux kernel 4.13 through 4.13.6 allows local users to gain root privileges through waitid(). The waitid() handlers pass an unchecked infop pointer to unsafe_put_user(), allowing result fields to be written into kernel memory. A local process, including one confined by a seccomp sandbox that permits waitid(), can corrupt kernel memory, crash the host, or escape the sandbox with root privileges.
Summary
What happened
Improper input validation in Linux kernel 4.13 through 4.13.6 allows local users to gain root privileges through waitid(). The waitid() handlers pass an unchecked infop pointer to unsafe_put_user(), allowing result fields to be written into kernel memory. A local process, including one confined by a seccomp sandbox that permits waitid(), can corrupt kernel memory, crash the host, or escape the sandbox with root privileges.
The record
- CVE
- CVE-2017-5123
- Published
- Nov 2, 2021
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-20, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 2, 2021CVE publishedPublication date reported by the CVE source.
- Aug 5, 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.
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
- waitid() SMEP/SMAP and Chrome sandbox exploitfunctional · demonstrated
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