CVE-2025-39835
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-09-16

Last updated on: 2025-11-03

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: xfs: do not propagate ENODATA disk errors into xattr code ENODATA (aka ENOATTR) has a very specific meaning in the xfs xattr code; namely, that the requested attribute name could not be found. However, a medium error from disk may also return ENODATA. At best, this medium error may escape to userspace as "attribute not found" when in fact it's an IO (disk) error. At worst, we may oops in xfs_attr_leaf_get() when we do: error = xfs_attr_leaf_hasname(args, &bp); if (error == -ENOATTR) { xfs_trans_brelse(args->trans, bp); return error; } because an ENODATA/ENOATTR error from disk leaves us with a null bp, and the xfs_trans_brelse will then null-deref it. As discussed on the list, we really need to modify the lower level IO functions to trap all disk errors and ensure that we don't let unique errors like this leak up into higher xfs functions - many like this should be remapped to EIO. However, this patch directly addresses a reported bug in the xattr code, and should be safe to backport to stable kernels. A larger-scope patch to handle more unique errors at lower levels can follow later. (Note, prior to 07120f1abdff we did not oops, but we did return the wrong error code to userspace.)
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-09-16
Last Modified
2025-11-03
Generated
2026-05-09
AI Q&A
2025-09-16
EPSS Evaluated
2026-05-08
NVD
CVE-2025-39835
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
linux linux_kernel 5.10.244
linux linux_kernel 6.1.153
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability in the Linux kernel's xfs filesystem code involves improper handling of disk errors represented by the ENODATA (also known as ENOATTR) error code. ENODATA is supposed to indicate that a requested extended attribute (xattr) was not found. However, disk medium errors can also return ENODATA, causing the system to mistakenly treat a disk IO error as a missing attribute. This can lead to incorrect error reporting to userspace or, worse, a kernel oops (crash) due to a null pointer dereference when the code tries to release a buffer that was never properly allocated.


How can this vulnerability impact me? :

This vulnerability can cause the system to misreport disk IO errors as missing extended attributes, potentially leading to confusion or incorrect error handling in applications relying on xattr. In the worst case, it can cause a kernel crash (oops), leading to system instability or downtime.


What immediate steps should I take to mitigate this vulnerability?

Apply the patch that addresses the xfs xattr code bug to your Linux kernel. This patch prevents propagation of ENODATA disk errors into xattr code and avoids kernel oops. Backporting this patch to stable kernels is recommended. Additionally, monitor for kernel updates that include this fix and apply them promptly.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart