CVE-2023-54293
Linux Kernel vulnerability analysis and mitigation

Overview

CVE-2023-54293 is a kernel crash vulnerability in the Linux kernel's bcache subsystem, specifically in the btree cache wait list handling. The flaw causes list corruption when multiple threads (such as bch_btree_check_thread() and bch_dirty_init_thread()) concurrently attempt to cannibalize cached btree nodes via mca_cannibalize(), leading to a kernel panic with the error "list_add corruption. next->prev should be prev." It was published on December 30, 2025, and affects the Linux kernel. No CVSS score has been publicly assigned at this time (Feedly, CVE.org).

Technical details

The root cause is a race condition (CWE-362) in the bcache subsystem's mca_cannibalize_lock() function, where concurrent threads can corrupt the btree_cache_wait linked list. When multiple threads call mca_cannibalize() simultaneously, improper synchronization allows a thread to add itself to the wait list after the list node has already been zeroed or invalidated, resulting in a corrupted list_head structure with null next/prev pointers. The crash manifests in the call chain: prepare_to_waitmca_cannibalize_lockmca_allocbch_btree_node_getbch_btree_check_thread. Fixes are available as stable kernel patches (Kernel Git, Kernel Git).

Impact

Successful triggering of this vulnerability results in a kernel panic (system crash), causing a complete loss of availability for the affected Linux system. The impact is limited to availability — there is no evidence of confidentiality or integrity compromise. Systems using the bcache block layer caching subsystem under concurrent btree check or dirty initialization workloads are at risk of unexpected reboots or unplanned downtime (Feedly).

Indicators of compromise

  • Logs: Kernel logs (dmesg or /var/log/kern.log) containing "list_add corruption. next->prev should be prev" with associated memory addresses.
  • Logs: Kernel oops/panic traces referencing prepare_to_wait, mca_cannibalize_lock, mca_alloc, bch_btree_node_get, or bch_btree_check_thread in the call trace.
  • System Behavior: Unexpected system reboots or kernel panics on systems with bcache (block layer cache) enabled under heavy I/O workloads.

Mitigation and workarounds

Apply the upstream Linux kernel stable patches that fix the btree_cache_wait list corruption in the bcache subsystem. The fixes are available at multiple stable kernel commits: 25ec477, 2882a4c, bcb2957, cbdd5b3, and f085448. As a workaround, systems not requiring bcache can disable the module to eliminate exposure. Users should update to a patched kernel version as provided by their Linux distribution vendor (Feedly).

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