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

net: hns3: fix a deadlock problem when config TC during resetting

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 20 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 5 Aug 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: 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 20 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.

19 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 15 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.10.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.112-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.10.7-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.10.7-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-gkeopAffected, 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-nvidiaAffected, 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-nvidia-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
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, 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.

3 current
CVE-2024-44995 · CSAF 2.0 · revision 18 · interimSUSE Product Security TeamCVE-2024-44995
295 known affected

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

  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 12 SP5
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 12 SP5
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP2
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP2
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP2
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP2
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP2
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP2
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP4
Summary
In the Linux kernel, the following vulnerability has been resolved: net: hns3: fix a deadlock problem when config TC during resetting When config TC during the reset process, may cause a deadlock, the flow is as below: pf reset start | v ...... setup tc | | v v DOWN: napi_disable() napi_disable()(skip) | | | v v ...... ...... | | v | napi_enable() | v UINIT: netif_napi_del() | v ...... | v INIT: netif_napi_add() | v ...... global reset start | | v v UP: napi_enable()(skip) ...... | | v v ...... napi_disable() In reset process, the driver will DOWN the port and then UINIT, in this case, the setup tc process will UP the port before UINIT, so cause the problem. Adds a DOWN process in UINIT to fix it.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
SSA-355557 · CSAF 2.0 · revision 3 · interimSiemens ProductCERTSSA-355557: Multiple Vulnerabilities in Third-Party Components in SINEC OS before V3.2
3 known affected

The vendor explicitly identifies these products as 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
net: hns3: a deadlock problem when config TC during resetting.
Remediation
Update to V3.2 or later version
SSA-613116 · CSAF 2.0 · revision 3 · interimSiemens ProductCERTSSA-613116: Multiple Vulnerabilities in Third-Party Components in SINEC OS before V3.1
2 known affected

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

  • RUGGEDCOM RST2428P (6GK6242-6PA00)
  • SCALANCE XCM-/XRM-/XCH-/XRH-300 family
Summary
net: hns3: a deadlock problem when config TC during resetting.
Remediation
Update to V3.1 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-41197

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 20 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: net: hns3: fix a deadlock problem when config TC during resetting When config TC during the reset process, may cause a deadlock, the flow is as below: pf reset start │ ▼ ...... setup tc │ │ ▼ ▼ DOWN: napi_disable() napi_disable()(skip) │ │ │ ▼ ▼ ...... ...... │ │ ▼ │ napi_enable() │ ▼ UINIT: netif_napi_del() │ ▼ ...... │ ▼ INIT: netif_napi_add() │ ▼ ...... global reset start │ │ ▼ ▼ UP: napi_enable()(skip) ...... │ │ ▼ ▼ ...... napi_disable() In reset process, the driver will DOWN the port and then UINIT, in this case, the setup tc process will UP the port before UINIT, so cause the problem. Adds a DOWN process in UINIT to fix it.

What

In the Linux kernel, the following vulnerability has been resolved: net: hns3: fix a deadlock problem when config TC during resetting When config TC during the reset process, may cause a deadlock, the flow is as below: pf reset start │ ▼ ...... setup tc │ │ ▼ ▼ DOWN: napi_disable() napi_disable()(skip) │ │ │ ▼ ▼ ...... ...... │ │ ▼ │ napi_enable() │ ▼ UINIT: netif_napi_del() │ ▼ ...... │ ▼ INIT: netif_napi_add() │ ▼ ...... global reset start │ │ ▼ ▼ UP: napi_enable()(skip) ...... │ │ ▼ ▼ ...... napi_disable() In reset process, the driver will DOWN the port and then UINIT, in this case, the setup tc process will UP the port before UINIT, so cause the problem. Adds a DOWN process in UINIT to fix it.

Why

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

How

An attacker operating through local access may attempt exploitation with 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: net: hns3: fix a deadlock problem when config TC during resetting When config TC during the reset process, may cause a deadlock, the flow is as below: pf reset start │ ▼ ...... setup tc │ │ ▼ ▼ DOWN: napi_disable() napi_disable()(skip) │ │ │ ▼ ▼ ...... ...... │ │ ▼ │ napi_enable() │ ▼ UINIT: netif_napi_del() │ ▼ ...... │ ▼ INIT: netif_napi_add() │ ▼ ...... global reset start │ │ ▼ ▼ UP: napi_enable()(skip) ...... │ │ ▼ ▼ ...... napi_disable() In reset process, the driver will DOWN the port and then UINIT, in this case, the setup tc process will UP the port before UINIT, so cause the problem. Adds a DOWN process in UINIT to fix it.

Why

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

How

An attacker operating through local access may attempt exploitation with 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-2057Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service oder unspezifischer Angriff

Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder weitere unspezifische Angriffe durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240911Security Bulletin 11 Sep 2024

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 11 Sep 2024, published on 11 September 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-44954 Référence CVE CVE-2024-44960 https://www.cve.org/CVERecord?id=CVE-2024-44960 Référence CVE CVE-2024-44965 https://www.cve.org/CVERecord?id=CVE-2024-44965 Référence CVE CVE-2024-44969 https://www.cve.org/CVERecord?id=CVE-2024-44969 Référence CVE CVE-2024-44971 https://www.cve.org/CVERecord?id=CVE-2024-44971 Référence CVE CVE-2024-44987 https://www.cve.org/CVERecord?id=CVE-2024-44987 Référence CVE CVE-2024-44988 https://www.cve.org/CVERecord?id=CVE-2024-44988 Référence CVE CVE-2024-44989 https://www.cve.org/CVERecord?id=CVE-2024-44989 Référence CVE CVE-2024-44990 https://www.cve.org/CVERecord?id=CVE-2024-44990 Référence CVE CVE-2024-44995 https://www.cve.org/CVERecord?id=CVE-2024-44995 Référence CVE CVE-2024-44998 https://www.cve.org/CVERecord?id=CVE-2024-44998 Référence CVE CVE-2024-44999 https://www.cve.org/CVERecord?id=CVE-2024-44999 Référence CVE CVE-2024-45003 https://www.cve.org/CVERecord?id=CVE-2024-45003 Référence CVE CVE-2024-45006 https://www.cve.org/CVERecord?id=CVE-2024-45006 Référence CVE CVE-2024-45008 https://www.cve.org/CVERecord?id=CVE-2024-45008 Référence CVE CVE-2024-45021 https://www.cve.org/CVERecord?id=CVE-2024-45021 Référence CVE CVE-2024-45025 https://www.cve.org/CVERecord?id=CVE-2024-45025 Référence CVE CVE-2024-46673 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-41082 Référence CVE CVE-2024-42098 https://www.cve.org/CVERecord?id=CVE-2024-42098 Référence CVE CVE-2024-42114 https://www.cve.org/CVERecord?id=CVE-2024-42114 Référence CVE CVE-2024-42131 https://www.cve.org/CVERecord?id=CVE-2024-42131 Référence CVE CVE-2024-42145 https://www.cve.org/CVERecord?id=CVE-2024-42145 Référence CVE CVE-2024-42229 https://www.cve.org/CVERecord?id=CVE-2024-42229 Référence CVE CVE-2024-42253 https://www.cve.org/CVERecord?id=CVE-2024-42253 Référence CVE CVE-2024-44931 https://www.cve.org/CVERecord?id=CVE-2024-44931 Référence CVE CVE-2024-44958 https://www.cve.org/CVERecord?id=CVE-2024-44958 Référence CVE CVE-2024-44995 https://www.cve.org/CVERecord?id=CVE-2024-44995 Référence CVE CVE-2024-45016 https://www.cve.org/CVERecord?id=CVE-2024-45016 Référence CVE CVE-2024-46724 https://www.cve.org/CVERecord?id=CVE-2024-46724 Référence CVE CVE-2024-46755 https://www.cve.org/CVERecord?id=CVE-2024-46755 Référence CVE CVE-2024-46771 https://www.cve.org/CVERecord?id=CVE-2024-46771 Référence CVE CVE-2024-46777 https://www.cve.org/CVERecord?id=CVE-2024-46777 Référence CVE CVE-2024-46800 https://www.cve.org/CVERecord?id=CVE-2024-46800 Référence CVE CVE-2024-46802 https://www.cve.org/CVERecord?id=CVE-2024-46802 Référence CVE CVE-2024-46809 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-44984 Référence CVE CVE-2024-44985 https://www.cve.org/CVERecord?id=CVE-2024-44985 Référence CVE CVE-2024-44986 https://www.cve.org/CVERecord?id=CVE-2024-44986 Référence CVE CVE-2024-44987 https://www.cve.org/CVERecord?id=CVE-2024-44987 Référence CVE CVE-2024-44988 https://www.cve.org/CVERecord?id=CVE-2024-44988 Référence CVE CVE-2024-44989 https://www.cve.org/CVERecord?id=CVE-2024-44989 Référence CVE CVE-2024-44990 https://www.cve.org/CVERecord?id=CVE-2024-44990 Référence CVE CVE-2024-44991 https://www.cve.org/CVERecord?id=CVE-2024-44991 Référence CVE CVE-2024-44993 https://www.cve.org/CVERecord?id=CVE-2024-44993 Référence CVE CVE-2024-44995 https://www.cve.org/CVERecord?id=CVE-2024-44995 Référence CVE CVE-2024-44996 https://www.cve.org/CVERecord?id=CVE-2024-44996 Référence CVE CVE-2024-44998 https://www.cve.org/CVERecord?id=CVE-2024-44998 Référence CVE CVE-2024-44999 https://www.cve.org/CVERecord?id=CVE-2024-44999 Référence CVE CVE-2024-45000 https://www.cve.org/CVERecord?id=CVE-2024-45000 Référence CVE CVE-2024-45001 https://www.cve.org/CVERecord?id=CVE-2024-45001 Référence CVE CVE-2024-45002 https://www.cve.org/CVERecord?id=CVE-2024-45002 Référence CVE CVE-2024-45003 https://www.cve.org/CVERecord?id=CVE-2024-45003 Référence CVE CVE-2024-45005 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-44982 Référence CVE CVE-2024-44983 https://www.cve.org/CVERecord?id=CVE-2024-44983 Référence CVE CVE-2024-44985 https://www.cve.org/CVERecord?id=CVE-2024-44985 Référence CVE CVE-2024-44986 https://www.cve.org/CVERecord?id=CVE-2024-44986 Référence CVE CVE-2024-44987 https://www.cve.org/CVERecord?id=CVE-2024-44987 Référence CVE CVE-2024-44988 https://www.cve.org/CVERecord?id=CVE-2024-44988 Référence CVE CVE-2024-44989 https://www.cve.org/CVERecord?id=CVE-2024-44989 Référence CVE CVE-2024-44990 https://www.cve.org/CVERecord?id=CVE-2024-44990 Référence CVE CVE-2024-44991 https://www.cve.org/CVERecord?id=CVE-2024-44991 Référence CVE CVE-2024-44995 https://www.cve.org/CVERecord?id=CVE-2024-44995 Référence CVE CVE-2024-44998 https://www.cve.org/CVERecord?id=CVE-2024-44998 Référence CVE CVE-2024-44999 https://www.cve.org/CVERecord?id=CVE-2024-44999 Référence CVE CVE-2024-45000 https://www.cve.org/CVERecord?id=CVE-2024-45000 Référence CVE CVE-2024-45002 https://www.cve.org/CVERecord?id=CVE-2024-45002 Référence CVE CVE-2024-45003 https://www.cve.org/CVERecord?id=CVE-2024-45003 Référence CVE CVE-2024-45006 https://www.cve.org/CVERecord?id=CVE-2024-45006 Référence CVE CVE-2024-45007 https://www.cve.org/CVERecord?id=CVE-2024-45007 Référence CVE CVE-2024-45008 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-42253 Référence CVE CVE-2024-43817 https://www.cve.org/CVERecord?id=CVE-2024-43817 Référence CVE CVE-2024-43854 https://www.cve.org/CVERecord?id=CVE-2024-43854 Référence CVE CVE-2024-43897 https://www.cve.org/CVERecord?id=CVE-2024-43897 Référence CVE CVE-2024-44931 https://www.cve.org/CVERecord?id=CVE-2024-44931 Référence CVE CVE-2024-44932 https://www.cve.org/CVERecord?id=CVE-2024-44932 Référence CVE CVE-2024-44947 https://www.cve.org/CVERecord?id=CVE-2024-44947 Référence CVE CVE-2024-44958 https://www.cve.org/CVERecord?id=CVE-2024-44958 Référence CVE CVE-2024-44964 https://www.cve.org/CVERecord?id=CVE-2024-44964 Référence CVE CVE-2024-44995 https://www.cve.org/CVERecord?id=CVE-2024-44995 Référence CVE CVE-2024-45016 https://www.cve.org/CVERecord?id=CVE-2024-45016 Référence CVE CVE-2024-45025 https://www.cve.org/CVERecord?id=CVE-2024-45025 Référence CVE CVE-2024-46678 https://www.cve.org/CVERecord?id=CVE-2024-46678 Référence CVE CVE-2024-46680 https://www.cve.org/CVERecord?id=CVE-2024-46680 Référence CVE CVE-2024-46681 https://www.cve.org/CVERecord?id=CVE-2024-46681 Référence CVE CVE-2024-46716 https://www.cve.org/CVERecord?id=CVE-2024-46716 Référence CVE CVE-2024-46719 https://www.cve.org/CVERecord?id=CVE-2024-46719 Référence CVE CVE-2024-46721 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-44984 Référence CVE CVE-2024-44985 https://www.cve.org/CVERecord?id=CVE-2024-44985 Référence CVE CVE-2024-44986 https://www.cve.org/CVERecord?id=CVE-2024-44986 Référence CVE CVE-2024-44987 https://www.cve.org/CVERecord?id=CVE-2024-44987 Référence CVE CVE-2024-44988 https://www.cve.org/CVERecord?id=CVE-2024-44988 Référence CVE CVE-2024-44989 https://www.cve.org/CVERecord?id=CVE-2024-44989 Référence CVE CVE-2024-44990 https://www.cve.org/CVERecord?id=CVE-2024-44990 Référence CVE CVE-2024-44991 https://www.cve.org/CVERecord?id=CVE-2024-44991 Référence CVE CVE-2024-44993 https://www.cve.org/CVERecord?id=CVE-2024-44993 Référence CVE CVE-2024-44995 https://www.cve.org/CVERecord?id=CVE-2024-44995 Référence CVE CVE-2024-44996 https://www.cve.org/CVERecord?id=CVE-2024-44996 Référence CVE CVE-2024-44998 https://www.cve.org/CVERecord?id=CVE-2024-44998 Référence CVE CVE-2024-44999 https://www.cve.org/CVERecord?id=CVE-2024-44999 Référence CVE CVE-2024-45000 https://www.cve.org/CVERecord?id=CVE-2024-45000 Référence CVE CVE-2024-45001 https://www.cve.org/CVERecord?id=CVE-2024-45001 Référence CVE CVE-2024-45002 https://www.cve.org/CVERecord?id=CVE-2024-45002 Référence CVE CVE-2024-45003 https://www.cve.org/CVERecord?id=CVE-2024-45003 Référence CVE CVE-2024-45005 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-44974 Référence CVE CVE-2024-44982 https://www.cve.org/CVERecord?id=CVE-2024-44982 Référence CVE CVE-2024-44983 https://www.cve.org/CVERecord?id=CVE-2024-44983 Référence CVE CVE-2024-44985 https://www.cve.org/CVERecord?id=CVE-2024-44985 Référence CVE CVE-2024-44986 https://www.cve.org/CVERecord?id=CVE-2024-44986 Référence CVE CVE-2024-44987 https://www.cve.org/CVERecord?id=CVE-2024-44987 Référence CVE CVE-2024-44988 https://www.cve.org/CVERecord?id=CVE-2024-44988 Référence CVE CVE-2024-44989 https://www.cve.org/CVERecord?id=CVE-2024-44989 Référence CVE CVE-2024-44990 https://www.cve.org/CVERecord?id=CVE-2024-44990 Référence CVE CVE-2024-44995 https://www.cve.org/CVERecord?id=CVE-2024-44995 Référence CVE CVE-2024-44998 https://www.cve.org/CVERecord?id=CVE-2024-44998 Référence CVE CVE-2024-44999 https://www.cve.org/CVERecord?id=CVE-2024-44999 Référence CVE CVE-2024-45003 https://www.cve.org/CVERecord?id=CVE-2024-45003 Référence CVE CVE-2024-45006 https://www.cve.org/CVERecord?id=CVE-2024-45006 Référence CVE CVE-2024-45007 https://www.cve.org/CVERecord?id=CVE-2024-45007 Référence CVE CVE-2024-45008 https://www.cve.org/CVERecord?id=CVE-2024-45008 Référence CVE CVE-2024-45009 https://www.cve.org/CVERecord?id=CVE-2024-45009 Référence CVE CVE-2024-45011 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-44974 Référence CVE CVE-2024-44982 https://www.cve.org/CVERecord?id=CVE-2024-44982 Référence CVE CVE-2024-44983 https://www.cve.org/CVERecord?id=CVE-2024-44983 Référence CVE CVE-2024-44985 https://www.cve.org/CVERecord?id=CVE-2024-44985 Référence CVE CVE-2024-44986 https://www.cve.org/CVERecord?id=CVE-2024-44986 Référence CVE CVE-2024-44987 https://www.cve.org/CVERecord?id=CVE-2024-44987 Référence CVE CVE-2024-44988 https://www.cve.org/CVERecord?id=CVE-2024-44988 Référence CVE CVE-2024-44989 https://www.cve.org/CVERecord?id=CVE-2024-44989 Référence CVE CVE-2024-44990 https://www.cve.org/CVERecord?id=CVE-2024-44990 Référence CVE CVE-2024-44995 https://www.cve.org/CVERecord?id=CVE-2024-44995 Référence CVE CVE-2024-44998 https://www.cve.org/CVERecord?id=CVE-2024-44998 Référence CVE CVE-2024-44999 https://www.cve.org/CVERecord?id=CVE-2024-44999 Référence CVE CVE-2024-45003 https://www.cve.org/CVERecord?id=CVE-2024-45003 Référence CVE CVE-2024-45006 https://www.cve.org/CVERecord?id=CVE-2024-45006 Référence CVE CVE-2024-45007 https://www.cve.org/CVERecord?id=CVE-2024-45007 Référence CVE CVE-2024-45008 https://www.cve.org/CVERecord?id=CVE-2024-45008 Référence CVE CVE-2024-45009 https://www.cve.org/CVERecord?id=CVE-2024-45009 Référence CVE CVE-2024-45011 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-44947 Référence CVE CVE-2024-44948 https://www.cve.org/CVERecord?id=CVE-2024-44948 Référence CVE CVE-2024-44952 https://www.cve.org/CVERecord?id=CVE-2024-44952 Référence CVE CVE-2024-44954 https://www.cve.org/CVERecord?id=CVE-2024-44954 Référence CVE CVE-2024-44960 https://www.cve.org/CVERecord?id=CVE-2024-44960 Référence CVE CVE-2024-44965 https://www.cve.org/CVERecord?id=CVE-2024-44965 Référence CVE CVE-2024-44969 https://www.cve.org/CVERecord?id=CVE-2024-44969 Référence CVE CVE-2024-44987 https://www.cve.org/CVERecord?id=CVE-2024-44987 Référence CVE CVE-2024-44988 https://www.cve.org/CVERecord?id=CVE-2024-44988 Référence CVE CVE-2024-44995 https://www.cve.org/CVERecord?id=CVE-2024-44995 Référence CVE CVE-2024-44998 https://www.cve.org/CVERecord?id=CVE-2024-44998 Référence CVE CVE-2024-44999 https://www.cve.org/CVERecord?id=CVE-2024-44999 Référence CVE CVE-2024-45001 https://www.cve.org/CVERecord?id=CVE-2024-45001 Référence CVE CVE-2024-45003 https://www.cve.org/CVERecord?id=CVE-2024-45003 Référence CVE CVE-2024-45006 https://www.cve.org/CVERecord?id=CVE-2024-45006 Référence CVE CVE-2024-45008 https://www.cve.org/CVERecord?id=CVE-2024-45008 Référence CVE CVE-2024-45016 https://www.cve.org/CVERecord?id=CVE-2024-45016 Référence CVE CVE-2024-45021 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-44960 Référence CVE CVE-2024-44965 https://www.cve.org/CVERecord?id=CVE-2024-44965 Référence CVE CVE-2024-44968 https://www.cve.org/CVERecord?id=CVE-2024-44968 Référence CVE CVE-2024-44971 https://www.cve.org/CVERecord?id=CVE-2024-44971 Référence CVE CVE-2024-44974 https://www.cve.org/CVERecord?id=CVE-2024-44974 Référence CVE CVE-2024-44987 https://www.cve.org/CVERecord?id=CVE-2024-44987 Référence CVE CVE-2024-44988 https://www.cve.org/CVERecord?id=CVE-2024-44988 Référence CVE CVE-2024-44989 https://www.cve.org/CVERecord?id=CVE-2024-44989 Référence CVE CVE-2024-44990 https://www.cve.org/CVERecord?id=CVE-2024-44990 Référence CVE CVE-2024-44995 https://www.cve.org/CVERecord?id=CVE-2024-44995 Référence CVE CVE-2024-44998 https://www.cve.org/CVERecord?id=CVE-2024-44998 Référence CVE CVE-2024-44999 https://www.cve.org/CVERecord?id=CVE-2024-44999 Référence CVE CVE-2024-45003 https://www.cve.org/CVERecord?id=CVE-2024-45003 Référence CVE CVE-2024-45006 https://www.cve.org/CVERecord?id=CVE-2024-45006 Référence CVE CVE-2024-45008 https://www.cve.org/CVERecord?id=CVE-2024-45008 Référence CVE CVE-2024-45016 https://www.cve.org/CVERecord?id=CVE-2024-45016 Référence CVE CVE-2024-45018 https://www.cve.org/CVERecord?id=CVE-2024-45018 Référence CVE CVE-2024-45021 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-44982 Référence CVE CVE-2024-44983 https://www.cve.org/CVERecord?id=CVE-2024-44983 Référence CVE CVE-2024-44985 https://www.cve.org/CVERecord?id=CVE-2024-44985 Référence CVE CVE-2024-44986 https://www.cve.org/CVERecord?id=CVE-2024-44986 Référence CVE CVE-2024-44987 https://www.cve.org/CVERecord?id=CVE-2024-44987 Référence CVE CVE-2024-44988 https://www.cve.org/CVERecord?id=CVE-2024-44988 Référence CVE CVE-2024-44989 https://www.cve.org/CVERecord?id=CVE-2024-44989 Référence CVE CVE-2024-44990 https://www.cve.org/CVERecord?id=CVE-2024-44990 Référence CVE CVE-2024-44991 https://www.cve.org/CVERecord?id=CVE-2024-44991 Référence CVE CVE-2024-44995 https://www.cve.org/CVERecord?id=CVE-2024-44995 Référence CVE CVE-2024-44998 https://www.cve.org/CVERecord?id=CVE-2024-44998 Référence CVE CVE-2024-44999 https://www.cve.org/CVERecord?id=CVE-2024-44999 Référence CVE CVE-2024-45000 https://www.cve.org/CVERecord?id=CVE-2024-45000 Référence CVE CVE-2024-45002 https://www.cve.org/CVERecord?id=CVE-2024-45002 Référence CVE CVE-2024-45003 https://www.cve.org/CVERecord?id=CVE-2024-45003 Référence CVE CVE-2024-45006 https://www.cve.org/CVERecord?id=CVE-2024-45006 Référence CVE CVE-2024-45007 https://www.cve.org/CVERecord?id=CVE-2024-45007 Référence CVE CVE-2024-45008 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-007582Linux の 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.15, 5.4.283 ≤ 5.4.*, 5.10.225 ≤ 5.10.*, 5.15.166 ≤ 5.15.*, 6.1.107 ≤ 6.1.*, 6.6.48 ≤ 6.6.*, 6.10.7 ≤ 6.10.*, 6.11 ≤ *
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 4 Sept 2024 · Last source change 5 Aug 2026, 11:37 UTC · CWE-667 · Improper Locking

CVE recordCVE.org · 5.2
CVSS sourceCNA
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-41197
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2024-41197↗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-44995 · cve.blacktree.nl