Local denial of service via leaked kobject name
Published Feb 12, 2024 · Updated May 7, 2025
Memory leak in the UBI driver in Linux kernel 6.7.4 and earlier allows local users to exhaust memory through UBI_IOCATT. During failed sysfs slab-cache creation in ubi_attach, sysfs_slab_add returns without dropping the initialized kobject reference, leaving kobj->name allocated. Repeated attach operations require local access to the UBI control device and can consume unreclaimable kernel memory until service is interrupted.
Summary
What happened
Memory leak in the UBI driver in Linux kernel 6.7.4 and earlier allows local users to exhaust memory through UBI_IOCATT. During failed sysfs slab-cache creation in ubi_attach, sysfs_slab_add returns without dropping the initialized kobject reference, leaving kobj->name allocated. Repeated attach operations require local access to the UBI control device and can consume unreclaimable kernel memory until service is interrupted.
The record
- CVE
- CVE-2024-25740
- Published
- Feb 12, 2024
- Updated
- May 7, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1499.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 12, 2024CVE publishedPublication date reported by the CVE source.
- May 7, 2025Record 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
- ubi_attach Syzkaller and C reproducersproof 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