BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2024
CVE-2021-46972High confidence

ovl: fix leaked dentry

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Low, lowered one band.downgradedsince 11 May 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.25% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: No default targetRemediation target: Normal maintenance

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Distribution package intelligence

Release-specific package status

Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

4 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.10.38-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.10.38-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.10.38-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.10.38-1Debian Security Tracker ↗Source updated 5 Oct 2026
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2021-33620

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
01

What, why and how

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.

What

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.

Why

The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Missing Release of Memory after Effective Lifetime → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-401 ↗

CWE-401: Missing Release of Memory after Effective Lifetime. The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-401
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2024-1905IBM QRadar SIEM: Mehrere Schwachstellen

Ein entfernter, anonymer oder lokaler Angreifer kann mehrere Schwachstellen in IBM QRadar SIEM ausnutzen, um seine Privilegien zu erhöhen, beliebigen Code auszuführen, Daten zu manipulieren, vertrauliche Informationen offenzulegen, eine Man-in-the-Middle-Situation zu schaffen, Sicherheitsmaßnahmen zu umgehen oder eine Denial-of-Service-Situation zu schaffen.

Official advisory ↗
BSI · German · WID-SEC-2024-0500Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240228Security Bulletin 28 Feb 2024

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 28 Feb 2024, published on 28 February 2024. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1165Multiples vulnérabilités dans les produits IBM

d?id=CVE-2021-41182 Référence CVE CVE-2021-41183 https://www.cve.org/CVERecord?id=CVE-2021-41183 Référence CVE CVE-2021-41184 https://www.cve.org/CVERecord?id=CVE-2021-41184 Référence CVE CVE-2021-41973 https://www.cve.org/CVERecord?id=CVE-2021-41973 Référence CVE CVE-2021-42550 https://www.cve.org/CVERecord?id=CVE-2021-42550 Référence CVE CVE-2021-43797 https://www.cve.org/CVERecord?id=CVE-2021-43797 Référence CVE CVE-2021-44906 https://www.cve.org/CVERecord?id=CVE-2021-44906 Référence CVE CVE-2021-46909 https://www.cve.org/CVERecord?id=CVE-2021-46909 Référence CVE CVE-2021-46939 https://www.cve.org/CVERecord?id=CVE-2021-46939 Référence CVE CVE-2021-46972 https://www.cve.org/CVERecord?id=CVE-2021-46972 Référence CVE CVE-2021-46984 https://www.cve.org/CVERecord?id=CVE-2021-46984 Référence CVE CVE-2021-47018 https://www.cve.org/CVERecord?id=CVE-2021-47018 Référence CVE CVE-2021-47069 https://www.cve.org/CVERecord?id=CVE-2021-47069 Référence CVE CVE-2021-47073 https://www.cve.org/CVERecord?id=CVE-2021-47073 Référence CVE CVE-2021-47097 https://www.cve.org/CVERecord?id=CVE-2021-47097 Référence CVE CVE-2021-47101 https://www.cve.org/CVERecord?id=CVE-2021-47101 Référence CVE CVE-2021-47236 https://www.cve.org/CVERecord?id=CVE-2021-47236 Référence CVE CVE-2021-47257 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0903Multiples vulnérabilités dans les produits IBM

cord?id=CVE-2018-1311 Référence CVE CVE-2020-25219 https://www.cve.org/CVERecord?id=CVE-2020-25219 Référence CVE CVE-2020-26137 https://www.cve.org/CVERecord?id=CVE-2020-26137 Référence CVE CVE-2020-26154 https://www.cve.org/CVERecord?id=CVE-2020-26154 Référence CVE CVE-2020-26555 https://www.cve.org/CVERecord?id=CVE-2020-26555 Référence CVE CVE-2020-7212 https://www.cve.org/CVERecord?id=CVE-2020-7212 Référence CVE CVE-2021-42771 https://www.cve.org/CVERecord?id=CVE-2021-42771 Référence CVE CVE-2021-45429 https://www.cve.org/CVERecord?id=CVE-2021-45429 Référence CVE CVE-2021-46909 https://www.cve.org/CVERecord?id=CVE-2021-46909 Référence CVE CVE-2021-46972 https://www.cve.org/CVERecord?id=CVE-2021-46972 Référence CVE CVE-2021-47069 https://www.cve.org/CVERecord?id=CVE-2021-47069 Référence CVE CVE-2021-47073 https://www.cve.org/CVERecord?id=CVE-2021-47073 Référence CVE CVE-2021-47236 https://www.cve.org/CVERecord?id=CVE-2021-47236 Référence CVE CVE-2021-47310 https://www.cve.org/CVERecord?id=CVE-2021-47310 Référence CVE CVE-2021-47311 https://www.cve.org/CVERecord?id=CVE-2021-47311 Référence CVE CVE-2021-47353 https://www.cve.org/CVERecord?id=CVE-2021-47353 Référence CVE CVE-2021-47356 https://www.cve.org/CVERecord?id=CVE-2021-47356 Référence CVE CVE-2021-47456 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0741Multiples vulnérabilités dans Juniper Secure Analytics

d?id=CVE-2020-23064 Référence CVE CVE-2020-26555 https://www.cve.org/CVERecord?id=CVE-2020-26555 Référence CVE CVE-2020-36777 https://www.cve.org/CVERecord?id=CVE-2020-36777 Référence CVE CVE-2021-33198 https://www.cve.org/CVERecord?id=CVE-2021-33198 Référence CVE CVE-2021-34558 https://www.cve.org/CVERecord?id=CVE-2021-34558 Référence CVE CVE-2021-40153 https://www.cve.org/CVERecord?id=CVE-2021-40153 Référence CVE CVE-2021-41072 https://www.cve.org/CVERecord?id=CVE-2021-41072 Référence CVE CVE-2021-46909 https://www.cve.org/CVERecord?id=CVE-2021-46909 Référence CVE CVE-2021-46934 https://www.cve.org/CVERecord?id=CVE-2021-46934 Référence CVE CVE-2021-46972 https://www.cve.org/CVERecord?id=CVE-2021-46972 Référence CVE CVE-2021-47013 https://www.cve.org/CVERecord?id=CVE-2021-47013 Référence CVE CVE-2021-47055 https://www.cve.org/CVERecord?id=CVE-2021-47055 Référence CVE CVE-2021-47069 https://www.cve.org/CVERecord?id=CVE-2021-47069 Référence CVE CVE-2021-47073 https://www.cve.org/CVERecord?id=CVE-2021-47073 Référence CVE CVE-2021-47118 https://www.cve.org/CVERecord?id=CVE-2021-47118 Référence CVE CVE-2021-47153 https://www.cve.org/CVERecord?id=CVE-2021-47153 Référence CVE CVE-2021-47171 https://www.cve.org/CVERecord?id=CVE-2021-47171 Référence CVE CVE-2021-47185 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0720Multiples vulnérabilités dans IBM QRadar SIEM

IF02 Résumé De multiples vulnérabilités ont été découvertes dans IBM QRadar SIEM. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, une élévation de privilèges et un déni de service à distance. Solutions Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité IBM 7166204 du 22 août 2024 https://www.ibm.com/support/pages/node/7166204 Référence CVE CVE-2020-26555 https://www.cve.org/CVERecord?id=CVE-2020-26555 Référence CVE CVE-2021-46909 https://www.cve.org/CVERecord?id=CVE-2021-46909 Référence CVE CVE-2021-46972 https://www.cve.org/CVERecord?id=CVE-2021-46972 Référence CVE CVE-2021-47069 https://www.cve.org/CVERecord?id=CVE-2021-47069 Référence CVE CVE-2021-47073 https://www.cve.org/CVERecord?id=CVE-2021-47073 Référence CVE CVE-2021-47236 https://www.cve.org/CVERecord?id=CVE-2021-47236 Référence CVE CVE-2021-47310 https://www.cve.org/CVERecord?id=CVE-2021-47310 Référence CVE CVE-2021-47311 https://www.cve.org/CVERecord?id=CVE-2021-47311 Référence CVE CVE-2021-47353 https://www.cve.org/CVERecord?id=CVE-2021-47353 Référence CVE CVE-2021-47356 https://www.cve.org/CVERecord?id=CVE-2021-47356 Référence CVE CVE-2021-47456 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0577Multiples vulnérabilités dans le noyau Linux de Red Hat

cess.redhat.com/errata/RHSA-2024:4349 Bulletin de sécurité Red Hat RHSA-2024:4352 du 08 juillet 2024 https://access.redhat.com/errata/RHSA-2024:4352 Bulletin de sécurité Red Hat RHSA-2024:4412 du 09 juillet 2024 https://access.redhat.com/errata/RHSA-2024:4412 Bulletin de sécurité Red Hat RHSA-2024:4415 du 09 juillet 2024 https://access.redhat.com/errata/RHSA-2024:4415 Bulletin de sécurité Red Hat RHSA-2024:4447 du 10 juillet 2024 https://access.redhat.com/errata/RHSA-2024:4447 Référence CVE CVE-2020-26555 https://www.cve.org/CVERecord?id=CVE-2020-26555 Référence CVE CVE-2021-46909 https://www.cve.org/CVERecord?id=CVE-2021-46909 Référence CVE CVE-2021-46972 https://www.cve.org/CVERecord?id=CVE-2021-46972 Référence CVE CVE-2021-47069 https://www.cve.org/CVERecord?id=CVE-2021-47069 Référence CVE CVE-2021-47073 https://www.cve.org/CVERecord?id=CVE-2021-47073 Référence CVE CVE-2021-47236 https://www.cve.org/CVERecord?id=CVE-2021-47236 Référence CVE CVE-2021-47293 https://www.cve.org/CVERecord?id=CVE-2021-47293 Référence CVE CVE-2021-47310 https://www.cve.org/CVERecord?id=CVE-2021-47310 Référence CVE CVE-2021-47311 https://www.cve.org/CVERecord?id=CVE-2021-47311 Référence CVE CVE-2021-47353 https://www.cve.org/CVERecord?id=CVE-2021-47353 Référence CVE CVE-2021-47356 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2021-021554Linux の Linux Kernel における有効期限後のメモリの解放の欠如に関する脆弱性

Linux の Linux Kernel には、有効期限後のメモリの解放の欠如に関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Linux: 6815f479ca90ee7fd2e28b2a420f796b974155fe < 71d58457a8afc650da5d3292a7f7029317654d95, 6815f479ca90ee7fd2e28b2a420f796b974155fe < cf3e3330bc5719fa9d658e3e2f596bde89344a94, 6815f479ca90ee7fd2e28b2a420f796b974155fe < d587cfaef72b1b6f4b2774827123bce91f497cc8, 6815f479ca90ee7fd2e28b2a420f796b974155fe < eaab1d45cdb4bb0c846bd23c3d666d5b90af7b41, 5.8
Fixed
Linux: < 5.8, 5.10.35 ≤ 5.10.*, 5.11.19 ≤ 5.11.*, 5.12.2 ≤ 5.12.*, 5.13 ≤ *
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 27 Feb 2024 · Last source change 11 May 2026, 13:45 UTC · CWE-401 · Missing Release of Memory after Effective Lifetime

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2021-33620
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceNIST NVD
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2021-33620↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2021-46972 · cve.blacktree.nl