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

USB: core: Make do_proc_control() and do_proc_bulk() killable

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.20% 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.15-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.15.15-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.15.15-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.15.15-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-47582 · CSAF 2.0 · revision 61 · interimSUSE Product Security TeamCVE-2021-47582
15 known affected

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

  • SLES 15 SP1 CHOST Images for Amazon EC2
  • SLES 15 SP2 CHOST Images for Amazon EC2
  • SLES 15 SP3 CHOST Images for Amazon EC2
  • SLES 15 SP4 CHOST Images for Amazon EC2
  • SLES 15 SP5 CHOST Images for Amazon EC2
  • SLES 15 SP1 CHOST Images for Google
  • SLES 15 SP2 CHOST Images for Google
  • SLES 15 SP3 CHOST Images for Google
  • SLES 15 SP4 CHOST Images for Google
  • SLES 15 SP5 CHOST Images for Google
  • SLES 15 SP1 CHOST Images for Microsoft Azure
  • SLES 15 SP2 CHOST Images for Microsoft Azure
Summary
In the Linux kernel, the following vulnerability has been resolved: USB: core: Make do_proc_control() and do_proc_bulk() killable The USBDEVFS_CONTROL and USBDEVFS_BULK ioctls invoke usb_start_wait_urb(), which contains an uninterruptible wait with a user-specified timeout value. If timeout value is very large and the device being accessed does not respond in a reasonable amount of time, the kernel will complain about "Task X blocked for more than N seconds", as found in testing by syzbot: INFO: task syz-executor.0:8700 blocked for more than 143 seconds. Not tainted 5.14.0-rc7-syzkaller #0 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:syz-executor.0 state:D stack:23192 pid: 8700 ppid: 8455 flags:0x00004004 Call Trace: context_switch kernel/sched/core.c:4681 [inline] __schedule+0xc07/0x11f0 kernel/sched/core.c:5938 schedule+0x14b/0x210 kernel/sched/core.c:6017 schedule_timeout+0x98/0x2f0 kernel/time/timer.c:1857 do_wait_for_common+0x2da/0x480 kernel/sched/completion.c:85 __wait_for_common kernel/sched/completion.c:106 [inline] wait_for_common kernel/sched/completion.c:117 [inline] wait_for_completion_timeout+0x46/0x60 kernel/sched/completion.c:157 usb_start_wait_urb+0x167/0x550 drivers/usb/core/message.c:63 do_proc_bulk+0x978/0x1080 drivers/usb/core/devio.c:1236 proc_bulk drivers/usb/core/devio.c:1273 [inline] usbdev_do_ioctl drivers/usb/core/devio.c:2547 [inline] usbdev_ioctl+0x3441/0x6b10 drivers/usb/core/devio.c:2713 ... To fix this problem, this patch replaces usbfs's calls to usb_control_msg() and usb_bulk_msg() with special-purpose code that does essentially the same thing (as recommended in the comment for usb_start_wait_urb()), except that it always uses a killable wait and it uses GFP_KERNEL rather than GFP_NOIO.
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-34584

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: USB: core: Make do_proc_control() and do_proc_bulk() killable The USBDEVFS_CONTROL and USBDEVFS_BULK ioctls invoke usb_start_wait_urb(), which contains an uninterruptible wait with a user-specified timeout value. If timeout value is very large and the device being accessed does not respond in a reasonable amount of time, the kernel will complain about "Task X blocked for more than N seconds", as found in testing by syzbot: INFO: task syz-executor.0:8700 blocked for more than 143 seconds. Not tainted 5.14.0-rc7-syzkaller #0 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:syz-executor.0 state:D stack:23192 pid: 8700 ppid: 8455 flags:0x00004004 Call Trace: context_switch kernel/sched/core.c:4681 [inline] __schedule+0xc07/0x11f0 kernel/sched/core.c:5938 schedule+0x14b/0x210 kernel/sched/core.c:6017 schedule_timeout+0x98/0x2f0 kernel/time/timer.c:1857 do_wait_for_common+0x2da/0x480 kernel/sched/completion.c:85 __wait_for_common kernel/sched/completion.c:106 [inline] wait_for_common kernel/sched/completion.c:117 [inline] wait_for_completion_timeout+0x46/0x60 kernel/sched/completion.c:157 usb_start_wait_urb+0x167/0x550 drivers/usb/core/message.c:63 do_proc_bulk+0x978/0x1080 drivers/usb/core/devio.c:1236 proc_bulk drivers/usb/core/devio.c:1273 [inline] usbdev_do_ioctl drivers/usb/core/devio.c:2547 [inline] usbdev_ioctl+0x3441/0x6b10 drivers/usb/core/devio.c:2713 ... To fix this problem, this patch replaces usbfs's calls to usb_control_msg() and usb_bulk_msg() with special-purpose code that does essentially the same thing (as recommended in the comment for usb_start_wait_urb()), except that it always uses a killable wait and it uses GFP_KERNEL rather than GFP_NOIO.

What

In the Linux kernel, the following vulnerability has been resolved: USB: core: Make do_proc_control() and do_proc_bulk() killable The USBDEVFS_CONTROL and USBDEVFS_BULK ioctls invoke usb_start_wait_urb(), which contains an uninterruptible wait with a user-specified timeout value. If timeout value is very large and the device being accessed does not respond in a reasonable amount of time, the kernel will complain about "Task X blocked for more than N seconds", as found in testing by syzbot: INFO: task syz-executor.0:8700 blocked for more than 143 seconds. Not tainted 5.14.0-rc7-syzkaller #0 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:syz-executor.0 state:D stack:23192 pid: 8700 ppid: 8455 flags:0x00004004 Call Trace: context_switch kernel/sched/core.c:4681 [inline] __schedule+0xc07/0x11f0 kernel/sched/core.c:5938 schedule+0x14b/0x210 kernel/sched/core.c:6017 schedule_timeout+0x98/0x2f0 kernel/time/timer.c:1857 do_wait_for_common+0x2da/0x480 kernel/sched/completion.c:85 __wait_for_common kernel/sched/completion.c:106 [inline] wait_for_common kernel/sched/completion.c:117 [inline] wait_for_completion_timeout+0x46/0x60 kernel/sched/completion.c:157 usb_start_wait_urb+0x167/0x550 drivers/usb/core/message.c:63 do_proc_bulk+0x978/0x1080 drivers/usb/core/devio.c:1236 proc_bulk drivers/usb/core/devio.c:1273 [inline] usbdev_do_ioctl drivers/usb/core/devio.c:2547 [inline] usbdev_ioctl+0x3441/0x6b10 drivers/usb/core/devio.c:2713 ... To fix this problem, this patch replaces usbfs's calls to usb_control_msg() and usb_bulk_msg() with special-purpose code that does essentially the same thing (as recommended in the comment for usb_start_wait_urb()), except that it always uses a killable wait and it uses GFP_KERNEL rather than GFP_NOIO.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

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: USB: core: Make do_proc_control() and do_proc_bulk() killable The USBDEVFS_CONTROL and USBDEVFS_BULK ioctls invoke usb_start_wait_urb(), which contains an uninterruptible wait with a user-specified timeout value. If timeout value is very large and the device being accessed does not respond in a reasonable amount of time, the kernel will complain about "Task X blocked for more than N seconds", as found in testing by syzbot: INFO: task syz-executor.0:8700 blocked for more than 143 seconds. Not tainted 5.14.0-rc7-syzkaller #0 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:syz-executor.0 state:D stack:23192 pid: 8700 ppid: 8455 flags:0x00004004 Call Trace: context_switch kernel/sched/core.c:4681 [inline] __schedule+0xc07/0x11f0 kernel/sched/core.c:5938 schedule+0x14b/0x210 kernel/sched/core.c:6017 schedule_timeout+0x98/0x2f0 kernel/time/timer.c:1857 do_wait_for_common+0x2da/0x480 kernel/sched/completion.c:85 __wait_for_common kernel/sched/completion.c:106 [inline] wait_for_common kernel/sched/completion.c:117 [inline] wait_for_completion_timeout+0x46/0x60 kernel/sched/completion.c:157 usb_start_wait_urb+0x167/0x550 drivers/usb/core/message.c:63 do_proc_bulk+0x978/0x1080 drivers/usb/core/devio.c:1236 proc_bulk drivers/usb/core/devio.c:1273 [inline] usbdev_do_ioctl drivers/usb/core/devio.c:2547 [inline] usbdev_ioctl+0x3441/0x6b10 drivers/usb/core/devio.c:2713 ... To fix this problem, this patch replaces usbfs's calls to usb_control_msg() and usb_bulk_msg() with special-purpose code that does essentially the same thing (as recommended in the comment for usb_start_wait_urb()), except that it always uses a killable wait and it uses GFP_KERNEL rather than GFP_NOIO.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

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 → vulnerable operation → 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.
CWE not yet assigned
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.
A

Official authority intelligence

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

BSI · German · WID-SEC-2024-1418Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

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

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240626Security Bulletin 26 Jun 2024

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 26 Jun 2024, published on 26 June 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-47466 Référence CVE CVE-2021-47468 https://www.cve.org/CVERecord?id=CVE-2021-47468 Référence CVE CVE-2021-47491 https://www.cve.org/CVERecord?id=CVE-2021-47491 Référence CVE CVE-2021-47495 https://www.cve.org/CVERecord?id=CVE-2021-47495 Référence CVE CVE-2021-47497 https://www.cve.org/CVERecord?id=CVE-2021-47497 Référence CVE CVE-2021-47527 https://www.cve.org/CVERecord?id=CVE-2021-47527 Référence CVE CVE-2021-47548 https://www.cve.org/CVERecord?id=CVE-2021-47548 Référence CVE CVE-2021-47560 https://www.cve.org/CVERecord?id=CVE-2021-47560 Référence CVE CVE-2021-47579 https://www.cve.org/CVERecord?id=CVE-2021-47579 Référence CVE CVE-2021-47582 https://www.cve.org/CVERecord?id=CVE-2021-47582 Référence CVE CVE-2021-47609 https://www.cve.org/CVERecord?id=CVE-2021-47609 Référence CVE CVE-2021-47624 https://www.cve.org/CVERecord?id=CVE-2021-47624 Référence CVE CVE-2022-2047 https://www.cve.org/CVERecord?id=CVE-2022-2047 Référence CVE CVE-2022-24785 https://www.cve.org/CVERecord?id=CVE-2022-24785 Référence CVE CVE-2022-24823 https://www.cve.org/CVERecord?id=CVE-2022-24823 Référence CVE CVE-2022-25168 https://www.cve.org/CVERecord?id=CVE-2022-25168 Référence CVE CVE-2022-25647 https://www.cve.org/CVERecord?id=CVE-2022-25647 Référence CVE CVE-2022-26612 https://www.cve.org/CVERecord?id=CV

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

d?id=CVE-2021-47412 Référence CVE CVE-2021-47432 https://www.cve.org/CVERecord?id=CVE-2021-47432 Référence CVE CVE-2021-47441 https://www.cve.org/CVERecord?id=CVE-2021-47441 Référence CVE CVE-2021-47455 https://www.cve.org/CVERecord?id=CVE-2021-47455 Référence CVE CVE-2021-47466 https://www.cve.org/CVERecord?id=CVE-2021-47466 Référence CVE CVE-2021-47492 https://www.cve.org/CVERecord?id=CVE-2021-47492 Référence CVE CVE-2021-47497 https://www.cve.org/CVERecord?id=CVE-2021-47497 Référence CVE CVE-2021-47527 https://www.cve.org/CVERecord?id=CVE-2021-47527 Référence CVE CVE-2021-47560 https://www.cve.org/CVERecord?id=CVE-2021-47560 Référence CVE CVE-2021-47582 https://www.cve.org/CVERecord?id=CVE-2021-47582 Référence CVE CVE-2021-47609 https://www.cve.org/CVERecord?id=CVE-2021-47609 Référence CVE CVE-2022-48619 https://www.cve.org/CVERecord?id=CVE-2022-48619 Référence CVE CVE-2022-48638 https://www.cve.org/CVERecord?id=CVE-2022-48638 Référence CVE CVE-2022-48686 https://www.cve.org/CVERecord?id=CVE-2022-48686 Référence CVE CVE-2022-48687 https://www.cve.org/CVERecord?id=CVE-2022-48687 Référence CVE CVE-2022-48754 https://www.cve.org/CVERecord?id=CVE-2022-48754 Référence CVE CVE-2022-48760 https://www.cve.org/CVERecord?id=CVE-2022-48760 Référence CVE CVE-2022-48804 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2021-47501 Référence CVE CVE-2021-47506 https://www.cve.org/CVERecord?id=CVE-2021-47506 Référence CVE CVE-2021-47516 https://www.cve.org/CVERecord?id=CVE-2021-47516 Référence CVE CVE-2021-47520 https://www.cve.org/CVERecord?id=CVE-2021-47520 Référence CVE CVE-2021-47542 https://www.cve.org/CVERecord?id=CVE-2021-47542 Référence CVE CVE-2021-47546 https://www.cve.org/CVERecord?id=CVE-2021-47546 Référence CVE CVE-2021-47547 https://www.cve.org/CVERecord?id=CVE-2021-47547 Référence CVE CVE-2021-47559 https://www.cve.org/CVERecord?id=CVE-2021-47559 Référence CVE CVE-2021-47580 https://www.cve.org/CVERecord?id=CVE-2021-47580 Référence CVE CVE-2021-47582 https://www.cve.org/CVERecord?id=CVE-2021-47582 Référence CVE CVE-2021-47588 https://www.cve.org/CVERecord?id=CVE-2021-47588 Référence CVE CVE-2021-47590 https://www.cve.org/CVERecord?id=CVE-2021-47590 Référence CVE CVE-2021-47591 https://www.cve.org/CVERecord?id=CVE-2021-47591 Référence CVE CVE-2021-47593 https://www.cve.org/CVERecord?id=CVE-2021-47593 Référence CVE CVE-2021-47597 https://www.cve.org/CVERecord?id=CVE-2021-47597 Référence CVE CVE-2021-47598 https://www.cve.org/CVERecord?id=CVE-2021-47598 Référence CVE CVE-2021-47599 https://www.cve.org/CVERecord?id=CVE-2021-47599 Référence CVE CVE-2021-47600 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2021-47555 Référence CVE CVE-2021-47559 https://www.cve.org/CVERecord?id=CVE-2021-47559 Référence CVE CVE-2021-47566 https://www.cve.org/CVERecord?id=CVE-2021-47566 Référence CVE CVE-2021-47571 https://www.cve.org/CVERecord?id=CVE-2021-47571 Référence CVE CVE-2021-47572 https://www.cve.org/CVERecord?id=CVE-2021-47572 Référence CVE CVE-2021-47576 https://www.cve.org/CVERecord?id=CVE-2021-47576 Référence CVE CVE-2021-47577 https://www.cve.org/CVERecord?id=CVE-2021-47577 Référence CVE CVE-2021-47578 https://www.cve.org/CVERecord?id=CVE-2021-47578 Référence CVE CVE-2021-47580 https://www.cve.org/CVERecord?id=CVE-2021-47580 Référence CVE CVE-2021-47582 https://www.cve.org/CVERecord?id=CVE-2021-47582 Référence CVE CVE-2021-47583 https://www.cve.org/CVERecord?id=CVE-2021-47583 Référence CVE CVE-2021-47584 https://www.cve.org/CVERecord?id=CVE-2021-47584 Référence CVE CVE-2021-47585 https://www.cve.org/CVERecord?id=CVE-2021-47585 Référence CVE CVE-2021-47586 https://www.cve.org/CVERecord?id=CVE-2021-47586 Référence CVE CVE-2021-47587 https://www.cve.org/CVERecord?id=CVE-2021-47587 Référence CVE CVE-2021-47588 https://www.cve.org/CVERecord?id=CVE-2021-47588 Référence CVE CVE-2021-47589 https://www.cve.org/CVERecord?id=CVE-2021-47589 Référence CVE CVE-2021-47590 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2021-47544 Référence CVE CVE-2021-47555 https://www.cve.org/CVERecord?id=CVE-2021-47555 Référence CVE CVE-2021-47566 https://www.cve.org/CVERecord?id=CVE-2021-47566 Référence CVE CVE-2021-47571 https://www.cve.org/CVERecord?id=CVE-2021-47571 Référence CVE CVE-2021-47572 https://www.cve.org/CVERecord?id=CVE-2021-47572 Référence CVE CVE-2021-47576 https://www.cve.org/CVERecord?id=CVE-2021-47576 Référence CVE CVE-2021-47577 https://www.cve.org/CVERecord?id=CVE-2021-47577 Référence CVE CVE-2021-47578 https://www.cve.org/CVERecord?id=CVE-2021-47578 Référence CVE CVE-2021-47580 https://www.cve.org/CVERecord?id=CVE-2021-47580 Référence CVE CVE-2021-47582 https://www.cve.org/CVERecord?id=CVE-2021-47582 Référence CVE CVE-2021-47583 https://www.cve.org/CVERecord?id=CVE-2021-47583 Référence CVE CVE-2021-47584 https://www.cve.org/CVERecord?id=CVE-2021-47584 Référence CVE CVE-2021-47585 https://www.cve.org/CVERecord?id=CVE-2021-47585 Référence CVE CVE-2021-47586 https://www.cve.org/CVERecord?id=CVE-2021-47586 Référence CVE CVE-2021-47587 https://www.cve.org/CVERecord?id=CVE-2021-47587 Référence CVE CVE-2021-47589 https://www.cve.org/CVERecord?id=CVE-2021-47589 Référence CVE CVE-2021-47592 https://www.cve.org/CVERecord?id=CVE-2021-47592 Référence CVE CVE-2021-47595 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2021-022013Linux の 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.12, 5.15.11 ≤ 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 19 Jun 2024 · Last source change 11 May 2026, 13:57 UTC · CWE not yet assigned

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-34584
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD enriched

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

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-34584↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor 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-47582 · cve.blacktree.nl