CVE-2025-22079: ocfs2: validate l_tree_depth to avoid out-of-bounds access
In the Linux kernel, the following vulnerability has been resolved:
ocfs2: validate l_tree_depth to avoid out-of-bounds access
The l_tree_depth field is 16-bit (__le16), but the actual maximum depth is
limited to OCFS2_MAX_PATH_DEPTH.
Add a check to prevent out-of-bounds access if l_tree_depth has an invalid
value, which may occur when reading from a corrupted mounted disk [1].
Security readout for executives and security teams
Plain-English summary
A flaw in Linux’s OCFS2 filesystem handling can let malformed metadata from a corrupted mounted disk cause kernel memory access outside expected bounds. A successful trigger could affect system confidentiality, integrity, or availability. Risk is concentrated on Linux systems using OCFS2, not ordinary network exposure.
Executive priority
Prioritize prompt remediation on production, clustered-storage, or sensitive hosts using OCFS2. Treat non-OCFS2 systems as lower priority after confirming the filesystem is neither mounted nor operationally available. Coordinate kernel updates through normal maintenance and reboot procedures.
Technical view
OCFS2 accepted the 16-bit l_tree_depth value without ensuring it stayed within OCFS2_MAX_PATH_DEPTH. Invalid on-disk metadata could therefore cause out-of-bounds kernel access. The supplied CVSS 3.1 assessment is 7.8, with a local, low-complexity, low-privilege vector requiring no user interaction.
Likely exposure
Exposure is most likely where affected Linux kernels mount OCFS2 filesystems, particularly disks or images that may be corrupted or untrusted. Systems not using OCFS2 are unlikely to expose the vulnerable path. The supplied version list is broad, so distribution-specific package status should determine applicability.
Exploitation context
The source bundle does not identify active exploitation, and the CVE is not listed as KEV. It also provides no evidence of a public exploit. The issue requires local interaction with a mounted OCFS2 filesystem rather than direct remote network access.
Researcher notes
The correction validates l_tree_depth before path traversal. Assess backported fixes by package changelog or commit inclusion rather than version strings alone. The supplied affected data contains broad version entries and repeated commit identifiers, limiting precise branch-level conclusions without distribution guidance.
Mitigation direction
Inventory Linux hosts that load or mount OCFS2 filesystems.
Apply the distribution kernel update containing the applicable upstream stable validation fix.
Until patched, avoid mounting untrusted or suspected-corrupt OCFS2 disks and images.
Restrict local access and filesystem mount administration on affected hosts.
Validation and detection
Confirm whether OCFS2 is enabled, loaded, or mounted on each Linux host.
Compare the running kernel package against vendor advisories and the cited stable fixes.
Verify the patched kernel is running after reboot, not merely installed.
Review kernel logs for OCFS2 errors or crashes associated with corrupted media.
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.
cve · low confidence lookup
CVE-2025-22079 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
1CVSS vectors
3Timeline events
1ADP providers
12Source links
CVSS vector scores
1 official score
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.