In the Linux kernel, the following vulnerability has been resolved:
ubi: fastmap: Fix duplicate slab cache names while attaching
Since commit 4c39529663b9 ("slab: Warn on duplicate cache names when DEBUGVM=y"), the duplicate slab cache names can be detected and a kernel WARNING is thrown out. In UBI fast attaching process, allocai() could be invoked twice with the same slab cache name 'ubiaebslabcache', which will trigger following warning messages: kmemcache of name 'ubiaebslabcache' already exists WARNING: CPU: 0 PID: 7519 at mm/slabcommon.c:107 kmemcachecreateargs+0x100/0x5f0 Modules linked in: ubi(+) nandsim [last unloaded: nandsim] CPU: 0 UID: 0 PID: 7519 Comm: modprobe Tainted: G 6.12.0-rc2 RIP: 0010:kmemcachecreateargs+0x100/0x5f0 Call Trace: _kmemcachecreateargs+0x100/0x5f0 allocai+0x295/0x3f0 [ubi] ubiattach+0x3c3/0xcc0 [ubi] ubiattachmtddev+0x17cf/0x3fa0 [ubi] ubiinit+0x3fb/0x800 [ubi] doinitmodule+0x265/0x7d0 _x64sysfinitmodule+0x7a/0xc0
The problem could be easily reproduced by loading UBI device by fastmap with CONFIGDEBUGVM=y. Fix it by using different slab names for alloc_ai() callers.