CVE-2021-47470: mm, slub: fix potential use-after-free in slab_debugfs_fops
In the Linux kernel, the following vulnerability has been resolved:
mm, slub: fix potential use-after-free in slab_debugfs_fops
When sysfs_slab_add failed, we shouldn't call debugfs_slab_add() for s
because s will be freed soon. And slab_debugfs_fops will use s later
leading to a use-after-free.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel memory-safety flaw in SLUB debug handling. Under a failure path, the kernel could keep a debugfs operation tied to slab state that is about to be freed, creating a possible use-after-free condition.
Executive priority
Track and remediate through normal kernel patch management unless vendor guidance raises severity. The current public evidence does not support emergency treatment, but kernel memory-safety flaws should not be left unpatched indefinitely.
Technical view
The issue is in slab_debugfs_fops. If sysfs_slab_add failed, debugfs_slab_add could still be called for a slab object that would soon be freed. Later use through slab_debugfs_fops could dereference freed memory. The record identifies Linux kernel versions around 5.14, with fixes in stable kernel commits.
Likely exposure
Exposure appears limited to Linux systems running affected kernel versions identified in the CVE record, including 5.14-era kernels before the referenced stable fixes. Distribution kernel backports may differ from upstream version numbers, so package-level advisory checks are required.
Exploitation context
The source bundle does not report active exploitation, KEV listing, public exploit use, CVSS, or detailed attack prerequisites. Treat exploitability and impact as not established from the provided evidence.
Researcher notes
The record describes a failure-path use-after-free caused by continuing into debugfs setup after sysfs_slab_add failure. No CWE, CVSS, exploitability details, or runtime prerequisites are provided in the source bundle.
Mitigation direction
Check vendor kernel advisories for CVE-2021-47470 coverage.
Update affected Linux kernels to packages containing the stable fixes.
Prioritize internet-facing or multi-user Linux systems after vendor confirmation.
Avoid mapping upstream commit hashes directly to distribution package status.
Validation and detection
Inventory Linux kernel versions across managed systems.
Compare installed kernel packages with vendor advisories or changelogs.
Confirm whether fixes matching the referenced stable commits are present.
Record systems still on affected 5.14-era kernels for remediation tracking.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2021-47470 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.