Independent & educational platform Not a government body. No link or affiliation with any government organisation. Made for learning only. Test only systems you own or are authorised to test. Become a Partner or Sponsor → Full disclaimer

CVE-2025-39835

high

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 ver…

Vendor / product: Linux — linux kernel

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
7.8
7.8 (CVSS v3.1)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Severity source: NVD CVSS v3.1 (nvd@nist.gov)
Timeline (UTC)
Published: 2025-09-16 14:15
Modified: 2026-11-05 22:17
NVD status: Modified
Last synced 1 week ago
Verified against the source API 2026-11-05 22:23 UTC
Exploitation
Not listed in CISA KEV (as of last catalog sync)
Absence from KEV does not mean a CVE is not exploited. Exploitation status: unknown (no authoritative evidence in our sources).

Affected products

linux / linux_kernel ≥5.9 <5.10.242, ≥5.11 <5.15.191, ≥5.16 <6.1.150, ≥6.2 <6.6.104, ≥6.7 <6.12.45, ≥6.13 <6.16.5
debian / debian_linux 11.0

Weakness classification (CWE)

NVD-CWE-noinfo

Source: NVD / CISA. “NVD-CWE-Other” and “NVD-CWE-noinfo” mean NVD could not assign a specific weakness.

Mitigation & advisories

Patch / mitigation: https://git.kernel.org/stable/c/157ddfb05961c68ab7d457a462822a698e4e4bf4
Patch / mitigation: https://git.kernel.org/stable/c/39fc2742ca14f7fbc621ce9b43bcbd00248cb9a8
Patch / mitigation: https://git.kernel.org/stable/c/90bae69c2959c39912f0c2f07a9a7894f3fc49f5
Patch / mitigation: https://git.kernel.org/stable/c/ae668cd567a6a7622bc813ee0bb61c42bed61ba7
Patch / mitigation: https://git.kernel.org/stable/c/d3cc7476b89fb45b7e00874f4f56f6b928467c60
Patch / mitigation: https://git.kernel.org/stable/c/dcdf36f1b67884c722abce9b8946e34ffb9f67c8
Patch / mitigation: https://git.kernel.org/stable/c/e358d4b6225e4c1eb208686a05e360ef8df59e07

References

Data sources

NVD CVE API 2.0 — fetched 2026-11-05 22:23 UTC · record ↗

Learn the basics

Understanding CVEs and CVSS Scores

Related CVEs