CVE-2026-80809

ocfs2: fix missing metadata reservation for large xattrs

N/A
Published: September 4, 2026 at 03:13 PM UTC
Updated: October 19, 2026 at 09:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix missing metadata reservation for large xattrs [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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.34.22.6.3592f61d8a31e270f9391e7bcc0ac638bd4262a8e0a78f9f4668949a6588b8872f162e86685c63d023
Vendor states this is fixed in 04ba24bce61c917b5b3009f0db470cbb72e26a0d (fixed)
Vendor states this is fixed in 0cdc7dde00ec63ac714271fa8b2918d630b8da1a (fixed)
Vendor states this is fixed in 50f0cbec45b0f3fd7e1263d01916518dbf31eb3f (fixed)
Vendor states this is fixed in 6176313622e34fa3e2b66b9d0682d1e1c6b365c5 (fixed)
Vendor states this is fixed in 6a009f1e61b11d9e23d3c5aa1dacfb010945da45 (fixed)
Vendor states this is fixed in 743ac908282ac97ef6e73ac3a92df2cc8ecb7479 (fixed)
Vendor states this is fixed in a3ccb57086dd7652d5ecb826486144198a98a8e9 (fixed)
Vendor states this is fixed in b4663405ae29d36011cd712d243456f3f9ab700d (fixed)
Vendor states this is fixed in b9eb5c9fdd81d82976d4d5be2b2458eb7d7e46ec (fixed)
Vendor states this is fixed in 2.6.35 (unaffected)
Vendor states this is fixed in 5.10.267 (unaffected)
Vendor states this is fixed in 5.15.218 (unaffected)
Vendor states this is fixed in 6.1.185 (unaffected)
Vendor states this is fixed in 6.12.106 (unaffected)
Vendor states this is fixed in 6.18.47 (unaffected)
Vendor states this is fixed in 6.6.154 (unaffected)
Vendor states this is fixed in 7.1.11 (unaffected)
Vendor states this is fixed in 7.2.1 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card