CVE-2021-47116: ext4: fix memory leak in ext4_mb_init_backend on error path.
In the Linux kernel, the following vulnerability has been resolved:
ext4: fix memory leak in ext4_mb_init_backend on error path.
Fix a memory leak discovered by syzbot when a file system is corrupted
with an illegally large s_log_groups_per_flex.
Security readout for executives and security teams
Plain-English summary
CVE-2021-47116 is a Linux kernel ext4 filesystem bug that can leak memory when handling a corrupted filesystem with an illegally large flex group setting. Business impact is most likely availability risk on systems that process malformed ext4 media or images. The provided sources do not include a CVSS score or evidence of active exploitation.
Executive priority
Handle through normal kernel patch management unless the organization processes untrusted filesystem images at scale. Escalate priority for forensic, hosting, sandboxing, build, or appliance environments where malformed ext4 content is routine.
Technical view
The issue is in ext4_mb_init_backend, where an error path failed to release allocated memory after encountering corrupted ext4 metadata, specifically an illegally large s_log_groups_per_flex. Kernel stable commits are referenced as fixes. The source bundle does not provide exploitability details, privilege requirements, or a CVSS vector.
Likely exposure
Exposure is most relevant to Linux systems using ext4 that may process corrupted or untrusted filesystems, disk images, or removable media. Systems that never mount or inspect untrusted ext4 content appear less exposed, based on the limited source evidence.
Exploitation context
The provided sources describe a syzbot-discovered memory leak caused by corrupted filesystem metadata. They do not show public exploitation, inclusion in CISA KEV, weaponized proof-of-concept activity, or remote attack conditions.
Researcher notes
The record identifies a memory leak in an ext4 error path, not memory corruption or privilege escalation. Evidence is sparse: no CVSS, CWE, detailed exploit preconditions, or impact rating are included. Analysis should stay tied to ext4 metadata handling and the referenced stable fixes.
Mitigation direction
Check distribution kernel advisories for CVE-2021-47116 coverage.
Apply vendor kernel updates containing the referenced ext4 stable fixes.
Avoid processing untrusted ext4 filesystems or disk images on sensitive hosts.
Use standard memory and availability monitoring on exposed Linux systems.
Validation and detection
Inventory Linux kernel versions on ext4-capable systems.
Confirm vendor changelogs or packages include the referenced stable commits.
Identify workflows that mount or inspect external ext4 media or images.
Review logs for kernel memory pressure or ext4 errors around untrusted media handling.
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-47116 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.