ocfs2: fix missing metadata reservation for large xattrs
Published Sep 4, 2026
No CVSS score
EPSS 0.24%
Description
[BUG] lsetxattr() panics the kernel when setting a large xattr value on a fragmented filesystem where the file already has an external xattr block.
[CAUSE] ocfs2_calc_xattr_set_need() never reserves metadata blocks for a new xattr value's extent tree when the file already has an external xattr block. The not_found path leaves meta_add at zero, so meta_ac is NULL when ocfs2_xattr_extend_allocation() runs.
A new value root has room for a single extent record. On a fragmented filesystem, the allocator cannot satisfy the xattr value in one contiguous run, so each non-contiguous run requires its own extent record. When the value root's extent list is full and meta_ac is NULL, ocfs2_add_clusters_in_btree() returns RESTART_META, and ocfs2_xattr_extend_allocation() hits BUG_ON(why == RESTART_META).
[FIX] The case where no xattr block exists yet already calls ocfs2_extend_meta_needed(&def_xv.xv.xr_list) to reserve value tree metadata. Add the same reservation to the case where an xattr block already exists, making the two cases consistent.
Replace the BUG_ON with a -ENOSPC return so that if RESTART_META is returned despite the reservation, the error propagates to userspace instead of panicking the kernel.
Affected products
-
- Version 2.6.34.2StatusaffectedConstraints<2.6.35
- Version
-
- Version StatusaffectedConstraints-
- Version StatusaffectedConstraints
- Version StatusaffectedConstraints
- Version StatusaffectedConstraints
- Version StatusaffectedConstraints
- Version StatusaffectedConstraints
- Version StatusaffectedConstraints
- Version StatusaffectedConstraints
- Version StatusaffectedConstraints
- Version StatusaffectedConstraints
- Version
-
- Version 2.6.35StatusaffectedConstraints-
- Version 0StatusunaffectedConstraints<2.6.35
- Version 5.10.267StatusunaffectedConstraints<=5.10.*
- Version 5.15.218StatusunaffectedConstraints<=5.15.*
- Version 6.1.185StatusunaffectedConstraints<=6.1.*
- Version 6.12.106StatusunaffectedConstraints<=6.12.*
- Version 6.18.47StatusunaffectedConstraints<=6.18.*
- Version 6.6.154StatusunaffectedConstraints<=6.6.*
- Version 7.1.11StatusunaffectedConstraints<=7.1.*
- Version 7.2.1StatusunaffectedConstraints<=7.2.*
- Version 7.3-rc1StatusunaffectedConstraints<=*
- Version
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Linux | Linux | unaffected |
| ||||||||||||||||||||||||||||||||||||
| Linux | Linux | unaffected |
| ||||||||||||||||||||||||||||||||||||
| Linux | Linux | affected |
|
No data.
No data.
No Red Hat product state for this CVE.
No package ranges for this CVE.
Remediation
No remediation recorded yet.
No CWE recorded.
References (10)
- https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-71244 Advisory
- https://git.kernel.org/stable/c/04ba24bce61c917b5b3009f0db470cbb72e26a0d
- https://git.kernel.org/stable/c/0cdc7dde00ec63ac714271fa8b2918d630b8da1a
- https://git.kernel.org/stable/c/50f0cbec45b0f3fd7e1263d01916518dbf31eb3f
- https://git.kernel.org/stable/c/6176313622e34fa3e2b66b9d0682d1e1c6b365c5
- https://git.kernel.org/stable/c/6a009f1e61b11d9e23d3c5aa1dacfb010945da45
- https://git.kernel.org/stable/c/743ac908282ac97ef6e73ac3a92df2cc8ecb7479
- https://git.kernel.org/stable/c/a3ccb57086dd7652d5ecb826486144198a98a8e9
- https://git.kernel.org/stable/c/b4663405ae29d36011cd712d243456f3f9ab700d
- https://git.kernel.org/stable/c/b9eb5c9fdd81d82976d4d5be2b2458eb7d7e46ec
Change history (0)
No recorded changes yet.