CVE-2026-64378

Debilidad

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 (umoun

Productos afectados

• linux linux_kernel

Referencias

• https://git.kernel.org/stable/c/087d5b8b501c570f84bf655164e6698c3ce146e0
• https://git.kernel.org/stable/c/3c9c9648f77e4d14e50676bc51c2174ba9c8d361
• https://git.kernel.org/stable/c/53eeaf4d63068dbc7708b0c7adb20151c812feca
• https://git.kernel.org/stable/c/5c3265f3252b2ee50707adaaa3f9bd0df3df72de
• https://git.kernel.org/stable/c/685fc15a410885b6d4dee64de0dce721b9428b12
• https://git.kernel.org/stable/c/c923cc3cb5cd8945ceaf08252754110643446593