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

blk-mq: fix IO hang from sbitmap wakeup race

Linux · Linux

4.7MediumCVSS 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 5 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published 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.19% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: 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 5 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

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

4 package states
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.6.7.7-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.82-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.7.7-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.7.7-1Debian Security Tracker ↗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.

3 current
CVE-2024-26671 · CSAF 2.0 · revision 99 · interimSUSE Product Security TeamCVE-2024-26671
135 known affected

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

  • kernel-default as component of SUSE Enterprise Storage 7.1
  • kernel-default-devel as component of SUSE Enterprise Storage 7.1
  • kernel-devel as component of SUSE Enterprise Storage 7.1
  • kernel-macros as component of SUSE Enterprise Storage 7.1
  • kernel-source as component of SUSE Enterprise Storage 7.1
  • reiserfs-kmp-default as component of SUSE Enterprise Storage 7.1
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP2-LTSS
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2-LTSS
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2-LTSS
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP2-LTSS
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP2-LTSS
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP2
Summary
In the Linux kernel, the following vulnerability has been resolved: blk-mq: fix IO hang from sbitmap wakeup race In blk_mq_mark_tag_wait(), __add_wait_queue() may be re-ordered with the following blk_mq_get_driver_tag() in case of getting driver tag failure. Then in __sbitmap_queue_wake_up(), waitqueue_active() may not observe the added waiter in blk_mq_mark_tag_wait() and wake up nothing, meantime blk_mq_mark_tag_wait() can't get driver tag successfully. This issue can be reproduced by running the following test in loop, and fio hang can be observed in < 30min when running it on my test VM in laptop. modprobe -r scsi_debug modprobe scsi_debug delay=0 dev_size_mb=4096 max_queue=1 host_max_queue=1 submit_queues=4 dev=`ls -d /sys/bus/pseudo/drivers/scsi_debug/adapter*/host*/target*/*/block/* | head -1 | xargs basename` fio --filename=/dev/"$dev" --direct=1 --rw=randrw --bs=4k --iodepth=1 \ --runtime=100 --numjobs=40 --time_based --name=test \ --ioengine=libaio Fix the issue by adding one explicit barrier in blk_mq_mark_tag_wait(), which is just fine in case of running out of tag.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
SSA-613116 · CSAF 2.0 · revision 3 · interimSiemens ProductCERTSSA-613116: Multiple Vulnerabilities in Third-Party Components in SINEC OS before V3.1
3 known not affected

The vendor explicitly states that these products are not affected by this CVE.

  • RUGGEDCOM RST2428P (6GK6242-6PA00)
  • SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family
  • SCALANCE XCM-/XRM-/XCH-/XRH-300 family
Summary
In the Linux kernel, the following vulnerability has been resolved: blk-mq: fix IO hang from sbitmap wakeup race.
Remediation
No remediation text is recorded.
SSA-398330 · CSAF 2.0 · revision 18 · interimSiemens ProductCERTSSA-398330: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP >= V3.1.0 and < V3.1.5
5 known affected

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

  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0)
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0)
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0)
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0)
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0)
Summary
In the Linux kernel, the following vulnerability has been resolved: blk-mq: fix IO hang from sbitmap wakeup race.
Remediation
Update to V3.1.5 or later version
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-2024-23933

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 5 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: blk-mq: fix IO hang from sbitmap wakeup race In blk_mq_mark_tag_wait(), __add_wait_queue() may be re-ordered with the following blk_mq_get_driver_tag() in case of getting driver tag failure. Then in __sbitmap_queue_wake_up(), waitqueue_active() may not observe the added waiter in blk_mq_mark_tag_wait() and wake up nothing, meantime blk_mq_mark_tag_wait() can't get driver tag successfully. This issue can be reproduced by running the following test in loop, and fio hang can be observed in < 30min when running it on my test VM in laptop. modprobe -r scsi_debug modprobe scsi_debug delay=0 dev_size_mb=4096 max_queue=1 host_max_queue=1 submit_queues=4 dev=`ls -d /sys/bus/pseudo/drivers/scsi_debug/adapter*/host*/target*/*/block/* | head -1 | xargs basename` fio --filename=/dev/"$dev" --direct=1 --rw=randrw --bs=4k --iodepth=1 \ --runtime=100 --numjobs=40 --time_based --name=test \ --ioengine=libaio Fix the issue by adding one explicit barrier in blk_mq_mark_tag_wait(), which is just fine in case of running out of tag.

What

In the Linux kernel, the following vulnerability has been resolved: blk-mq: fix IO hang from sbitmap wakeup race In blk_mq_mark_tag_wait(), __add_wait_queue() may be re-ordered with the following blk_mq_get_driver_tag() in case of getting driver tag failure. Then in __sbitmap_queue_wake_up(), waitqueue_active() may not observe the added waiter in blk_mq_mark_tag_wait() and wake up nothing, meantime blk_mq_mark_tag_wait() can't get driver tag successfully. This issue can be reproduced by running the following test in loop, and fio hang can be observed in < 30min when running it on my test VM in laptop. modprobe -r scsi_debug modprobe scsi_debug delay=0 dev_size_mb=4096 max_queue=1 host_max_queue=1 submit_queues=4 dev=`ls -d /sys/bus/pseudo/drivers/scsi_debug/adapter*/host*/target*/*/block/* | head -1 | xargs basename` fio --filename=/dev/"$dev" --direct=1 --rw=randrw --bs=4k --iodepth=1 \ --runtime=100 --numjobs=40 --time_based --name=test \ --ioengine=libaio Fix the issue by adding one explicit barrier in blk_mq_mark_tag_wait(), which is just fine in case of running out of tag.

Why

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

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: blk-mq: fix IO hang from sbitmap wakeup race In blk_mq_mark_tag_wait(), __add_wait_queue() may be re-ordered with the following blk_mq_get_driver_tag() in case of getting driver tag failure. Then in __sbitmap_queue_wake_up(), waitqueue_active() may not observe the added waiter in blk_mq_mark_tag_wait() and wake up nothing, meantime blk_mq_mark_tag_wait() can't get driver tag successfully. This issue can be reproduced by running the following test in loop, and fio hang can be observed in < 30min when running it on my test VM in laptop. modprobe -r scsi_debug modprobe scsi_debug delay=0 dev_size_mb=4096 max_queue=1 host_max_queue=1 submit_queues=4 dev=`ls -d /sys/bus/pseudo/drivers/scsi_debug/adapter*/host*/target*/*/block/* | head -1 | xargs basename` fio --filename=/dev/"$dev" --direct=1 --rw=randrw --bs=4k --iodepth=1 \ --runtime=100 --numjobs=40 --time_based --name=test \ --ioengine=libaio Fix the issue by adding one explicit barrier in blk_mq_mark_tag_wait(), which is just fine in case of running out of tag.

Why

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

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 → Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') → 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
High: exploitation depends on specific conditions
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-362 ↗

CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'). The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

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:H/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.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.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-362
A

Official authority intelligence

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

BSI · German · WID-SEC-2024-0749Linux Kernel: Mehrere Schwachstellen

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

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

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 03 Apr 2024, published on 3 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-0677Multiples vulnérabilités dans les produits Siemens

d?id=CVE-2024-26602 Référence CVE CVE-2024-26606 https://www.cve.org/CVERecord?id=CVE-2024-26606 Référence CVE CVE-2024-26615 https://www.cve.org/CVERecord?id=CVE-2024-26615 Référence CVE CVE-2024-26625 https://www.cve.org/CVERecord?id=CVE-2024-26625 Référence CVE CVE-2024-26635 https://www.cve.org/CVERecord?id=CVE-2024-26635 Référence CVE CVE-2024-26636 https://www.cve.org/CVERecord?id=CVE-2024-26636 Référence CVE CVE-2024-26645 https://www.cve.org/CVERecord?id=CVE-2024-26645 Référence CVE CVE-2024-26663 https://www.cve.org/CVERecord?id=CVE-2024-26663 Référence CVE CVE-2024-26664 https://www.cve.org/CVERecord?id=CVE-2024-26664 Référence CVE CVE-2024-26671 https://www.cve.org/CVERecord?id=CVE-2024-26671 Référence CVE CVE-2024-26673 https://www.cve.org/CVERecord?id=CVE-2024-26673 Référence CVE CVE-2024-26675 https://www.cve.org/CVERecord?id=CVE-2024-26675 Référence CVE CVE-2024-26679 https://www.cve.org/CVERecord?id=CVE-2024-26679 Référence CVE CVE-2024-26684 https://www.cve.org/CVERecord?id=CVE-2024-26684 Référence CVE CVE-2024-26685 https://www.cve.org/CVERecord?id=CVE-2024-26685 Référence CVE CVE-2024-26688 https://www.cve.org/CVERecord?id=CVE-2024-26688 Référence CVE CVE-2024-26696 https://www.cve.org/CVERecord?id=CVE-2024-26696 Référence CVE CVE-2024-26697 https://www.cve.org/CVERecord?id=

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

ecord?id=CVE-2021-47461 Référence CVE CVE-2022-0500 https://www.cve.org/CVERecord?id=CVE-2022-0500 Référence CVE CVE-2022-23222 https://www.cve.org/CVERecord?id=CVE-2022-23222 Référence CVE CVE-2022-48686 https://www.cve.org/CVERecord?id=CVE-2022-48686 Référence CVE CVE-2022-48773 https://www.cve.org/CVERecord?id=CVE-2022-48773 Référence CVE CVE-2022-48786 https://www.cve.org/CVERecord?id=CVE-2022-48786 Référence CVE CVE-2022-48929 https://www.cve.org/CVERecord?id=CVE-2022-48929 Référence CVE CVE-2023-0597 https://www.cve.org/CVERecord?id=CVE-2023-0597 Référence CVE CVE-2023-52489 https://www.cve.org/CVERecord?id=CVE-2023-52489 Référence CVE CVE-2024-26671 https://www.cve.org/CVERecord?id=CVE-2024-26671 Référence CVE CVE-2024-26961 https://www.cve.org/CVERecord?id=CVE-2024-26961 Référence CVE CVE-2024-27043 https://www.cve.org/CVERecord?id=CVE-2024-27043 Référence CVE CVE-2024-27399 https://www.cve.org/CVERecord?id=CVE-2024-27399 Référence CVE CVE-2024-31076 https://www.cve.org/CVERecord?id=CVE-2024-31076 Référence CVE CVE-2024-35823 https://www.cve.org/CVERecord?id=CVE-2024-35823 Référence CVE CVE-2024-36889 https://www.cve.org/CVERecord?id=CVE-2024-36889 Référence CVE CVE-2024-36920 https://www.cve.org/CVERecord?id=CVE-2024-36920 Référence CVE CVE-2024-38564 https://www.cve.org/CVERecord?id=

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

De multiples vulnérabilités ont été découvertes dans le noyau Linux de Red Hat. Elles permettent à un attaquant de provoquer un problème de sécurité non spécifié par l'éditeur.

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

e sécurité Red Hat RHSA-2024:8617 du 30 octobre 2024 https://access.redhat.com/errata/RHSA-2024:8617 Référence CVE CVE-2021-47383 https://www.cve.org/CVERecord?id=CVE-2021-47383 Référence CVE CVE-2021-47384 https://www.cve.org/CVERecord?id=CVE-2021-47384 Référence CVE CVE-2022-48773 https://www.cve.org/CVERecord?id=CVE-2022-48773 Référence CVE CVE-2023-1252 https://www.cve.org/CVERecord?id=CVE-2023-1252 Référence CVE CVE-2023-52489 https://www.cve.org/CVERecord?id=CVE-2023-52489 Référence CVE CVE-2024-2201 https://www.cve.org/CVERecord?id=CVE-2024-2201 Référence CVE CVE-2024-26640 https://www.cve.org/CVERecord?id=CVE-2024-26640 Référence CVE CVE-2024-26671 https://www.cve.org/CVERecord?id=CVE-2024-26671 Référence CVE CVE-2024-26686 https://www.cve.org/CVERecord?id=CVE-2024-26686 Référence CVE CVE-2024-26826 https://www.cve.org/CVERecord?id=CVE-2024-26826 Référence CVE CVE-2024-26923 https://www.cve.org/CVERecord?id=CVE-2024-26923 Référence CVE CVE-2024-26935 https://www.cve.org/CVERecord?id=CVE-2024-26935 Référence CVE CVE-2024-26961 https://www.cve.org/CVERecord?id=CVE-2024-26961 Référence CVE CVE-2024-36244 https://www.cve.org/CVERecord?id=CVE-2024-36244 Référence CVE CVE-2024-36889 https://www.cve.org/CVERecord?id=CVE-2024-36889 Référence CVE CVE-2024-39472 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-2024-26650 Référence CVE CVE-2024-26652 https://www.cve.org/CVERecord?id=CVE-2024-26652 Référence CVE CVE-2024-26654 https://www.cve.org/CVERecord?id=CVE-2024-26654 Référence CVE CVE-2024-26656 https://www.cve.org/CVERecord?id=CVE-2024-26656 Référence CVE CVE-2024-26657 https://www.cve.org/CVERecord?id=CVE-2024-26657 Référence CVE CVE-2024-26659 https://www.cve.org/CVERecord?id=CVE-2024-26659 Référence CVE CVE-2024-26661 https://www.cve.org/CVERecord?id=CVE-2024-26661 Référence CVE CVE-2024-26663 https://www.cve.org/CVERecord?id=CVE-2024-26663 Référence CVE CVE-2024-26665 https://www.cve.org/CVERecord?id=CVE-2024-26665 Référence CVE CVE-2024-26671 https://www.cve.org/CVERecord?id=CVE-2024-26671 Référence CVE CVE-2024-26673 https://www.cve.org/CVERecord?id=CVE-2024-26673 Référence CVE CVE-2024-26674 https://www.cve.org/CVERecord?id=CVE-2024-26674 Référence CVE CVE-2024-26676 https://www.cve.org/CVERecord?id=CVE-2024-26676 Référence CVE CVE-2024-26679 https://www.cve.org/CVERecord?id=CVE-2024-26679 Référence CVE CVE-2024-26684 https://www.cve.org/CVERecord?id=CVE-2024-26684 Référence CVE CVE-2024-26685 https://www.cve.org/CVERecord?id=CVE-2024-26685 Référence CVE CVE-2024-26691 https://www.cve.org/CVERecord?id=CVE-2024-26691 Référence CVE CVE-2024-26704 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26643 Référence CVE CVE-2024-26644 https://www.cve.org/CVERecord?id=CVE-2024-26644 Référence CVE CVE-2024-26645 https://www.cve.org/CVERecord?id=CVE-2024-26645 Référence CVE CVE-2024-26651 https://www.cve.org/CVERecord?id=CVE-2024-26651 Référence CVE CVE-2024-26654 https://www.cve.org/CVERecord?id=CVE-2024-26654 Référence CVE CVE-2024-26659 https://www.cve.org/CVERecord?id=CVE-2024-26659 Référence CVE CVE-2024-26663 https://www.cve.org/CVERecord?id=CVE-2024-26663 Référence CVE CVE-2024-26664 https://www.cve.org/CVERecord?id=CVE-2024-26664 Référence CVE CVE-2024-26665 https://www.cve.org/CVERecord?id=CVE-2024-26665 Référence CVE CVE-2024-26671 https://www.cve.org/CVERecord?id=CVE-2024-26671 Référence CVE CVE-2024-26673 https://www.cve.org/CVERecord?id=CVE-2024-26673 Référence CVE CVE-2024-26675 https://www.cve.org/CVERecord?id=CVE-2024-26675 Référence CVE CVE-2024-26679 https://www.cve.org/CVERecord?id=CVE-2024-26679 Référence CVE CVE-2024-26684 https://www.cve.org/CVERecord?id=CVE-2024-26684 Référence CVE CVE-2024-26685 https://www.cve.org/CVERecord?id=CVE-2024-26685 Référence CVE CVE-2024-26687 https://www.cve.org/CVERecord?id=CVE-2024-26687 Référence CVE CVE-2024-26688 https://www.cve.org/CVERecord?id=CVE-2024-26688 Référence CVE CVE-2024-26689 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26625 Référence CVE CVE-2024-26632 https://www.cve.org/CVERecord?id=CVE-2024-26632 Référence CVE CVE-2024-26638 https://www.cve.org/CVERecord?id=CVE-2024-26638 Référence CVE CVE-2024-26642 https://www.cve.org/CVERecord?id=CVE-2024-26642 Référence CVE CVE-2024-26643 https://www.cve.org/CVERecord?id=CVE-2024-26643 Référence CVE CVE-2024-26652 https://www.cve.org/CVERecord?id=CVE-2024-26652 Référence CVE CVE-2024-26654 https://www.cve.org/CVERecord?id=CVE-2024-26654 Référence CVE CVE-2024-26656 https://www.cve.org/CVERecord?id=CVE-2024-26656 Référence CVE CVE-2024-26657 https://www.cve.org/CVERecord?id=CVE-2024-26657 Référence CVE CVE-2024-26671 https://www.cve.org/CVERecord?id=CVE-2024-26671 Référence CVE CVE-2024-26673 https://www.cve.org/CVERecord?id=CVE-2024-26673 Référence CVE CVE-2024-26674 https://www.cve.org/CVERecord?id=CVE-2024-26674 Référence CVE CVE-2024-26675 https://www.cve.org/CVERecord?id=CVE-2024-26675 Référence CVE CVE-2024-26679 https://www.cve.org/CVERecord?id=CVE-2024-26679 Référence CVE CVE-2024-26684 https://www.cve.org/CVERecord?id=CVE-2024-26684 Référence CVE CVE-2024-26685 https://www.cve.org/CVERecord?id=CVE-2024-26685 Référence CVE CVE-2024-26692 https://www.cve.org/CVERecord?id=CVE-2024-26692 Référence CVE CVE-2024-26696 https://www.cve.org/CVERecord?id=

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

cord?id=CVE-2024-1086 Référence CVE CVE-2024-1488 https://www.cve.org/CVERecord?id=CVE-2024-1488 Référence CVE CVE-2024-22243 https://www.cve.org/CVERecord?id=CVE-2024-22243 Référence CVE CVE-2024-22259 https://www.cve.org/CVERecord?id=CVE-2024-22259 Référence CVE CVE-2024-22262 https://www.cve.org/CVERecord?id=CVE-2024-22262 Référence CVE CVE-2024-25742 https://www.cve.org/CVERecord?id=CVE-2024-25742 Référence CVE CVE-2024-25743 https://www.cve.org/CVERecord?id=CVE-2024-25743 Référence CVE CVE-2024-26602 https://www.cve.org/CVERecord?id=CVE-2024-26602 Référence CVE CVE-2024-26609 https://www.cve.org/CVERecord?id=CVE-2024-26609 Référence CVE CVE-2024-26671 https://www.cve.org/CVERecord?id=CVE-2024-26671 Référence CVE CVE-2024-27269 https://www.cve.org/CVERecord?id=CVE-2024-27269 Référence CVE CVE-2024-28784 https://www.cve.org/CVERecord?id=CVE-2024-28784 Gestion détaillée du document le 19 juin 2024 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

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

Record?id=CVE-2023-6915 Référence CVE CVE-2023-6932 https://www.cve.org/CVERecord?id=CVE-2023-6932 Référence CVE CVE-2024-0841 https://www.cve.org/CVERecord?id=CVE-2024-0841 Référence CVE CVE-2024-22257 https://www.cve.org/CVERecord?id=CVE-2024-22257 Référence CVE CVE-2024-22262 https://www.cve.org/CVERecord?id=CVE-2024-22262 Référence CVE CVE-2024-25742 https://www.cve.org/CVERecord?id=CVE-2024-25742 Référence CVE CVE-2024-25743 https://www.cve.org/CVERecord?id=CVE-2024-25743 Référence CVE CVE-2024-26602 https://www.cve.org/CVERecord?id=CVE-2024-26602 Référence CVE CVE-2024-26609 https://www.cve.org/CVERecord?id=CVE-2024-26609 Référence CVE CVE-2024-26671 https://www.cve.org/CVERecord?id=CVE-2024-26671 Référence CVE CVE-2024-28757 https://www.cve.org/CVERecord?id=CVE-2024-28757 Référence CVE CVE-2024-29131 https://www.cve.org/CVERecord?id=CVE-2024-29131 Référence CVE CVE-2024-29133 https://www.cve.org/CVERecord?id=CVE-2024-29133 Gestion détaillée du document le 14 juin 2024 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des sy

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

rd?id=CVE-2024-2201 Référence CVE CVE-2024-22099 https://www.cve.org/CVERecord?id=CVE-2024-22099 Référence CVE CVE-2024-23307 https://www.cve.org/CVERecord?id=CVE-2024-23307 Référence CVE CVE-2024-23848 https://www.cve.org/CVERecord?id=CVE-2024-23848 Référence CVE CVE-2024-24855 https://www.cve.org/CVERecord?id=CVE-2024-24855 Référence CVE CVE-2024-24861 https://www.cve.org/CVERecord?id=CVE-2024-24861 Référence CVE CVE-2024-26614 https://www.cve.org/CVERecord?id=CVE-2024-26614 Référence CVE CVE-2024-26642 https://www.cve.org/CVERecord?id=CVE-2024-26642 Référence CVE CVE-2024-26651 https://www.cve.org/CVERecord?id=CVE-2024-26651 Référence CVE CVE-2024-26671 https://www.cve.org/CVERecord?id=CVE-2024-26671 Référence CVE CVE-2024-26675 https://www.cve.org/CVERecord?id=CVE-2024-26675 Référence CVE CVE-2024-26689 https://www.cve.org/CVERecord?id=CVE-2024-26689 Référence CVE CVE-2024-26704 https://www.cve.org/CVERecord?id=CVE-2024-26704 Référence CVE CVE-2024-26733 https://www.cve.org/CVERecord?id=CVE-2024-26733 Référence CVE CVE-2024-26739 https://www.cve.org/CVERecord?id=CVE-2024-26739 Référence CVE CVE-2024-26743 https://www.cve.org/CVERecord?id=CVE-2024-26743 Référence CVE CVE-2024-26744 https://www.cve.org/CVERecord?id=CVE-2024-26744 Référence CVE CVE-2024-26747 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26640 Référence CVE CVE-2024-26641 https://www.cve.org/CVERecord?id=CVE-2024-26641 Référence CVE CVE-2024-26644 https://www.cve.org/CVERecord?id=CVE-2024-26644 Référence CVE CVE-2024-26645 https://www.cve.org/CVERecord?id=CVE-2024-26645 Référence CVE CVE-2024-26660 https://www.cve.org/CVERecord?id=CVE-2024-26660 Référence CVE CVE-2024-26663 https://www.cve.org/CVERecord?id=CVE-2024-26663 Référence CVE CVE-2024-26664 https://www.cve.org/CVERecord?id=CVE-2024-26664 Référence CVE CVE-2024-26665 https://www.cve.org/CVERecord?id=CVE-2024-26665 Référence CVE CVE-2024-26668 https://www.cve.org/CVERecord?id=CVE-2024-26668 Référence CVE CVE-2024-26671 https://www.cve.org/CVERecord?id=CVE-2024-26671 Référence CVE CVE-2024-26673 https://www.cve.org/CVERecord?id=CVE-2024-26673 Référence CVE CVE-2024-26675 https://www.cve.org/CVERecord?id=CVE-2024-26675 Référence CVE CVE-2024-26676 https://www.cve.org/CVERecord?id=CVE-2024-26676 Référence CVE CVE-2024-26679 https://www.cve.org/CVERecord?id=CVE-2024-26679 Référence CVE CVE-2024-26684 https://www.cve.org/CVERecord?id=CVE-2024-26684 Référence CVE CVE-2024-26685 https://www.cve.org/CVERecord?id=CVE-2024-26685 Référence CVE CVE-2024-26689 https://www.cve.org/CVERecord?id=CVE-2024-26689 Référence CVE CVE-2024-26695 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26640 Référence CVE CVE-2024-26641 https://www.cve.org/CVERecord?id=CVE-2024-26641 Référence CVE CVE-2024-26644 https://www.cve.org/CVERecord?id=CVE-2024-26644 Référence CVE CVE-2024-26645 https://www.cve.org/CVERecord?id=CVE-2024-26645 Référence CVE CVE-2024-26660 https://www.cve.org/CVERecord?id=CVE-2024-26660 Référence CVE CVE-2024-26663 https://www.cve.org/CVERecord?id=CVE-2024-26663 Référence CVE CVE-2024-26664 https://www.cve.org/CVERecord?id=CVE-2024-26664 Référence CVE CVE-2024-26665 https://www.cve.org/CVERecord?id=CVE-2024-26665 Référence CVE CVE-2024-26668 https://www.cve.org/CVERecord?id=CVE-2024-26668 Référence CVE CVE-2024-26671 https://www.cve.org/CVERecord?id=CVE-2024-26671 Référence CVE CVE-2024-26673 https://www.cve.org/CVERecord?id=CVE-2024-26673 Référence CVE CVE-2024-26675 https://www.cve.org/CVERecord?id=CVE-2024-26675 Référence CVE CVE-2024-26676 https://www.cve.org/CVERecord?id=CVE-2024-26676 Référence CVE CVE-2024-26679 https://www.cve.org/CVERecord?id=CVE-2024-26679 Référence CVE CVE-2024-26684 https://www.cve.org/CVERecord?id=CVE-2024-26684 Référence CVE CVE-2024-26685 https://www.cve.org/CVERecord?id=CVE-2024-26685 Référence CVE CVE-2024-26689 https://www.cve.org/CVERecord?id=CVE-2024-26689 Référence CVE CVE-2024-26695 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-2024-23848 Référence CVE CVE-2024-24855 https://www.cve.org/CVERecord?id=CVE-2024-24855 Référence CVE CVE-2024-24861 https://www.cve.org/CVERecord?id=CVE-2024-24861 Référence CVE CVE-2024-26585 https://www.cve.org/CVERecord?id=CVE-2024-26585 Référence CVE CVE-2024-26610 https://www.cve.org/CVERecord?id=CVE-2024-26610 Référence CVE CVE-2024-26614 https://www.cve.org/CVERecord?id=CVE-2024-26614 Référence CVE CVE-2024-26622 https://www.cve.org/CVERecord?id=CVE-2024-26622 Référence CVE CVE-2024-26642 https://www.cve.org/CVERecord?id=CVE-2024-26642 Référence CVE CVE-2024-26651 https://www.cve.org/CVERecord?id=CVE-2024-26651 Référence CVE CVE-2024-26671 https://www.cve.org/CVERecord?id=CVE-2024-26671 Référence CVE CVE-2024-26675 https://www.cve.org/CVERecord?id=CVE-2024-26675 Référence CVE CVE-2024-26689 https://www.cve.org/CVERecord?id=CVE-2024-26689 Référence CVE CVE-2024-26704 https://www.cve.org/CVERecord?id=CVE-2024-26704 Référence CVE CVE-2024-26733 https://www.cve.org/CVERecord?id=CVE-2024-26733 Référence CVE CVE-2024-26739 https://www.cve.org/CVERecord?id=CVE-2024-26739 Référence CVE CVE-2024-26743 https://www.cve.org/CVERecord?id=CVE-2024-26743 Référence CVE CVE-2024-26744 https://www.cve.org/CVERecord?id=CVE-2024-26744 Référence CVE CVE-2024-26747 https://www.cve.org/CVERecord?id=

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

Record?id=CVE-2023-6932 Référence CVE CVE-2024-0841 https://www.cve.org/CVERecord?id=CVE-2024-0841 Référence CVE CVE-2024-1086 https://www.cve.org/CVERecord?id=CVE-2024-1086 Référence CVE CVE-2024-25742 https://www.cve.org/CVERecord?id=CVE-2024-25742 Référence CVE CVE-2024-25743 https://www.cve.org/CVERecord?id=CVE-2024-25743 Référence CVE CVE-2024-26602 https://www.cve.org/CVERecord?id=CVE-2024-26602 Référence CVE CVE-2024-26609 https://www.cve.org/CVERecord?id=CVE-2024-26609 Référence CVE CVE-2024-26642 https://www.cve.org/CVERecord?id=CVE-2024-26642 Référence CVE CVE-2024-26643 https://www.cve.org/CVERecord?id=CVE-2024-26643 Référence CVE CVE-2024-26671 https://www.cve.org/CVERecord?id=CVE-2024-26671 Référence CVE CVE-2024-26673 https://www.cve.org/CVERecord?id=CVE-2024-26673 Référence CVE CVE-2024-26804 https://www.cve.org/CVERecord?id=CVE-2024-26804 Gestion détaillée du document le 24 mai 2024 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

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

d?id=CVE-2024-26640 Référence CVE CVE-2024-26641 https://www.cve.org/CVERecord?id=CVE-2024-26641 Référence CVE CVE-2024-26644 https://www.cve.org/CVERecord?id=CVE-2024-26644 Référence CVE CVE-2024-26645 https://www.cve.org/CVERecord?id=CVE-2024-26645 Référence CVE CVE-2024-26660 https://www.cve.org/CVERecord?id=CVE-2024-26660 Référence CVE CVE-2024-26663 https://www.cve.org/CVERecord?id=CVE-2024-26663 Référence CVE CVE-2024-26664 https://www.cve.org/CVERecord?id=CVE-2024-26664 Référence CVE CVE-2024-26665 https://www.cve.org/CVERecord?id=CVE-2024-26665 Référence CVE CVE-2024-26668 https://www.cve.org/CVERecord?id=CVE-2024-26668 Référence CVE CVE-2024-26671 https://www.cve.org/CVERecord?id=CVE-2024-26671 Référence CVE CVE-2024-26673 https://www.cve.org/CVERecord?id=CVE-2024-26673 Référence CVE CVE-2024-26675 https://www.cve.org/CVERecord?id=CVE-2024-26675 Référence CVE CVE-2024-26676 https://www.cve.org/CVERecord?id=CVE-2024-26676 Référence CVE CVE-2024-26679 https://www.cve.org/CVERecord?id=CVE-2024-26679 Référence CVE CVE-2024-26684 https://www.cve.org/CVERecord?id=CVE-2024-26684 Référence CVE CVE-2024-26685 https://www.cve.org/CVERecord?id=CVE-2024-26685 Référence CVE CVE-2024-26689 https://www.cve.org/CVERecord?id=CVE-2024-26689 Référence CVE CVE-2024-26695 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-2024-25742 Référence CVE CVE-2024-26601 https://www.cve.org/CVERecord?id=CVE-2024-26601 Référence CVE CVE-2024-26610 https://www.cve.org/CVERecord?id=CVE-2024-26610 Référence CVE CVE-2024-26614 https://www.cve.org/CVERecord?id=CVE-2024-26614 Référence CVE CVE-2024-26622 https://www.cve.org/CVERecord?id=CVE-2024-26622 Référence CVE CVE-2024-26642 https://www.cve.org/CVERecord?id=CVE-2024-26642 Référence CVE CVE-2024-26651 https://www.cve.org/CVERecord?id=CVE-2024-26651 Référence CVE CVE-2024-26656 https://www.cve.org/CVERecord?id=CVE-2024-26656 Référence CVE CVE-2024-26660 https://www.cve.org/CVERecord?id=CVE-2024-26660 Référence CVE CVE-2024-26671 https://www.cve.org/CVERecord?id=CVE-2024-26671 Référence CVE CVE-2024-26673 https://www.cve.org/CVERecord?id=CVE-2024-26673 Référence CVE CVE-2024-26675 https://www.cve.org/CVERecord?id=CVE-2024-26675 Référence CVE CVE-2024-26679 https://www.cve.org/CVERecord?id=CVE-2024-26679 Référence CVE CVE-2024-26680 https://www.cve.org/CVERecord?id=CVE-2024-26680 Référence CVE CVE-2024-26681 https://www.cve.org/CVERecord?id=CVE-2024-26681 Référence CVE CVE-2024-26684 https://www.cve.org/CVERecord?id=CVE-2024-26684 Référence CVE CVE-2024-26685 https://www.cve.org/CVERecord?id=CVE-2024-26685 Référence CVE CVE-2024-26687 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26649 Référence CVE CVE-2024-26650 https://www.cve.org/CVERecord?id=CVE-2024-26650 Référence CVE CVE-2024-26660 https://www.cve.org/CVERecord?id=CVE-2024-26660 Référence CVE CVE-2024-26663 https://www.cve.org/CVERecord?id=CVE-2024-26663 Référence CVE CVE-2024-26664 https://www.cve.org/CVERecord?id=CVE-2024-26664 Référence CVE CVE-2024-26665 https://www.cve.org/CVERecord?id=CVE-2024-26665 Référence CVE CVE-2024-26668 https://www.cve.org/CVERecord?id=CVE-2024-26668 Référence CVE CVE-2024-26669 https://www.cve.org/CVERecord?id=CVE-2024-26669 Référence CVE CVE-2024-26670 https://www.cve.org/CVERecord?id=CVE-2024-26670 Référence CVE CVE-2024-26671 https://www.cve.org/CVERecord?id=CVE-2024-26671 Référence CVE CVE-2024-26673 https://www.cve.org/CVERecord?id=CVE-2024-26673 Référence CVE CVE-2024-26675 https://www.cve.org/CVERecord?id=CVE-2024-26675 Référence CVE CVE-2024-26676 https://www.cve.org/CVERecord?id=CVE-2024-26676 Référence CVE CVE-2024-26679 https://www.cve.org/CVERecord?id=CVE-2024-26679 Référence CVE CVE-2024-26684 https://www.cve.org/CVERecord?id=CVE-2024-26684 Référence CVE CVE-2024-26685 https://www.cve.org/CVERecord?id=CVE-2024-26685 Référence CVE CVE-2024-26689 https://www.cve.org/CVERecord?id=CVE-2024-26689 Référence CVE CVE-2024-26695 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26643 Référence CVE CVE-2024-26644 https://www.cve.org/CVERecord?id=CVE-2024-26644 Référence CVE CVE-2024-26645 https://www.cve.org/CVERecord?id=CVE-2024-26645 Référence CVE CVE-2024-26651 https://www.cve.org/CVERecord?id=CVE-2024-26651 Référence CVE CVE-2024-26654 https://www.cve.org/CVERecord?id=CVE-2024-26654 Référence CVE CVE-2024-26659 https://www.cve.org/CVERecord?id=CVE-2024-26659 Référence CVE CVE-2024-26663 https://www.cve.org/CVERecord?id=CVE-2024-26663 Référence CVE CVE-2024-26664 https://www.cve.org/CVERecord?id=CVE-2024-26664 Référence CVE CVE-2024-26665 https://www.cve.org/CVERecord?id=CVE-2024-26665 Référence CVE CVE-2024-26671 https://www.cve.org/CVERecord?id=CVE-2024-26671 Référence CVE CVE-2024-26673 https://www.cve.org/CVERecord?id=CVE-2024-26673 Référence CVE CVE-2024-26675 https://www.cve.org/CVERecord?id=CVE-2024-26675 Référence CVE CVE-2024-26679 https://www.cve.org/CVERecord?id=CVE-2024-26679 Référence CVE CVE-2024-26684 https://www.cve.org/CVERecord?id=CVE-2024-26684 Référence CVE CVE-2024-26685 https://www.cve.org/CVERecord?id=CVE-2024-26685 Référence CVE CVE-2024-26687 https://www.cve.org/CVERecord?id=CVE-2024-26687 Référence CVE CVE-2024-26688 https://www.cve.org/CVERecord?id=CVE-2024-26688 Référence CVE CVE-2024-26689 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26643 Référence CVE CVE-2024-26651 https://www.cve.org/CVERecord?id=CVE-2024-26651 Référence CVE CVE-2024-26654 https://www.cve.org/CVERecord?id=CVE-2024-26654 Référence CVE CVE-2024-26659 https://www.cve.org/CVERecord?id=CVE-2024-26659 Référence CVE CVE-2024-26660 https://www.cve.org/CVERecord?id=CVE-2024-26660 Référence CVE CVE-2024-26663 https://www.cve.org/CVERecord?id=CVE-2024-26663 Référence CVE CVE-2024-26664 https://www.cve.org/CVERecord?id=CVE-2024-26664 Référence CVE CVE-2024-26665 https://www.cve.org/CVERecord?id=CVE-2024-26665 Référence CVE CVE-2024-26667 https://www.cve.org/CVERecord?id=CVE-2024-26667 Référence CVE CVE-2024-26671 https://www.cve.org/CVERecord?id=CVE-2024-26671 Référence CVE CVE-2024-26673 https://www.cve.org/CVERecord?id=CVE-2024-26673 Référence CVE CVE-2024-26675 https://www.cve.org/CVERecord?id=CVE-2024-26675 Référence CVE CVE-2024-26676 https://www.cve.org/CVERecord?id=CVE-2024-26676 Référence CVE CVE-2024-26679 https://www.cve.org/CVERecord?id=CVE-2024-26679 Référence CVE CVE-2024-26680 https://www.cve.org/CVERecord?id=CVE-2024-26680 Référence CVE CVE-2024-26681 https://www.cve.org/CVERecord?id=CVE-2024-26681 Référence CVE CVE-2024-26684 https://www.cve.org/CVERecord?id=CVE-2024-26684 Référence CVE CVE-2024-26685 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-020603Linux の Linux Kernel 等複数ベンダの製品における競合状態に関する脆弱性

Linux の Linux Kernel 等複数ベンダの製品には、競合状態に関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 4.11, 4.19.307 ≤ 4.19.*, 5.4.269 ≤ 5.4.*, 5.10.210 ≤ 5.10.*, 5.15.149 ≤ 5.15.*, 6.1.77 ≤ 6.1.*, 6.6.16 ≤ 6.6.*, 6.7.4 ≤ 6.7.*, 6.8 ≤ *
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 2 Apr 2024 · Last source change 11 May 2026, 20:01 UTC · CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

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-2024-23933
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-2024-23933↗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-2024-26671 · cve.blacktree.nl