ocfs2: fix missing metadata reservation for large xattrs
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
- Fixed version: Linux Linux 04ba24bce61c917b5b3009f0db470cbb72e26a0d, 0cdc7dde00ec63ac714271fa8b2918d630b8da1a, 2.6.35.
Low priority for now. Upgrade to Linux Linux 04ba24bce61c917b5b3009f0db470cbb72e26a0d, 0cdc7dde00ec63ac714271fa8b2918d630b8da1a, 2.6.35 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 4, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 8th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 92f61d8a31e270f9391e7bcc0ac638bd4262a8e0, 2.6.35affected
- a78f9f4668949a6588b8872f162e86685c63d023 and later · before 743ac908282ac97ef6e73ac3a92df2cc8ecb7479affected · git
- a78f9f4668949a6588b8872f162e86685c63d023 and later · before 04ba24bce61c917b5b3009f0db470cbb72e26a0daffected · git
- a78f9f4668949a6588b8872f162e86685c63d023 and later · before b4663405ae29d36011cd712d243456f3f9ab700daffected · git
- a78f9f4668949a6588b8872f162e86685c63d023 and later · before 6a009f1e61b11d9e23d3c5aa1dacfb010945da45affected · git
- a78f9f4668949a6588b8872f162e86685c63d023 and later · before b9eb5c9fdd81d82976d4d5be2b2458eb7d7e46ecaffected · git
- a78f9f4668949a6588b8872f162e86685c63d023 and later · before 6176313622e34fa3e2b66b9d0682d1e1c6b365c5affected · git
- a78f9f4668949a6588b8872f162e86685c63d023 and later · before a3ccb57086dd7652d5ecb826486144198a98a8e9affected · git
- a78f9f4668949a6588b8872f162e86685c63d023 and later · before 50f0cbec45b0f3fd7e1263d01916518dbf31eb3faffected · git
- a78f9f4668949a6588b8872f162e86685c63d023 and later · before 0cdc7dde00ec63ac714271fa8b2918d630b8da1aaffected · git
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.107-1~deb12u1 | 6.12.107-1~deb12u1 |
| Debian:13 | linux | before 6.12.107-1 | 6.12.107-1 |
| Debian:14 | linux | before 7.1.12-1 | 7.1.12-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-80807Sep 4, 2026 · nilfs2: reject invalid block index in GC ioctl0Monitor
- ← EarlierCVE-2026-80808Sep 4, 2026 · ext4: stop retrying saturated xattr cache entries0Monitor
- Later →CVE-2026-80810Sep 4, 2026 · io_uring/rsrc: fix folio size overflow in io_vec_fill_bvec()0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 04ba24bce61c917b5b3009f0db470cbb72e26a0d | Vendor (CNA) |
| Linux Linux | 0cdc7dde00ec63ac714271fa8b2918d630b8da1a | Vendor (CNA) |
| Linux Linux | 2.6.35 | Vendor (CNA) |
| Linux Linux | 50f0cbec45b0f3fd7e1263d01916518dbf31eb3f | Vendor (CNA) |
| Linux Linux | 6176313622e34fa3e2b66b9d0682d1e1c6b365c5 | Vendor (CNA) |
| Linux Linux | 6a009f1e61b11d9e23d3c5aa1dacfb010945da45 | Vendor (CNA) |
| Linux Linux | 743ac908282ac97ef6e73ac3a92df2cc8ecb7479 | Vendor (CNA) |
| Linux Linux | a3ccb57086dd7652d5ecb826486144198a98a8e9 | Vendor (CNA) |
| Linux Linux | b4663405ae29d36011cd712d243456f3f9ab700d | Vendor (CNA) |
| Linux Linux | b9eb5c9fdd81d82976d4d5be2b2458eb7d7e46ec | Vendor (CNA) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.107-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- git.kernel.org/stable/c/0cdc7dde00ec63ac714271fa8b2918d630b8da1a
- git.kernel.org/stable/c/50f0cbec45b0f3fd7e1263d01916518dbf31eb3f
- git.kernel.org/stable/c/6176313622e34fa3e2b66b9d0682d1e1c6b365c5
- git.kernel.org/stable/c/6a009f1e61b11d9e23d3c5aa1dacfb010945da45
- git.kernel.org/stable/c/743ac908282ac97ef6e73ac3a92df2cc8ecb7479
- git.kernel.org/stable/c/a3ccb57086dd7652d5ecb826486144198a98a8e9
- git.kernel.org/stable/c/b4663405ae29d36011cd712d243456f3f9ab700d
- git.kernel.org/stable/c/b9eb5c9fdd81d82976d4d5be2b2458eb7d7e46ec
Vendor advisories and official records. Exploit/PoC links are deliberately left out.