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

tipc: wait and exit until all work queues are done

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 49 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.19% 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 49 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 6 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-47163 · CSAF 2.0 · revision 65 · interimSUSE Product Security TeamCVE-2021-47163
192 known affected

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

  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 12 SP5
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 12 SP5
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • 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
Summary
In the Linux kernel, the following vulnerability has been resolved: tipc: wait and exit until all work queues are done On some host, a crash could be triggered simply by repeating these commands several times: # modprobe tipc # tipc bearer enable media udp name UDP1 localip 127.0.0.1 # rmmod tipc [] BUG: unable to handle kernel paging request at ffffffffc096bb00 [] Workqueue: events 0xffffffffc096bb00 [] Call Trace: [] ? process_one_work+0x1a7/0x360 [] ? worker_thread+0x30/0x390 [] ? create_worker+0x1a0/0x1a0 [] ? kthread+0x116/0x130 [] ? kthread_flush_work_fn+0x10/0x10 [] ? ret_from_fork+0x35/0x40 When removing the TIPC module, the UDP tunnel sock will be delayed to release in a work queue as sock_release() can't be done in rtnl_lock(). If the work queue is schedule to run after the TIPC module is removed, kernel will crash as the work queue function cleanup_beareri() code no longer exists when trying to invoke it. To fix it, this patch introduce a member wq_count in tipc_net to track the numbers of work queues in schedule, and wait and exit until all work queues are done in tipc_exit_net().
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2021-47163 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: tipc: wait and exit until all work queues are done
48 known affected

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

  • bpftool as a component of Red Hat Enterprise Linux 8
  • kernel as a component of Red Hat Enterprise Linux 8
  • kernel-abi-stablelists as a component of Red Hat Enterprise Linux 8
  • kernel-abi-whitelists as a component of Red Hat Enterprise Linux 8
  • kernel-core as a component of Red Hat Enterprise Linux 8
  • kernel-cross-headers as a component of Red Hat Enterprise Linux 8
  • kernel-debug as a component of Red Hat Enterprise Linux 8
  • kernel-debug-core as a component of Red Hat Enterprise Linux 8
  • kernel-debug-devel as a component of Red Hat Enterprise Linux 8
  • kernel-debug-modules as a component of Red Hat Enterprise Linux 8
  • kernel-debug-modules-extra as a component of Red Hat Enterprise Linux 8
  • kernel-debug-modules-internal as a component of Red Hat Enterprise Linux 8
Summary
This linux kernel vulnerability occurs in the TIPC (Transparent Inter-Process Communication) networking module, specifically concerning how background tasks are handled during module removal. The issue arises when the TIPC module is being unloaded while a UDP tunnel socket is still delayed for release within a scheduled work queue. If this delayed cleanup task executes after the module has already been removed from the system, the kernel attempts to invoke a cleanup function that no longer exists in memory, resulting in a paging request failure and a subsequent kernel crash. Patched kernel versions resolve the issue by introducing a tracking mechanism that forces the system to explicitly wait until all pending work queues have successfully finished their tasks before allowing the TIPC module to safely exit.
Remediation
Fix deferred
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-33811

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 49 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: tipc: wait and exit until all work queues are done On some host, a crash could be triggered simply by repeating these commands several times: # modprobe tipc # tipc bearer enable media udp name UDP1 localip 127.0.0.1 # rmmod tipc [] BUG: unable to handle kernel paging request at ffffffffc096bb00 [] Workqueue: events 0xffffffffc096bb00 [] Call Trace: [] ? process_one_work+0x1a7/0x360 [] ? worker_thread+0x30/0x390 [] ? create_worker+0x1a0/0x1a0 [] ? kthread+0x116/0x130 [] ? kthread_flush_work_fn+0x10/0x10 [] ? ret_from_fork+0x35/0x40 When removing the TIPC module, the UDP tunnel sock will be delayed to release in a work queue as sock_release() can't be done in rtnl_lock(). If the work queue is schedule to run after the TIPC module is removed, kernel will crash as the work queue function cleanup_beareri() code no longer exists when trying to invoke it. To fix it, this patch introduce a member wq_count in tipc_net to track the numbers of work queues in schedule, and wait and exit until all work queues are done in tipc_exit_net().

What

In the Linux kernel, the following vulnerability has been resolved: tipc: wait and exit until all work queues are done On some host, a crash could be triggered simply by repeating these commands several times: # modprobe tipc # tipc bearer enable media udp name UDP1 localip 127.0.0.1 # rmmod tipc [] BUG: unable to handle kernel paging request at ffffffffc096bb00 [] Workqueue: events 0xffffffffc096bb00 [] Call Trace: [] ? process_one_work+0x1a7/0x360 [] ? worker_thread+0x30/0x390 [] ? create_worker+0x1a0/0x1a0 [] ? kthread+0x116/0x130 [] ? kthread_flush_work_fn+0x10/0x10 [] ? ret_from_fork+0x35/0x40 When removing the TIPC module, the UDP tunnel sock will be delayed to release in a work queue as sock_release() can't be done in rtnl_lock(). If the work queue is schedule to run after the TIPC module is removed, kernel will crash as the work queue function cleanup_beareri() code no longer exists when trying to invoke it. To fix it, this patch introduce a member wq_count in tipc_net to track the numbers of work queues in schedule, and wait and exit until all work queues are done in tipc_exit_net().

Why

The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.

What

In the Linux kernel, the following vulnerability has been resolved: tipc: wait and exit until all work queues are done On some host, a crash could be triggered simply by repeating these commands several times: # modprobe tipc # tipc bearer enable media udp name UDP1 localip 127.0.0.1 # rmmod tipc [] BUG: unable to handle kernel paging request at ffffffffc096bb00 [] Workqueue: events 0xffffffffc096bb00 [] Call Trace: [] ? process_one_work+0x1a7/0x360 [] ? worker_thread+0x30/0x390 [] ? create_worker+0x1a0/0x1a0 [] ? kthread+0x116/0x130 [] ? kthread_flush_work_fn+0x10/0x10 [] ? ret_from_fork+0x35/0x40 When removing the TIPC module, the UDP tunnel sock will be delayed to release in a work queue as sock_release() can't be done in rtnl_lock(). If the work queue is schedule to run after the TIPC module is removed, kernel will crash as the work queue function cleanup_beareri() code no longer exists when trying to invoke it. To fix it, this patch introduce a member wq_count in tipc_net to track the numbers of work queues in schedule, and wait and exit until all work queues are done in tipc_exit_net().

Why

The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.

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 → Improper Locking → disrupt the affected service
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-667 ↗

CWE-667: Improper Locking. The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

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.
Denial of serviceCWE-667
A

Official authority intelligence

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

BSI · German · WID-SEC-2024-0699Linux-Kernel: Mehrere Schwachstellen ermöglichen Denial of Service und unspezifische Angriffe

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen und einen nicht spezifizierten Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240327Security Bulletin 27 Mar 2024

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

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

su-202501675-1 Bulletin de sécurité SUSE SUSE-SU-2025:01676-1 du 22 mai 2025 https://www.suse.com/support/update/announcement/2025/suse-su-202501676-1 Bulletin de sécurité SUSE SUSE-SU-2025:01677-1 du 22 mai 2025 https://www.suse.com/support/update/announcement/2025/suse-su-202501677-1 Bulletin de sécurité SUSE SUSE-SU-2025:01682-1 du 22 mai 2025 https://www.suse.com/support/update/announcement/2025/suse-su-202501682-1 Bulletin de sécurité SUSE SUSE-SU-2025:01683-1 du 22 mai 2025 https://www.suse.com/support/update/announcement/2025/suse-su-202501683-1 Référence CVE CVE-2020-36789 https://www.cve.org/CVERecord?id=CVE-2020-36789 Référence CVE CVE-2021-47163 https://www.cve.org/CVERecord?id=CVE-2021-47163 Référence CVE CVE-2021-47659 https://www.cve.org/CVERecord?id=CVE-2021-47659 Référence CVE CVE-2021-47668 https://www.cve.org/CVERecord?id=CVE-2021-47668 Référence CVE CVE-2021-47669 https://www.cve.org/CVERecord?id=CVE-2021-47669 Référence CVE CVE-2021-47670 https://www.cve.org/CVERecord?id=CVE-2021-47670 Référence CVE CVE-2021-47671 https://www.cve.org/CVERecord?id=CVE-2021-47671 Référence CVE CVE-2022-48933 https://www.cve.org/CVERecord?id=CVE-2022-48933 Référence CVE CVE-2022-49044 https://www.cve.org/CVERecord?id=CVE-2022-49044 Référence CVE CVE-2022-49055 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0387Multiples vulnérabilités dans le noyau Linux d'Ubuntu

untu USN-7496-5 du 07 mai 2025 https://ubuntu.com/security/notices/USN-7496-5 Bulletin de sécurité Ubuntu USN-7498-1 du 07 mai 2025 https://ubuntu.com/security/notices/USN-7498-1 Bulletin de sécurité Ubuntu USN-7499-1 du 07 mai 2025 https://ubuntu.com/security/notices/USN-7499-1 Bulletin de sécurité Ubuntu USN-7500-1 du 07 mai 2025 https://ubuntu.com/security/notices/USN-7500-1 Bulletin de sécurité Ubuntu USN-7500-2 du 07 mai 2025 https://ubuntu.com/security/notices/USN-7500-2 Référence CVE CVE-2021-47119 https://www.cve.org/CVERecord?id=CVE-2021-47119 Référence CVE CVE-2021-47150 https://www.cve.org/CVERecord?id=CVE-2021-47150 Référence CVE CVE-2021-47163 https://www.cve.org/CVERecord?id=CVE-2021-47163 Référence CVE CVE-2021-47191 https://www.cve.org/CVERecord?id=CVE-2021-47191 Référence CVE CVE-2021-47219 https://www.cve.org/CVERecord?id=CVE-2021-47219 Référence CVE CVE-2022-0995 https://www.cve.org/CVERecord?id=CVE-2022-0995 Référence CVE CVE-2023-52458 https://www.cve.org/CVERecord?id=CVE-2023-52458 Référence CVE CVE-2023-52664 https://www.cve.org/CVERecord?id=CVE-2023-52664 Référence CVE CVE-2023-52741 https://www.cve.org/CVERecord?id=CVE-2023-52741 Référence CVE CVE-2023-52927 https://www.cve.org/CVERecord?id=CVE-2023-52927 Référence CVE CVE-2024-26689 https://www.cve.org/CVERecord?id=CV

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

de service à distance et une atteinte à la confidentialité des données. 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é SUSE SUSE-SU-2025:0034-1 du 08 janvier 2025 https://www.suse.com/support/update/announcement/2025/suse-su-20250034-1 Bulletin de sécurité SUSE SUSE-SU-2025:0035-1 du 08 janvier 2025 https://www.suse.com/support/update/announcement/2025/suse-su-20250035-1 Référence CVE CVE-2021-46936 https://www.cve.org/CVERecord?id=CVE-2021-46936 Référence CVE CVE-2021-47162 https://www.cve.org/CVERecord?id=CVE-2021-47162 Référence CVE CVE-2021-47163 https://www.cve.org/CVERecord?id=CVE-2021-47163 Référence CVE CVE-2021-47416 https://www.cve.org/CVERecord?id=CVE-2021-47416 Référence CVE CVE-2021-47612 https://www.cve.org/CVERecord?id=CVE-2021-47612 Référence CVE CVE-2022-48788 https://www.cve.org/CVERecord?id=CVE-2022-48788 Référence CVE CVE-2022-48789 https://www.cve.org/CVERecord?id=CVE-2022-48789 Référence CVE CVE-2022-48790 https://www.cve.org/CVERecord?id=CVE-2022-48790 Référence CVE CVE-2022-48809 https://www.cve.org/CVERecord?id=CVE-2022-48809 Référence CVE CVE-2022-48853 https://www.cve.org/CVERecord?id=CVE-2022-48853 Référence CVE CVE-2022-48946 https://www.cve.org/CVERecord?id=

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

-1 Bulletin de sécurité SUSE SUSE-SU-2024:4218-1 du 05 décembre 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20244218-1 Bulletin de sécurité SUSE SUSE-SU-2024:4219-1 du 05 décembre 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20244219-1 Bulletin de sécurité SUSE SUSE-SU-2024:4220-1 du 05 décembre 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20244220-1 Bulletin de sécurité SUSE SUSE-SU-2024:4221-1 du 05 décembre 2024 https://www.suse.com/support/update/announcement/2024/suse-su-20244221-1 Référence CVE CVE-2021-46936 https://www.cve.org/CVERecord?id=CVE-2021-46936 Référence CVE CVE-2021-47163 https://www.cve.org/CVERecord?id=CVE-2021-47163 Référence CVE CVE-2021-47291 https://www.cve.org/CVERecord?id=CVE-2021-47291 Référence CVE CVE-2021-47378 https://www.cve.org/CVERecord?id=CVE-2021-47378 Référence CVE CVE-2021-47383 https://www.cve.org/CVERecord?id=CVE-2021-47383 Référence CVE CVE-2021-47402 https://www.cve.org/CVERecord?id=CVE-2021-47402 Référence CVE CVE-2021-47416 https://www.cve.org/CVERecord?id=CVE-2021-47416 Référence CVE CVE-2021-47517 https://www.cve.org/CVERecord?id=CVE-2021-47517 Référence CVE CVE-2021-47534 https://www.cve.org/CVERecord?id=CVE-2021-47534 Référence CVE CVE-2021-47589 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2021-021664Linux の 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: < 4.1, 5.4.124 ≤ 5.4.*, 5.10.42 ≤ 5.10.*, 5.12.9 ≤ 5.12.*, 5.13 ≤ *
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 25 Mar 2024 · Last source change 5 Aug 2026, 08:46 UTC · CWE-667 · Improper Locking

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-33811
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-33811↗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-47163 · cve.blacktree.nl