CVE-2024-25739: create_empty_lvol in drivers/mtd/ubi/vtbl.c in the Linux kernel through 6.7.4 can attempt to allocate zero...
create_empty_lvol in drivers/mtd/ubi/vtbl.c in the Linux kernel through 6.7.4 can attempt to allocate zero bytes, and crash, because of a missing check for ubi->leb_size.
Security readout for executives and security teams
Plain-English summary
CVE-2024-25739 is a Linux kernel crash bug in the UBI flash storage code. A local user with low privileges may be able to trigger a denial of service. The sources do not show data theft, integrity impact, or active exploitation.
Executive priority
Treat as a targeted availability risk, not an internet-scale emergency based on supplied evidence. Patch during normal kernel maintenance, but elevate embedded, industrial, or appliance systems where local crashes can interrupt operations.
Technical view
In drivers/mtd/ubi/vtbl.c, create_empty_lvol lacks a check for ubi->leb_size. On Linux kernels through 6.7.4, this can lead to a zero-byte allocation attempt and crash. CVSS 3.1 is 5.5: local attack vector, low complexity, low privileges, availability impact only.
Likely exposure
Most exposed assets are Linux systems using the MTD/UBI flash subsystem, especially embedded or appliance-style deployments. General servers without UBI/MTD usage may have lower practical exposure, but kernel package provenance still matters.
Exploitation context
The CVE is not listed as KEV in the supplied bundle, and no cited source states active exploitation. The reported attack path is local with low privileges and no user interaction, with impact limited to availability.
Researcher notes
The evidence points to CWE-754 insufficient exceptional-condition handling in UBI volume table logic. Public references include the syzkaller report, kernel mailing list discussion, upstream commit, stable backport, Debian advisories, and Siemens advisory. Affected product metadata in the CVE bundle is incomplete.
Mitigation direction
Update affected Linux kernels through the relevant vendor or distribution channel.
Prioritize kernels that include upstream commit 68a24aba7c593eafa8fd00f2f76407b9b32b47a9 or matching stable fixes.
Apply Debian LTS kernel updates where Debian advisories apply.
For embedded or industrial products, check vendor advisories such as Siemens SSA-265688.
Limit unnecessary local shell or application access on systems using UBI/MTD.
Validation and detection
Inventory Linux kernel versions and identify systems at or below 6.7.4.
Confirm whether MTD/UBI support is enabled and used on each asset.
Verify vendor packages or source trees include the referenced kernel fix.
Check Debian DLA coverage for Debian-based systems.
Review product vendor advisories for embedded appliances before assuming coverage.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-754: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-754 · source CWE mapping
Improper Check for Unusual or Exceptional Conditions
Improper Check for Unusual or Exceptional Conditions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.