VYPR
Unrated severityNVD Advisory· Published Jan 13, 2026· Updated Apr 15, 2026

CVE-2025-68820

CVE-2025-68820

Description

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.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

A null pointer dereference in ext4_xattr_inode_dec_ref_all() can crash the Linux kernel when ext4_get_inode_loc() fails on corrupted filesystems.

Vulnerability

Overview

In the Linux kernel's ext4 filesystem driver, the function ext4_xattr_inode_dec_ref_all() calls ext4_get_inode_loc() to obtain the inode buffer head. If that call fails (e.g., due to filesystem corruption returning -EFSCORRUPTED), the buffer head pointer iloc.bh remains NULL. The code then proceeds to call ext4_raw_inode() without checking for this failure, which dereferences the NULL pointer, causing a kernel crash (denial of service) [1].

Attack

Vector and Prerequisites

The vulnerability is triggered by attempting to access extended attributes on a corrupted ext4 filesystem. No special privileges are required beyond mounting and accessing the filesystem; an attacker who can induce or exploit filesystem corruption (e.g., via physical access, compromised storage, or a crafted image) can cause the kernel to panic [1]. The issue was discovered by the Linux Verification Center using the SVACE static analysis tool [2].

Impact

A successful exploit leads to a null pointer dereference in kernel space, resulting in a system crash (denial of service). There is no indication of memory corruption or privilege escalation. The impact is limited to availability, as the attacker cannot execute arbitrary code or bypass security boundaries [1].

Mitigation

Status

The fix has been applied to the stable kernel trees, as shown in commits [1], [2], and [3]. Users should update their kernels to versions containing this patch (e.g., later releases of the 5.x and 6.x series). No workaround is available other than avoiding access to corrupted ext4 filesystems or applying the kernel update [1].

AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

1

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

7

News mentions

0

No linked articles in our index yet.