System crash via zero-erasesize UBI attachment
Published Apr 24, 2023 · Updated Aug 2, 2024
Divide-by-zero in the Linux kernel 6.2 UBI driver allows local users to crash the system by attaching a zero-erasesize MTD device. During UBI device attachment, ctrl_cdev_ioctl reaches mtd_div_by_eb, which passes mtd->erasesize to do_div without rejecting a zero value. Triggering the ioctl requires CAP_SYS_RESOURCE in the initial user namespace; the demonstrated consequence is a kernel crash, not data access or code execution.
Summary
What happened
Divide-by-zero in the Linux kernel 6.2 UBI driver allows local users to crash the system by attaching a zero-erasesize MTD device. During UBI device attachment, ctrl_cdev_ioctl reaches mtd_div_by_eb, which passes mtd->erasesize to do_div without rejecting a zero value. Triggering the ioctl requires CAP_SYS_RESOURCE in the initial user namespace; the demonstrated consequence is a kernel crash, not data access or code execution.
The record
- CVE
- CVE-2023-31085
- Published
- Apr 24, 2023
- Updated
- Aug 2, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-369, T1499.004
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Apr 24, 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.
Public exploit references
- Syzkaller UBI attachment crash reportproof of concept · 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