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
DEBUG_VM=y"), the duplicate slab cache names can be detected and a
kernel WARNING is thrown out.
In UBI fast attaching process, alloc_ai() could be invoked twice
with the same slab cache name 'ubi_aeb_slab_cache', which will trigger
following warning messages:
kmem_cache of name 'ubi_aeb_slab_cache' already exists
WARNING: CPU: 0 PID: 7519 at mm/slab_common.c:107
__kmem_cache_create_args+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:__kmem_cache_create_args+0x100/0x5f0
Call Trace:
__kmem_cache_create_args+0x100/0x5f0
alloc_ai+0x295/0x3f0 [ubi]
ubi_attach+0x3c3/0xcc0 [ubi]
ubi_attach_mtd_dev+0x17cf/0x3fa0 [ubi]
ubi_init+0x3fb/0x800 [ubi]
do_init_module+0x265/0x7d0
__x64_sys_finit_module+0x7a/0xc0
The problem could be easily reproduced by loading UBI device by fastmap
with CONFIG_DEBUG_VM=y.
Fix it by using different slab names for alloc_ai() callers.
ubi: fastmap: Fix duplicate slab cache names while attaching
Since commit 4c39529663b9 ("slab: Warn on duplicate cache names when
DEBUG_VM=y"), the duplicate slab cache names can be detected and a
kernel WARNING is thrown out.
In UBI fast attaching process, alloc_ai() could be invoked twice
with the same slab cache name 'ubi_aeb_slab_cache', which will trigger
following warning messages:
kmem_cache of name 'ubi_aeb_slab_cache' already exists
WARNING: CPU: 0 PID: 7519 at mm/slab_common.c:107
__kmem_cache_create_args+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:__kmem_cache_create_args+0x100/0x5f0
Call Trace:
__kmem_cache_create_args+0x100/0x5f0
alloc_ai+0x295/0x3f0 [ubi]
ubi_attach+0x3c3/0xcc0 [ubi]
ubi_attach_mtd_dev+0x17cf/0x3fa0 [ubi]
ubi_init+0x3fb/0x800 [ubi]
do_init_module+0x265/0x7d0
__x64_sys_finit_module+0x7a/0xc0
The problem could be easily reproduced by loading UBI device by fastmap
with CONFIG_DEBUG_VM=y.
Fix it by using different slab names for alloc_ai() callers.
Metrics
Affected Vendors & Products
Advisories
Source | ID | Title |
---|---|---|
![]() |
DLA-4075-1 | linux security update |
![]() |
DLA-4076-1 | linux-6.1 security update |
![]() |
EUVD-2024-51844 | 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 DEBUG_VM=y"), the duplicate slab cache names can be detected and a kernel WARNING is thrown out. In UBI fast attaching process, alloc_ai() could be invoked twice with the same slab cache name 'ubi_aeb_slab_cache', which will trigger following warning messages: kmem_cache of name 'ubi_aeb_slab_cache' already exists WARNING: CPU: 0 PID: 7519 at mm/slab_common.c:107 __kmem_cache_create_args+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:__kmem_cache_create_args+0x100/0x5f0 Call Trace: __kmem_cache_create_args+0x100/0x5f0 alloc_ai+0x295/0x3f0 [ubi] ubi_attach+0x3c3/0xcc0 [ubi] ubi_attach_mtd_dev+0x17cf/0x3fa0 [ubi] ubi_init+0x3fb/0x800 [ubi] do_init_module+0x265/0x7d0 __x64_sys_finit_module+0x7a/0xc0 The problem could be easily reproduced by loading UBI device by fastmap with CONFIG_DEBUG_VM=y. Fix it by using different slab names for alloc_ai() callers. |
![]() |
USN-7276-1 | Linux kernel vulnerabilities |
![]() |
USN-7277-1 | Linux kernel vulnerabilities |
![]() |
USN-7310-1 | Linux kernel vulnerabilities |
![]() |
USN-7387-1 | Linux kernel vulnerabilities |
![]() |
USN-7387-2 | Linux kernel (FIPS) vulnerabilities |
![]() |
USN-7387-3 | Linux kernel (Real-time) vulnerabilities |
![]() |
USN-7388-1 | Linux kernel vulnerabilities |
![]() |
USN-7389-1 | Linux kernel (NVIDIA Tegra) vulnerabilities |
![]() |
USN-7390-1 | Linux kernel (Xilinx ZynqMP) vulnerabilities |
![]() |
USN-7391-1 | Linux kernel vulnerabilities |
![]() |
USN-7392-1 | Linux kernel vulnerabilities |
![]() |
USN-7392-2 | Linux kernel vulnerabilities |
![]() |
USN-7392-3 | Linux kernel (AWS) vulnerabilities |
![]() |
USN-7392-4 | Linux kernel (AWS FIPS) vulnerabilities |
![]() |
USN-7393-1 | Linux kernel (FIPS) vulnerabilities |
![]() |
USN-7401-1 | Linux kernel (AWS) vulnerabilities |
![]() |
USN-7407-1 | Linux kernel (HWE) vulnerabilities |
![]() |
USN-7413-1 | Linux kernel (IoT) vulnerabilities |
![]() |
USN-7421-1 | Linux kernel (Azure) vulnerabilities |
![]() |
USN-7449-1 | Linux kernel vulnerabilities |
![]() |
USN-7449-2 | Linux kernel (HWE) vulnerabilities |
![]() |
USN-7450-1 | Linux kernel vulnerabilities |
![]() |
USN-7451-1 | Linux kernel vulnerabilities |
![]() |
USN-7452-1 | Linux kernel vulnerabilities |
![]() |
USN-7453-1 | Linux kernel (Real-time) vulnerabilities |
![]() |
USN-7458-1 | Linux kernel (IBM) vulnerabilities |
![]() |
USN-7459-1 | Linux kernel (Intel IoTG) vulnerabilities |
![]() |
USN-7459-2 | Linux kernel (GCP) vulnerabilities |
![]() |
USN-7463-1 | Linux kernel (IBM) vulnerabilities |
![]() |
USN-7468-1 | Linux kernel (Azure, N-Series) vulnerabilities |
![]() |
USN-7523-1 | Linux kernel (Raspberry Pi Real-time) vulnerabilities |
![]() |
USN-7524-1 | Linux kernel (Raspberry Pi) vulnerabilities |
![]() |
USN-7539-1 | Linux kernel (Raspberry Pi) vulnerabilities |
![]() |
USN-7540-1 | Linux kernel (Raspberry Pi) vulnerabilities |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Wed, 08 Oct 2025 14:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Weaknesses | NVD-CWE-noinfo | |
CPEs | cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* |
Wed, 16 Jul 2025 13:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Metrics |
epss
|
epss
|
Thu, 13 Feb 2025 00:30:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Weaknesses | CWE-20 |
Mon, 30 Dec 2024 01:30:00 +0000
Type | Values Removed | Values Added |
---|---|---|
References |
| |
Metrics |
threat_severity
|
cvssV3_1
|
Fri, 27 Dec 2024 14:00:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Description | 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 DEBUG_VM=y"), the duplicate slab cache names can be detected and a kernel WARNING is thrown out. In UBI fast attaching process, alloc_ai() could be invoked twice with the same slab cache name 'ubi_aeb_slab_cache', which will trigger following warning messages: kmem_cache of name 'ubi_aeb_slab_cache' already exists WARNING: CPU: 0 PID: 7519 at mm/slab_common.c:107 __kmem_cache_create_args+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:__kmem_cache_create_args+0x100/0x5f0 Call Trace: __kmem_cache_create_args+0x100/0x5f0 alloc_ai+0x295/0x3f0 [ubi] ubi_attach+0x3c3/0xcc0 [ubi] ubi_attach_mtd_dev+0x17cf/0x3fa0 [ubi] ubi_init+0x3fb/0x800 [ubi] do_init_module+0x265/0x7d0 __x64_sys_finit_module+0x7a/0xc0 The problem could be easily reproduced by loading UBI device by fastmap with CONFIG_DEBUG_VM=y. Fix it by using different slab names for alloc_ai() callers. | |
Title | ubi: fastmap: Fix duplicate slab cache names while attaching | |
References |
|
|

Status: PUBLISHED
Assigner: Linux
Published:
Updated: 2025-05-04T09:54:51.996Z
Reserved: 2024-11-19T17:17:25.006Z
Link: CVE-2024-53172

No data.

Status : Analyzed
Published: 2024-12-27T14:15:24.433
Modified: 2025-10-08T14:40:27.183
Link: CVE-2024-53172


Updated: 2025-07-12T22:44:26Z