All vulnerabilities

Servers and applications

CVE-2026-53122

btrfs: fix deadlock between reflink and transaction commit when using flushoncommit

Severity
Unrated
Published
24 Jun 2026
Last changed
30 Oct 2026
Added to UpHeron
30 Oct 2026
Fixed in
6.1.191, 6.6.160, 6.12.91, 6.18.33, 7.0.10
Exploit chance
0.1% in the next 30 daysHigher than 2% of CVEs. EPSS by FIRST, 19 Nov 2026
Sources
CVE Program

Description

In the Linux kernel, the following vulnerability has been resolved:

When using the flushoncommit mount option, we can have a deadlock between a transaction commit and a reflink operation that copied an inline extent to an offset beyond the current i_size of the destination node.

The deadlock happens like this:

  • Task A clones an inline extent from inode X to an offset of inode Y that is beyond Y's current i_size. This means we copied the inline extent's data to a folio of inode Y that is beyond its EOF, using a call to copy_inline_to_page();
  • Task B starts a transaction commit and calls btrfs_start_delalloc_flush() to flush delalloc;
  • The delalloc flushing sees the new dirty folio of inode Y and when it attempts to flush it, it ends up at extent_writepage() and sees that the offset of the folio is beyond the i_size of inode Y, so it attempts to invalidate the folio by calling folio_invalidate(), which ends up at btrfs' folio invalidate callback - btrfs_invalidate_folio().
From the CVE Program. Shortened; the full text is there.

Affected software

SoftwareAffected versions
Linux kernelServers and applications · cna:linux|linux
  • From 5.7 before 6.1.191
  • From 6.2 before 6.6.160
  • From 6.7 before 6.12.91
  • From 6.13 before 6.18.33
  • From 6.19 before 7.0.10

About Linux kernel

Unix-like operating system kernel, basis for all Linux operating systems

From Wikidata, CC0 1.0.
GitHub stars
255,726GitHub, 15 Nov 2026
Forks
67,394GitHub, 15 Nov 2026
Developer
Linus TorvaldsWikidata
License
GNU General Public License, version 2.0Wikidata
Written in
CWikidata
First released
25 Aug 1991Wikidata
First published on GitHub
4 Sept 2011GitHub

References

  • CVE.org https://www.cve.org/CVERecord?id=CVE-2026-53122