CVE-2026-23181
Linux Kernel vulnerability analysis and mitigation

Overview

CVE-2026-23181 is a vulnerability in the Linux kernel's btrfs filesystem subsystem involving a race condition between block size changes and read cache page allocation. When a user executes the BLKBSZSET ioctl command to change a block device's block size (e.g., from 0x1000 to 0x4000), the change affects mapping->flags and the result of mapping_min_folio_order(). If a folio is allocated before the block size change but used after, a mismatch in folio order can trigger a VM_BUG_ON_FOLIO assertion or a null pointer dereference in create_empty_buffers() due to buffer head allocation failure. The vulnerability was published on February 14, 2026, and is estimated as Medium severity with an EPSS score of 0.00018 (Feedly).

Technical details

The root cause is a synchronization gap (CWE-362: Race Condition) between the BLKBSZSET ioctl command and the read cache page allocation path in the btrfs filesystem. When do_read_cache_folio() allocates a folio with order 0 (corresponding to block size 0x1000), and subsequently BLKBSZSET increases the block size to 0x4000 — causing mapping_min_folio_order() to return 2 — the already-allocated folio's order no longer satisfies the mapping's minimum folio order requirement. This leads to two failure modes: (1) a VM_BUG_ON_FOLIO(folio_order(folio) < mapping_min_folio_order(mapping)) assertion failure, and (2) a null pointer dereference in create_empty_buffers() when buffer head allocation fails, as reported by syzbot. The fix requires establishing proper synchronization between the BLKBSZSET command and the read cache page path based on the inode (Feedly, Kernel Patch 1, Kernel Patch 2).

Impact

Successful exploitation of this vulnerability can cause a kernel crash (denial of service) on systems using the btrfs filesystem. The null pointer dereference in create_empty_buffers() and the VM_BUG_ON_FOLIO assertion can both result in a kernel panic, leading to system unavailability. There is no evidence of confidentiality or integrity impact beyond the availability disruption caused by the crash.

Mitigation and workarounds

The Linux kernel maintainers have addressed this vulnerability by synchronizing the BLKBSZSET command and read cache page allocation based on the inode. Patches are available in the stable kernel tree at the referenced commits. Users should update to a patched Linux kernel version that includes the fix for btrfs disk super sync and block size setting (Kernel Patch 1, Kernel Patch 2). As a workaround, avoiding the use of BLKBSZSET on block devices used by btrfs filesystems can mitigate the risk until a patched kernel is deployed.

Additional resources


SourceThis report was generated using AI

Related Linux Kernel vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-64557NONEN/A
  • Linux Kernel logoLinux Kernel
  • kernel-rt-selftests-internal
NoNoJul 29, 2026
CVE-2026-64556NONEN/A
  • Linux Kernel logoLinux Kernel
  • kernel-64k-devel
NoNoJul 29, 2026
CVE-2026-64555NONEN/A
  • Linux Kernel logoLinux Kernel
  • linux-azure-fde-6.14
NoNoJul 27, 2026
CVE-2026-64554NONEN/A
  • Linux Kernel logoLinux Kernel
  • linux-gcp-6.14
NoYesJul 27, 2026
CVE-2026-64553NONEN/A
  • Linux Kernel logoLinux Kernel
  • kernel-rt-64k-debug-modules-internal
NoYesJul 27, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management