Security readout for executives and security teams
Plain-English summary
This is a Linux kernel memory-read flaw in the UBI flash storage subsystem. A local low-privileged user could trigger an out-of-bounds read, potentially exposing kernel memory or crashing the system. It matters most for embedded or appliance-style Linux systems using UBI/MTD flash storage.
Executive priority
Treat this as high priority for embedded Linux and appliance fleets, especially where local users, containers, support accounts, or exposed management paths exist. For standard servers with no UBI/MTD usage, validate exposure before escalating operational urgency.
Technical view
The bug is a slab out-of-bounds read in UBI when VID header offset plus VID header size can exceed the allocated buffer. The trace shows crc32 processing via ubi_io_write_vid_hdr during UBI attach/ioctl handling. CVSS 7.1 rates local attack, low complexity, low privileges, high confidentiality impact, and high availability impact.
Likely exposure
Exposure is likely limited to affected Linux kernels where UBI/MTD support is present and reachable. Embedded Linux, network appliances, industrial devices, and systems using raw flash with UBI deserve priority review. General-purpose servers without UBI/MTD usage are less likely to be practically exposed.
Exploitation context
The source bundle does not show active exploitation, and KEV is false. Evidence is a KASAN/syzkaller-style crash trace and upstream stable kernel fixes. The CVSS vector indicates local access with low privileges, no user interaction, and no remote network attack path.
Researcher notes
The affected area is drivers/mtd/ubi, with bounds validation added for VID header offset plus header size against allocation size. The provided affected-version data is broad and commit-based, so researchers should rely on vendor backport status or exact stable commit presence rather than version strings alone.
Mitigation direction
Apply vendor kernel updates containing the referenced upstream stable fixes.
Prioritize Linux devices using UBI/MTD flash storage.
Check distribution or device vendor guidance for supported backports.
If immediate patching is unavailable, reduce untrusted local access to affected systems.
Do not deploy direct kernel changes without vendor validation for managed appliances.
Validation and detection
Inventory Linux kernel versions across embedded and appliance fleets.
Confirm whether UBI and MTD subsystems are enabled or used.
Map each kernel branch to vendor advisories or upstream stable fix commits.
Review local access paths to UBI control or MTD device interfaces.
Retest affected device images after kernel update or vendor firmware upgrade.
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-125: 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-125 · source CWE mapping
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.