In the Linux kernel, the following vulnerability has been resolved:
f2fs: fix to avoid racing on fsyncentryslab by multi filesystem instances
As syzbot reported, there is an use-after-free issue during f2fs recovery:
Use-after-free write at 0xffff88823bc16040 (in kfence-#10): kmemcachedestroy+0x1f/0x120 mm/slabcommon.c:486 f2fsrecoverfsyncdata+0x75b0/0x8380 fs/f2fs/recovery.c:869 f2fsfillsuper+0x9393/0xa420 fs/f2fs/super.c:3945 mountbdev+0x26c/0x3a0 fs/super.c:1367 legacygettree+0xea/0x180 fs/fscontext.c:592 vfsgettree+0x86/0x270 fs/super.c:1497 donewmount fs/namespace.c:2905 [inline] pathmount+0x196f/0x2be0 fs/namespace.c:3235 domount fs/namespace.c:3248 [inline] _dosysmount fs/namespace.c:3456 [inline] _sesysmount+0x2f9/0x3b0 fs/namespace.c:3433 dosyscall64+0x3f/0xb0 arch/x86/entry/common.c:47 entrySYSCALL64afterhwframe+0x44/0xae
The root cause is multi f2fs filesystem instances can race on accessing global fsyncentryslab pointer, result in use-after-free issue of slab cache, fixes to init/destroy this slab cache only once during module init/destroy procedure to avoid this issue.