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

btrfs: do not BUG_ON() when freeing tree block after error

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 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 severityMediumOperational priority:Low, lowered one band.downgradedsince 11 May 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.24% for the current model date.

Compensating controls

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

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: No default targetRemediation target: Normal maintenance

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

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 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.10.6-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.10.6-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.10.6-1Debian Security Tracker ↗Source updated 6 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.

1 current
CVE-2024-44963 · CSAF 2.0 · revision 105 · interimSUSE Product Security TeamCVE-2024-44963
444 known affected

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

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-default-devel as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-macros as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
Summary
In the Linux kernel, the following vulnerability has been resolved: btrfs: do not BUG_ON() when freeing tree block after error When freeing a tree block, at btrfs_free_tree_block(), if we fail to create a delayed reference we don't deal with the error and just do a BUG_ON(). The error most likely to happen is -ENOMEM, and we have a comment mentioning that only -ENOMEM can happen, but that is not true, because in case qgroups are enabled any error returned from btrfs_qgroup_trace_extent_post() (can be -EUCLEAN or anything returned from btrfs_search_slot() for example) can be propagated back to btrfs_free_tree_block(). So stop doing a BUG_ON() and return the error to the callers and make them abort the transaction to prevent leaking space. Syzbot was triggering this, likely due to memory allocation failure injection.
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-41166

No EUVD known-exploited evidence

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

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

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 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: btrfs: do not BUG_ON() when freeing tree block after error When freeing a tree block, at btrfs_free_tree_block(), if we fail to create a delayed reference we don't deal with the error and just do a BUG_ON(). The error most likely to happen is -ENOMEM, and we have a comment mentioning that only -ENOMEM can happen, but that is not true, because in case qgroups are enabled any error returned from btrfs_qgroup_trace_extent_post() (can be -EUCLEAN or anything returned from btrfs_search_slot() for example) can be propagated back to btrfs_free_tree_block(). So stop doing a BUG_ON() and return the error to the callers and make them abort the transaction to prevent leaking space. Syzbot was triggering this, likely due to memory allocation failure injection.

What

In the Linux kernel, the following vulnerability has been resolved: btrfs: do not BUG_ON() when freeing tree block after error When freeing a tree block, at btrfs_free_tree_block(), if we fail to create a delayed reference we don't deal with the error and just do a BUG_ON(). The error most likely to happen is -ENOMEM, and we have a comment mentioning that only -ENOMEM can happen, but that is not true, because in case qgroups are enabled any error returned from btrfs_qgroup_trace_extent_post() (can be -EUCLEAN or anything returned from btrfs_search_slot() for example) can be propagated back to btrfs_free_tree_block(). So stop doing a BUG_ON() and return the error to the callers and make them abort the transaction to prevent leaking space. Syzbot was triggering this, likely due to memory allocation failure injection.

Why

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

How

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

What

In the Linux kernel, the following vulnerability has been resolved: btrfs: do not BUG_ON() when freeing tree block after error When freeing a tree block, at btrfs_free_tree_block(), if we fail to create a delayed reference we don't deal with the error and just do a BUG_ON(). The error most likely to happen is -ENOMEM, and we have a comment mentioning that only -ENOMEM can happen, but that is not true, because in case qgroups are enabled any error returned from btrfs_qgroup_trace_extent_post() (can be -EUCLEAN or anything returned from btrfs_search_slot() for example) can be propagated back to btrfs_free_tree_block(). So stop doing a BUG_ON() and return the error to the callers and make them abort the transaction to prevent leaking space. Syzbot was triggering this, likely due to memory allocation failure injection.

Why

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

How

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

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
A

Official authority intelligence

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

BSI · German · WID-SEC-2024-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-2026-AVI-0326Multiples vulnérabilités dans les produits VMware

d?id=CVE-2024-43844 Référence CVE CVE-2024-43866 https://www.cve.org/CVERecord?id=CVE-2024-43866 Référence CVE CVE-2024-43872 https://www.cve.org/CVERecord?id=CVE-2024-43872 Référence CVE CVE-2024-43899 https://www.cve.org/CVERecord?id=CVE-2024-43899 Référence CVE CVE-2024-43911 https://www.cve.org/CVERecord?id=CVE-2024-43911 Référence CVE CVE-2024-43912 https://www.cve.org/CVERecord?id=CVE-2024-43912 Référence CVE CVE-2024-44950 https://www.cve.org/CVERecord?id=CVE-2024-44950 Référence CVE CVE-2024-44961 https://www.cve.org/CVERecord?id=CVE-2024-44961 Référence CVE CVE-2024-44962 https://www.cve.org/CVERecord?id=CVE-2024-44962 Référence CVE CVE-2024-44963 https://www.cve.org/CVERecord?id=CVE-2024-44963 Référence CVE CVE-2024-44970 https://www.cve.org/CVERecord?id=CVE-2024-44970 Référence CVE CVE-2024-45010 https://www.cve.org/CVERecord?id=CVE-2024-45010 Référence CVE CVE-2024-45015 https://www.cve.org/CVERecord?id=CVE-2024-45015 Référence CVE CVE-2024-45337 https://www.cve.org/CVERecord?id=CVE-2024-45337 Référence CVE CVE-2024-45774 https://www.cve.org/CVERecord?id=CVE-2024-45774 Référence CVE CVE-2024-45775 https://www.cve.org/CVERecord?id=CVE-2024-45775 Référence CVE CVE-2024-45776 https://www.cve.org/CVERecord?id=CVE-2024-45776 Référence CVE CVE-2024-45777 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-43844 Référence CVE CVE-2024-43866 https://www.cve.org/CVERecord?id=CVE-2024-43866 Référence CVE CVE-2024-43872 https://www.cve.org/CVERecord?id=CVE-2024-43872 Référence CVE CVE-2024-43899 https://www.cve.org/CVERecord?id=CVE-2024-43899 Référence CVE CVE-2024-43911 https://www.cve.org/CVERecord?id=CVE-2024-43911 Référence CVE CVE-2024-43912 https://www.cve.org/CVERecord?id=CVE-2024-43912 Référence CVE CVE-2024-44950 https://www.cve.org/CVERecord?id=CVE-2024-44950 Référence CVE CVE-2024-44961 https://www.cve.org/CVERecord?id=CVE-2024-44961 Référence CVE CVE-2024-44962 https://www.cve.org/CVERecord?id=CVE-2024-44962 Référence CVE CVE-2024-44963 https://www.cve.org/CVERecord?id=CVE-2024-44963 Référence CVE CVE-2024-44970 https://www.cve.org/CVERecord?id=CVE-2024-44970 Référence CVE CVE-2024-45010 https://www.cve.org/CVERecord?id=CVE-2024-45010 Référence CVE CVE-2024-45015 https://www.cve.org/CVERecord?id=CVE-2024-45015 Référence CVE CVE-2024-45337 https://www.cve.org/CVERecord?id=CVE-2024-45337 Référence CVE CVE-2024-45774 https://www.cve.org/CVERecord?id=CVE-2024-45774 Référence CVE CVE-2024-45775 https://www.cve.org/CVERecord?id=CVE-2024-45775 Référence CVE CVE-2024-45776 https://www.cve.org/CVERecord?id=CVE-2024-45776 Référence CVE CVE-2024-45777 https://www.cve.org/CVERecord?id=

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

nnouncement/2025/suse-su-202520626-1 Bulletin de sécurité SUSE SUSE-SU-2025:03023-1 du 29 août 2025 https://www.suse.com/support/update/announcement/2025/suse-su-202503023-1 Référence CVE CVE-2019-11135 https://www.cve.org/CVERecord?id=CVE-2019-11135 Référence CVE CVE-2024-36028 https://www.cve.org/CVERecord?id=CVE-2024-36028 Référence CVE CVE-2024-36348 https://www.cve.org/CVERecord?id=CVE-2024-36348 Référence CVE CVE-2024-36349 https://www.cve.org/CVERecord?id=CVE-2024-36349 Référence CVE CVE-2024-36350 https://www.cve.org/CVERecord?id=CVE-2024-36350 Référence CVE CVE-2024-36357 https://www.cve.org/CVERecord?id=CVE-2024-36357 Référence CVE CVE-2024-44963 https://www.cve.org/CVERecord?id=CVE-2024-44963 Référence CVE CVE-2024-53125 https://www.cve.org/CVERecord?id=CVE-2024-53125 Référence CVE CVE-2024-56664 https://www.cve.org/CVERecord?id=CVE-2024-56664 Référence CVE CVE-2024-56742 https://www.cve.org/CVERecord?id=CVE-2024-56742 Référence CVE CVE-2024-57947 https://www.cve.org/CVERecord?id=CVE-2024-57947 Référence CVE CVE-2025-21702 https://www.cve.org/CVERecord?id=CVE-2025-21702 Référence CVE CVE-2025-21839 https://www.cve.org/CVERecord?id=CVE-2025-21839 Référence CVE CVE-2025-21872 https://www.cve.org/CVERecord?id=CVE-2025-21872 Référence CVE CVE-2025-23163 https://www.cve.org/CVERecord?id=

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

suse-su-202503011-1 Référence CVE CVE-2019-11135 https://www.cve.org/CVERecord?id=CVE-2019-11135 Référence CVE CVE-2024-36028 https://www.cve.org/CVERecord?id=CVE-2024-36028 Référence CVE CVE-2024-36348 https://www.cve.org/CVERecord?id=CVE-2024-36348 Référence CVE CVE-2024-36349 https://www.cve.org/CVERecord?id=CVE-2024-36349 Référence CVE CVE-2024-36350 https://www.cve.org/CVERecord?id=CVE-2024-36350 Référence CVE CVE-2024-36357 https://www.cve.org/CVERecord?id=CVE-2024-36357 Référence CVE CVE-2024-39298 https://www.cve.org/CVERecord?id=CVE-2024-39298 Référence CVE CVE-2024-42134 https://www.cve.org/CVERecord?id=CVE-2024-42134 Référence CVE CVE-2024-44963 https://www.cve.org/CVERecord?id=CVE-2024-44963 Référence CVE CVE-2024-49861 https://www.cve.org/CVERecord?id=CVE-2024-49861 Référence CVE CVE-2024-49996 https://www.cve.org/CVERecord?id=CVE-2024-49996 Référence CVE CVE-2024-56742 https://www.cve.org/CVERecord?id=CVE-2024-56742 Référence CVE CVE-2024-57947 https://www.cve.org/CVERecord?id=CVE-2024-57947 Référence CVE CVE-2025-21839 https://www.cve.org/CVERecord?id=CVE-2025-21839 Référence CVE CVE-2025-21854 https://www.cve.org/CVERecord?id=CVE-2025-21854 Référence CVE CVE-2025-21872 https://www.cve.org/CVERecord?id=CVE-2025-21872 Référence CVE CVE-2025-22090 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-36348 Référence CVE CVE-2024-36349 https://www.cve.org/CVERecord?id=CVE-2024-36349 Référence CVE CVE-2024-36350 https://www.cve.org/CVERecord?id=CVE-2024-36350 Référence CVE CVE-2024-36357 https://www.cve.org/CVERecord?id=CVE-2024-36357 Référence CVE CVE-2024-36972 https://www.cve.org/CVERecord?id=CVE-2024-36972 Référence CVE CVE-2024-36978 https://www.cve.org/CVERecord?id=CVE-2024-36978 Référence CVE CVE-2024-42134 https://www.cve.org/CVERecord?id=CVE-2024-42134 Référence CVE CVE-2024-42265 https://www.cve.org/CVERecord?id=CVE-2024-42265 Référence CVE CVE-2024-43869 https://www.cve.org/CVERecord?id=CVE-2024-43869 Référence CVE CVE-2024-44963 https://www.cve.org/CVERecord?id=CVE-2024-44963 Référence CVE CVE-2024-46713 https://www.cve.org/CVERecord?id=CVE-2024-46713 Référence CVE CVE-2024-49568 https://www.cve.org/CVERecord?id=CVE-2024-49568 Référence CVE CVE-2024-49861 https://www.cve.org/CVERecord?id=CVE-2024-49861 Référence CVE CVE-2024-50106 https://www.cve.org/CVERecord?id=CVE-2024-50106 Référence CVE CVE-2024-53057 https://www.cve.org/CVERecord?id=CVE-2024-53057 Référence CVE CVE-2024-53164 https://www.cve.org/CVERecord?id=CVE-2024-53164 Référence CVE CVE-2024-56613 https://www.cve.org/CVERecord?id=CVE-2024-56613 Référence CVE CVE-2024-56699 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-44953 Référence CVE CVE-2024-44954 https://www.cve.org/CVERecord?id=CVE-2024-44954 Référence CVE CVE-2024-44956 https://www.cve.org/CVERecord?id=CVE-2024-44956 Référence CVE CVE-2024-44957 https://www.cve.org/CVERecord?id=CVE-2024-44957 Référence CVE CVE-2024-44958 https://www.cve.org/CVERecord?id=CVE-2024-44958 Référence CVE CVE-2024-44959 https://www.cve.org/CVERecord?id=CVE-2024-44959 Référence CVE CVE-2024-44960 https://www.cve.org/CVERecord?id=CVE-2024-44960 Référence CVE CVE-2024-44961 https://www.cve.org/CVERecord?id=CVE-2024-44961 Référence CVE CVE-2024-44962 https://www.cve.org/CVERecord?id=CVE-2024-44962 Référence CVE CVE-2024-44963 https://www.cve.org/CVERecord?id=CVE-2024-44963 Référence CVE CVE-2024-44965 https://www.cve.org/CVERecord?id=CVE-2024-44965 Référence CVE CVE-2024-44966 https://www.cve.org/CVERecord?id=CVE-2024-44966 Référence CVE CVE-2024-44967 https://www.cve.org/CVERecord?id=CVE-2024-44967 Référence CVE CVE-2024-44969 https://www.cve.org/CVERecord?id=CVE-2024-44969 Référence CVE CVE-2024-44970 https://www.cve.org/CVERecord?id=CVE-2024-44970 Référence CVE CVE-2024-44971 https://www.cve.org/CVERecord?id=CVE-2024-44971 Référence CVE CVE-2024-44972 https://www.cve.org/CVERecord?id=CVE-2024-44972 Référence CVE CVE-2024-44973 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-44953 Référence CVE CVE-2024-44954 https://www.cve.org/CVERecord?id=CVE-2024-44954 Référence CVE CVE-2024-44956 https://www.cve.org/CVERecord?id=CVE-2024-44956 Référence CVE CVE-2024-44957 https://www.cve.org/CVERecord?id=CVE-2024-44957 Référence CVE CVE-2024-44958 https://www.cve.org/CVERecord?id=CVE-2024-44958 Référence CVE CVE-2024-44959 https://www.cve.org/CVERecord?id=CVE-2024-44959 Référence CVE CVE-2024-44960 https://www.cve.org/CVERecord?id=CVE-2024-44960 Référence CVE CVE-2024-44961 https://www.cve.org/CVERecord?id=CVE-2024-44961 Référence CVE CVE-2024-44962 https://www.cve.org/CVERecord?id=CVE-2024-44962 Référence CVE CVE-2024-44963 https://www.cve.org/CVERecord?id=CVE-2024-44963 Référence CVE CVE-2024-44965 https://www.cve.org/CVERecord?id=CVE-2024-44965 Référence CVE CVE-2024-44966 https://www.cve.org/CVERecord?id=CVE-2024-44966 Référence CVE CVE-2024-44967 https://www.cve.org/CVERecord?id=CVE-2024-44967 Référence CVE CVE-2024-44969 https://www.cve.org/CVERecord?id=CVE-2024-44969 Référence CVE CVE-2024-44970 https://www.cve.org/CVERecord?id=CVE-2024-44970 Référence CVE CVE-2024-44971 https://www.cve.org/CVERecord?id=CVE-2024-44971 Référence CVE CVE-2024-44972 https://www.cve.org/CVERecord?id=CVE-2024-44972 Référence CVE CVE-2024-44973 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-009856Linux の Linux Kernel における脆弱性

Linux の Linux Kernel には、不特定の脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 4.11, 6.6.64 ≤ 6.6.*, 6.10.5 ≤ 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 11 May 2026, 20:32 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2024-41166
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD modified after enrichment

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

Material change intelligence

What changed after publication

View recent updates ↗

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

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