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

bpf: Defer work in bpf_timer_cancel_and_free

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 16 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 3 Oct 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.29% 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 16 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 16 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.9.10-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian bookwormbookworm · sourcelinuxAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 7 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.9.10-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.9.10-1Debian Security Tracker ↗Source updated 7 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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-41045 · CSAF 2.0 · revision 71 · interimSUSE Product Security TeamCVE-2024-41045
15 known affected

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

  • SLES 15 SP1 CHOST Images for Amazon EC2
  • SLES 15 SP2 CHOST Images for Amazon EC2
  • SLES 15 SP3 CHOST Images for Amazon EC2
  • SLES 15 SP4 CHOST Images for Amazon EC2
  • SLES 15 SP5 CHOST Images for Amazon EC2
  • SLES 15 SP1 CHOST Images for Google
  • SLES 15 SP2 CHOST Images for Google
  • SLES 15 SP3 CHOST Images for Google
  • SLES 15 SP4 CHOST Images for Google
  • SLES 15 SP5 CHOST Images for Google
  • SLES 15 SP1 CHOST Images for Microsoft Azure
  • SLES 15 SP2 CHOST Images for Microsoft Azure
Summary
In the Linux kernel, the following vulnerability has been resolved: bpf: Defer work in bpf_timer_cancel_and_free Currently, the same case as previous patch (two timer callbacks trying to cancel each other) can be invoked through bpf_map_update_elem as well, or more precisely, freeing map elements containing timers. Since this relies on hrtimer_cancel as well, it is prone to the same deadlock situation as the previous patch. It would be sufficient to use hrtimer_try_to_cancel to fix this problem, as the timer cannot be enqueued after async_cancel_and_free. Once async_cancel_and_free has been done, the timer must be reinitialized before it can be armed again. The callback running in parallel trying to arm the timer will fail, and freeing bpf_hrtimer without waiting is sufficient (given kfree_rcu), and bpf_timer_cb will return HRTIMER_NORESTART, preventing the timer from being rearmed again. However, there exists a UAF scenario where the callback arms the timer before entering this function, such that if cancellation fails (due to timer callback invoking this routine, or the target timer callback running concurrently). In such a case, if the timer expiration is significantly far in the future, the RCU grace period expiration happening before it will free the bpf_hrtimer state and along with it the struct hrtimer, that is enqueued. Hence, it is clear cancellation needs to occur after async_cancel_and_free, and yet it cannot be done inline due to deadlock issues. We thus modify bpf_timer_cancel_and_free to defer work to the global workqueue, adding a work_struct alongside rcu_head (both used at _different_ points of time, so can share space). Update existing code comments to reflect the new state of affairs.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2024-39174

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: bpf: Defer work in bpf_timer_cancel_and_free Currently, the same case as previous patch (two timer callbacks trying to cancel each other) can be invoked through bpf_map_update_elem as well, or more precisely, freeing map elements containing timers. Since this relies on hrtimer_cancel as well, it is prone to the same deadlock situation as the previous patch. It would be sufficient to use hrtimer_try_to_cancel to fix this problem, as the timer cannot be enqueued after async_cancel_and_free. Once async_cancel_and_free has been done, the timer must be reinitialized before it can be armed again. The callback running in parallel trying to arm the timer will fail, and freeing bpf_hrtimer without waiting is sufficient (given kfree_rcu), and bpf_timer_cb will return HRTIMER_NORESTART, preventing the timer from being rearmed again. However, there exists a UAF scenario where the callback arms the timer before entering this function, such that if cancellation fails (due to timer callback invoking this routine, or the target timer callback running concurrently). In such a case, if the timer expiration is significantly far in the future, the RCU grace period expiration happening before it will free the bpf_hrtimer state and along with it the struct hrtimer, that is enqueued. Hence, it is clear cancellation needs to occur after async_cancel_and_free, and yet it cannot be done inline due to deadlock issues. We thus modify bpf_timer_cancel_and_free to defer work to the global workqueue, adding a work_struct alongside rcu_head (both used at _different_ points of time, so can share space). Update existing code comments to reflect the new state of affairs.

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
7.8 · CVSS 3.1
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 16 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: bpf: Defer work in bpf_timer_cancel_and_free Currently, the same case as previous patch (two timer callbacks trying to cancel each other) can be invoked through bpf_map_update_elem as well, or more precisely, freeing map elements containing timers. Since this relies on hrtimer_cancel as well, it is prone to the same deadlock situation as the previous patch. It would be sufficient to use hrtimer_try_to_cancel to fix this problem, as the timer cannot be enqueued after async_cancel_and_free. Once async_cancel_and_free has been done, the timer must be reinitialized before it can be armed again. The callback running in parallel trying to arm the timer will fail, and freeing bpf_hrtimer without waiting is sufficient (given kfree_rcu), and bpf_timer_cb will return HRTIMER_NORESTART, preventing the timer from being rearmed again. However, there exists a UAF scenario where the callback arms the timer before entering this function, such that if cancellation fails (due to timer callback invoking this routine, or the target timer callback running concurrently). In such a case, if the timer expiration is significantly far in the future, the RCU grace period expiration happening before it will free the bpf_hrtimer state and along with it the struct hrtimer, that is enqueued. Hence, it is clear cancellation needs to occur after async_cancel_and_free, and yet it cannot be done inline due to deadlock issues. We thus modify bpf_timer_cancel_and_free to defer work to the global workqueue, adding a work_struct alongside rcu_head (both used at _different_ points of time, so can share space). Update existing code comments to reflect the new state of affairs.

What

In the Linux kernel, the following vulnerability has been resolved: bpf: Defer work in bpf_timer_cancel_and_free Currently, the same case as previous patch (two timer callbacks trying to cancel each other) can be invoked through bpf_map_update_elem as well, or more precisely, freeing map elements containing timers. Since this relies on hrtimer_cancel as well, it is prone to the same deadlock situation as the previous patch. It would be sufficient to use hrtimer_try_to_cancel to fix this problem, as the timer cannot be enqueued after async_cancel_and_free. Once async_cancel_and_free has been done, the timer must be reinitialized before it can be armed again. The callback running in parallel trying to arm the timer will fail, and freeing bpf_hrtimer without waiting is sufficient (given kfree_rcu), and bpf_timer_cb will return HRTIMER_NORESTART, preventing the timer from being rearmed again. However, there exists a UAF scenario where the callback arms the timer before entering this function, such that if cancellation fails (due to timer callback invoking this routine, or the target timer callback running concurrently). In such a case, if the timer expiration is significantly far in the future, the RCU grace period expiration happening before it will free the bpf_hrtimer state and along with it the struct hrtimer, that is enqueued. Hence, it is clear cancellation needs to occur after async_cancel_and_free, and yet it cannot be done inline due to deadlock issues. We thus modify bpf_timer_cancel_and_free to defer work to the global workqueue, adding a work_struct alongside rcu_head (both used at _different_ points of time, so can share space). Update existing code comments to reflect the new state of affairs.

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

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: bpf: Defer work in bpf_timer_cancel_and_free Currently, the same case as previous patch (two timer callbacks trying to cancel each other) can be invoked through bpf_map_update_elem as well, or more precisely, freeing map elements containing timers. Since this relies on hrtimer_cancel as well, it is prone to the same deadlock situation as the previous patch. It would be sufficient to use hrtimer_try_to_cancel to fix this problem, as the timer cannot be enqueued after async_cancel_and_free. Once async_cancel_and_free has been done, the timer must be reinitialized before it can be armed again. The callback running in parallel trying to arm the timer will fail, and freeing bpf_hrtimer without waiting is sufficient (given kfree_rcu), and bpf_timer_cb will return HRTIMER_NORESTART, preventing the timer from being rearmed again. However, there exists a UAF scenario where the callback arms the timer before entering this function, such that if cancellation fails (due to timer callback invoking this routine, or the target timer callback running concurrently). In such a case, if the timer expiration is significantly far in the future, the RCU grace period expiration happening before it will free the bpf_hrtimer state and along with it the struct hrtimer, that is enqueued. Hence, it is clear cancellation needs to occur after async_cancel_and_free, and yet it cannot be done inline due to deadlock issues. We thus modify bpf_timer_cancel_and_free to defer work to the global workqueue, adding a work_struct alongside rcu_head (both used at _different_ points of time, so can share space). Update existing code comments to reflect the new state of affairs.

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

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 → Use After Free → 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-416 ↗

CWE-416: Use After Free. The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.

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-416
A

Official authority intelligence

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

ENISA EUVD · EUVD-2024-39174Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: bpf: Defer work in bpf_timer_cancel_and_free Currently, the same case as previous patch (two timer callbacks trying to cancel each other) can be invoked through bpf_map_update_elem as well, or more precisely, freeing map elements containing timers. Since this relies on hrtimer_cancel as well, it is prone to the same deadlock situation as the previous patch. It would be sufficient to use hrtimer_try_to_cancel to fix this problem, as the timer cannot be enqueued after async_cancel_and_free. Once async_cancel_and_free has been done, the timer must be reinitialized before it can be armed again. The callback running in parallel trying to arm the timer will fail, and freeing bpf_hrtimer without waiting is sufficient (given kfree_rcu), and bpf_timer_cb will return HRTIMER_NORESTART, preventing the timer from being rearmed again. However, there exists a UAF scenario where the callback arms the timer before entering this function, such that if cancellation fails (due to timer callback invoking this routine, or the target timer callback running concurrently). In such a case, if the timer expiration is significantly far in the future, the RCU grace period expiration happening before it will free the bpf_hrtimer state and along with it the struct hrtimer, that is enqueued. Hence, it is clear cancellation needs to occur after async_cancel_and_free, and yet it cannot be done inline due to deadlock issues. We thus modify bpf_timer_cancel_and_free to defer work to the global workqueue, adding a work_struct alongside rcu_head (both used at _different_ points of time, so can share space). Update existing code comments to reflect the new state of affairs.

Official EUVD record ↗
BSI · German · WID-SEC-2024-1722Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

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

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240731Security Bulletin 31 Jul 2024

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

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

d?id=CVE-2024-40999 Référence CVE CVE-2024-41001 https://www.cve.org/CVERecord?id=CVE-2024-41001 Référence CVE CVE-2024-41008 https://www.cve.org/CVERecord?id=CVE-2024-41008 Référence CVE CVE-2024-41013 https://www.cve.org/CVERecord?id=CVE-2024-41013 Référence CVE CVE-2024-41014 https://www.cve.org/CVERecord?id=CVE-2024-41014 Référence CVE CVE-2024-41023 https://www.cve.org/CVERecord?id=CVE-2024-41023 Référence CVE CVE-2024-41030 https://www.cve.org/CVERecord?id=CVE-2024-41030 Référence CVE CVE-2024-41031 https://www.cve.org/CVERecord?id=CVE-2024-41031 Référence CVE CVE-2024-41036 https://www.cve.org/CVERecord?id=CVE-2024-41036 Référence CVE CVE-2024-41045 https://www.cve.org/CVERecord?id=CVE-2024-41045 Référence CVE CVE-2024-41050 https://www.cve.org/CVERecord?id=CVE-2024-41050 Référence CVE CVE-2024-41062 https://www.cve.org/CVERecord?id=CVE-2024-41062 Référence CVE CVE-2024-41067 https://www.cve.org/CVERecord?id=CVE-2024-41067 Référence CVE CVE-2024-41069 https://www.cve.org/CVERecord?id=CVE-2024-41069 Référence CVE CVE-2024-41074 https://www.cve.org/CVERecord?id=CVE-2024-41074 Référence CVE CVE-2024-41075 https://www.cve.org/CVERecord?id=CVE-2024-41075 Référence CVE CVE-2024-41079 https://www.cve.org/CVERecord?id=CVE-2024-41079 Référence CVE CVE-2024-41082 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-40999 Référence CVE CVE-2024-41001 https://www.cve.org/CVERecord?id=CVE-2024-41001 Référence CVE CVE-2024-41008 https://www.cve.org/CVERecord?id=CVE-2024-41008 Référence CVE CVE-2024-41013 https://www.cve.org/CVERecord?id=CVE-2024-41013 Référence CVE CVE-2024-41014 https://www.cve.org/CVERecord?id=CVE-2024-41014 Référence CVE CVE-2024-41023 https://www.cve.org/CVERecord?id=CVE-2024-41023 Référence CVE CVE-2024-41030 https://www.cve.org/CVERecord?id=CVE-2024-41030 Référence CVE CVE-2024-41031 https://www.cve.org/CVERecord?id=CVE-2024-41031 Référence CVE CVE-2024-41036 https://www.cve.org/CVERecord?id=CVE-2024-41036 Référence CVE CVE-2024-41045 https://www.cve.org/CVERecord?id=CVE-2024-41045 Référence CVE CVE-2024-41050 https://www.cve.org/CVERecord?id=CVE-2024-41050 Référence CVE CVE-2024-41062 https://www.cve.org/CVERecord?id=CVE-2024-41062 Référence CVE CVE-2024-41067 https://www.cve.org/CVERecord?id=CVE-2024-41067 Référence CVE CVE-2024-41069 https://www.cve.org/CVERecord?id=CVE-2024-41069 Référence CVE CVE-2024-41074 https://www.cve.org/CVERecord?id=CVE-2024-41074 Référence CVE CVE-2024-41075 https://www.cve.org/CVERecord?id=CVE-2024-41075 Référence CVE CVE-2024-41079 https://www.cve.org/CVERecord?id=CVE-2024-41079 Référence CVE CVE-2024-41082 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-40992 Référence CVE CVE-2024-40994 https://www.cve.org/CVERecord?id=CVE-2024-40994 Référence CVE CVE-2024-41003 https://www.cve.org/CVERecord?id=CVE-2024-41003 Référence CVE CVE-2024-41010 https://www.cve.org/CVERecord?id=CVE-2024-41010 Référence CVE CVE-2024-41031 https://www.cve.org/CVERecord?id=CVE-2024-41031 Référence CVE CVE-2024-41032 https://www.cve.org/CVERecord?id=CVE-2024-41032 Référence CVE CVE-2024-41037 https://www.cve.org/CVERecord?id=CVE-2024-41037 Référence CVE CVE-2024-41038 https://www.cve.org/CVERecord?id=CVE-2024-41038 Référence CVE CVE-2024-41039 https://www.cve.org/CVERecord?id=CVE-2024-41039 Référence CVE CVE-2024-41045 https://www.cve.org/CVERecord?id=CVE-2024-41045 Référence CVE CVE-2024-41047 https://www.cve.org/CVERecord?id=CVE-2024-41047 Référence CVE CVE-2024-41056 https://www.cve.org/CVERecord?id=CVE-2024-41056 Référence CVE CVE-2024-41057 https://www.cve.org/CVERecord?id=CVE-2024-41057 Référence CVE CVE-2024-41058 https://www.cve.org/CVERecord?id=CVE-2024-41058 Référence CVE CVE-2024-41084 https://www.cve.org/CVERecord?id=CVE-2024-41084 Référence CVE CVE-2024-41085 https://www.cve.org/CVERecord?id=CVE-2024-41085 Référence CVE CVE-2024-41094 https://www.cve.org/CVERecord?id=CVE-2024-41094 Référence CVE CVE-2024-42085 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-41034 Référence CVE CVE-2024-41035 https://www.cve.org/CVERecord?id=CVE-2024-41035 Référence CVE CVE-2024-41036 https://www.cve.org/CVERecord?id=CVE-2024-41036 Référence CVE CVE-2024-41037 https://www.cve.org/CVERecord?id=CVE-2024-41037 Référence CVE CVE-2024-41038 https://www.cve.org/CVERecord?id=CVE-2024-41038 Référence CVE CVE-2024-41039 https://www.cve.org/CVERecord?id=CVE-2024-41039 Référence CVE CVE-2024-41041 https://www.cve.org/CVERecord?id=CVE-2024-41041 Référence CVE CVE-2024-41042 https://www.cve.org/CVERecord?id=CVE-2024-41042 Référence CVE CVE-2024-41044 https://www.cve.org/CVERecord?id=CVE-2024-41044 Référence CVE CVE-2024-41045 https://www.cve.org/CVERecord?id=CVE-2024-41045 Référence CVE CVE-2024-41046 https://www.cve.org/CVERecord?id=CVE-2024-41046 Référence CVE CVE-2024-41047 https://www.cve.org/CVERecord?id=CVE-2024-41047 Référence CVE CVE-2024-41048 https://www.cve.org/CVERecord?id=CVE-2024-41048 Référence CVE CVE-2024-41049 https://www.cve.org/CVERecord?id=CVE-2024-41049 Référence CVE CVE-2024-41050 https://www.cve.org/CVERecord?id=CVE-2024-41050 Référence CVE CVE-2024-41051 https://www.cve.org/CVERecord?id=CVE-2024-41051 Référence CVE CVE-2024-41052 https://www.cve.org/CVERecord?id=CVE-2024-41052 Référence CVE CVE-2024-41053 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-41034 Référence CVE CVE-2024-41035 https://www.cve.org/CVERecord?id=CVE-2024-41035 Référence CVE CVE-2024-41036 https://www.cve.org/CVERecord?id=CVE-2024-41036 Référence CVE CVE-2024-41037 https://www.cve.org/CVERecord?id=CVE-2024-41037 Référence CVE CVE-2024-41038 https://www.cve.org/CVERecord?id=CVE-2024-41038 Référence CVE CVE-2024-41039 https://www.cve.org/CVERecord?id=CVE-2024-41039 Référence CVE CVE-2024-41041 https://www.cve.org/CVERecord?id=CVE-2024-41041 Référence CVE CVE-2024-41042 https://www.cve.org/CVERecord?id=CVE-2024-41042 Référence CVE CVE-2024-41044 https://www.cve.org/CVERecord?id=CVE-2024-41044 Référence CVE CVE-2024-41045 https://www.cve.org/CVERecord?id=CVE-2024-41045 Référence CVE CVE-2024-41046 https://www.cve.org/CVERecord?id=CVE-2024-41046 Référence CVE CVE-2024-41047 https://www.cve.org/CVERecord?id=CVE-2024-41047 Référence CVE CVE-2024-41048 https://www.cve.org/CVERecord?id=CVE-2024-41048 Référence CVE CVE-2024-41049 https://www.cve.org/CVERecord?id=CVE-2024-41049 Référence CVE CVE-2024-41050 https://www.cve.org/CVERecord?id=CVE-2024-41050 Référence CVE CVE-2024-41051 https://www.cve.org/CVERecord?id=CVE-2024-41051 Référence CVE CVE-2024-41052 https://www.cve.org/CVERecord?id=CVE-2024-41052 Référence CVE CVE-2024-41053 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-41034 Référence CVE CVE-2024-41035 https://www.cve.org/CVERecord?id=CVE-2024-41035 Référence CVE CVE-2024-41036 https://www.cve.org/CVERecord?id=CVE-2024-41036 Référence CVE CVE-2024-41037 https://www.cve.org/CVERecord?id=CVE-2024-41037 Référence CVE CVE-2024-41038 https://www.cve.org/CVERecord?id=CVE-2024-41038 Référence CVE CVE-2024-41039 https://www.cve.org/CVERecord?id=CVE-2024-41039 Référence CVE CVE-2024-41041 https://www.cve.org/CVERecord?id=CVE-2024-41041 Référence CVE CVE-2024-41042 https://www.cve.org/CVERecord?id=CVE-2024-41042 Référence CVE CVE-2024-41044 https://www.cve.org/CVERecord?id=CVE-2024-41044 Référence CVE CVE-2024-41045 https://www.cve.org/CVERecord?id=CVE-2024-41045 Référence CVE CVE-2024-41046 https://www.cve.org/CVERecord?id=CVE-2024-41046 Référence CVE CVE-2024-41047 https://www.cve.org/CVERecord?id=CVE-2024-41047 Référence CVE CVE-2024-41048 https://www.cve.org/CVERecord?id=CVE-2024-41048 Référence CVE CVE-2024-41049 https://www.cve.org/CVERecord?id=CVE-2024-41049 Référence CVE CVE-2024-41050 https://www.cve.org/CVERecord?id=CVE-2024-41050 Référence CVE CVE-2024-41051 https://www.cve.org/CVERecord?id=CVE-2024-41051 Référence CVE CVE-2024-41052 https://www.cve.org/CVERecord?id=CVE-2024-41052 Référence CVE CVE-2024-41053 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-41034 Référence CVE CVE-2024-41035 https://www.cve.org/CVERecord?id=CVE-2024-41035 Référence CVE CVE-2024-41036 https://www.cve.org/CVERecord?id=CVE-2024-41036 Référence CVE CVE-2024-41037 https://www.cve.org/CVERecord?id=CVE-2024-41037 Référence CVE CVE-2024-41038 https://www.cve.org/CVERecord?id=CVE-2024-41038 Référence CVE CVE-2024-41039 https://www.cve.org/CVERecord?id=CVE-2024-41039 Référence CVE CVE-2024-41041 https://www.cve.org/CVERecord?id=CVE-2024-41041 Référence CVE CVE-2024-41042 https://www.cve.org/CVERecord?id=CVE-2024-41042 Référence CVE CVE-2024-41044 https://www.cve.org/CVERecord?id=CVE-2024-41044 Référence CVE CVE-2024-41045 https://www.cve.org/CVERecord?id=CVE-2024-41045 Référence CVE CVE-2024-41046 https://www.cve.org/CVERecord?id=CVE-2024-41046 Référence CVE CVE-2024-41047 https://www.cve.org/CVERecord?id=CVE-2024-41047 Référence CVE CVE-2024-41048 https://www.cve.org/CVERecord?id=CVE-2024-41048 Référence CVE CVE-2024-41049 https://www.cve.org/CVERecord?id=CVE-2024-41049 Référence CVE CVE-2024-41050 https://www.cve.org/CVERecord?id=CVE-2024-41050 Référence CVE CVE-2024-41051 https://www.cve.org/CVERecord?id=CVE-2024-41051 Référence CVE CVE-2024-41052 https://www.cve.org/CVERecord?id=CVE-2024-41052 Référence CVE CVE-2024-41053 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-41011 Référence CVE CVE-2024-41016 https://www.cve.org/CVERecord?id=CVE-2024-41016 Référence CVE CVE-2024-41020 https://www.cve.org/CVERecord?id=CVE-2024-41020 Référence CVE CVE-2024-41022 https://www.cve.org/CVERecord?id=CVE-2024-41022 Référence CVE CVE-2024-41035 https://www.cve.org/CVERecord?id=CVE-2024-41035 Référence CVE CVE-2024-41036 https://www.cve.org/CVERecord?id=CVE-2024-41036 Référence CVE CVE-2024-41038 https://www.cve.org/CVERecord?id=CVE-2024-41038 Référence CVE CVE-2024-41039 https://www.cve.org/CVERecord?id=CVE-2024-41039 Référence CVE CVE-2024-41042 https://www.cve.org/CVERecord?id=CVE-2024-41042 Référence CVE CVE-2024-41045 https://www.cve.org/CVERecord?id=CVE-2024-41045 Référence CVE CVE-2024-41056 https://www.cve.org/CVERecord?id=CVE-2024-41056 Référence CVE CVE-2024-41060 https://www.cve.org/CVERecord?id=CVE-2024-41060 Référence CVE CVE-2024-41062 https://www.cve.org/CVERecord?id=CVE-2024-41062 Référence CVE CVE-2024-41065 https://www.cve.org/CVERecord?id=CVE-2024-41065 Référence CVE CVE-2024-41068 https://www.cve.org/CVERecord?id=CVE-2024-41068 Référence CVE CVE-2024-41073 https://www.cve.org/CVERecord?id=CVE-2024-41073 Référence CVE CVE-2024-41079 https://www.cve.org/CVERecord?id=CVE-2024-41079 Référence CVE CVE-2024-41080 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-41032 Référence CVE CVE-2024-41035 https://www.cve.org/CVERecord?id=CVE-2024-41035 Référence CVE CVE-2024-41036 https://www.cve.org/CVERecord?id=CVE-2024-41036 Référence CVE CVE-2024-41037 https://www.cve.org/CVERecord?id=CVE-2024-41037 Référence CVE CVE-2024-41038 https://www.cve.org/CVERecord?id=CVE-2024-41038 Référence CVE CVE-2024-41039 https://www.cve.org/CVERecord?id=CVE-2024-41039 Référence CVE CVE-2024-41040 https://www.cve.org/CVERecord?id=CVE-2024-41040 Référence CVE CVE-2024-41041 https://www.cve.org/CVERecord?id=CVE-2024-41041 Référence CVE CVE-2024-41044 https://www.cve.org/CVERecord?id=CVE-2024-41044 Référence CVE CVE-2024-41045 https://www.cve.org/CVERecord?id=CVE-2024-41045 Référence CVE CVE-2024-41048 https://www.cve.org/CVERecord?id=CVE-2024-41048 Référence CVE CVE-2024-41049 https://www.cve.org/CVERecord?id=CVE-2024-41049 Référence CVE CVE-2024-41050 https://www.cve.org/CVERecord?id=CVE-2024-41050 Référence CVE CVE-2024-41051 https://www.cve.org/CVERecord?id=CVE-2024-41051 Référence CVE CVE-2024-41056 https://www.cve.org/CVERecord?id=CVE-2024-41056 Référence CVE CVE-2024-41057 https://www.cve.org/CVERecord?id=CVE-2024-41057 Référence CVE CVE-2024-41058 https://www.cve.org/CVERecord?id=CVE-2024-41058 Référence CVE CVE-2024-41059 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-41035 Référence CVE CVE-2024-41036 https://www.cve.org/CVERecord?id=CVE-2024-41036 Référence CVE CVE-2024-41037 https://www.cve.org/CVERecord?id=CVE-2024-41037 Référence CVE CVE-2024-41038 https://www.cve.org/CVERecord?id=CVE-2024-41038 Référence CVE CVE-2024-41039 https://www.cve.org/CVERecord?id=CVE-2024-41039 Référence CVE CVE-2024-41040 https://www.cve.org/CVERecord?id=CVE-2024-41040 Référence CVE CVE-2024-41041 https://www.cve.org/CVERecord?id=CVE-2024-41041 Référence CVE CVE-2024-41042 https://www.cve.org/CVERecord?id=CVE-2024-41042 Référence CVE CVE-2024-41044 https://www.cve.org/CVERecord?id=CVE-2024-41044 Référence CVE CVE-2024-41045 https://www.cve.org/CVERecord?id=CVE-2024-41045 Référence CVE CVE-2024-41048 https://www.cve.org/CVERecord?id=CVE-2024-41048 Référence CVE CVE-2024-41049 https://www.cve.org/CVERecord?id=CVE-2024-41049 Référence CVE CVE-2024-41050 https://www.cve.org/CVERecord?id=CVE-2024-41050 Référence CVE CVE-2024-41051 https://www.cve.org/CVERecord?id=CVE-2024-41051 Référence CVE CVE-2024-41056 https://www.cve.org/CVERecord?id=CVE-2024-41056 Référence CVE CVE-2024-41057 https://www.cve.org/CVERecord?id=CVE-2024-41057 Référence CVE CVE-2024-41058 https://www.cve.org/CVERecord?id=CVE-2024-41058 Référence CVE CVE-2024-41059 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-028444Linux の 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: < 5.15, 6.6.158 ≤ 6.6.*, 6.9.10 ≤ 6.9.*, 6.10 ≤ *
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 29 Jul 2024 · Last source change 3 Oct 2026, 10:55 UTC · CWE-416 · Use After Free

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-39174
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 ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    b00628b1c7d595ae5b544e059c27b1f5828314b4 < 7aa5a19279c3639ae8b758b63f05d0c616a39fa1; b00628b1c7d595ae5b544e059c27b1f5828314b4 < a6fcd19d7eac1335eb76bc16b6a66b7f574d1d69; 5.15 · Fixed: < 5.15; 6.9.10 ≤ 6.9.*; 6.10 ≤ *
    After
    Linux: b00628b1c7d595ae5b544e059c27b1f5828314b4 < 5eaa11c500ed07f505f86cec07d5593a71927e26, b00628b1c7d595ae5b544e059c27b1f5828314b4 < 7aa5a19279c3639ae8b758b63f05d0c616a39fa1, b00628b1c7d595ae5b544e059c27b1f5828314b4 < a6fcd19d7eac1335eb76bc16b6a66b7f574d1d69, 5.15 · Fixed: Linux: < 5.15, 6.6.158 ≤ 6.6.*, 6.9.10 ≤ 6.9.*, 6.10 ≤ *
    CNA ↗
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-39174↗Vendor CSAF · SUSE Product Security Team↗Patch or update reference↗Patch or update reference↗CVE authority or vendor 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-41045 · cve.blacktree.nl