ceph: bound xattr value length in __build_xattrs()
Summary
| CVE | CVE-2026-89649 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-09-11 20:19:50 UTC |
| Updated | 2026-09-11 20:19:50 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved: ceph: bound xattr value length in __build_xattrs() __build_xattrs() decodes the MDS-supplied xattr blob one attribute at a time. For each attribute it reads a 32-bit name length, advances past the name bytes, reads a 32-bit value length, records the value pointer, and advances past the value bytes. The two length fields are read with ceph_decode_32_safe(), but the value bytes themselves are advanced over with a bare "p += len" and no ceph_decode_need() check that "len" bytes remain in the blob. For every attribute except the last, the next iteration's ceph_decode_32_safe() on the following name length implicitly verifies that the previous value did not run past the blob end. The final attribute has no successor, so its decoded value length is never checked against the blob bounds. A malicious or compromised metadata server can set the last attribute's value length larger than the bytes actually present in the blob. The blob is a dedicated kvmalloc() allocation sized to the wire length (ceph_buffer_new() in ceph_fill_inode()). __set_xattr() records the oversized length in xattr->val_len verbatim, and a later getxattr(2) runs memcpy(value, xattr->val, xattr->val_len) into a user-supplied buffer, copying bytes past the end of the allocation back to user space. Impact: a malicious metadata server discloses adjacent kernel heap bytes to a local user via getxattr(2) on a CephFS file. Add the missing ceph_decode_need() so an out-of-bounds value length on the final attribute fails the decode and returns -EIO instead of being stored. |
Risk And Classification
EPSS: 0.001910000 probability, percentile 0.088850000 (date 2026-09-12)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 355da1eb7a1f91c276b991764e951bbcd8047599 38be2f3c41ecaba58bb92dc16603e09ba9fd64f1 git | Not specified |
| CNA | Linux | Linux | affected 355da1eb7a1f91c276b991764e951bbcd8047599 1dd356310b1660215f9a3626580bf8b363ef981e git | Not specified |
| CNA | Linux | Linux | affected 355da1eb7a1f91c276b991764e951bbcd8047599 b12b3320c81fd72ab36388fb2445fec9c3038f10 git | Not specified |
| CNA | Linux | Linux | affected 355da1eb7a1f91c276b991764e951bbcd8047599 68d541754d6cd3bb98d1fd8314f57e5eb533557d git | Not specified |
| CNA | Linux | Linux | affected 2.6.34 | Not specified |
| CNA | Linux | Linux | unaffected 2.6.34 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.109 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.50 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2.4 7.2.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.3-rc1 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/1dd356310b1660215f9a3626580bf8b363ef981e | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/68d541754d6cd3bb98d1fd8314f57e5eb533557d | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/b12b3320c81fd72ab36388fb2445fec9c3038f10 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/38be2f3c41ecaba58bb92dc16603e09ba9fd64f1 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.