CVE-2026-64378

In the Linux kernel, the following vulnerability has been resolved: writeback: fix race between cgroup_writeback_umount() and inode_switch_wbs() When a container exits, the following BUG_ON() is occasionally triggered: ================================================================== VFS: Busy inodes after unmount of sdb (ext4) ------------[ cut here ]------------ kernel BUG at fs/super.c:695! CPU: 3 PID: 6 Comm: containerd-shim Tainted: G OE K 6.6 #1 pstate: 63400009 (nZCv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--) pc : generic_shutdown_super+0xf0/0x100 lr : generic_shutdown_super+0xf0/0x100 Call trace: generic_shutdown_super+0xf0/0x100 kill_block_super+0x20/0x48 ext4_kill_sb+0x28/0x60 deactivate_locked_super+0x54/0x130 deactivate_super+0x84/0xa0 cleanup_mnt+0xa4/0x140 __cleanup_mnt+0x18/0x28 task_work_run+0x78/0xe0 do_notify_resume+0x204/0x240 ================================================================== The root cause is a race between cgroup_writeback_umount() and inode_switch_wbs()/cleanup_offline_cgwb(). There is a window between inode_prepare_wbs_switch() returning true and the subsequent wb_queue_isw() call. Following is the process that triggers the issue: CPU A (umount) | CPU B (writeback) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ inode_switch_wbs/cleanup_offline_cgwb atomic_inc(&isw_nr_in_flight) inode_prepare_wbs_switch -> passes SB_ACTIVE check __iget(inode) generic_shutdown_super sb->s_flags &= ~SB_ACTIVE cgroup_writeback_umount(sb) smp_mb() atomic_read(&isw_nr_in_flight) rcu_barrier() -> no pending RCU callbacks flush_workqueue(isw_wq) -> nothing queued, returns evict_inodes(sb) -> Inode skipped as isw still holds a ref. sop->put_super(sb) /* destroys percpu counters */ -> VFS: Busy inodes after unmount! wb_queue_isw() queue_work(isw_wq, ...) /* later in work function */ inode_switch_wbs_work_fn process_inode_switch_wbs iput() -> evict percpu_counter_dec() // UAF! Fix this by extending the RCU read-side critical secti

What this means for your business

It affects Linux Kernel. It matters if your company, or a supplier that handles your data, runs it.
An attacker can use it only with access to the machine itself, with an ordinary user login, and without anyone at your company clicking anything.
FIRST's prediction model gives it a 0.1% chance of attack attempts being seen in the next 30 days, ranking above 0% of all known flaws.

What to do

1Check whether your company or your suppliers run Linux Kernel, and which version. The affected versions are listed further down this page.
2If you do, apply the vendor's fix. A patch or vendor advisory has been published.

Fastnexa security experts

Not sure if your company is exposed to CVE-2026-64378?

Tell us where you run Linux Linux Kernel and a Fastnexa penetration tester will check whether this flaw, or others like it, can be used against your websites, apps and network.

The full test is free for our first 10 founding clients until 31 December 2026. See the offer

Book a 30-min call WhatsApp us

Think you’ve already been hit? Don’t wait on a form: call or WhatsApp +1 (732) 454 2616. We reply within 1 hour, 24/7. Emergency help →

Scoring

CVSS: 7.8 (v3.1)
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness: CWE-362
Assigned by: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Dates

Published: 2026-07-25
Last modified: 2026-09-08
Sources: NVD

Affected products

Linux Linux Kernel4.4.5 - 4.5, 4.5.1 - 5.10.261, 5.11 - 6.1.178, 6.2 - 6.6.145, 6.7 - 6.12.96, 6.13 - 6.18.39, 6.19 - 7.1.4, 4.5

As listed in the NVD configuration data. Not a statement about your estate.