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

tracing: Restructure trace_clock_global() to never block

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 1 structured product or package state 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 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.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 1 structured product or package state 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.10.38-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.10.38-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.10.38-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.10.38-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.

1 current
CVE-2021-46939 · CSAF 2.0 · revision 58 · interimSUSE Product Security TeamCVE-2021-46939
129 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 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
  • 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
Summary
In the Linux kernel, the following vulnerability has been resolved: tracing: Restructure trace_clock_global() to never block It was reported that a fix to the ring buffer recursion detection would cause a hung machine when performing suspend / resume testing. The following backtrace was extracted from debugging that case: Call Trace: trace_clock_global+0x91/0xa0 __rb_reserve_next+0x237/0x460 ring_buffer_lock_reserve+0x12a/0x3f0 trace_buffer_lock_reserve+0x10/0x50 __trace_graph_return+0x1f/0x80 trace_graph_return+0xb7/0xf0 ? trace_clock_global+0x91/0xa0 ftrace_return_to_handler+0x8b/0xf0 ? pv_hash+0xa0/0xa0 return_to_handler+0x15/0x30 ? ftrace_graph_caller+0xa0/0xa0 ? trace_clock_global+0x91/0xa0 ? __rb_reserve_next+0x237/0x460 ? ring_buffer_lock_reserve+0x12a/0x3f0 ? trace_event_buffer_lock_reserve+0x3c/0x120 ? trace_event_buffer_reserve+0x6b/0xc0 ? trace_event_raw_event_device_pm_callback_start+0x125/0x2d0 ? dpm_run_callback+0x3b/0xc0 ? pm_ops_is_empty+0x50/0x50 ? platform_get_irq_byname_optional+0x90/0x90 ? trace_device_pm_callback_start+0x82/0xd0 ? dpm_run_callback+0x49/0xc0 With the following RIP: RIP: 0010:native_queued_spin_lock_slowpath+0x69/0x200 Since the fix to the recursion detection would allow a single recursion to happen while tracing, this lead to the trace_clock_global() taking a spin lock and then trying to take it again: ring_buffer_lock_reserve() { trace_clock_global() { arch_spin_lock() { queued_spin_lock_slowpath() { /* lock taken */ (something else gets traced by function graph tracer) ring_buffer_lock_reserve() { trace_clock_global() { arch_spin_lock() { queued_spin_lock_slowpath() { /* DEAD LOCK! */ Tracing should *never* block, as it can lead to strange lockups like the above. Restructure the trace_clock_global() code to instead of simply taking a lock to update the recorded "prev_time" simply use it, as two events happening on two different CPUs that calls this at the same time, really doesn't matter which one goes first. Use a trylock to grab the lock for updating the prev_time, and if it fails, simply try again the next time. If it failed to be taken, that means something else is already updating it. Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=212761
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
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-33587

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

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 1 structured product or package state 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: tracing: Restructure trace_clock_global() to never block It was reported that a fix to the ring buffer recursion detection would cause a hung machine when performing suspend / resume testing. The following backtrace was extracted from debugging that case: Call Trace: trace_clock_global+0x91/0xa0 __rb_reserve_next+0x237/0x460 ring_buffer_lock_reserve+0x12a/0x3f0 trace_buffer_lock_reserve+0x10/0x50 __trace_graph_return+0x1f/0x80 trace_graph_return+0xb7/0xf0 ? trace_clock_global+0x91/0xa0 ftrace_return_to_handler+0x8b/0xf0 ? pv_hash+0xa0/0xa0 return_to_handler+0x15/0x30 ? ftrace_graph_caller+0xa0/0xa0 ? trace_clock_global+0x91/0xa0 ? __rb_reserve_next+0x237/0x460 ? ring_buffer_lock_reserve+0x12a/0x3f0 ? trace_event_buffer_lock_reserve+0x3c/0x120 ? trace_event_buffer_reserve+0x6b/0xc0 ? trace_event_raw_event_device_pm_callback_start+0x125/0x2d0 ? dpm_run_callback+0x3b/0xc0 ? pm_ops_is_empty+0x50/0x50 ? platform_get_irq_byname_optional+0x90/0x90 ? trace_device_pm_callback_start+0x82/0xd0 ? dpm_run_callback+0x49/0xc0 With the following RIP: RIP: 0010:native_queued_spin_lock_slowpath+0x69/0x200 Since the fix to the recursion detection would allow a single recursion to happen while tracing, this lead to the trace_clock_global() taking a spin lock and then trying to take it again: ring_buffer_lock_reserve() { trace_clock_global() { arch_spin_lock() { queued_spin_lock_slowpath() { /* lock taken */ (something else gets traced by function graph tracer) ring_buffer_lock_reserve() { trace_clock_global() { arch_spin_lock() { queued_spin_lock_slowpath() { /* DEAD LOCK! */ Tracing should *never* block, as it can lead to strange lockups like the above. Restructure the trace_clock_global() code to instead of simply taking a lock to update the recorded "prev_time" simply use it, as two events happening on two different CPUs that calls this at the same time, really doesn't matter which one goes first. Use a trylock to grab the lock for updating the prev_time, and if it fails, simply try again the next time. If it failed to be taken, that means something else is already updating it. Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=212761

What

In the Linux kernel, the following vulnerability has been resolved: tracing: Restructure trace_clock_global() to never block It was reported that a fix to the ring buffer recursion detection would cause a hung machine when performing suspend / resume testing. The following backtrace was extracted from debugging that case: Call Trace: trace_clock_global+0x91/0xa0 __rb_reserve_next+0x237/0x460 ring_buffer_lock_reserve+0x12a/0x3f0 trace_buffer_lock_reserve+0x10/0x50 __trace_graph_return+0x1f/0x80 trace_graph_return+0xb7/0xf0 ? trace_clock_global+0x91/0xa0 ftrace_return_to_handler+0x8b/0xf0 ? pv_hash+0xa0/0xa0 return_to_handler+0x15/0x30 ? ftrace_graph_caller+0xa0/0xa0 ? trace_clock_global+0x91/0xa0 ? __rb_reserve_next+0x237/0x460 ? ring_buffer_lock_reserve+0x12a/0x3f0 ? trace_event_buffer_lock_reserve+0x3c/0x120 ? trace_event_buffer_reserve+0x6b/0xc0 ? trace_event_raw_event_device_pm_callback_start+0x125/0x2d0 ? dpm_run_callback+0x3b/0xc0 ? pm_ops_is_empty+0x50/0x50 ? platform_get_irq_byname_optional+0x90/0x90 ? trace_device_pm_callback_start+0x82/0xd0 ? dpm_run_callback+0x49/0xc0 With the following RIP: RIP: 0010:native_queued_spin_lock_slowpath+0x69/0x200 Since the fix to the recursion detection would allow a single recursion to happen while tracing, this lead to the trace_clock_global() taking a spin lock and then trying to take it again: ring_buffer_lock_reserve() { trace_clock_global() { arch_spin_lock() { queued_spin_lock_slowpath() { /* lock taken */ (something else gets traced by function graph tracer) ring_buffer_lock_reserve() { trace_clock_global() { arch_spin_lock() { queued_spin_lock_slowpath() { /* DEAD LOCK! */ Tracing should *never* block, as it can lead to strange lockups like the above. Restructure the trace_clock_global() code to instead of simply taking a lock to update the recorded "prev_time" simply use it, as two events happening on two different CPUs that calls this at the same time, really doesn't matter which one goes first. Use a trylock to grab the lock for updating the prev_time, and if it fails, simply try again the next time. If it failed to be taken, that means something else is already updating it. Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=212761

Why

The product does not properly control the allocation and maintenance of a limited resource.

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: tracing: Restructure trace_clock_global() to never block It was reported that a fix to the ring buffer recursion detection would cause a hung machine when performing suspend / resume testing. The following backtrace was extracted from debugging that case: Call Trace: trace_clock_global+0x91/0xa0 __rb_reserve_next+0x237/0x460 ring_buffer_lock_reserve+0x12a/0x3f0 trace_buffer_lock_reserve+0x10/0x50 __trace_graph_return+0x1f/0x80 trace_graph_return+0xb7/0xf0 ? trace_clock_global+0x91/0xa0 ftrace_return_to_handler+0x8b/0xf0 ? pv_hash+0xa0/0xa0 return_to_handler+0x15/0x30 ? ftrace_graph_caller+0xa0/0xa0 ? trace_clock_global+0x91/0xa0 ? __rb_reserve_next+0x237/0x460 ? ring_buffer_lock_reserve+0x12a/0x3f0 ? trace_event_buffer_lock_reserve+0x3c/0x120 ? trace_event_buffer_reserve+0x6b/0xc0 ? trace_event_raw_event_device_pm_callback_start+0x125/0x2d0 ? dpm_run_callback+0x3b/0xc0 ? pm_ops_is_empty+0x50/0x50 ? platform_get_irq_byname_optional+0x90/0x90 ? trace_device_pm_callback_start+0x82/0xd0 ? dpm_run_callback+0x49/0xc0 With the following RIP: RIP: 0010:native_queued_spin_lock_slowpath+0x69/0x200 Since the fix to the recursion detection would allow a single recursion to happen while tracing, this lead to the trace_clock_global() taking a spin lock and then trying to take it again: ring_buffer_lock_reserve() { trace_clock_global() { arch_spin_lock() { queued_spin_lock_slowpath() { /* lock taken */ (something else gets traced by function graph tracer) ring_buffer_lock_reserve() { trace_clock_global() { arch_spin_lock() { queued_spin_lock_slowpath() { /* DEAD LOCK! */ Tracing should *never* block, as it can lead to strange lockups like the above. Restructure the trace_clock_global() code to instead of simply taking a lock to update the recorded "prev_time" simply use it, as two events happening on two different CPUs that calls this at the same time, really doesn't matter which one goes first. Use a trylock to grab the lock for updating the prev_time, and if it fails, simply try again the next time. If it failed to be taken, that means something else is already updating it. Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=212761

Why

The product does not properly control the allocation and maintenance of a limited resource.

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 → Uncontrolled Resource Consumption → 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-400 ↗

CWE-400: Uncontrolled Resource Consumption. The product does not properly control the allocation and maintenance of a limited resource.

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-400
A

Official authority intelligence

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

BSI · German · WID-SEC-2024-1913Red Hat OpenShift Container Platform: Mehrere Schwachstellen

Ein entfernter anonymer oder lokaler Angreifer kann mehrere Schwachstellen in Red Hat OpenShift Container Platform ausnutzen, um seine Privilegien zu erhöhen, beliebigen Code auszuführen, einen Denial-of-Service-Zustand zu erzeugen, vertrauliche Informationen offenzulegen, Dateien und Daten zu manipulieren oder Sicherheitsmaßnahmen zu umgehen.

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-38296 Référence CVE CVE-2021-41182 https://www.cve.org/CVERecord?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=

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

5.0 UP10 IF02 Résumé De multiples vulnérabilités ont été découvertes dans les produits Juniper Networks. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire, une atteinte à la confidentialité des données et une atteinte à l'intégrité 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é Juniper Networks JSA93839 du 24 janvier 2025 https://supportportal.juniper.net/s/article/On-Demand-JSA-Series-Multiple-vulnerabilities-resolved-in-Juniper-Secure-Analytics-in-7-5-0-UP10-IF02 Référence CVE CVE-2021-46939 https://www.cve.org/CVERecord?id=CVE-2021-46939 Référence CVE CVE-2021-47018 https://www.cve.org/CVERecord?id=CVE-2021-47018 Référence CVE CVE-2021-47257 https://www.cve.org/CVERecord?id=CVE-2021-47257 Référence CVE CVE-2021-47284 https://www.cve.org/CVERecord?id=CVE-2021-47284 Référence CVE CVE-2021-47304 https://www.cve.org/CVERecord?id=CVE-2021-47304 Référence CVE CVE-2021-47373 https://www.cve.org/CVERecord?id=CVE-2021-47373 Référence CVE CVE-2021-47408 https://www.cve.org/CVERecord?id=CVE-2021-47408 Référence CVE CVE-2021-47461 https://www.cve.org/CVERecord?id=CVE-2021-47461 Référence CVE CVE-2021-47468 https://www.cve.org/CVERecord?id=

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

ecord?id=CVE-2019-20444 Référence CVE CVE-2019-20445 https://www.cve.org/CVERecord?id=CVE-2019-20445 Référence CVE CVE-2020-7238 https://www.cve.org/CVERecord?id=CVE-2020-7238 Référence CVE CVE-2020-7676 https://www.cve.org/CVERecord?id=CVE-2020-7676 Référence CVE CVE-2021-21290 https://www.cve.org/CVERecord?id=CVE-2021-21290 Référence CVE CVE-2021-21295 https://www.cve.org/CVERecord?id=CVE-2021-21295 Référence CVE CVE-2021-32036 https://www.cve.org/CVERecord?id=CVE-2021-32036 Référence CVE CVE-2021-32040 https://www.cve.org/CVERecord?id=CVE-2021-32040 Référence CVE CVE-2021-43797 https://www.cve.org/CVERecord?id=CVE-2021-43797 Référence CVE CVE-2021-46939 https://www.cve.org/CVERecord?id=CVE-2021-46939 Référence CVE CVE-2021-47321 https://www.cve.org/CVERecord?id=CVE-2021-47321 Référence CVE CVE-2022-21680 https://www.cve.org/CVERecord?id=CVE-2022-21680 Référence CVE CVE-2022-21681 https://www.cve.org/CVERecord?id=CVE-2022-21681 Référence CVE CVE-2022-25869 https://www.cve.org/CVERecord?id=CVE-2022-25869 Référence CVE CVE-2022-3602 https://www.cve.org/CVERecord?id=CVE-2022-3602 Référence CVE CVE-2022-3786 https://www.cve.org/CVERecord?id=CVE-2022-3786 Référence CVE CVE-2022-46751 https://www.cve.org/CVERecord?id=CVE-2022-46751 Référence CVE CVE-2023-26116 https://www.cve.org/CVERecord?id=CVE-

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

d?id=CVE-2020-25659 Référence CVE CVE-2020-36242 https://www.cve.org/CVERecord?id=CVE-2020-36242 Référence CVE CVE-2021-35937 https://www.cve.org/CVERecord?id=CVE-2021-35937 Référence CVE CVE-2021-35938 https://www.cve.org/CVERecord?id=CVE-2021-35938 Référence CVE CVE-2021-35939 https://www.cve.org/CVERecord?id=CVE-2021-35939 Référence CVE CVE-2021-42340 https://www.cve.org/CVERecord?id=CVE-2021-42340 Référence CVE CVE-2021-42694 https://www.cve.org/CVERecord?id=CVE-2021-42694 Référence CVE CVE-2021-43618 https://www.cve.org/CVERecord?id=CVE-2021-43618 Référence CVE CVE-2021-43980 https://www.cve.org/CVERecord?id=CVE-2021-43980 Référence CVE CVE-2021-46939 https://www.cve.org/CVERecord?id=CVE-2021-46939 Référence CVE CVE-2021-47018 https://www.cve.org/CVERecord?id=CVE-2021-47018 Référence CVE CVE-2021-47231 https://www.cve.org/CVERecord?id=CVE-2021-47231 Référence CVE CVE-2021-47257 https://www.cve.org/CVERecord?id=CVE-2021-47257 Référence CVE CVE-2021-47284 https://www.cve.org/CVERecord?id=CVE-2021-47284 Référence CVE CVE-2021-47304 https://www.cve.org/CVERecord?id=CVE-2021-47304 Référence CVE CVE-2021-47373 https://www.cve.org/CVERecord?id=CVE-2021-47373 Référence CVE CVE-2021-47408 https://www.cve.org/CVERecord?id=CVE-2021-47408 Référence CVE CVE-2021-47449 https://www.cve.org/CVERecord?id=

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

écurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité Red Hat RHSA-2024:5065 du 07 août 2024 https://access.redhat.com/errata/RHSA-2024:5065 Bulletin de sécurité Red Hat RHSA-2024:5066 du 07 août 2024 https://access.redhat.com/errata/RHSA-2024:5066 Bulletin de sécurité Red Hat RHSA-2024:5067 du 07 août 2024 https://access.redhat.com/errata/RHSA-2024:5067 Bulletin de sécurité Red Hat RHSA-2024:5101 du 08 août 2024 https://access.redhat.com/errata/RHSA-2024:5101 Bulletin de sécurité Red Hat RHSA-2024:5102 du 08 août 2024 https://access.redhat.com/errata/RHSA-2024:5102 Référence CVE CVE-2021-46939 https://www.cve.org/CVERecord?id=CVE-2021-46939 Référence CVE CVE-2021-47018 https://www.cve.org/CVERecord?id=CVE-2021-47018 Référence CVE CVE-2021-47257 https://www.cve.org/CVERecord?id=CVE-2021-47257 Référence CVE CVE-2021-47284 https://www.cve.org/CVERecord?id=CVE-2021-47284 Référence CVE CVE-2021-47304 https://www.cve.org/CVERecord?id=CVE-2021-47304 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-47408 https://www.cve.org/CVERecord?id=CVE-2021-47408 Référence CVE CVE-2021-47461 https://www.cve.org/CVERecord?id=

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

/suse-su-20241870-1 Référence CVE CVE-2019-25160 https://www.cve.org/CVERecord?id=CVE-2019-25160 Référence CVE CVE-2020-36312 https://www.cve.org/CVERecord?id=CVE-2020-36312 Référence CVE CVE-2021-23134 https://www.cve.org/CVERecord?id=CVE-2021-23134 Référence CVE CVE-2021-46904 https://www.cve.org/CVERecord?id=CVE-2021-46904 Référence CVE CVE-2021-46905 https://www.cve.org/CVERecord?id=CVE-2021-46905 Référence CVE CVE-2021-46907 https://www.cve.org/CVERecord?id=CVE-2021-46907 Référence CVE CVE-2021-46909 https://www.cve.org/CVERecord?id=CVE-2021-46909 Référence CVE CVE-2021-46938 https://www.cve.org/CVERecord?id=CVE-2021-46938 Référence CVE CVE-2021-46939 https://www.cve.org/CVERecord?id=CVE-2021-46939 Référence CVE CVE-2021-46941 https://www.cve.org/CVERecord?id=CVE-2021-46941 Référence CVE CVE-2021-46950 https://www.cve.org/CVERecord?id=CVE-2021-46950 Référence CVE CVE-2021-46958 https://www.cve.org/CVERecord?id=CVE-2021-46958 Référence CVE CVE-2021-46960 https://www.cve.org/CVERecord?id=CVE-2021-46960 Référence CVE CVE-2021-46963 https://www.cve.org/CVERecord?id=CVE-2021-46963 Référence CVE CVE-2021-46964 https://www.cve.org/CVERecord?id=CVE-2021-46964 Référence CVE CVE-2021-46966 https://www.cve.org/CVERecord?id=CVE-2021-46966 Référence CVE CVE-2021-46975 https://www.cve.org/CVERecord?id=

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

/suse-su-20241760-1 Référence CVE CVE-2019-25160 https://www.cve.org/CVERecord?id=CVE-2019-25160 Référence CVE CVE-2020-36312 https://www.cve.org/CVERecord?id=CVE-2020-36312 Référence CVE CVE-2021-23134 https://www.cve.org/CVERecord?id=CVE-2021-23134 Référence CVE CVE-2021-46904 https://www.cve.org/CVERecord?id=CVE-2021-46904 Référence CVE CVE-2021-46905 https://www.cve.org/CVERecord?id=CVE-2021-46905 Référence CVE CVE-2021-46907 https://www.cve.org/CVERecord?id=CVE-2021-46907 Référence CVE CVE-2021-46909 https://www.cve.org/CVERecord?id=CVE-2021-46909 Référence CVE CVE-2021-46938 https://www.cve.org/CVERecord?id=CVE-2021-46938 Référence CVE CVE-2021-46939 https://www.cve.org/CVERecord?id=CVE-2021-46939 Référence CVE CVE-2021-46941 https://www.cve.org/CVERecord?id=CVE-2021-46941 Référence CVE CVE-2021-46950 https://www.cve.org/CVERecord?id=CVE-2021-46950 Référence CVE CVE-2021-46958 https://www.cve.org/CVERecord?id=CVE-2021-46958 Référence CVE CVE-2021-46960 https://www.cve.org/CVERecord?id=CVE-2021-46960 Référence CVE CVE-2021-46963 https://www.cve.org/CVERecord?id=CVE-2021-46963 Référence CVE CVE-2021-46964 https://www.cve.org/CVERecord?id=CVE-2021-46964 Référence CVE CVE-2021-46966 https://www.cve.org/CVERecord?id=CVE-2021-46966 Référence CVE CVE-2021-46975 https://www.cve.org/CVERecord?id=

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

m/security/notices/USN-6766-2 Bulletin de sécurité Ubuntu USN-6767-2 du 14 mai 2024 https://ubuntu.com/security/notices/USN-6767-2 Bulletin de sécurité Ubuntu USN-6774-1 du 16 mai 2024 https://ubuntu.com/security/notices/USN-6774-1 Bulletin de sécurité Ubuntu USN-6775-1 du 16 mai 2024 https://ubuntu.com/security/notices/USN-6775-1 Bulletin de sécurité Ubuntu USN-6776-1 du 16 mai 2024 https://ubuntu.com/security/notices/USN-6776-1 Bulletin de sécurité Ubuntu USN-6777-1 du 16 mai 2024 https://ubuntu.com/security/notices/USN-6777-1 Bulletin de sécurité Ubuntu USN-6778-1 du 16 mai 2024 https://ubuntu.com/security/notices/USN-6778-1 Référence CVE CVE-2021-46939 https://www.cve.org/CVERecord?id=CVE-2021-46939 Référence CVE CVE-2021-46981 https://www.cve.org/CVERecord?id=CVE-2021-46981 Référence CVE CVE-2023-47233 https://www.cve.org/CVERecord?id=CVE-2023-47233 Référence CVE CVE-2023-52435 https://www.cve.org/CVERecord?id=CVE-2023-52435 Référence CVE CVE-2023-52439 https://www.cve.org/CVERecord?id=CVE-2023-52439 Référence CVE CVE-2023-52486 https://www.cve.org/CVERecord?id=CVE-2023-52486 Référence CVE CVE-2023-52489 https://www.cve.org/CVERecord?id=CVE-2023-52489 Référence CVE CVE-2023-52491 https://www.cve.org/CVERecord?id=CVE-2023-52491 Référence CVE CVE-2023-52492 https://www.cve.org/CVERecord?id=

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

/suse-su-20241663-1 Référence CVE CVE-2019-25160 https://www.cve.org/CVERecord?id=CVE-2019-25160 Référence CVE CVE-2020-36312 https://www.cve.org/CVERecord?id=CVE-2020-36312 Référence CVE CVE-2021-23134 https://www.cve.org/CVERecord?id=CVE-2021-23134 Référence CVE CVE-2021-46904 https://www.cve.org/CVERecord?id=CVE-2021-46904 Référence CVE CVE-2021-46905 https://www.cve.org/CVERecord?id=CVE-2021-46905 Référence CVE CVE-2021-46907 https://www.cve.org/CVERecord?id=CVE-2021-46907 Référence CVE CVE-2021-46909 https://www.cve.org/CVERecord?id=CVE-2021-46909 Référence CVE CVE-2021-46938 https://www.cve.org/CVERecord?id=CVE-2021-46938 Référence CVE CVE-2021-46939 https://www.cve.org/CVERecord?id=CVE-2021-46939 Référence CVE CVE-2021-46941 https://www.cve.org/CVERecord?id=CVE-2021-46941 Référence CVE CVE-2021-46950 https://www.cve.org/CVERecord?id=CVE-2021-46950 Référence CVE CVE-2021-46955 https://www.cve.org/CVERecord?id=CVE-2021-46955 Référence CVE CVE-2021-46958 https://www.cve.org/CVERecord?id=CVE-2021-46958 Référence CVE CVE-2021-46960 https://www.cve.org/CVERecord?id=CVE-2021-46960 Référence CVE CVE-2021-46963 https://www.cve.org/CVERecord?id=CVE-2021-46963 Référence CVE CVE-2021-46964 https://www.cve.org/CVERecord?id=CVE-2021-46964 Référence CVE CVE-2021-46966 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2021-46926 Référence CVE CVE-2021-46927 https://www.cve.org/CVERecord?id=CVE-2021-46927 Référence CVE CVE-2021-46929 https://www.cve.org/CVERecord?id=CVE-2021-46929 Référence CVE CVE-2021-46930 https://www.cve.org/CVERecord?id=CVE-2021-46930 Référence CVE CVE-2021-46931 https://www.cve.org/CVERecord?id=CVE-2021-46931 Référence CVE CVE-2021-46933 https://www.cve.org/CVERecord?id=CVE-2021-46933 Référence CVE CVE-2021-46934 https://www.cve.org/CVERecord?id=CVE-2021-46934 Référence CVE CVE-2021-46936 https://www.cve.org/CVERecord?id=CVE-2021-46936 Référence CVE CVE-2021-46938 https://www.cve.org/CVERecord?id=CVE-2021-46938 Référence CVE CVE-2021-46939 https://www.cve.org/CVERecord?id=CVE-2021-46939 Référence CVE CVE-2021-46943 https://www.cve.org/CVERecord?id=CVE-2021-46943 Référence CVE CVE-2021-46944 https://www.cve.org/CVERecord?id=CVE-2021-46944 Référence CVE CVE-2021-46950 https://www.cve.org/CVERecord?id=CVE-2021-46950 Référence CVE CVE-2021-46951 https://www.cve.org/CVERecord?id=CVE-2021-46951 Référence CVE CVE-2021-46956 https://www.cve.org/CVERecord?id=CVE-2021-46956 Référence CVE CVE-2021-46958 https://www.cve.org/CVERecord?id=CVE-2021-46958 Référence CVE CVE-2021-46959 https://www.cve.org/CVERecord?id=CVE-2021-46959 Référence CVE CVE-2021-46960 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2021-020880Linux の 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: < 2.6.30, 4.4.269 ≤ 4.4.*, 4.9.269 ≤ 4.9.*, 4.14.233 ≤ 4.14.*, 4.19.191 ≤ 4.19.*, 5.4.118 ≤ 5.4.*, 5.10.36 ≤ 5.10.*, 5.11.20 ≤ 5.11.*, 5.12.3 ≤ 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 27 Feb 2024 · Last source change 11 May 2026, 13:44 UTC · CWE-400 · Uncontrolled Resource Consumption

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-33587
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCISA ADP
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-33587↗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-46939 · cve.blacktree.nl