Local privilege escalation via unchecked MTU-derived lmax
Published Apr 28, 2023 · Updated Oct 21, 2024
Out-of-bounds write in the Linux kernel before 6.2.13 allows local users to crash the system or gain elevated privileges. When TCA_QFQ_LMAX is absent, qfq_change_class uses the device MTU as lmax without applying the explicit-input bounds check, producing an index above QFQ_MAX_INDEX. Exploitation requires local low-privileged access and the ability to configure QFQ; successful abuse can crash the host or execute code with kernel privileges.
Summary
What happened
Out-of-bounds write in the Linux kernel before 6.2.13 allows local users to crash the system or gain elevated privileges. When TCA_QFQ_LMAX is absent, qfq_change_class uses the device MTU as lmax without applying the explicit-input bounds check, producing an index above QFQ_MAX_INDEX. Exploitation requires local low-privileged access and the ability to configure QFQ; successful abuse can crash the host or execute code with kernel privileges.
The record
- CVE
- CVE-2023-31436
- Published
- Apr 28, 2023
- Updated
- Oct 21, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 28, 2023CVE publishedPublication date reported by the CVE source.
- Oct 21, 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.
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