In the Linux kernel, the following vulnerability has been resolved:
ovl: fix leaked dentry
Since commit 6815f479ca90 ("ovl: use only uppermetacopy state in
ovl_lookup()"), overlayfs doesn't put temporary dentry when there is a
metacopy error, which leads to dentry leaks when shutting down the related
superblock:
overlayfs: refusing to follow metacopy origin for (/file0)
...
BUG: Dentry (____ptrval____){i=3f33,n=file3} still in use (1) [unmount of overlay overlay]
...
WARNING: CPU: 1 PID: 432 at umount_check.cold+0x107/0x14d
CPU: 1 PID: 432 Comm: unmount-overlay Not tainted 5.12.0-rc5 #1
...
RIP: 0010:umount_check.cold+0x107/0x14d
...
Call Trace:
d_walk+0x28c/0x950
? dentry_lru_isolate+0x2b0/0x2b0
? __kasan_slab_free+0x12/0x20
do_one_tree+0x33/0x60
shrink_dcache_for_umount+0x78/0x1d0
generic_shutdown_super+0x70/0x440
kill_anon_super+0x3e/0x70
deactivate_locked_super+0xc4/0x160
deactivate_super+0xfa/0x140
cleanup_mnt+0x22e/0x370
__cleanup_mnt+0x1a/0x30
task_work_run+0x139/0x210
do_exit+0xb0c/0x2820
? __kasan_check_read+0x1d/0x30
? find_held_lock+0x35/0x160
? lock_release+0x1b6/0x660
? mm_update_next_owner+0xa20/0xa20
? reacquire_held_locks+0x3f0/0x3f0
? __sanitizer_cov_trace_const_cmp4+0x22/0x30
do_group_exit+0x135/0x380
__do_sys_exit_group.isra.0+0x20/0x20
__x64_sys_exit_group+0x3c/0x50
do_syscall_64+0x45/0x70
entry_SYSCALL_64_after_hwframe+0x44/0xae
...
VFS: Busy inodes after unmount of overlay. Self-destruct in 5 seconds. Have a nice day...
This fix has been tested with a syzkaller reproducer.
Security readout for executives and security teams
Plain-English summary
CVE-2021-46972 is a Linux kernel overlayfs bug that can leak a temporary filesystem entry during a metacopy error. The public record shows kernel warnings and busy inodes during unmount, not data theft or remote compromise. Business urgency depends on whether affected Linux kernels and overlayfs are used.
Executive priority
Handle through normal kernel maintenance unless affected overlayfs-heavy systems show instability. There is no sourced evidence of active exploitation or severe impact, but kernel filesystem bugs can affect availability and operational reliability.
Technical view
The bug is in overlayfs lookup handling after commit 6815f479ca90. On a metacopy error path, a temporary dentry was not released, causing dentry leaks and unmount-time warnings. The fix releases the dentry correctly and was tested with a syzkaller reproducer. Public sources do not provide CVSS or CWE details.
Likely exposure
Exposure is most plausible on Linux systems using affected kernel builds with overlayfs, especially container or layered-filesystem environments. The supplied data does not map cleanly to every distribution kernel, so teams should validate against vendor kernel advisories and the cited upstream stable fixes.
Exploitation context
The source bundle does not report active exploitation, and KEV is false. The evidence describes a syzkaller-triggered kernel bug causing leaked dentries and unmount warnings. No public source in the bundle claims a privilege escalation, remote attack path, or weaponized exploit.
Researcher notes
Useful focus areas are exact kernel lineage, whether commit 6815f479ca90 is present, and whether the stable fix is backported by the distribution. The source evidence is limited to overlayfs dentry leakage and syzkaller validation.
Mitigation direction
Update to a vendor-supported kernel containing the cited upstream stable fixes.
Check Linux distribution advisories for exact fixed package versions.
Prioritize systems that use overlayfs for containers or layered mounts.
Monitor kernel logs for overlayfs metacopy and busy-inode warnings.
Avoid relying on unverified workarounds not named by vendor guidance.
Validation and detection
Inventory Linux kernel versions across hosts and container platforms.
Identify systems using overlayfs or overlay-backed container storage.
Compare running kernels against vendor advisories and cited stable commits.
Review kernel logs for overlayfs metacopy errors and unmount warnings.
Confirm patched kernels are active after reboot or live patching.
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-46972 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.