CVE-2026-80638
nicheOut-of-bounds write in Linux kernel ocfs2 filesystem refcount handling
CVE-2026-80638 is an out-of-bounds write in the ocfs2 filesystem's refcount code in the Linux kernel. It is triggered when the last leaf block is removed from a refcount tree (for example, while unlinking a refcounted file): ocfs2_remove_refcount_extent() performs a bulk memset over rf_records while the aliased rl_count field is 0, causing writes past the 16-byte declared size of the structure, which the kernel's fortify checks catch as a panic. An attacker who can create and delete refcounted files on a mounted ocfs2 volume could corrupt adjacent kernel memory; the CVSS 3.1 score of 8.8 (High) reflects high confidentiality, integrity, and availability impact, and the observed symptom in the fix report is a fortify panic (kernel crash). Only systems running Linux kernels with ocfs2 mounted and using refcounted files whose refcount trees have leaf blocks are affected; most Linux installations never mount this clustered filesystem. There is no known exploitation: the flaw is not in CISA KEV, no public proof-of-concept exists, and EPSS estimates only a 0.3% probability of exploitation within 30 days.
What to do: Track your distribution's kernel updates and install a release containing the ocfs2 fix (bounded memset on rl_recs[] after setting rl_count) once published; no fixed version number is available in the data yet. To assess exposure, check whether ocfs2 is in use (e.g., 'mount | grep ocfs2') and whether any volumes use the refcount feature; systems without ocfs2 mounted are unaffected. As an interim measure, avoid unlinking refcounted ocfs2 files with multi-level refcount trees, or unmount ocfs2 volumes if they are not required.
| Linux kernel (ocfs2 filesystem) | — |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix out-of-bounds write in ocfs2_remove_refcount_extent [BUG] Unlinking a refcounted file whose refcount tree has leaf blocks triggers a fortify panic due to an out-of-bounds write. [CAUSE] When the last leaf block is removed from a refcount tree, ocfs2_remove_refcount_extent() converts the root back to leaf mode with a bulk memset on &rb->rf_records. rf_records sits in an anonymous union with rf_list. rf_list.l_tree_depth aliases rf_records.rl_count, and is 0 for a single-level tree. With rl_count equal to 0, the memset writes past the 16-byte declared size of rf_records, which the fortify checker catches. [FIX] Replace the bulk memset on &rb->rf_records with a correctly-bounded memset on rl_recs[] alone, after setting rl_count to the correct value.
- Vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
In the news0 stories
No ingested article mentions this CVE yet.