Skip to content
Noroxi
CVE-2024-53172· NVD / CVE Program· CNA Linux

ubi: fastmap: Fix duplicate slab cache names while attaching

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.25% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 04c0b0f37617099479c34e207c5550d081f585a6, 3d8558135cd56a2a8052024be4073e160f36658c, 612824dd0c9465ef365ace38b056c663d110956d.

Low priority for now. Upgrade to Linux Linux 04c0b0f37617099479c34e207c5550d081f585a6, 3d8558135cd56a2a8052024be4073e160f36658c, 612824dd0c9465ef365ace38b056c663d110956d or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Dec 27, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 15th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-53172

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel4.1 and later · before 4.19.325
  • linux linux kernel4.20 and later · before 5.4.287
  • linux linux kernel5.5 and later · before 5.10.231
  • linux linux kernel5.11 and later · before 5.15.174
  • linux linux kernel5.16 and later · before 6.1.120
  • linux linux kernel6.2 and later · before 6.6.64
  • linux linux kernel6.7 and later · before 6.11.11
  • linux linux kernel6.12 and later · before 6.12.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.1affected
    • d2158f69a7d469c21c37f7028c18aa8c54707de3 and later · before ef52b7191ac41e68b1bf070d00c5b04ed16e4920affected · git
    • d2158f69a7d469c21c37f7028c18aa8c54707de3 and later · before 871c148f8e0c32e505df9393ba4a303c3c3fe988affected · git
    • d2158f69a7d469c21c37f7028c18aa8c54707de3 and later · before 04c0b0f37617099479c34e207c5550d081f585a6affected · git
    • d2158f69a7d469c21c37f7028c18aa8c54707de3 and later · before b1ee0aa4945c49cbbd779da81040fcec4de80fd1affected · git
    • d2158f69a7d469c21c37f7028c18aa8c54707de3 and later · before 6afdcb285794e75d2c8995e3a44f523c176cc2deaffected · git
    • d2158f69a7d469c21c37f7028c18aa8c54707de3 and later · before 612824dd0c9465ef365ace38b056c663d110956daffected · git
    • d2158f69a7d469c21c37f7028c18aa8c54707de3 and later · before 3d8558135cd56a2a8052024be4073e160f36658caffected · git
    • d2158f69a7d469c21c37f7028c18aa8c54707de3 and later · before 7402c4bcb8a3f0d2ef4e687cd45c76be489cf509affected · git
    • d2158f69a7d469c21c37f7028c18aa8c54707de3 and later · before bcddf52b7a17adcebc768d26f4e27cf79adb424caffected · git

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.123-16.1.123-1
Debian:13linuxbefore 6.12.3-16.12.3-1

Other highest-scoring records for the same primary product.

  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now
  • CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
    83Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-53169Dec 27, 2024 · nvme-fabrics: fix kernel crash while shutting down controller
    18Monitor
  • ← EarlierCVE-2024-53171Dec 27, 2024 · ubifs: authentication: Fix use-after-free in ubifs_tnc_end_commit
    31Monitor
  • Later →CVE-2024-53173Dec 27, 2024 · NFSv4.0: Fix a use-after-free problem in the asynchronous open()
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux04c0b0f37617099479c34e207c5550d081f585a6Vendor (CNA)
Linux Linux3d8558135cd56a2a8052024be4073e160f36658cVendor (CNA)
Linux Linux612824dd0c9465ef365ace38b056c663d110956dVendor (CNA)
Linux Linux6afdcb285794e75d2c8995e3a44f523c176cc2deVendor (CNA)
Linux Linux7402c4bcb8a3f0d2ef4e687cd45c76be489cf509Vendor (CNA)
Linux Linux871c148f8e0c32e505df9393ba4a303c3c3fe988Vendor (CNA)
Linux Linuxb1ee0aa4945c49cbbd779da81040fcec4de80fd1Vendor (CNA)
Linux Linuxbcddf52b7a17adcebc768d26f4e27cf79adb424cVendor (CNA)
Linux Linuxef52b7191ac41e68b1bf070d00c5b04ed16e4920Vendor (CNA)
debian:linux6.1.123-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records