CVE-2025-68820: ext4: xattr: fix null pointer deref in ext4_raw_inode()
In the Linux kernel, the following vulnerability has been resolved:
ext4: xattr: fix null pointer deref in ext4_raw_inode()
If ext4_get_inode_loc() fails (e.g. if it returns -EFSCORRUPTED),
iloc.bh will remain set to NULL. Since ext4_xattr_inode_dec_ref_all()
lacks error checking, this will lead to a null pointer dereference
in ext4_raw_inode(), called right after ext4_get_inode_loc().
Found by Linux Verification Center (linuxtesting.org) with SVACE.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can crash kernel code handling ext4 extended attributes when an inode lookup fails and a NULL buffer is used. The public record does not provide a CVSS score or confirmed attack path. Treat it primarily as a possible stability and denial-of-service risk for systems using ext4.
Executive priority
Handle through normal but timely kernel maintenance unless ext4-backed systems process untrusted storage or support critical uptime. The current public evidence supports remediation, but not emergency response for known exploitation.
Technical view
The flaw is a NULL pointer dereference in ext4_raw_inode() after ext4_get_inode_loc() fails, leaving iloc.bh NULL. ext4_xattr_inode_dec_ref_all() lacked error checking before the subsequent call. The issue was resolved in Linux stable commits referenced by the CVE record.
Likely exposure
Exposure is most relevant to Linux systems using ext4 filesystems, especially kernels in the affected version ranges listed by the CVE record. Product-specific exposure needs vendor confirmation, including Siemens environments referencing SSA-019113.
Exploitation context
The bundle provides no evidence of active exploitation, and KEV status is false. It also does not confirm remote exploitation, privilege escalation, or a public exploit. The likely impact from the described bug is kernel crash or denial of service under error conditions.
Researcher notes
The core condition is ext4_get_inode_loc() returning an error such as -EFSCORRUPTED while callers continue with iloc.bh unset. Public data identifies stable fixes but omits CVSS, CWE, and exploitability details, so validation should stay focused on version and patch provenance.
Mitigation direction
Apply vendor-supported kernel updates containing the referenced ext4 stable fixes.
Check Linux distribution advisories for backported fixes and exact package versions.
Review Siemens SSA-019113 if operating Siemens products or managed environments.
Restrict use of untrusted removable media or filesystem images until patched.
Prioritize hosts where ext4-backed availability is business-critical.
Validation and detection
Inventory Linux kernel versions and ext4 usage across servers and appliances.
Compare installed kernels against vendor advisories and CVE affected-version data.
Confirm distribution kernel changelogs include the referenced ext4 xattr fix.
Check Siemens advisory applicability for affected product deployments.
Monitor for kernel oops or panic events involving ext4_raw_inode or ext4 xattrs.
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-68820 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.