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

dm btree remove: assign new_root only when removal succeeds

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 93 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 5 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.27% 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: As exposure requiresRemediation target: Within 365 days

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.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 93 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

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

5 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 1 affected package state shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

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.14.6-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.14.6-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.14.6-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.14.6-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

2 current
CVE-2021-47343 · CSAF 2.0 · revision 57 · interimSUSE Product Security TeamCVE-2021-47343
163 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
Summary
In the Linux kernel, the following vulnerability has been resolved: dm btree remove: assign new_root only when removal succeeds remove_raw() in dm_btree_remove() may fail due to IO read error (e.g. read the content of origin block fails during shadowing), and the value of shadow_spine::root is uninitialized, but the uninitialized value is still assign to new_root in the end of dm_btree_remove(). For dm-thin, the value of pmd->details_root or pmd->root will become an uninitialized value, so if trying to read details_info tree again out-of-bound memory may occur as showed below: general protection fault, probably for non-canonical address 0x3fdcb14c8d7520 CPU: 4 PID: 515 Comm: dmsetup Not tainted 5.13.0-rc6 Hardware name: QEMU Standard PC RIP: 0010:metadata_ll_load_ie+0x14/0x30 Call Trace: sm_metadata_count_is_more_than_one+0xb9/0xe0 dm_tm_shadow_block+0x52/0x1c0 shadow_step+0x59/0xf0 remove_raw+0xb2/0x170 dm_btree_remove+0xf4/0x1c0 dm_pool_delete_thin_device+0xc3/0x140 pool_message+0x218/0x2b0 target_message+0x251/0x290 ctl_ioctl+0x1c4/0x4d0 dm_ctl_ioctl+0xe/0x20 __x64_sys_ioctl+0x7b/0xb0 do_syscall_64+0x40/0xb0 entry_SYSCALL_64_after_hwframe+0x44/0xae Fixing it by only assign new_root when removal succeeds
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2021-47343 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: dm btree remove: assign new_root only when removal succeeds
92 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel as a component of Red Hat Enterprise Linux 6
  • kernel-abi-whitelists as a component of Red Hat Enterprise Linux 6
  • kernel-bootwrapper as a component of Red Hat Enterprise Linux 6
  • kernel-debug as a component of Red Hat Enterprise Linux 6
  • kernel-debug-devel as a component of Red Hat Enterprise Linux 6
  • kernel-devel as a component of Red Hat Enterprise Linux 6
  • kernel-doc as a component of Red Hat Enterprise Linux 6
  • kernel-firmware as a component of Red Hat Enterprise Linux 6
  • kernel-headers as a component of Red Hat Enterprise Linux 6
  • kernel-kdump as a component of Red Hat Enterprise Linux 6
  • kernel-kdump-devel as a component of Red Hat Enterprise Linux 6
  • kernel.src as a component of Red Hat Enterprise Linux 6
Summary
A vulnerability was found in the Linux kernel's device-mapper subsystem, where the dm_btree_remove function could assign an uninitialized value to new_root if a tree removal operation failed. This issue could result in reading invalid memory locations, leading to system instability or crashes.
Remediation
Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.
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-34348

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 actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 93 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: dm btree remove: assign new_root only when removal succeeds remove_raw() in dm_btree_remove() may fail due to IO read error (e.g. read the content of origin block fails during shadowing), and the value of shadow_spine::root is uninitialized, but the uninitialized value is still assign to new_root in the end of dm_btree_remove(). For dm-thin, the value of pmd->details_root or pmd->root will become an uninitialized value, so if trying to read details_info tree again out-of-bound memory may occur as showed below: general protection fault, probably for non-canonical address 0x3fdcb14c8d7520 CPU: 4 PID: 515 Comm: dmsetup Not tainted 5.13.0-rc6 Hardware name: QEMU Standard PC RIP: 0010:metadata_ll_load_ie+0x14/0x30 Call Trace: sm_metadata_count_is_more_than_one+0xb9/0xe0 dm_tm_shadow_block+0x52/0x1c0 shadow_step+0x59/0xf0 remove_raw+0xb2/0x170 dm_btree_remove+0xf4/0x1c0 dm_pool_delete_thin_device+0xc3/0x140 pool_message+0x218/0x2b0 target_message+0x251/0x290 ctl_ioctl+0x1c4/0x4d0 dm_ctl_ioctl+0xe/0x20 __x64_sys_ioctl+0x7b/0xb0 do_syscall_64+0x40/0xb0 entry_SYSCALL_64_after_hwframe+0x44/0xae Fixing it by only assign new_root when removal succeeds

What

In the Linux kernel, the following vulnerability has been resolved: dm btree remove: assign new_root only when removal succeeds remove_raw() in dm_btree_remove() may fail due to IO read error (e.g. read the content of origin block fails during shadowing), and the value of shadow_spine::root is uninitialized, but the uninitialized value is still assign to new_root in the end of dm_btree_remove(). For dm-thin, the value of pmd->details_root or pmd->root will become an uninitialized value, so if trying to read details_info tree again out-of-bound memory may occur as showed below: general protection fault, probably for non-canonical address 0x3fdcb14c8d7520 CPU: 4 PID: 515 Comm: dmsetup Not tainted 5.13.0-rc6 Hardware name: QEMU Standard PC RIP: 0010:metadata_ll_load_ie+0x14/0x30 Call Trace: sm_metadata_count_is_more_than_one+0xb9/0xe0 dm_tm_shadow_block+0x52/0x1c0 shadow_step+0x59/0xf0 remove_raw+0xb2/0x170 dm_btree_remove+0xf4/0x1c0 dm_pool_delete_thin_device+0xc3/0x140 pool_message+0x218/0x2b0 target_message+0x251/0x290 ctl_ioctl+0x1c4/0x4d0 dm_ctl_ioctl+0xe/0x20 __x64_sys_ioctl+0x7b/0xb0 do_syscall_64+0x40/0xb0 entry_SYSCALL_64_after_hwframe+0x44/0xae Fixing it by only assign new_root when removal succeeds

Why

The product initializes or sets a resource with a default that is intended to be changed by the product's installer, administrator, or maintainer, but the default is not secure.

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: dm btree remove: assign new_root only when removal succeeds remove_raw() in dm_btree_remove() may fail due to IO read error (e.g. read the content of origin block fails during shadowing), and the value of shadow_spine::root is uninitialized, but the uninitialized value is still assign to new_root in the end of dm_btree_remove(). For dm-thin, the value of pmd->details_root or pmd->root will become an uninitialized value, so if trying to read details_info tree again out-of-bound memory may occur as showed below: general protection fault, probably for non-canonical address 0x3fdcb14c8d7520 CPU: 4 PID: 515 Comm: dmsetup Not tainted 5.13.0-rc6 Hardware name: QEMU Standard PC RIP: 0010:metadata_ll_load_ie+0x14/0x30 Call Trace: sm_metadata_count_is_more_than_one+0xb9/0xe0 dm_tm_shadow_block+0x52/0x1c0 shadow_step+0x59/0xf0 remove_raw+0xb2/0x170 dm_btree_remove+0xf4/0x1c0 dm_pool_delete_thin_device+0xc3/0x140 pool_message+0x218/0x2b0 target_message+0x251/0x290 ctl_ioctl+0x1c4/0x4d0 dm_ctl_ioctl+0xe/0x20 __x64_sys_ioctl+0x7b/0xb0 do_syscall_64+0x40/0xb0 entry_SYSCALL_64_after_hwframe+0x44/0xae Fixing it by only assign new_root when removal succeeds

Why

The product initializes or sets a resource with a default that is intended to be changed by the product's installer, administrator, or maintainer, but the default is not secure.

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 → Initialization of a Resource with an Insecure Default → 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-1188 ↗

CWE-1188: Initialization of a Resource with an Insecure Default. The product initializes or sets a resource with a default that is intended to be changed by the product's installer, administrator, or maintainer, but the default is not secure.

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:H/I:H/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.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.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-1188
A

Official authority intelligence

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

Cyber Security Agency of Singapore · English · CSA-SB-20240522Security Bulletin 22 May 2024

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

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1057Multiples vulnérabilités dans les produits VMware

d?id=CVE-2021-47237 Référence CVE CVE-2021-47239 https://www.cve.org/CVERecord?id=CVE-2021-47239 Référence CVE CVE-2021-47250 https://www.cve.org/CVERecord?id=CVE-2021-47250 Référence CVE CVE-2021-47251 https://www.cve.org/CVERecord?id=CVE-2021-47251 Référence CVE CVE-2021-47261 https://www.cve.org/CVERecord?id=CVE-2021-47261 Référence CVE CVE-2021-47266 https://www.cve.org/CVERecord?id=CVE-2021-47266 Référence CVE CVE-2021-47316 https://www.cve.org/CVERecord?id=CVE-2021-47316 Référence CVE CVE-2021-47318 https://www.cve.org/CVERecord?id=CVE-2021-47318 Référence CVE CVE-2021-47325 https://www.cve.org/CVERecord?id=CVE-2021-47325 Référence CVE CVE-2021-47343 https://www.cve.org/CVERecord?id=CVE-2021-47343 Référence CVE CVE-2021-47346 https://www.cve.org/CVERecord?id=CVE-2021-47346 Référence CVE CVE-2021-47349 https://www.cve.org/CVERecord?id=CVE-2021-47349 Référence CVE CVE-2021-47360 https://www.cve.org/CVERecord?id=CVE-2021-47360 Référence CVE CVE-2021-47365 https://www.cve.org/CVERecord?id=CVE-2021-47365 Référence CVE CVE-2021-47373 https://www.cve.org/CVERecord?id=CVE-2021-47373 Référence CVE CVE-2021-47393 https://www.cve.org/CVERecord?id=CVE-2021-47393 Référence CVE CVE-2021-47398 https://www.cve.org/CVERecord?id=CVE-2021-47398 Référence CVE CVE-2021-47404 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2021-47329 Référence CVE CVE-2021-47330 https://www.cve.org/CVERecord?id=CVE-2021-47330 Référence CVE CVE-2021-47332 https://www.cve.org/CVERecord?id=CVE-2021-47332 Référence CVE CVE-2021-47333 https://www.cve.org/CVERecord?id=CVE-2021-47333 Référence CVE CVE-2021-47334 https://www.cve.org/CVERecord?id=CVE-2021-47334 Référence CVE CVE-2021-47337 https://www.cve.org/CVERecord?id=CVE-2021-47337 Référence CVE CVE-2021-47338 https://www.cve.org/CVERecord?id=CVE-2021-47338 Référence CVE CVE-2021-47340 https://www.cve.org/CVERecord?id=CVE-2021-47340 Référence CVE CVE-2021-47341 https://www.cve.org/CVERecord?id=CVE-2021-47341 Référence CVE CVE-2021-47343 https://www.cve.org/CVERecord?id=CVE-2021-47343 Référence CVE CVE-2021-47344 https://www.cve.org/CVERecord?id=CVE-2021-47344 Référence CVE CVE-2021-47345 https://www.cve.org/CVERecord?id=CVE-2021-47345 Référence CVE CVE-2021-47347 https://www.cve.org/CVERecord?id=CVE-2021-47347 Référence CVE CVE-2021-47348 https://www.cve.org/CVERecord?id=CVE-2021-47348 Référence CVE CVE-2021-47350 https://www.cve.org/CVERecord?id=CVE-2021-47350 Référence CVE CVE-2021-47352 https://www.cve.org/CVERecord?id=CVE-2021-47352 Référence CVE CVE-2021-47353 https://www.cve.org/CVERecord?id=CVE-2021-47353 Référence CVE CVE-2021-47354 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2021-47329 Référence CVE CVE-2021-47330 https://www.cve.org/CVERecord?id=CVE-2021-47330 Référence CVE CVE-2021-47332 https://www.cve.org/CVERecord?id=CVE-2021-47332 Référence CVE CVE-2021-47333 https://www.cve.org/CVERecord?id=CVE-2021-47333 Référence CVE CVE-2021-47334 https://www.cve.org/CVERecord?id=CVE-2021-47334 Référence CVE CVE-2021-47337 https://www.cve.org/CVERecord?id=CVE-2021-47337 Référence CVE CVE-2021-47338 https://www.cve.org/CVERecord?id=CVE-2021-47338 Référence CVE CVE-2021-47340 https://www.cve.org/CVERecord?id=CVE-2021-47340 Référence CVE CVE-2021-47341 https://www.cve.org/CVERecord?id=CVE-2021-47341 Référence CVE CVE-2021-47343 https://www.cve.org/CVERecord?id=CVE-2021-47343 Référence CVE CVE-2021-47344 https://www.cve.org/CVERecord?id=CVE-2021-47344 Référence CVE CVE-2021-47345 https://www.cve.org/CVERecord?id=CVE-2021-47345 Référence CVE CVE-2021-47347 https://www.cve.org/CVERecord?id=CVE-2021-47347 Référence CVE CVE-2021-47348 https://www.cve.org/CVERecord?id=CVE-2021-47348 Référence CVE CVE-2021-47350 https://www.cve.org/CVERecord?id=CVE-2021-47350 Référence CVE CVE-2021-47352 https://www.cve.org/CVERecord?id=CVE-2021-47352 Référence CVE CVE-2021-47353 https://www.cve.org/CVERecord?id=CVE-2021-47353 Référence CVE CVE-2021-47354 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2021-021855Linux の 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.
Fix availability varies by product
Affected
Fixed
Linux: < 3.2, 4.4.276 ≤ 4.4.*, 4.9.276 ≤ 4.9.*, 4.14.240 ≤ 4.14.*, 4.19.198 ≤ 4.19.*, 5.4.133 ≤ 5.4.*, 5.10.51 ≤ 5.10.*, 5.12.18 ≤ 5.12.*, 5.13.3 ≤ 5.13.*, 5.14 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 21 May 2024 · Last source change 5 Aug 2026, 08:47 UTC · CWE-1188 · Initialization of a Resource with an Insecure Default

CVE recordCVE.org · 5.2
CVSS sourceCNA
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-34348
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

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-34348↗Vendor CSAF · SUSE Product Security Team↗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-47343 · cve.blacktree.nl