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

tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc

Linux · Linux

4.4MediumCVSS 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.18% 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.15.5-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.15.5-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.15.5-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.15.5-1Debian Security Tracker ↗Source updated 5 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-47185 · CSAF 2.0 · revision 61 · interimSUSE Product Security TeamCVE-2021-47185
130 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: tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc When running ltp testcase(ltp/testcases/kernel/pty/pty04.c) with arm64, there is a soft lockup, which look like this one: Workqueue: events_unbound flush_to_ldisc Call trace: dump_backtrace+0x0/0x1ec show_stack+0x24/0x30 dump_stack+0xd0/0x128 panic+0x15c/0x374 watchdog_timer_fn+0x2b8/0x304 __run_hrtimer+0x88/0x2c0 __hrtimer_run_queues+0xa4/0x120 hrtimer_interrupt+0xfc/0x270 arch_timer_handler_phys+0x40/0x50 handle_percpu_devid_irq+0x94/0x220 __handle_domain_irq+0x88/0xf0 gic_handle_irq+0x84/0xfc el1_irq+0xc8/0x180 slip_unesc+0x80/0x214 [slip] tty_ldisc_receive_buf+0x64/0x80 tty_port_default_receive_buf+0x50/0x90 flush_to_ldisc+0xbc/0x110 process_one_work+0x1d4/0x4b0 worker_thread+0x180/0x430 kthread+0x11c/0x120 In the testcase pty04, The first process call the write syscall to send data to the pty master. At the same time, the workqueue will do the flush_to_ldisc to pop data in a loop until there is no more data left. When the sender and workqueue running in different core, the sender sends data fastly in full time which will result in workqueue doing work in loop for a long time and occuring softlockup in flush_to_ldisc with kernel configured without preempt. So I add need_resched check and cond_resched in the flush_to_ldisc loop to avoid it.
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-33833

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: tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc When running ltp testcase(ltp/testcases/kernel/pty/pty04.c) with arm64, there is a soft lockup, which look like this one: Workqueue: events_unbound flush_to_ldisc Call trace: dump_backtrace+0x0/0x1ec show_stack+0x24/0x30 dump_stack+0xd0/0x128 panic+0x15c/0x374 watchdog_timer_fn+0x2b8/0x304 __run_hrtimer+0x88/0x2c0 __hrtimer_run_queues+0xa4/0x120 hrtimer_interrupt+0xfc/0x270 arch_timer_handler_phys+0x40/0x50 handle_percpu_devid_irq+0x94/0x220 __handle_domain_irq+0x88/0xf0 gic_handle_irq+0x84/0xfc el1_irq+0xc8/0x180 slip_unesc+0x80/0x214 [slip] tty_ldisc_receive_buf+0x64/0x80 tty_port_default_receive_buf+0x50/0x90 flush_to_ldisc+0xbc/0x110 process_one_work+0x1d4/0x4b0 worker_thread+0x180/0x430 kthread+0x11c/0x120 In the testcase pty04, The first process call the write syscall to send data to the pty master. At the same time, the workqueue will do the flush_to_ldisc to pop data in a loop until there is no more data left. When the sender and workqueue running in different core, the sender sends data fastly in full time which will result in workqueue doing work in loop for a long time and occuring softlockup in flush_to_ldisc with kernel configured without preempt. So I add need_resched check and cond_resched in the flush_to_ldisc loop to avoid it.

What

In the Linux kernel, the following vulnerability has been resolved: tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc When running ltp testcase(ltp/testcases/kernel/pty/pty04.c) with arm64, there is a soft lockup, which look like this one: Workqueue: events_unbound flush_to_ldisc Call trace: dump_backtrace+0x0/0x1ec show_stack+0x24/0x30 dump_stack+0xd0/0x128 panic+0x15c/0x374 watchdog_timer_fn+0x2b8/0x304 __run_hrtimer+0x88/0x2c0 __hrtimer_run_queues+0xa4/0x120 hrtimer_interrupt+0xfc/0x270 arch_timer_handler_phys+0x40/0x50 handle_percpu_devid_irq+0x94/0x220 __handle_domain_irq+0x88/0xf0 gic_handle_irq+0x84/0xfc el1_irq+0xc8/0x180 slip_unesc+0x80/0x214 [slip] tty_ldisc_receive_buf+0x64/0x80 tty_port_default_receive_buf+0x50/0x90 flush_to_ldisc+0xbc/0x110 process_one_work+0x1d4/0x4b0 worker_thread+0x180/0x430 kthread+0x11c/0x120 In the testcase pty04, The first process call the write syscall to send data to the pty master. At the same time, the workqueue will do the flush_to_ldisc to pop data in a loop until there is no more data left. When the sender and workqueue running in different core, the sender sends data fastly in full time which will result in workqueue doing work in loop for a long time and occuring softlockup in flush_to_ldisc with kernel configured without preempt. So I add need_resched check and cond_resched in the flush_to_ldisc loop to avoid it.

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 elevated 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: tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc When running ltp testcase(ltp/testcases/kernel/pty/pty04.c) with arm64, there is a soft lockup, which look like this one: Workqueue: events_unbound flush_to_ldisc Call trace: dump_backtrace+0x0/0x1ec show_stack+0x24/0x30 dump_stack+0xd0/0x128 panic+0x15c/0x374 watchdog_timer_fn+0x2b8/0x304 __run_hrtimer+0x88/0x2c0 __hrtimer_run_queues+0xa4/0x120 hrtimer_interrupt+0xfc/0x270 arch_timer_handler_phys+0x40/0x50 handle_percpu_devid_irq+0x94/0x220 __handle_domain_irq+0x88/0xf0 gic_handle_irq+0x84/0xfc el1_irq+0xc8/0x180 slip_unesc+0x80/0x214 [slip] tty_ldisc_receive_buf+0x64/0x80 tty_port_default_receive_buf+0x50/0x90 flush_to_ldisc+0xbc/0x110 process_one_work+0x1d4/0x4b0 worker_thread+0x180/0x430 kthread+0x11c/0x120 In the testcase pty04, The first process call the write syscall to send data to the pty master. At the same time, the workqueue will do the flush_to_ldisc to pop data in a loop until there is no more data left. When the sender and workqueue running in different core, the sender sends data fastly in full time which will result in workqueue doing work in loop for a long time and occuring softlockup in flush_to_ldisc with kernel configured without preempt. So I add need_resched check and cond_resched in the flush_to_ldisc loop to avoid it.

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 elevated 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 → Improper Locking → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
High: elevated access 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:H/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.PRHighPrivileges required: The attacker needs elevated or administrative 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-667
A

Official authority intelligence

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

BSI · German · WID-SEC-2025-1293IBM DataPower Gateway: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in IBM DataPower Gateway ausnutzen, um seine Privilegien zu erhöhen, Informationen auszuspähen, einen Denial-of-Service auszulösen oder weitere unspezifizierte Auswirkungen zu erzielen.

Official advisory ↗
BSI · German · WID-SEC-2024-0851Linux Kernel: Mehrere Schwachstellen

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder unbekannte Auswirkungen zu verursachen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240417Security Bulletin 17 Apr 2024

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

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

51 du 28 juillet 2025 https://access.redhat.com/errata/RHSA-2025:11851 Bulletin de sécurité Red Hat RHSA-2025:11855 du 28 juillet 2025 https://access.redhat.com/errata/RHSA-2025:11855 Bulletin de sécurité Red Hat RHSA-2025:11861 du 28 juillet 2025 https://access.redhat.com/errata/RHSA-2025:11861 Bulletin de sécurité Red Hat RHSA-2025:12209 du 29 juillet 2025 https://access.redhat.com/errata/RHSA-2025:12209 Bulletin de sécurité Red Hat RHSA-2025:12238 du 30 juillet 2025 https://access.redhat.com/errata/RHSA-2025:12238 Bulletin de sécurité Red Hat RHSA-2025:12311 du 30 juillet 2025 https://access.redhat.com/errata/RHSA-2025:12311 Référence CVE CVE-2021-47185 https://www.cve.org/CVERecord?id=CVE-2021-47185 Référence CVE CVE-2022-49058 https://www.cve.org/CVERecord?id=CVE-2022-49058 Référence CVE CVE-2022-49977 https://www.cve.org/CVERecord?id=CVE-2022-49977 Référence CVE CVE-2022-50022 https://www.cve.org/CVERecord?id=CVE-2022-50022 Référence CVE CVE-2023-52835 https://www.cve.org/CVERecord?id=CVE-2023-52835 Référence CVE CVE-2024-26660 https://www.cve.org/CVERecord?id=CVE-2024-26660 Référence CVE CVE-2024-27025 https://www.cve.org/CVERecord?id=CVE-2024-27025 Référence CVE CVE-2024-41039 https://www.cve.org/CVERecord?id=CVE-2024-41039 Référence CVE CVE-2024-41065 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-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=CVE-2021-47185 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=CVE-2021-47456 Référence CVE CVE-2021-47495 https://www.cve.org/CVERecord?id=CVE-2021-47495 Référence CVE CVE-2022-2879 https://www.cve.org/CVERecord?id=C

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

d?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-46934 https://www.cve.org/CVERecord?id=CVE-2021-46934 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-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=CVE-2021-47185 Référence CVE CVE-2022-2879 https://www.cve.org/CVERecord?id=CVE-2022-2879 Référence CVE CVE-2022-2880 https://www.cve.org/CVERecord?id=CVE-2022-2880 Référence CVE CVE-2022-38096 https://www.cve.org/CVERecord?id=CVE-2022-38096 Référence CVE CVE-2022-41715 https://www.cve.org/CVERecord?id=CVE-2022-41715 Référence CVE CVE-2022-48624 https://www.cve.org/CVERecord?id=CVE-2022-48624 Référence CVE CVE-2022-48627 https://www.cve.org/CVERecord?id=CVE-2022-48627 Référence CVE CVE-2022-48669 https://www.cve.org/CVERecord?id=CVE-2022-48669 Référence CVE CVE-2023-29400 https://www.cve.org/CVERecord?id=CVE-

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

rata/RHSA-2024:3627 Référence CVE CVE-2019-25162 https://www.cve.org/CVERecord?id=CVE-2019-25162 Référence CVE CVE-2020-36777 https://www.cve.org/CVERecord?id=CVE-2020-36777 Référence CVE CVE-2021-46934 https://www.cve.org/CVERecord?id=CVE-2021-46934 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-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=CVE-2021-47185 Référence CVE CVE-2022-48627 https://www.cve.org/CVERecord?id=CVE-2022-48627 Référence CVE CVE-2022-48669 https://www.cve.org/CVERecord?id=CVE-2022-48669 Référence CVE CVE-2023-2166 https://www.cve.org/CVERecord?id=CVE-2023-2166 Référence CVE CVE-2023-2176 https://www.cve.org/CVERecord?id=CVE-2023-2176 Référence CVE CVE-2023-52439 https://www.cve.org/CVERecord?id=CVE-2023-52439 Référence CVE CVE-2023-52445 https://www.cve.org/CVERecord?id=CVE-2023-52445 Référence CVE CVE-2023-52477 https://www.cve.org/CVERecord?id=CVE-2023-52477 Référence CVE CVE-2023-52513 https://www.cve.org/CVERecord?id=CVE-

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

d?id=CVE-2021-47171 Référence CVE CVE-2021-47173 https://www.cve.org/CVERecord?id=CVE-2021-47173 Référence CVE CVE-2021-47177 https://www.cve.org/CVERecord?id=CVE-2021-47177 Référence CVE CVE-2021-47179 https://www.cve.org/CVERecord?id=CVE-2021-47179 Référence CVE CVE-2021-47180 https://www.cve.org/CVERecord?id=CVE-2021-47180 Référence CVE CVE-2021-47181 https://www.cve.org/CVERecord?id=CVE-2021-47181 Référence CVE CVE-2021-47182 https://www.cve.org/CVERecord?id=CVE-2021-47182 Référence CVE CVE-2021-47183 https://www.cve.org/CVERecord?id=CVE-2021-47183 Référence CVE CVE-2021-47184 https://www.cve.org/CVERecord?id=CVE-2021-47184 Référence CVE CVE-2021-47185 https://www.cve.org/CVERecord?id=CVE-2021-47185 Référence CVE CVE-2021-47188 https://www.cve.org/CVERecord?id=CVE-2021-47188 Référence CVE CVE-2021-47189 https://www.cve.org/CVERecord?id=CVE-2021-47189 Référence CVE CVE-2021-47198 https://www.cve.org/CVERecord?id=CVE-2021-47198 Référence CVE CVE-2021-47202 https://www.cve.org/CVERecord?id=CVE-2021-47202 Référence CVE CVE-2021-47203 https://www.cve.org/CVERecord?id=CVE-2021-47203 Référence CVE CVE-2021-47204 https://www.cve.org/CVERecord?id=CVE-2021-47204 Référence CVE CVE-2021-47205 https://www.cve.org/CVERecord?id=CVE-2021-47205 Référence CVE CVE-2021-47207 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2021-47171 Référence CVE CVE-2021-47173 https://www.cve.org/CVERecord?id=CVE-2021-47173 Référence CVE CVE-2021-47177 https://www.cve.org/CVERecord?id=CVE-2021-47177 Référence CVE CVE-2021-47179 https://www.cve.org/CVERecord?id=CVE-2021-47179 Référence CVE CVE-2021-47180 https://www.cve.org/CVERecord?id=CVE-2021-47180 Référence CVE CVE-2021-47181 https://www.cve.org/CVERecord?id=CVE-2021-47181 Référence CVE CVE-2021-47182 https://www.cve.org/CVERecord?id=CVE-2021-47182 Référence CVE CVE-2021-47183 https://www.cve.org/CVERecord?id=CVE-2021-47183 Référence CVE CVE-2021-47184 https://www.cve.org/CVERecord?id=CVE-2021-47184 Référence CVE CVE-2021-47185 https://www.cve.org/CVERecord?id=CVE-2021-47185 Référence CVE CVE-2021-47188 https://www.cve.org/CVERecord?id=CVE-2021-47188 Référence CVE CVE-2021-47189 https://www.cve.org/CVERecord?id=CVE-2021-47189 Référence CVE CVE-2021-47198 https://www.cve.org/CVERecord?id=CVE-2021-47198 Référence CVE CVE-2021-47202 https://www.cve.org/CVERecord?id=CVE-2021-47202 Référence CVE CVE-2021-47203 https://www.cve.org/CVERecord?id=CVE-2021-47203 Référence CVE CVE-2021-47204 https://www.cve.org/CVERecord?id=CVE-2021-47204 Référence CVE CVE-2021-47205 https://www.cve.org/CVERecord?id=CVE-2021-47205 Référence CVE CVE-2021-47207 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2021-47171 Référence CVE CVE-2021-47173 https://www.cve.org/CVERecord?id=CVE-2021-47173 Référence CVE CVE-2021-47177 https://www.cve.org/CVERecord?id=CVE-2021-47177 Référence CVE CVE-2021-47179 https://www.cve.org/CVERecord?id=CVE-2021-47179 Référence CVE CVE-2021-47180 https://www.cve.org/CVERecord?id=CVE-2021-47180 Référence CVE CVE-2021-47181 https://www.cve.org/CVERecord?id=CVE-2021-47181 Référence CVE CVE-2021-47182 https://www.cve.org/CVERecord?id=CVE-2021-47182 Référence CVE CVE-2021-47183 https://www.cve.org/CVERecord?id=CVE-2021-47183 Référence CVE CVE-2021-47184 https://www.cve.org/CVERecord?id=CVE-2021-47184 Référence CVE CVE-2021-47185 https://www.cve.org/CVERecord?id=CVE-2021-47185 Référence CVE CVE-2021-47187 https://www.cve.org/CVERecord?id=CVE-2021-47187 Référence CVE CVE-2021-47188 https://www.cve.org/CVERecord?id=CVE-2021-47188 Référence CVE CVE-2021-47189 https://www.cve.org/CVERecord?id=CVE-2021-47189 Référence CVE CVE-2021-47191 https://www.cve.org/CVERecord?id=CVE-2021-47191 Référence CVE CVE-2021-47192 https://www.cve.org/CVERecord?id=CVE-2021-47192 Référence CVE CVE-2021-47193 https://www.cve.org/CVERecord?id=CVE-2021-47193 Référence CVE CVE-2021-47194 https://www.cve.org/CVERecord?id=CVE-2021-47194 Référence CVE CVE-2021-47195 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-47174 Référence CVE CVE-2021-47175 https://www.cve.org/CVERecord?id=CVE-2021-47175 Référence CVE CVE-2021-47176 https://www.cve.org/CVERecord?id=CVE-2021-47176 Référence CVE CVE-2021-47177 https://www.cve.org/CVERecord?id=CVE-2021-47177 Référence CVE CVE-2021-47179 https://www.cve.org/CVERecord?id=CVE-2021-47179 Référence CVE CVE-2021-47180 https://www.cve.org/CVERecord?id=CVE-2021-47180 Référence CVE CVE-2021-47181 https://www.cve.org/CVERecord?id=CVE-2021-47181 Référence CVE CVE-2021-47182 https://www.cve.org/CVERecord?id=CVE-2021-47182 Référence CVE CVE-2021-47183 https://www.cve.org/CVERecord?id=CVE-2021-47183 Référence CVE CVE-2021-47185 https://www.cve.org/CVERecord?id=CVE-2021-47185 Référence CVE CVE-2021-47189 https://www.cve.org/CVERecord?id=CVE-2021-47189 Référence CVE CVE-2021-47202 https://www.cve.org/CVERecord?id=CVE-2021-47202 Référence CVE CVE-2022-0487 https://www.cve.org/CVERecord?id=CVE-2022-0487 Référence CVE CVE-2022-4744 https://www.cve.org/CVERecord?id=CVE-2022-4744 Référence CVE CVE-2022-48626 https://www.cve.org/CVERecord?id=CVE-2022-48626 Référence CVE CVE-2022-48627 https://www.cve.org/CVERecord?id=CVE-2022-48627 Référence CVE CVE-2022-48628 https://www.cve.org/CVERecord?id=CVE-2022-48628 Référence CVE CVE-2022-48629 https://www.cve.org/CVERecord?id=CVE-

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2021-021721Linux の 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.0, 4.4.293 ≤ 4.4.*, 4.9.291 ≤ 4.9.*, 4.14.256 ≤ 4.14.*, 4.19.218 ≤ 4.19.*, 5.4.162 ≤ 5.4.*, 5.10.82 ≤ 5.10.*, 5.15.5 ≤ 5.15.*, 5.16 ≤ *
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 10 Apr 2024 · Last source change 11 May 2026, 13:49 UTC · CWE-667 · Improper Locking

CVE recordCVE.org · 5.2
CVSS sourceCISA ADP
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-33833
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
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-33833↗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-47185 · cve.blacktree.nl