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

USB: core: Fix deadlock in port "disable" sysfs attribute

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 11 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 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: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 11 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

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

15 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 11 affected package states 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.6.7.12-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.85-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.7.12-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.7.12-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, 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
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, 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
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, 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
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, 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
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, 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
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, 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
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, 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
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.8Affected, 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
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, 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
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, 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
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, 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-2024-26933 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: USB: core: Fix deadlock in port "disable" sysfs attribute
50 known affected

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

  • bpftool as a component of Red Hat Enterprise Linux 7
  • kernel as a component of Red Hat Enterprise Linux 7
  • kernel-abi-whitelists as a component of Red Hat Enterprise Linux 7
  • kernel-bootwrapper as a component of Red Hat Enterprise Linux 7
  • kernel-debug as a component of Red Hat Enterprise Linux 7
  • kernel-debug-devel as a component of Red Hat Enterprise Linux 7
  • kernel-devel as a component of Red Hat Enterprise Linux 7
  • kernel-doc as a component of Red Hat Enterprise Linux 7
  • kernel-headers as a component of Red Hat Enterprise Linux 7
  • kernel-kdump as a component of Red Hat Enterprise Linux 7
  • kernel-kdump-devel as a component of Red Hat Enterprise Linux 7
  • kernel-rt as a component of Red Hat Enterprise Linux 7
Summary
In the Linux kernel, the following vulnerability has been resolved: USB: core: Fix deadlock in port "disable" sysfs attribute The Linux kernel CVE team has assigned CVE-2024-26933 to this issue. Upstream advisory: https://lore.kernel.org/linux-cve-announce/2024050123-CVE-2024-26933-c18d@gregkh/T
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.
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-24195

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 11 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: USB: core: Fix deadlock in port "disable" sysfs attribute The show and store callback routines for the "disable" sysfs attribute file in port.c acquire the device lock for the port's parent hub device. This can cause problems if another process has locked the hub to remove it or change its configuration: Removing the hub or changing its configuration requires the hub interface to be removed, which requires the port device to be removed, and device_del() waits until all outstanding sysfs attribute callbacks for the ports have returned. The lock can't be released until then. But the disable_show() or disable_store() routine can't return until after it has acquired the lock. The resulting deadlock can be avoided by calling sysfs_break_active_protection(). This will cause the sysfs core not to wait for the attribute's callback routine to return, allowing the removal to proceed. The disadvantage is that after making this call, there is no guarantee that the hub structure won't be deallocated at any moment. To prevent this, we have to acquire a reference to it first by calling hub_get().

What

In the Linux kernel, the following vulnerability has been resolved: USB: core: Fix deadlock in port "disable" sysfs attribute The show and store callback routines for the "disable" sysfs attribute file in port.c acquire the device lock for the port's parent hub device. This can cause problems if another process has locked the hub to remove it or change its configuration: Removing the hub or changing its configuration requires the hub interface to be removed, which requires the port device to be removed, and device_del() waits until all outstanding sysfs attribute callbacks for the ports have returned. The lock can't be released until then. But the disable_show() or disable_store() routine can't return until after it has acquired the lock. The resulting deadlock can be avoided by calling sysfs_break_active_protection(). This will cause the sysfs core not to wait for the attribute's callback routine to return, allowing the removal to proceed. The disadvantage is that after making this call, there is no guarantee that the hub structure won't be deallocated at any moment. To prevent this, we have to acquire a reference to it first by calling hub_get().

Why

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

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: USB: core: Fix deadlock in port "disable" sysfs attribute The show and store callback routines for the "disable" sysfs attribute file in port.c acquire the device lock for the port's parent hub device. This can cause problems if another process has locked the hub to remove it or change its configuration: Removing the hub or changing its configuration requires the hub interface to be removed, which requires the port device to be removed, and device_del() waits until all outstanding sysfs attribute callbacks for the ports have returned. The lock can't be released until then. But the disable_show() or disable_store() routine can't return until after it has acquired the lock. The resulting deadlock can be avoided by calling sysfs_break_active_protection(). This will cause the sysfs core not to wait for the attribute's callback routine to return, allowing the removal to proceed. The disadvantage is that after making this call, there is no guarantee that the hub structure won't be deallocated at any moment. To prevent this, we have to acquire a reference to it first by calling hub_get().

Why

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

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may 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
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-667 ↗

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

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
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-2024-1008Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

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

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240508Security Bulletin 08 May 2024

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

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

d?id=CVE-2024-26803 Référence CVE CVE-2024-26815 https://www.cve.org/CVERecord?id=CVE-2024-26815 Référence CVE CVE-2024-26818 https://www.cve.org/CVERecord?id=CVE-2024-26818 Référence CVE CVE-2024-26831 https://www.cve.org/CVERecord?id=CVE-2024-26831 Référence CVE CVE-2024-26837 https://www.cve.org/CVERecord?id=CVE-2024-26837 Référence CVE CVE-2024-26838 https://www.cve.org/CVERecord?id=CVE-2024-26838 Référence CVE CVE-2024-26892 https://www.cve.org/CVERecord?id=CVE-2024-26892 Référence CVE CVE-2024-26899 https://www.cve.org/CVERecord?id=CVE-2024-26899 Référence CVE CVE-2024-26918 https://www.cve.org/CVERecord?id=CVE-2024-26918 Référence CVE CVE-2024-26933 https://www.cve.org/CVERecord?id=CVE-2024-26933 Référence CVE CVE-2024-26953 https://www.cve.org/CVERecord?id=CVE-2024-26953 Référence CVE CVE-2024-26964 https://www.cve.org/CVERecord?id=CVE-2024-26964 Référence CVE CVE-2024-26975 https://www.cve.org/CVERecord?id=CVE-2024-26975 Référence CVE CVE-2024-26987 https://www.cve.org/CVERecord?id=CVE-2024-26987 Référence CVE CVE-2024-26989 https://www.cve.org/CVERecord?id=CVE-2024-26989 Référence CVE CVE-2024-26990 https://www.cve.org/CVERecord?id=CVE-2024-26990 Référence CVE CVE-2024-26992 https://www.cve.org/CVERecord?id=CVE-2024-26992 Référence CVE CVE-2024-27003 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-2024-26826 Référence CVE CVE-2024-26859 https://www.cve.org/CVERecord?id=CVE-2024-26859 Référence CVE CVE-2024-26872 https://www.cve.org/CVERecord?id=CVE-2024-26872 Référence CVE CVE-2024-26892 https://www.cve.org/CVERecord?id=CVE-2024-26892 Référence CVE CVE-2024-26897 https://www.cve.org/CVERecord?id=CVE-2024-26897 Référence CVE CVE-2024-26901 https://www.cve.org/CVERecord?id=CVE-2024-26901 Référence CVE CVE-2024-26906 https://www.cve.org/CVERecord?id=CVE-2024-26906 Référence CVE CVE-2024-26907 https://www.cve.org/CVERecord?id=CVE-2024-26907 Référence CVE CVE-2024-26919 https://www.cve.org/CVERecord?id=CVE-2024-26919 Référence CVE CVE-2024-26933 https://www.cve.org/CVERecord?id=CVE-2024-26933 Référence CVE CVE-2024-26934 https://www.cve.org/CVERecord?id=CVE-2024-26934 Référence CVE CVE-2024-26964 https://www.cve.org/CVERecord?id=CVE-2024-26964 Référence CVE CVE-2024-26973 https://www.cve.org/CVERecord?id=CVE-2024-26973 Référence CVE CVE-2024-26974 https://www.cve.org/CVERecord?id=CVE-2024-26974 Référence CVE CVE-2024-26982 https://www.cve.org/CVERecord?id=CVE-2024-26982 Référence CVE CVE-2024-26993 https://www.cve.org/CVERecord?id=CVE-2024-26993 Référence CVE CVE-2024-27014 https://www.cve.org/CVERecord?id=CVE-2024-27014 Référence CVE CVE-2024-27048 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-26909 Référence CVE CVE-2024-26920 https://www.cve.org/CVERecord?id=CVE-2024-26920 Référence CVE CVE-2024-26921 https://www.cve.org/CVERecord?id=CVE-2024-26921 Référence CVE CVE-2024-26922 https://www.cve.org/CVERecord?id=CVE-2024-26922 Référence CVE CVE-2024-26923 https://www.cve.org/CVERecord?id=CVE-2024-26923 Référence CVE CVE-2024-26924 https://www.cve.org/CVERecord?id=CVE-2024-26924 Référence CVE CVE-2024-26925 https://www.cve.org/CVERecord?id=CVE-2024-26925 Référence CVE CVE-2024-26928 https://www.cve.org/CVERecord?id=CVE-2024-26928 Référence CVE CVE-2024-26932 https://www.cve.org/CVERecord?id=CVE-2024-26932 Référence CVE CVE-2024-26933 https://www.cve.org/CVERecord?id=CVE-2024-26933 Référence CVE CVE-2024-26934 https://www.cve.org/CVERecord?id=CVE-2024-26934 Référence CVE CVE-2024-26935 https://www.cve.org/CVERecord?id=CVE-2024-26935 Référence CVE CVE-2024-269355 https://www.cve.org/CVERecord?id=CVE-2024-269355 Référence CVE CVE-2024-26937 https://www.cve.org/CVERecord?id=CVE-2024-26937 Référence CVE CVE-2024-26938 https://www.cve.org/CVERecord?id=CVE-2024-26938 Référence CVE CVE-2024-26940 https://www.cve.org/CVERecord?id=CVE-2024-26940 Référence CVE CVE-2024-26943 https://www.cve.org/CVERecord?id=CVE-2024-26943 Référence CVE CVE-2024-26944 https://www.cve.org/CVERecord?i

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

d?id=CVE-2024-26694 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-26779 https://www.cve.org/CVERecord?id=CVE-2024-26779 Référence CVE CVE-2024-26872 https://www.cve.org/CVERecord?id=CVE-2024-26872 Référence CVE CVE-2024-26892 https://www.cve.org/CVERecord?id=CVE-2024-26892 Référence CVE CVE-2024-26897 https://www.cve.org/CVERecord?id=CVE-2024-26897 Référence CVE CVE-2024-26901 https://www.cve.org/CVERecord?id=CVE-2024-26901 Référence CVE CVE-2024-26919 https://www.cve.org/CVERecord?id=CVE-2024-26919 Référence CVE CVE-2024-26933 https://www.cve.org/CVERecord?id=CVE-2024-26933 Référence CVE CVE-2024-26934 https://www.cve.org/CVERecord?id=CVE-2024-26934 Référence CVE CVE-2024-26964 https://www.cve.org/CVERecord?id=CVE-2024-26964 Référence CVE CVE-2024-26973 https://www.cve.org/CVERecord?id=CVE-2024-26973 Référence CVE CVE-2024-26993 https://www.cve.org/CVERecord?id=CVE-2024-26993 Référence CVE CVE-2024-27014 https://www.cve.org/CVERecord?id=CVE-2024-27014 Référence CVE CVE-2024-27048 https://www.cve.org/CVERecord?id=CVE-2024-27048 Référence CVE CVE-2024-27052 https://www.cve.org/CVERecord?id=CVE-2024-27052 Référence CVE CVE-2024-27056 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26915 Référence CVE CVE-2024-26922 https://www.cve.org/CVERecord?id=CVE-2024-26922 Référence CVE CVE-2024-26924 https://www.cve.org/CVERecord?id=CVE-2024-26924 Référence CVE CVE-2024-26925 https://www.cve.org/CVERecord?id=CVE-2024-26925 Référence CVE CVE-2024-26927 https://www.cve.org/CVERecord?id=CVE-2024-26927 Référence CVE CVE-2024-26929 https://www.cve.org/CVERecord?id=CVE-2024-26929 Référence CVE CVE-2024-26930 https://www.cve.org/CVERecord?id=CVE-2024-26930 Référence CVE CVE-2024-26931 https://www.cve.org/CVERecord?id=CVE-2024-26931 Référence CVE CVE-2024-26932 https://www.cve.org/CVERecord?id=CVE-2024-26932 Référence CVE CVE-2024-26933 https://www.cve.org/CVERecord?id=CVE-2024-26933 Référence CVE CVE-2024-26934 https://www.cve.org/CVERecord?id=CVE-2024-26934 Référence CVE CVE-2024-26935 https://www.cve.org/CVERecord?id=CVE-2024-26935 Référence CVE CVE-2024-26937 https://www.cve.org/CVERecord?id=CVE-2024-26937 Référence CVE CVE-2024-26938 https://www.cve.org/CVERecord?id=CVE-2024-26938 Référence CVE CVE-2024-26939 https://www.cve.org/CVERecord?id=CVE-2024-26939 Référence CVE CVE-2024-26940 https://www.cve.org/CVERecord?id=CVE-2024-26940 Référence CVE CVE-2024-26941 https://www.cve.org/CVERecord?id=CVE-2024-26941 Référence CVE CVE-2024-26942 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-26921 Référence CVE CVE-2024-26922 https://www.cve.org/CVERecord?id=CVE-2024-26922 Référence CVE CVE-2024-26923 https://www.cve.org/CVERecord?id=CVE-2024-26923 Référence CVE CVE-2024-26925 https://www.cve.org/CVERecord?id=CVE-2024-26925 Référence CVE CVE-2024-26928 https://www.cve.org/CVERecord?id=CVE-2024-26928 Référence CVE CVE-2024-26929 https://www.cve.org/CVERecord?id=CVE-2024-26929 Référence CVE CVE-2024-26930 https://www.cve.org/CVERecord?id=CVE-2024-26930 Référence CVE CVE-2024-26931 https://www.cve.org/CVERecord?id=CVE-2024-26931 Référence CVE CVE-2024-26932 https://www.cve.org/CVERecord?id=CVE-2024-26932 Référence CVE CVE-2024-26933 https://www.cve.org/CVERecord?id=CVE-2024-26933 Référence CVE CVE-2024-26934 https://www.cve.org/CVERecord?id=CVE-2024-26934 Référence CVE CVE-2024-26935 https://www.cve.org/CVERecord?id=CVE-2024-26935 Référence CVE CVE-2024-26937 https://www.cve.org/CVERecord?id=CVE-2024-26937 Référence CVE CVE-2024-26938 https://www.cve.org/CVERecord?id=CVE-2024-26938 Référence CVE CVE-2024-26939 https://www.cve.org/CVERecord?id=CVE-2024-26939 Référence CVE CVE-2024-26940 https://www.cve.org/CVERecord?id=CVE-2024-26940 Référence CVE CVE-2024-26943 https://www.cve.org/CVERecord?id=CVE-2024-26943 Référence CVE CVE-2024-26945 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26919 Référence CVE CVE-2024-26920 https://www.cve.org/CVERecord?id=CVE-2024-26920 Référence CVE CVE-2024-26921 https://www.cve.org/CVERecord?id=CVE-2024-26921 Référence CVE CVE-2024-26922 https://www.cve.org/CVERecord?id=CVE-2024-26922 Référence CVE CVE-2024-26925 https://www.cve.org/CVERecord?id=CVE-2024-26925 Référence CVE CVE-2024-26928 https://www.cve.org/CVERecord?id=CVE-2024-26928 Référence CVE CVE-2024-26929 https://www.cve.org/CVERecord?id=CVE-2024-26929 Référence CVE CVE-2024-26930 https://www.cve.org/CVERecord?id=CVE-2024-26930 Référence CVE CVE-2024-26931 https://www.cve.org/CVERecord?id=CVE-2024-26931 Référence CVE CVE-2024-26933 https://www.cve.org/CVERecord?id=CVE-2024-26933 Référence CVE CVE-2024-26934 https://www.cve.org/CVERecord?id=CVE-2024-26934 Référence CVE CVE-2024-269355 https://www.cve.org/CVERecord?id=CVE-2024-269355 Référence CVE CVE-2024-26937 https://www.cve.org/CVERecord?id=CVE-2024-26937 Référence CVE CVE-2024-26938 https://www.cve.org/CVERecord?id=CVE-2024-26938 Référence CVE CVE-2024-26939 https://www.cve.org/CVERecord?id=CVE-2024-26939 Référence CVE CVE-2024-26940 https://www.cve.org/CVERecord?id=CVE-2024-26940 Référence CVE CVE-2024-26943 https://www.cve.org/CVERecord?id=CVE-2024-26943 Référence CVE CVE-2024-26957 https://www.cve.org/CVERecord?i

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

d?id=CVE-2024-26735 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-26779 https://www.cve.org/CVERecord?id=CVE-2024-26779 Référence CVE CVE-2024-26872 https://www.cve.org/CVERecord?id=CVE-2024-26872 Référence CVE CVE-2024-26892 https://www.cve.org/CVERecord?id=CVE-2024-26892 Référence CVE CVE-2024-26897 https://www.cve.org/CVERecord?id=CVE-2024-26897 Référence CVE CVE-2024-26901 https://www.cve.org/CVERecord?id=CVE-2024-26901 Référence CVE CVE-2024-26919 https://www.cve.org/CVERecord?id=CVE-2024-26919 Référence CVE CVE-2024-26933 https://www.cve.org/CVERecord?id=CVE-2024-26933 Référence CVE CVE-2024-26934 https://www.cve.org/CVERecord?id=CVE-2024-26934 Référence CVE CVE-2024-26964 https://www.cve.org/CVERecord?id=CVE-2024-26964 Référence CVE CVE-2024-26973 https://www.cve.org/CVERecord?id=CVE-2024-26973 Référence CVE CVE-2024-26993 https://www.cve.org/CVERecord?id=CVE-2024-26993 Référence CVE CVE-2024-27014 https://www.cve.org/CVERecord?id=CVE-2024-27014 Référence CVE CVE-2024-27048 https://www.cve.org/CVERecord?id=CVE-2024-27048 Référence CVE CVE-2024-27052 https://www.cve.org/CVERecord?id=CVE-2024-27052 Référence CVE CVE-2024-27056 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-26906 Référence CVE CVE-2024-26907 https://www.cve.org/CVERecord?id=CVE-2024-26907 Référence CVE CVE-2024-26915 https://www.cve.org/CVERecord?id=CVE-2024-26915 Référence CVE CVE-2024-26917 https://www.cve.org/CVERecord?id=CVE-2024-26917 Référence CVE CVE-2024-26922 https://www.cve.org/CVERecord?id=CVE-2024-26922 Référence CVE CVE-2024-26927 https://www.cve.org/CVERecord?id=CVE-2024-26927 Référence CVE CVE-2024-26929 https://www.cve.org/CVERecord?id=CVE-2024-26929 Référence CVE CVE-2024-26930 https://www.cve.org/CVERecord?id=CVE-2024-26930 Référence CVE CVE-2024-26931 https://www.cve.org/CVERecord?id=CVE-2024-26931 Référence CVE CVE-2024-26933 https://www.cve.org/CVERecord?id=CVE-2024-26933 Référence CVE CVE-2024-26939 https://www.cve.org/CVERecord?id=CVE-2024-26939 Référence CVE CVE-2024-26948 https://www.cve.org/CVERecord?id=CVE-2024-26948 Référence CVE CVE-2024-26950 https://www.cve.org/CVERecord?id=CVE-2024-26950 Référence CVE CVE-2024-26951 https://www.cve.org/CVERecord?id=CVE-2024-26951 Référence CVE CVE-2024-26955 https://www.cve.org/CVERecord?id=CVE-2024-26955 Référence CVE CVE-2024-26956 https://www.cve.org/CVERecord?id=CVE-2024-26956 Référence CVE CVE-2024-26960 https://www.cve.org/CVERecord?id=CVE-2024-26960 Référence CVE CVE-2024-26965 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-003245Linux の 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
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 1 May 2024 · Last source change 11 May 2026, 20:07 UTC · CWE-667 · Improper Locking

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-24195
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
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-24195↗Vendor CSAF · Red Hat Product Security↗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-26933 · cve.blacktree.nl