Look up another CVE · open CVE-2026-80638 in the interactive tracker
CVE-2026-80638
ocfs2: fix out-of-bounds write in ocfs2_remove_refcount_extent
Published 2026-08-28 (2 months ago) by the Linux kernel CNA. Subsystem fs/ocfs2. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2026-80638 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | not affected | 6.1.190-1 | Nothing to do. bookworm never shipped the vulnerable code. |
| Debian 13trixie | not affected | 6.12.113-1 | Nothing to do. trixie never shipped the vulnerable code. |
| Debian 14forky | fixed | 7.1.5-1 | Update the kernel and reboot. Fixed in 7.1.5-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.1.5-1 | Update the kernel and reboot. Fixed in 7.1.5-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
[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.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
fs/ocfs2/refcounttree.c
- What this is
- ORACLE CLUSTER FILESYSTEM 2 (OCFS2)MAINTAINERS section matched on fs/ocfs2/ · ocfs2-devel@lists.linux.dev · Supported
- Kernel module
- ocfs2
Check it on the machine
grep -w CONFIG_OCFS2_FS /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
lsmod | grep -w ocfs2Prints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.
Show whether Debian builds this, per release
Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed.
- bookworm, trixie, forky, sidMnot built on amd64/cloud-amd64, arm64/cloud-arm64
- M
- a module where it is built at all; some flavours do not build it
- Build switch
- CONFIG_OCFS2_FS
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-08-28 (2 months ago)source
- CVSS
- 8.8 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- network (AV:N)source
- EPSS
- 0.51%, higher than 42.1% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- Subsystem
- fs/ocfs2
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 6.19 | 7.1.5 | f5255516ec7a |
| 6.19 | 7.2 | 1ec3cca2d8b6 |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:NAttack vector, network
- OCFS2 registers NFS export operations and is commonly NFS-exported on shared cluster storage; remote NFS SETATTR/truncate or REMOVE/unlink on refcounted files reaches ocfs2_decrease_refcount() and the vulnerable memset via kernel nfsd.
- AC:LAttack complexity, low
- An attacker can deterministically create refcounted files with multi-block refcount trees via reflink/copy_file_range, then trigger removal of the last leaf through truncate or unlink; syzbot reproduced this reliably without races or victim-specific timing.
- PR:LPrivileges required, low
- Only normal filesystem write permission on the target file or parent directory is required to truncate/unlink refcounted data; no real-root or init-namespace capabilities are needed beyond access to the mounted OCFS2 volume.
- UI:NUser interaction, none
- Exploitation requires only attacker-initiated filesystem operations (reflink setup, truncate, or unlink) on objects they can write; no additional end-user or administrator interaction beyond routine file access is needed.
- S:UScope, unchanged
- Impact is confined to kernel/filesystem integrity and availability on systems running OCFS2; it does not cross a VM, container, or IOMMU security boundary into another authority domain.
- C:HConfidentiality impact, high
- The out-of-bounds memset corrupts refcount-tree metadata within the on-disk block image, which can misdirect subsequent metadata reads and expose stale or cross-file cluster data on shared cluster filesystems.
- I:HIntegrity impact, high
- This is an out-of-bounds write (FORTIFY reported a 384-byte write past a 16-byte declared rf_records object) that zeros arbitrary portions of the refcount root block, corrupting filesystem metadata and enabling further memory corruption primitives.
- A:HAvailability impact, high
- The fortify-detected out-of-bounds write triggers a kernel WARNING/panic during refcount-tree cleanup, causing node crash or denial of service on OCFS2 cluster members processing the malicious truncate or unlink.