Answer in brief
CVE-2025-39835 records a High severity (CVSS 7.8) vulnerability in xfs: do not propagate ENODATA disk errors into xattr code. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC CN 4100 (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC CN 4100 (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.17:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.17:rc2:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.17:rc3:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=07120f1abdff80f3d1351f733661abe28d609535 <157ddfb05961c68ab7d457a462822a698e4e4bf4 || >=07120f1abdff80f3d1351f733661abe28d609535 <90bae69c2959c39912f0c2f07a9a7894f3fc49f5 || >=07120f1abdff80f3d1351f733661abe28d609535 <e358d4b6225e4c1eb208686a05e360ef8df59e07 || >=07120f1abdff80f3d1351f733661abe28d609535 <d3cc7476b89fb45b7e00874f4f56f6b928467c60 || >=07120f1abdff80f3d1351f733661abe28d609535 <dcdf36f1b67884c722abce9b8946e34ffb9f67c8 || >=07120f1abdff80f3d1351f733661abe28d609535 <39fc2742ca14f7fbc621ce9b43bcbd00248cb9a8 || >=07120f1abdff80f3d1351f733661abe28d609535 <ae668cd567a6a7622bc813ee0bb61c42bed61ba7 | 157ddfb05961c68ab7d457a462822a698e4e4bf4, 90bae69c2959c39912f0c2f07a9a7894f3fc49f5, e358d4b6225e4c1eb208686a05e360ef8df59e07, d3cc7476b89fb45b7e00874f4f56f6b928467c60, dcdf36f1b67884c722abce9b8946e34ffb9f67c8, 39fc2742ca14f7fbc621ce9b43bcbd00248cb9a8, ae668cd567a6a7622bc813ee0bb61c42bed61ba7 |
| Linux/Linuxgeneric | 5.9 | Not reported |
| Siemens/SIMATIC CN 4100generic | >=0 <V5.0 | V5.0 |
Published upstream
Sep 16, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 28, 2026
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.)
Quoted source text, attributed separately from HOL analysis.