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

icmp: change the order of rate limits

Linux · Linux

9.4CriticalCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 17 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 severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.61% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • 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: Within 3 daysRemediation target: Within 90 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 17 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.

21 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 17 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.11.2-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.115-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.11.2-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.11.2-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-azure-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-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.11Affected, 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-realtimeAffected, 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-47678 · CSAF 2.0 · revision 86 · interimSUSE Product Security TeamCVE-2024-47678
289 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 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
Summary
In the Linux kernel, the following vulnerability has been resolved: icmp: change the order of rate limits ICMP messages are ratelimited : After the blamed commits, the two rate limiters are applied in this order: 1) host wide ratelimit (icmp_global_allow()) 2) Per destination ratelimit (inetpeer based) In order to avoid side-channels attacks, we need to apply the per destination check first. This patch makes the following change : 1) icmp_global_allow() checks if the host wide limit is reached. But credits are not yet consumed. This is deferred to 3) 2) The per destination limit is checked/updated. This might add a new node in inetpeer tree. 3) icmp_global_consume() consumes tokens if prior operations succeeded. This means that host wide ratelimit is still effective in keeping inetpeer tree small even under DDOS. As a bonus, I removed icmp_global.lock as the fast path can use a lock-free operation.
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-42599

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

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 17 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: icmp: change the order of rate limits ICMP messages are ratelimited : After the blamed commits, the two rate limiters are applied in this order: 1) host wide ratelimit (icmp_global_allow()) 2) Per destination ratelimit (inetpeer based) In order to avoid side-channels attacks, we need to apply the per destination check first. This patch makes the following change : 1) icmp_global_allow() checks if the host wide limit is reached. But credits are not yet consumed. This is deferred to 3) 2) The per destination limit is checked/updated. This might add a new node in inetpeer tree. 3) icmp_global_consume() consumes tokens if prior operations succeeded. This means that host wide ratelimit is still effective in keeping inetpeer tree small even under DDOS. As a bonus, I removed icmp_global.lock as the fast path can use a lock-free operation.

What

In the Linux kernel, the following vulnerability has been resolved: icmp: change the order of rate limits ICMP messages are ratelimited : After the blamed commits, the two rate limiters are applied in this order: 1) host wide ratelimit (icmp_global_allow()) 2) Per destination ratelimit (inetpeer based) In order to avoid side-channels attacks, we need to apply the per destination check first. This patch makes the following change : 1) icmp_global_allow() checks if the host wide limit is reached. But credits are not yet consumed. This is deferred to 3) 2) The per destination limit is checked/updated. This might add a new node in inetpeer tree. 3) icmp_global_consume() consumes tokens if prior operations succeeded. This means that host wide ratelimit is still effective in keeping inetpeer tree small even under DDOS. As a bonus, I removed icmp_global.lock as the fast path can use a lock-free operation.

Why

The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. 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: icmp: change the order of rate limits ICMP messages are ratelimited : After the blamed commits, the two rate limiters are applied in this order: 1) host wide ratelimit (icmp_global_allow()) 2) Per destination ratelimit (inetpeer based) In order to avoid side-channels attacks, we need to apply the per destination check first. This patch makes the following change : 1) icmp_global_allow() checks if the host wide limit is reached. But credits are not yet consumed. This is deferred to 3) 2) The per destination limit is checked/updated. This might add a new node in inetpeer tree. 3) icmp_global_consume() consumes tokens if prior operations succeeded. This means that host wide ratelimit is still effective in keeping inetpeer tree small even under DDOS. As a bonus, I removed icmp_global.lock as the fast path can use a lock-free operation.

Why

The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. 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
a network path → Observable Discrepancy → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
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-203 ↗

CWE-203: Observable Discrepancy. The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor.

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

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

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing 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.ALowAvailability impact: A successful attack can cause a limited loss.
Post-exploitation / living off the land
Stolen credentials, tokens and legitimate administration functions may provide continued access without deploying a large custom toolset.
NetworkUnauthenticatedCWE-203
A

Official authority intelligence

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

BSI · German · WID-SEC-2025-2855IBM DataPower Gateway: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM DataPower Gateway ausnutzen, um beliebigen Programmcode auszuführen, Daten zu manipulieren, vertrauliche Informationen offenzulegen, einen Denial-of-Service-Zustand zu verursachen oder andere, nicht spezifizierte Angriffe durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2024-3251Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere, nicht näher bekannte Auswirkungen zu erzielen..

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20241023Security Bulletin 23 Oct 2024

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 23 Oct 2024, published on 23 October 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

ord?id=CVE-2024-46870 Référence CVE CVE-2024-47081 https://www.cve.org/CVERecord?id=CVE-2024-47081 Référence CVE CVE-2024-47141 https://www.cve.org/CVERecord?id=CVE-2024-47141 Référence CVE CVE-2024-4741 https://www.cve.org/CVERecord?id=CVE-2024-4741 Référence CVE CVE-2024-47658 https://www.cve.org/CVERecord?id=CVE-2024-47658 Référence CVE CVE-2024-47661 https://www.cve.org/CVERecord?id=CVE-2024-47661 Référence CVE CVE-2024-47662 https://www.cve.org/CVERecord?id=CVE-2024-47662 Référence CVE CVE-2024-47664 https://www.cve.org/CVERecord?id=CVE-2024-47664 Référence CVE CVE-2024-47666 https://www.cve.org/CVERecord?id=CVE-2024-47666 Référence CVE CVE-2024-47678 https://www.cve.org/CVERecord?id=CVE-2024-47678 Référence CVE CVE-2024-47683 https://www.cve.org/CVERecord?id=CVE-2024-47683 Référence CVE CVE-2024-47689 https://www.cve.org/CVERecord?id=CVE-2024-47689 Référence CVE CVE-2024-47703 https://www.cve.org/CVERecord?id=CVE-2024-47703 Référence CVE CVE-2024-47704 https://www.cve.org/CVERecord?id=CVE-2024-47704 Référence CVE CVE-2024-47728 https://www.cve.org/CVERecord?id=CVE-2024-47728 Référence CVE CVE-2024-47736 https://www.cve.org/CVERecord?id=CVE-2024-47736 Référence CVE CVE-2024-47738 https://www.cve.org/CVERecord?id=CVE-2024-47738 Référence CVE CVE-2024-47745 https://www.cve.org/CVERecord?id=

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

ord?id=CVE-2024-46870 Référence CVE CVE-2024-47081 https://www.cve.org/CVERecord?id=CVE-2024-47081 Référence CVE CVE-2024-47141 https://www.cve.org/CVERecord?id=CVE-2024-47141 Référence CVE CVE-2024-4741 https://www.cve.org/CVERecord?id=CVE-2024-4741 Référence CVE CVE-2024-47658 https://www.cve.org/CVERecord?id=CVE-2024-47658 Référence CVE CVE-2024-47661 https://www.cve.org/CVERecord?id=CVE-2024-47661 Référence CVE CVE-2024-47662 https://www.cve.org/CVERecord?id=CVE-2024-47662 Référence CVE CVE-2024-47664 https://www.cve.org/CVERecord?id=CVE-2024-47664 Référence CVE CVE-2024-47666 https://www.cve.org/CVERecord?id=CVE-2024-47666 Référence CVE CVE-2024-47678 https://www.cve.org/CVERecord?id=CVE-2024-47678 Référence CVE CVE-2024-47683 https://www.cve.org/CVERecord?id=CVE-2024-47683 Référence CVE CVE-2024-47689 https://www.cve.org/CVERecord?id=CVE-2024-47689 Référence CVE CVE-2024-47703 https://www.cve.org/CVERecord?id=CVE-2024-47703 Référence CVE CVE-2024-47704 https://www.cve.org/CVERecord?id=CVE-2024-47704 Référence CVE CVE-2024-47728 https://www.cve.org/CVERecord?id=CVE-2024-47728 Référence CVE CVE-2024-47736 https://www.cve.org/CVERecord?id=CVE-2024-47736 Référence CVE CVE-2024-47738 https://www.cve.org/CVERecord?id=CVE-2024-47738 Référence CVE CVE-2024-47745 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-46841 Référence CVE CVE-2024-46871 https://www.cve.org/CVERecord?id=CVE-2024-46871 Référence CVE CVE-2024-47141 https://www.cve.org/CVERecord?id=CVE-2024-47141 Référence CVE CVE-2024-47143 https://www.cve.org/CVERecord?id=CVE-2024-47143 Référence CVE CVE-2024-47408 https://www.cve.org/CVERecord?id=CVE-2024-47408 Référence CVE CVE-2024-47670 https://www.cve.org/CVERecord?id=CVE-2024-47670 Référence CVE CVE-2024-47671 https://www.cve.org/CVERecord?id=CVE-2024-47671 Référence CVE CVE-2024-47672 https://www.cve.org/CVERecord?id=CVE-2024-47672 Référence CVE CVE-2024-47673 https://www.cve.org/CVERecord?id=CVE-2024-47673 Référence CVE CVE-2024-47678 https://www.cve.org/CVERecord?id=CVE-2024-47678 Référence CVE CVE-2024-47679 https://www.cve.org/CVERecord?id=CVE-2024-47679 Référence CVE CVE-2024-47684 https://www.cve.org/CVERecord?id=CVE-2024-47684 Référence CVE CVE-2024-47685 https://www.cve.org/CVERecord?id=CVE-2024-47685 Référence CVE CVE-2024-47689 https://www.cve.org/CVERecord?id=CVE-2024-47689 Référence CVE CVE-2024-47690 https://www.cve.org/CVERecord?id=CVE-2024-47690 Référence CVE CVE-2024-47691 https://www.cve.org/CVERecord?id=CVE-2024-47691 Référence CVE CVE-2024-47692 https://www.cve.org/CVERecord?id=CVE-2024-47692 Référence CVE CVE-2024-47693 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-53030 Référence CVE CVE-2023-53031 https://www.cve.org/CVERecord?id=CVE-2023-53031 Référence CVE CVE-2023-53033 https://www.cve.org/CVERecord?id=CVE-2023-53033 Référence CVE CVE-2024-26634 https://www.cve.org/CVERecord?id=CVE-2024-26634 Référence CVE CVE-2024-35910 https://www.cve.org/CVERecord?id=CVE-2024-35910 Référence CVE CVE-2024-36968 https://www.cve.org/CVERecord?id=CVE-2024-36968 Référence CVE CVE-2024-38559 https://www.cve.org/CVERecord?id=CVE-2024-38559 Référence CVE CVE-2024-41005 https://www.cve.org/CVERecord?id=CVE-2024-41005 Référence CVE CVE-2024-41090 https://www.cve.org/CVERecord?id=CVE-2024-41090 Référence CVE CVE-2024-47678 https://www.cve.org/CVERecord?id=CVE-2024-47678 Référence CVE CVE-2024-49571 https://www.cve.org/CVERecord?id=CVE-2024-49571 Référence CVE CVE-2024-49935 https://www.cve.org/CVERecord?id=CVE-2024-49935 Référence CVE CVE-2024-49940 https://www.cve.org/CVERecord?id=CVE-2024-49940 Référence CVE CVE-2024-50269 https://www.cve.org/CVERecord?id=CVE-2024-50269 Référence CVE CVE-2024-50290 https://www.cve.org/CVERecord?id=CVE-2024-50290 Référence CVE CVE-2024-53063 https://www.cve.org/CVERecord?id=CVE-2024-53063 Référence CVE CVE-2024-53124 https://www.cve.org/CVERecord?id=CVE-2024-53124 Référence CVE CVE-2024-53140 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-42098 Référence CVE CVE-2024-42229 https://www.cve.org/CVERecord?id=CVE-2024-42229 Référence CVE CVE-2024-42240 https://www.cve.org/CVERecord?id=CVE-2024-42240 Référence CVE CVE-2024-42307 https://www.cve.org/CVERecord?id=CVE-2024-42307 Référence CVE CVE-2024-43820 https://www.cve.org/CVERecord?id=CVE-2024-43820 Référence CVE CVE-2024-46736 https://www.cve.org/CVERecord?id=CVE-2024-46736 Référence CVE CVE-2024-46782 https://www.cve.org/CVERecord?id=CVE-2024-46782 Référence CVE CVE-2024-46796 https://www.cve.org/CVERecord?id=CVE-2024-46796 Référence CVE CVE-2024-47408 https://www.cve.org/CVERecord?id=CVE-2024-47408 Référence CVE CVE-2024-47678 https://www.cve.org/CVERecord?id=CVE-2024-47678 Référence CVE CVE-2024-47794 https://www.cve.org/CVERecord?id=CVE-2024-47794 Référence CVE CVE-2024-49571 https://www.cve.org/CVERecord?id=CVE-2024-49571 Référence CVE CVE-2024-49924 https://www.cve.org/CVERecord?id=CVE-2024-49924 Référence CVE CVE-2024-49940 https://www.cve.org/CVERecord?id=CVE-2024-49940 Référence CVE CVE-2024-49994 https://www.cve.org/CVERecord?id=CVE-2024-49994 Référence CVE CVE-2024-50056 https://www.cve.org/CVERecord?id=CVE-2024-50056 Référence CVE CVE-2024-50126 https://www.cve.org/CVERecord?id=CVE-2024-50126 Référence CVE CVE-2024-50140 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-47143 Référence CVE CVE-2024-47408 https://www.cve.org/CVERecord?id=CVE-2024-47408 Référence CVE CVE-2024-47670 https://www.cve.org/CVERecord?id=CVE-2024-47670 Référence CVE CVE-2024-47671 https://www.cve.org/CVERecord?id=CVE-2024-47671 Référence CVE CVE-2024-47672 https://www.cve.org/CVERecord?id=CVE-2024-47672 Référence CVE CVE-2024-47673 https://www.cve.org/CVERecord?id=CVE-2024-47673 Référence CVE CVE-2024-47674 https://www.cve.org/CVERecord?id=CVE-2024-47674 Référence CVE CVE-2024-47675 https://www.cve.org/CVERecord?id=CVE-2024-47675 Référence CVE CVE-2024-47677 https://www.cve.org/CVERecord?id=CVE-2024-47677 Référence CVE CVE-2024-47678 https://www.cve.org/CVERecord?id=CVE-2024-47678 Référence CVE CVE-2024-47679 https://www.cve.org/CVERecord?id=CVE-2024-47679 Référence CVE CVE-2024-47681 https://www.cve.org/CVERecord?id=CVE-2024-47681 Référence CVE CVE-2024-47682 https://www.cve.org/CVERecord?id=CVE-2024-47682 Référence CVE CVE-2024-47684 https://www.cve.org/CVERecord?id=CVE-2024-47684 Référence CVE CVE-2024-47685 https://www.cve.org/CVERecord?id=CVE-2024-47685 Référence CVE CVE-2024-47686 https://www.cve.org/CVERecord?id=CVE-2024-47686 Référence CVE CVE-2024-47687 https://www.cve.org/CVERecord?id=CVE-2024-47687 Référence CVE CVE-2024-47688 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-41055 Référence CVE CVE-2024-42232 https://www.cve.org/CVERecord?id=CVE-2024-42232 Référence CVE CVE-2024-44934 https://www.cve.org/CVERecord?id=CVE-2024-44934 Référence CVE CVE-2024-44974 https://www.cve.org/CVERecord?id=CVE-2024-44974 Référence CVE CVE-2024-45009 https://www.cve.org/CVERecord?id=CVE-2024-45009 Référence CVE CVE-2024-45010 https://www.cve.org/CVERecord?id=CVE-2024-45010 Référence CVE CVE-2024-45019 https://www.cve.org/CVERecord?id=CVE-2024-45019 Référence CVE CVE-2024-46858 https://www.cve.org/CVERecord?id=CVE-2024-46858 Référence CVE CVE-2024-47666 https://www.cve.org/CVERecord?id=CVE-2024-47666 Référence CVE CVE-2024-47678 https://www.cve.org/CVERecord?id=CVE-2024-47678 Référence CVE CVE-2024-47701 https://www.cve.org/CVERecord?id=CVE-2024-47701 Référence CVE CVE-2024-49867 https://www.cve.org/CVERecord?id=CVE-2024-49867 Référence CVE CVE-2024-49884 https://www.cve.org/CVERecord?id=CVE-2024-49884 Référence CVE CVE-2024-49944 https://www.cve.org/CVERecord?id=CVE-2024-49944 Référence CVE CVE-2024-49950 https://www.cve.org/CVERecord?id=CVE-2024-49950 Référence CVE CVE-2024-49952 https://www.cve.org/CVERecord?id=CVE-2024-49952 Référence CVE CVE-2024-49963 https://www.cve.org/CVERecord?id=CVE-2024-49963 Référence CVE CVE-2024-49975 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-46869 Référence CVE CVE-2024-47670 https://www.cve.org/CVERecord?id=CVE-2024-47670 Référence CVE CVE-2024-47671 https://www.cve.org/CVERecord?id=CVE-2024-47671 Référence CVE CVE-2024-47672 https://www.cve.org/CVERecord?id=CVE-2024-47672 Référence CVE CVE-2024-47673 https://www.cve.org/CVERecord?id=CVE-2024-47673 Référence CVE CVE-2024-47674 https://www.cve.org/CVERecord?id=CVE-2024-47674 Référence CVE CVE-2024-47675 https://www.cve.org/CVERecord?id=CVE-2024-47675 Référence CVE CVE-2024-47676 https://www.cve.org/CVERecord?id=CVE-2024-47676 Référence CVE CVE-2024-47677 https://www.cve.org/CVERecord?id=CVE-2024-47677 Référence CVE CVE-2024-47678 https://www.cve.org/CVERecord?id=CVE-2024-47678 Référence CVE CVE-2024-47679 https://www.cve.org/CVERecord?id=CVE-2024-47679 Référence CVE CVE-2024-47680 https://www.cve.org/CVERecord?id=CVE-2024-47680 Référence CVE CVE-2024-47681 https://www.cve.org/CVERecord?id=CVE-2024-47681 Référence CVE CVE-2024-47682 https://www.cve.org/CVERecord?id=CVE-2024-47682 Référence CVE CVE-2024-47684 https://www.cve.org/CVERecord?id=CVE-2024-47684 Référence CVE CVE-2024-47685 https://www.cve.org/CVERecord?id=CVE-2024-47685 Référence CVE CVE-2024-47686 https://www.cve.org/CVERecord?id=CVE-2024-47686 Référence CVE CVE-2024-47687 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-46853 Référence CVE CVE-2024-46854 https://www.cve.org/CVERecord?id=CVE-2024-46854 Référence CVE CVE-2024-47670 https://www.cve.org/CVERecord?id=CVE-2024-47670 Référence CVE CVE-2024-47671 https://www.cve.org/CVERecord?id=CVE-2024-47671 Référence CVE CVE-2024-47672 https://www.cve.org/CVERecord?id=CVE-2024-47672 Référence CVE CVE-2024-47673 https://www.cve.org/CVERecord?id=CVE-2024-47673 Référence CVE CVE-2024-47674 https://www.cve.org/CVERecord?id=CVE-2024-47674 Référence CVE CVE-2024-47675 https://www.cve.org/CVERecord?id=CVE-2024-47675 Référence CVE CVE-2024-47677 https://www.cve.org/CVERecord?id=CVE-2024-47677 Référence CVE CVE-2024-47678 https://www.cve.org/CVERecord?id=CVE-2024-47678 Référence CVE CVE-2024-47679 https://www.cve.org/CVERecord?id=CVE-2024-47679 Référence CVE CVE-2024-47681 https://www.cve.org/CVERecord?id=CVE-2024-47681 Référence CVE CVE-2024-47682 https://www.cve.org/CVERecord?id=CVE-2024-47682 Référence CVE CVE-2024-47684 https://www.cve.org/CVERecord?id=CVE-2024-47684 Référence CVE CVE-2024-47685 https://www.cve.org/CVERecord?id=CVE-2024-47685 Référence CVE CVE-2024-47686 https://www.cve.org/CVERecord?id=CVE-2024-47686 Référence CVE CVE-2024-47687 https://www.cve.org/CVERecord?id=CVE-2024-47687 Référence CVE CVE-2024-47688 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-26800 Référence CVE CVE-2024-26921 https://www.cve.org/CVERecord?id=CVE-2024-26921 Référence CVE CVE-2024-38630 https://www.cve.org/CVERecord?id=CVE-2024-38630 Référence CVE CVE-2024-43882 https://www.cve.org/CVERecord?id=CVE-2024-43882 Référence CVE CVE-2024-46869 https://www.cve.org/CVERecord?id=CVE-2024-46869 Référence CVE CVE-2024-47671 https://www.cve.org/CVERecord?id=CVE-2024-47671 Référence CVE CVE-2024-47675 https://www.cve.org/CVERecord?id=CVE-2024-47675 Référence CVE CVE-2024-47676 https://www.cve.org/CVERecord?id=CVE-2024-47676 Référence CVE CVE-2024-47677 https://www.cve.org/CVERecord?id=CVE-2024-47677 Référence CVE CVE-2024-47678 https://www.cve.org/CVERecord?id=CVE-2024-47678 Référence CVE CVE-2024-47679 https://www.cve.org/CVERecord?id=CVE-2024-47679 Référence CVE CVE-2024-47680 https://www.cve.org/CVERecord?id=CVE-2024-47680 Référence CVE CVE-2024-47681 https://www.cve.org/CVERecord?id=CVE-2024-47681 Référence CVE CVE-2024-47682 https://www.cve.org/CVERecord?id=CVE-2024-47682 Référence CVE CVE-2024-47684 https://www.cve.org/CVERecord?id=CVE-2024-47684 Référence CVE CVE-2024-47685 https://www.cve.org/CVERecord?id=CVE-2024-47685 Référence CVE CVE-2024-47686 https://www.cve.org/CVERecord?id=CVE-2024-47686 Référence CVE CVE-2024-47687 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-45828 Référence CVE CVE-2024-46680 https://www.cve.org/CVERecord?id=CVE-2024-46680 Référence CVE CVE-2024-46765 https://www.cve.org/CVERecord?id=CVE-2024-46765 Référence CVE CVE-2024-46771 https://www.cve.org/CVERecord?id=CVE-2024-46771 Référence CVE CVE-2024-46800 https://www.cve.org/CVERecord?id=CVE-2024-46800 Référence CVE CVE-2024-46896 https://www.cve.org/CVERecord?id=CVE-2024-46896 Référence CVE CVE-2024-47141 https://www.cve.org/CVERecord?id=CVE-2024-47141 Référence CVE CVE-2024-47143 https://www.cve.org/CVERecord?id=CVE-2024-47143 Référence CVE CVE-2024-47666 https://www.cve.org/CVERecord?id=CVE-2024-47666 Référence CVE CVE-2024-47678 https://www.cve.org/CVERecord?id=CVE-2024-47678 Référence CVE CVE-2024-47709 https://www.cve.org/CVERecord?id=CVE-2024-47709 Référence CVE CVE-2024-47809 https://www.cve.org/CVERecord?id=CVE-2024-47809 Référence CVE CVE-2024-48873 https://www.cve.org/CVERecord?id=CVE-2024-48873 Référence CVE CVE-2024-48881 https://www.cve.org/CVERecord?id=CVE-2024-48881 Référence CVE CVE-2024-49569 https://www.cve.org/CVERecord?id=CVE-2024-49569 Référence CVE CVE-2024-49854 https://www.cve.org/CVERecord?id=CVE-2024-49854 Référence CVE CVE-2024-49884 https://www.cve.org/CVERecord?id=CVE-2024-49884 Référence CVE CVE-2024-49915 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-41042 Référence CVE CVE-2024-41059 https://www.cve.org/CVERecord?id=CVE-2024-41059 Référence CVE CVE-2024-41087 https://www.cve.org/CVERecord?id=CVE-2024-41087 Référence CVE CVE-2024-42133 https://www.cve.org/CVERecord?id=CVE-2024-42133 Référence CVE CVE-2024-42232 https://www.cve.org/CVERecord?id=CVE-2024-42232 Référence CVE CVE-2024-43861 https://www.cve.org/CVERecord?id=CVE-2024-43861 Référence CVE CVE-2024-44934 https://www.cve.org/CVERecord?id=CVE-2024-44934 Référence CVE CVE-2024-44996 https://www.cve.org/CVERecord?id=CVE-2024-44996 Référence CVE CVE-2024-47666 https://www.cve.org/CVERecord?id=CVE-2024-47666 Référence CVE CVE-2024-47678 https://www.cve.org/CVERecord?id=CVE-2024-47678 Référence CVE CVE-2024-49854 https://www.cve.org/CVERecord?id=CVE-2024-49854 Référence CVE CVE-2024-49884 https://www.cve.org/CVERecord?id=CVE-2024-49884 Référence CVE CVE-2024-49915 https://www.cve.org/CVERecord?id=CVE-2024-49915 Référence CVE CVE-2024-49944 https://www.cve.org/CVERecord?id=CVE-2024-49944 Référence CVE CVE-2024-49952 https://www.cve.org/CVERecord?id=CVE-2024-49952 Référence CVE CVE-2024-50016 https://www.cve.org/CVERecord?id=CVE-2024-50016 Référence CVE CVE-2024-50018 https://www.cve.org/CVERecord?id=CVE-2024-50018 Référence CVE CVE-2024-50039 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-36964 Référence CVE CVE-2024-39480 https://www.cve.org/CVERecord?id=CVE-2024-39480 Référence CVE CVE-2024-40909 https://www.cve.org/CVERecord?id=CVE-2024-40909 Référence CVE CVE-2024-40954 https://www.cve.org/CVERecord?id=CVE-2024-40954 Référence CVE CVE-2024-41042 https://www.cve.org/CVERecord?id=CVE-2024-41042 Référence CVE CVE-2024-41059 https://www.cve.org/CVERecord?id=CVE-2024-41059 Référence CVE CVE-2024-43861 https://www.cve.org/CVERecord?id=CVE-2024-43861 Référence CVE CVE-2024-44934 https://www.cve.org/CVERecord?id=CVE-2024-44934 Référence CVE CVE-2024-44996 https://www.cve.org/CVERecord?id=CVE-2024-44996 Référence CVE CVE-2024-47678 https://www.cve.org/CVERecord?id=CVE-2024-47678 Référence CVE CVE-2024-49854 https://www.cve.org/CVERecord?id=CVE-2024-49854 Référence CVE CVE-2024-49884 https://www.cve.org/CVERecord?id=CVE-2024-49884 Référence CVE CVE-2024-49915 https://www.cve.org/CVERecord?id=CVE-2024-49915 Référence CVE CVE-2024-50016 https://www.cve.org/CVERecord?id=CVE-2024-50016 Référence CVE CVE-2024-50018 https://www.cve.org/CVERecord?id=CVE-2024-50018 Référence CVE CVE-2024-50039 https://www.cve.org/CVERecord?id=CVE-2024-50039 Référence CVE CVE-2024-50047 https://www.cve.org/CVERecord?id=CVE-2024-50047 Référence CVE CVE-2024-50143 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-47665 Référence CVE CVE-2024-47667 https://www.cve.org/CVERecord?id=CVE-2024-47667 Référence CVE CVE-2024-47668 https://www.cve.org/CVERecord?id=CVE-2024-47668 Référence CVE CVE-2024-47669 https://www.cve.org/CVERecord?id=CVE-2024-47669 Référence CVE CVE-2024-47670 https://www.cve.org/CVERecord?id=CVE-2024-47670 Référence CVE CVE-2024-47671 https://www.cve.org/CVERecord?id=CVE-2024-47671 Référence CVE CVE-2024-47672 https://www.cve.org/CVERecord?id=CVE-2024-47672 Référence CVE CVE-2024-47673 https://www.cve.org/CVERecord?id=CVE-2024-47673 Référence CVE CVE-2024-47674 https://www.cve.org/CVERecord?id=CVE-2024-47674 Référence CVE CVE-2024-47678 https://www.cve.org/CVERecord?id=CVE-2024-47678 Référence CVE CVE-2024-47679 https://www.cve.org/CVERecord?id=CVE-2024-47679 Référence CVE CVE-2024-47682 https://www.cve.org/CVERecord?id=CVE-2024-47682 Référence CVE CVE-2024-47683 https://www.cve.org/CVERecord?id=CVE-2024-47683 Référence CVE CVE-2024-47684 https://www.cve.org/CVERecord?id=CVE-2024-47684 Référence CVE CVE-2024-47685 https://www.cve.org/CVERecord?id=CVE-2024-47685 Référence CVE CVE-2024-47686 https://www.cve.org/CVERecord?id=CVE-2024-47686 Référence CVE CVE-2024-47690 https://www.cve.org/CVERecord?id=CVE-2024-47690 Référence CVE CVE-2024-47692 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-011048Linux の 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: < 3.18, 6.1.113 ≤ 6.1.*, 6.6.54 ≤ 6.6.*, 6.10.13 ≤ 6.10.*, 6.11.2 ≤ 6.11.*, 6.12 ≤ *
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. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 21 Oct 2024 · Last source change 5 Aug 2026, 11:39 UTC · CWE-203 · Observable Discrepancy

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-42599
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-42599↗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-47678 · cve.blacktree.nl