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

net: Fix icmp host relookup triggering ip_rt_bug

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 19 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 1 Jun 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.22% 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 19 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.

23 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 19 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.12.5-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.170-3Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.5-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.5-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-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-nvidia-tegraAffected, 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-raspi-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-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-56647 · CSAF 2.0 · revision 66 · interimSUSE Product Security TeamCVE-2024-56647
456 known affected

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

  • kernel-default as component of SLES-LTSS-TERADATA 15 SP2
  • kernel-source as component of SLES-LTSS-TERADATA 15 SP2
  • 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 High Availability Extension 12 SP5
Summary
In the Linux kernel, the following vulnerability has been resolved: net: Fix icmp host relookup triggering ip_rt_bug arp link failure may trigger ip_rt_bug while xfrm enabled, call trace is: WARNING: CPU: 0 PID: 0 at net/ipv4/route.c:1241 ip_rt_bug+0x14/0x20 Modules linked in: CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.12.0-rc6-00077-g2e1b3cc9d7f7 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:ip_rt_bug+0x14/0x20 Call Trace: ip_send_skb+0x14/0x40 __icmp_send+0x42d/0x6a0 ipv4_link_failure+0xe2/0x1d0 arp_error_report+0x3c/0x50 neigh_invalidate+0x8d/0x100 neigh_timer_handler+0x2e1/0x330 call_timer_fn+0x21/0x120 __run_timer_base.part.0+0x1c9/0x270 run_timer_softirq+0x4c/0x80 handle_softirqs+0xac/0x280 irq_exit_rcu+0x62/0x80 sysvec_apic_timer_interrupt+0x77/0x90 The script below reproduces this scenario: ip xfrm policy add src 0.0.0.0/0 dst 0.0.0.0/0 \ dir out priority 0 ptype main flag localok icmp ip l a veth1 type veth ip a a 192.168.141.111/24 dev veth0 ip l s veth0 up ping 192.168.141.155 -c 1 icmp_route_lookup() create input routes for locally generated packets while xfrm relookup ICMP traffic.Then it will set input route (dst->out = ip_rt_bug) to skb for DESTUNREACH. For ICMP err triggered by locally generated packets, dst->dev of output route is loopback. Generally, xfrm relookup verification is not required on loopback interfaces (net.ipv4.conf.lo.disable_xfrm = 1). Skip icmp relookup for locally generated packets to fix it.
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-53295

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 19 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: net: Fix icmp host relookup triggering ip_rt_bug arp link failure may trigger ip_rt_bug while xfrm enabled, call trace is: WARNING: CPU: 0 PID: 0 at net/ipv4/route.c:1241 ip_rt_bug+0x14/0x20 Modules linked in: CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.12.0-rc6-00077-g2e1b3cc9d7f7 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:ip_rt_bug+0x14/0x20 Call Trace: <IRQ> ip_send_skb+0x14/0x40 __icmp_send+0x42d/0x6a0 ipv4_link_failure+0xe2/0x1d0 arp_error_report+0x3c/0x50 neigh_invalidate+0x8d/0x100 neigh_timer_handler+0x2e1/0x330 call_timer_fn+0x21/0x120 __run_timer_base.part.0+0x1c9/0x270 run_timer_softirq+0x4c/0x80 handle_softirqs+0xac/0x280 irq_exit_rcu+0x62/0x80 sysvec_apic_timer_interrupt+0x77/0x90 The script below reproduces this scenario: ip xfrm policy add src 0.0.0.0/0 dst 0.0.0.0/0 \ dir out priority 0 ptype main flag localok icmp ip l a veth1 type veth ip a a 192.168.141.111/24 dev veth0 ip l s veth0 up ping 192.168.141.155 -c 1 icmp_route_lookup() create input routes for locally generated packets while xfrm relookup ICMP traffic.Then it will set input route (dst->out = ip_rt_bug) to skb for DESTUNREACH. For ICMP err triggered by locally generated packets, dst->dev of output route is loopback. Generally, xfrm relookup verification is not required on loopback interfaces (net.ipv4.conf.lo.disable_xfrm = 1). Skip icmp relookup for locally generated packets to fix it.

What

In the Linux kernel, the following vulnerability has been resolved: net: Fix icmp host relookup triggering ip_rt_bug arp link failure may trigger ip_rt_bug while xfrm enabled, call trace is: WARNING: CPU: 0 PID: 0 at net/ipv4/route.c:1241 ip_rt_bug+0x14/0x20 Modules linked in: CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.12.0-rc6-00077-g2e1b3cc9d7f7 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:ip_rt_bug+0x14/0x20 Call Trace: <IRQ> ip_send_skb+0x14/0x40 __icmp_send+0x42d/0x6a0 ipv4_link_failure+0xe2/0x1d0 arp_error_report+0x3c/0x50 neigh_invalidate+0x8d/0x100 neigh_timer_handler+0x2e1/0x330 call_timer_fn+0x21/0x120 __run_timer_base.part.0+0x1c9/0x270 run_timer_softirq+0x4c/0x80 handle_softirqs+0xac/0x280 irq_exit_rcu+0x62/0x80 sysvec_apic_timer_interrupt+0x77/0x90 The script below reproduces this scenario: ip xfrm policy add src 0.0.0.0/0 dst 0.0.0.0/0 \ dir out priority 0 ptype main flag localok icmp ip l a veth1 type veth ip a a 192.168.141.111/24 dev veth0 ip l s veth0 up ping 192.168.141.155 -c 1 icmp_route_lookup() create input routes for locally generated packets while xfrm relookup ICMP traffic.Then it will set input route (dst->out = ip_rt_bug) to skb for DESTUNREACH. For ICMP err triggered by locally generated packets, dst->dev of output route is loopback. Generally, xfrm relookup verification is not required on loopback interfaces (net.ipv4.conf.lo.disable_xfrm = 1). Skip icmp relookup for locally generated packets to fix it.

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: net: Fix icmp host relookup triggering ip_rt_bug arp link failure may trigger ip_rt_bug while xfrm enabled, call trace is: WARNING: CPU: 0 PID: 0 at net/ipv4/route.c:1241 ip_rt_bug+0x14/0x20 Modules linked in: CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.12.0-rc6-00077-g2e1b3cc9d7f7 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:ip_rt_bug+0x14/0x20 Call Trace: <IRQ> ip_send_skb+0x14/0x40 __icmp_send+0x42d/0x6a0 ipv4_link_failure+0xe2/0x1d0 arp_error_report+0x3c/0x50 neigh_invalidate+0x8d/0x100 neigh_timer_handler+0x2e1/0x330 call_timer_fn+0x21/0x120 __run_timer_base.part.0+0x1c9/0x270 run_timer_softirq+0x4c/0x80 handle_softirqs+0xac/0x280 irq_exit_rcu+0x62/0x80 sysvec_apic_timer_interrupt+0x77/0x90 The script below reproduces this scenario: ip xfrm policy add src 0.0.0.0/0 dst 0.0.0.0/0 \ dir out priority 0 ptype main flag localok icmp ip l a veth1 type veth ip a a 192.168.141.111/24 dev veth0 ip l s veth0 up ping 192.168.141.155 -c 1 icmp_route_lookup() create input routes for locally generated packets while xfrm relookup ICMP traffic.Then it will set input route (dst->out = ip_rt_bug) to skb for DESTUNREACH. For ICMP err triggered by locally generated packets, dst->dev of output route is loopback. Generally, xfrm relookup verification is not required on loopback interfaces (net.ipv4.conf.lo.disable_xfrm = 1). Skip icmp relookup for locally generated packets to fix it.

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-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-2025-1439Dell Secure Connect Gateway: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein Angreifer kann mehrere Schwachstellen in Dell Secure Connect Gateway ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.

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

Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht näher beschriebene Effekte zu erzielen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250101Security Bulletin 01 Jan 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 01 Jan 2025, published on 1 January 2025. 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-56588 Référence CVE CVE-2024-56591 https://www.cve.org/CVERecord?id=CVE-2024-56591 Référence CVE CVE-2024-56592 https://www.cve.org/CVERecord?id=CVE-2024-56592 Référence CVE CVE-2024-56604 https://www.cve.org/CVERecord?id=CVE-2024-56604 Référence CVE CVE-2024-56607 https://www.cve.org/CVERecord?id=CVE-2024-56607 Référence CVE CVE-2024-56609 https://www.cve.org/CVERecord?id=CVE-2024-56609 Référence CVE CVE-2024-56611 https://www.cve.org/CVERecord?id=CVE-2024-56611 Référence CVE CVE-2024-56639 https://www.cve.org/CVERecord?id=CVE-2024-56639 Référence CVE CVE-2024-56641 https://www.cve.org/CVERecord?id=CVE-2024-56641 Référence CVE CVE-2024-56647 https://www.cve.org/CVERecord?id=CVE-2024-56647 Référence CVE CVE-2024-56657 https://www.cve.org/CVERecord?id=CVE-2024-56657 Référence CVE CVE-2024-56660 https://www.cve.org/CVERecord?id=CVE-2024-56660 Référence CVE CVE-2024-56665 https://www.cve.org/CVERecord?id=CVE-2024-56665 Référence CVE CVE-2024-56671 https://www.cve.org/CVERecord?id=CVE-2024-56671 Référence CVE CVE-2024-56674 https://www.cve.org/CVERecord?id=CVE-2024-56674 Référence CVE CVE-2024-56677 https://www.cve.org/CVERecord?id=CVE-2024-56677 Référence CVE CVE-2024-56692 https://www.cve.org/CVERecord?id=CVE-2024-56692 Référence CVE CVE-2024-56703 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-56588 Référence CVE CVE-2024-56591 https://www.cve.org/CVERecord?id=CVE-2024-56591 Référence CVE CVE-2024-56592 https://www.cve.org/CVERecord?id=CVE-2024-56592 Référence CVE CVE-2024-56604 https://www.cve.org/CVERecord?id=CVE-2024-56604 Référence CVE CVE-2024-56607 https://www.cve.org/CVERecord?id=CVE-2024-56607 Référence CVE CVE-2024-56609 https://www.cve.org/CVERecord?id=CVE-2024-56609 Référence CVE CVE-2024-56611 https://www.cve.org/CVERecord?id=CVE-2024-56611 Référence CVE CVE-2024-56639 https://www.cve.org/CVERecord?id=CVE-2024-56639 Référence CVE CVE-2024-56641 https://www.cve.org/CVERecord?id=CVE-2024-56641 Référence CVE CVE-2024-56647 https://www.cve.org/CVERecord?id=CVE-2024-56647 Référence CVE CVE-2024-56657 https://www.cve.org/CVERecord?id=CVE-2024-56657 Référence CVE CVE-2024-56660 https://www.cve.org/CVERecord?id=CVE-2024-56660 Référence CVE CVE-2024-56665 https://www.cve.org/CVERecord?id=CVE-2024-56665 Référence CVE CVE-2024-56671 https://www.cve.org/CVERecord?id=CVE-2024-56671 Référence CVE CVE-2024-56674 https://www.cve.org/CVERecord?id=CVE-2024-56674 Référence CVE CVE-2024-56677 https://www.cve.org/CVERecord?id=CVE-2024-56677 Référence CVE CVE-2024-56692 https://www.cve.org/CVERecord?id=CVE-2024-56692 Référence CVE CVE-2024-56703 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-56636 Référence CVE CVE-2024-56637 https://www.cve.org/CVERecord?id=CVE-2024-56637 Référence CVE CVE-2024-56638 https://www.cve.org/CVERecord?id=CVE-2024-56638 Référence CVE CVE-2024-56640 https://www.cve.org/CVERecord?id=CVE-2024-56640 Référence CVE CVE-2024-56641 https://www.cve.org/CVERecord?id=CVE-2024-56641 Référence CVE CVE-2024-56642 https://www.cve.org/CVERecord?id=CVE-2024-56642 Référence CVE CVE-2024-56643 https://www.cve.org/CVERecord?id=CVE-2024-56643 Référence CVE CVE-2024-56644 https://www.cve.org/CVERecord?id=CVE-2024-56644 Référence CVE CVE-2024-56645 https://www.cve.org/CVERecord?id=CVE-2024-56645 Référence CVE CVE-2024-56647 https://www.cve.org/CVERecord?id=CVE-2024-56647 Référence CVE CVE-2024-56648 https://www.cve.org/CVERecord?id=CVE-2024-56648 Référence CVE CVE-2024-56649 https://www.cve.org/CVERecord?id=CVE-2024-56649 Référence CVE CVE-2024-56650 https://www.cve.org/CVERecord?id=CVE-2024-56650 Référence CVE CVE-2024-56651 https://www.cve.org/CVERecord?id=CVE-2024-56651 Référence CVE CVE-2024-56658 https://www.cve.org/CVERecord?id=CVE-2024-56658 Référence CVE CVE-2024-56659 https://www.cve.org/CVERecord?id=CVE-2024-56659 Référence CVE CVE-2024-56662 https://www.cve.org/CVERecord?id=CVE-2024-56662 Référence CVE CVE-2024-56663 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56636 Référence CVE CVE-2024-56637 https://www.cve.org/CVERecord?id=CVE-2024-56637 Référence CVE CVE-2024-56638 https://www.cve.org/CVERecord?id=CVE-2024-56638 Référence CVE CVE-2024-56640 https://www.cve.org/CVERecord?id=CVE-2024-56640 Référence CVE CVE-2024-56641 https://www.cve.org/CVERecord?id=CVE-2024-56641 Référence CVE CVE-2024-56642 https://www.cve.org/CVERecord?id=CVE-2024-56642 Référence CVE CVE-2024-56643 https://www.cve.org/CVERecord?id=CVE-2024-56643 Référence CVE CVE-2024-56644 https://www.cve.org/CVERecord?id=CVE-2024-56644 Référence CVE CVE-2024-56645 https://www.cve.org/CVERecord?id=CVE-2024-56645 Référence CVE CVE-2024-56647 https://www.cve.org/CVERecord?id=CVE-2024-56647 Référence CVE CVE-2024-56648 https://www.cve.org/CVERecord?id=CVE-2024-56648 Référence CVE CVE-2024-56649 https://www.cve.org/CVERecord?id=CVE-2024-56649 Référence CVE CVE-2024-56650 https://www.cve.org/CVERecord?id=CVE-2024-56650 Référence CVE CVE-2024-56651 https://www.cve.org/CVERecord?id=CVE-2024-56651 Référence CVE CVE-2024-56658 https://www.cve.org/CVERecord?id=CVE-2024-56658 Référence CVE CVE-2024-56659 https://www.cve.org/CVERecord?id=CVE-2024-56659 Référence CVE CVE-2024-56662 https://www.cve.org/CVERecord?id=CVE-2024-56662 Référence CVE CVE-2024-56663 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56638 Référence CVE CVE-2024-56639 https://www.cve.org/CVERecord?id=CVE-2024-56639 Référence CVE CVE-2024-56640 https://www.cve.org/CVERecord?id=CVE-2024-56640 Référence CVE CVE-2024-56641 https://www.cve.org/CVERecord?id=CVE-2024-56641 Référence CVE CVE-2024-56642 https://www.cve.org/CVERecord?id=CVE-2024-56642 Référence CVE CVE-2024-56643 https://www.cve.org/CVERecord?id=CVE-2024-56643 Référence CVE CVE-2024-56644 https://www.cve.org/CVERecord?id=CVE-2024-56644 Référence CVE CVE-2024-56645 https://www.cve.org/CVERecord?id=CVE-2024-56645 Référence CVE CVE-2024-56646 https://www.cve.org/CVERecord?id=CVE-2024-56646 Référence CVE CVE-2024-56647 https://www.cve.org/CVERecord?id=CVE-2024-56647 Référence CVE CVE-2024-56648 https://www.cve.org/CVERecord?id=CVE-2024-56648 Référence CVE CVE-2024-56649 https://www.cve.org/CVERecord?id=CVE-2024-56649 Référence CVE CVE-2024-56650 https://www.cve.org/CVERecord?id=CVE-2024-56650 Référence CVE CVE-2024-56651 https://www.cve.org/CVERecord?id=CVE-2024-56651 Référence CVE CVE-2024-56652 https://www.cve.org/CVERecord?id=CVE-2024-56652 Référence CVE CVE-2024-56653 https://www.cve.org/CVERecord?id=CVE-2024-56653 Référence CVE CVE-2024-56654 https://www.cve.org/CVERecord?id=CVE-2024-56654 Référence CVE CVE-2024-56655 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-53239 Référence CVE CVE-2024-56539 https://www.cve.org/CVERecord?id=CVE-2024-56539 Référence CVE CVE-2024-56548 https://www.cve.org/CVERecord?id=CVE-2024-56548 Référence CVE CVE-2024-56579 https://www.cve.org/CVERecord?id=CVE-2024-56579 Référence CVE CVE-2024-56600 https://www.cve.org/CVERecord?id=CVE-2024-56600 Référence CVE CVE-2024-56601 https://www.cve.org/CVERecord?id=CVE-2024-56601 Référence CVE CVE-2024-56605 https://www.cve.org/CVERecord?id=CVE-2024-56605 Référence CVE CVE-2024-56623 https://www.cve.org/CVERecord?id=CVE-2024-56623 Référence CVE CVE-2024-56633 https://www.cve.org/CVERecord?id=CVE-2024-56633 Référence CVE CVE-2024-56647 https://www.cve.org/CVERecord?id=CVE-2024-56647 Référence CVE CVE-2024-56648 https://www.cve.org/CVERecord?id=CVE-2024-56648 Référence CVE CVE-2024-56650 https://www.cve.org/CVERecord?id=CVE-2024-56650 Référence CVE CVE-2024-56658 https://www.cve.org/CVERecord?id=CVE-2024-56658 Référence CVE CVE-2024-56664 https://www.cve.org/CVERecord?id=CVE-2024-56664 Référence CVE CVE-2024-56720 https://www.cve.org/CVERecord?id=CVE-2024-56720 Référence CVE CVE-2024-56759 https://www.cve.org/CVERecord?id=CVE-2024-56759 Référence CVE CVE-2024-57791 https://www.cve.org/CVERecord?id=CVE-2024-57791 Référence CVE CVE-2024-57798 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-56605 Référence CVE CVE-2024-56619 https://www.cve.org/CVERecord?id=CVE-2024-56619 Référence CVE CVE-2024-56623 https://www.cve.org/CVERecord?id=CVE-2024-56623 Référence CVE CVE-2024-56629 https://www.cve.org/CVERecord?id=CVE-2024-56629 Référence CVE CVE-2024-56631 https://www.cve.org/CVERecord?id=CVE-2024-56631 Référence CVE CVE-2024-56633 https://www.cve.org/CVERecord?id=CVE-2024-56633 Référence CVE CVE-2024-56642 https://www.cve.org/CVERecord?id=CVE-2024-56642 Référence CVE CVE-2024-56644 https://www.cve.org/CVERecord?id=CVE-2024-56644 Référence CVE CVE-2024-56645 https://www.cve.org/CVERecord?id=CVE-2024-56645 Référence CVE CVE-2024-56647 https://www.cve.org/CVERecord?id=CVE-2024-56647 Référence CVE CVE-2024-56648 https://www.cve.org/CVERecord?id=CVE-2024-56648 Référence CVE CVE-2024-56650 https://www.cve.org/CVERecord?id=CVE-2024-56650 Référence CVE CVE-2024-56658 https://www.cve.org/CVERecord?id=CVE-2024-56658 Référence CVE CVE-2024-56661 https://www.cve.org/CVERecord?id=CVE-2024-56661 Référence CVE CVE-2024-56664 https://www.cve.org/CVERecord?id=CVE-2024-56664 Référence CVE CVE-2024-56678 https://www.cve.org/CVERecord?id=CVE-2024-56678 Référence CVE CVE-2024-56681 https://www.cve.org/CVERecord?id=CVE-2024-56681 Référence CVE CVE-2024-56688 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-53239 Référence CVE CVE-2024-56539 https://www.cve.org/CVERecord?id=CVE-2024-56539 Référence CVE CVE-2024-56548 https://www.cve.org/CVERecord?id=CVE-2024-56548 Référence CVE CVE-2024-56568 https://www.cve.org/CVERecord?id=CVE-2024-56568 Référence CVE CVE-2024-56579 https://www.cve.org/CVERecord?id=CVE-2024-56579 Référence CVE CVE-2024-56600 https://www.cve.org/CVERecord?id=CVE-2024-56600 Référence CVE CVE-2024-56601 https://www.cve.org/CVERecord?id=CVE-2024-56601 Référence CVE CVE-2024-56605 https://www.cve.org/CVERecord?id=CVE-2024-56605 Référence CVE CVE-2024-56623 https://www.cve.org/CVERecord?id=CVE-2024-56623 Référence CVE CVE-2024-56647 https://www.cve.org/CVERecord?id=CVE-2024-56647 Référence CVE CVE-2024-56650 https://www.cve.org/CVERecord?id=CVE-2024-56650 Référence CVE CVE-2024-56658 https://www.cve.org/CVERecord?id=CVE-2024-56658 Référence CVE CVE-2024-56664 https://www.cve.org/CVERecord?id=CVE-2024-56664 Référence CVE CVE-2024-56720 https://www.cve.org/CVERecord?id=CVE-2024-56720 Référence CVE CVE-2024-56759 https://www.cve.org/CVERecord?id=CVE-2024-56759 Référence CVE CVE-2024-57791 https://www.cve.org/CVERecord?id=CVE-2024-57791 Référence CVE CVE-2024-57798 https://www.cve.org/CVERecord?id=CVE-2024-57798 Référence CVE CVE-2024-57849 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-015790Linux の 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: < 2.6.25, 6.1.175 ≤ 6.1.*, 6.6.140 ≤ 6.6.*, 6.12.5 ≤ 6.12.*, 6.13 ≤ *
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 27 Dec 2024 · Last source change 1 Jun 2026, 16:04 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-53295
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-53295↗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-56647 · cve.blacktree.nl