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.
Security readout for executives and security teams
Plain-English summary
This Linux kernel flaw can trigger a kernel routing bug during ICMP error handling when XFRM/IPsec processing is involved. The practical impact is availability: a local, low-privileged actor may be able to cause a disruptive kernel warning or failure path. There is no source evidence of data theft, privilege escalation, or active exploitation.
Executive priority
Patch during the next normal kernel maintenance window, sooner for shared Linux platforms or systems relying on IPsec/XFRM. The urgency is moderate because exploitation requires local access, but the impact can affect availability.
Technical view
The issue is in IPv4 ICMP route lookup. Locally generated packet failures can be reprocessed through XFRM, assigning an input route with ip_rt_bug as output handling for destination-unreachable traffic. The kernel fix skips ICMP relookup for locally generated packets. CVSS is 5.5, local attack vector, low privileges, high availability impact.
Likely exposure
Exposure is mainly Linux systems running affected kernel builds where local users or workloads can exercise networking paths involving XFRM/IPsec and ICMP error generation. Internet-only exposure is not supported by the supplied sources because the CVSS vector is local.
Exploitation context
The source bundle includes a local reproduction scenario, but no KEV listing and no cited public evidence of active exploitation. Treat this as a reliability and denial-of-service risk for multi-user, container-hosting, or sensitive Linux infrastructure rather than a remote compromise issue.
Researcher notes
The provided evidence supports a local availability flaw in Linux IPv4 ICMP/XFRM routing behavior. Affected-version data in the bundle is not distribution-specific, so package-level exposure requires vendor mapping. No exploit-in-the-wild evidence is provided.
Mitigation direction
Apply Linux kernel updates containing the referenced stable fixes.
Check distribution advisories for exact package versions and backports.
Prioritize shared hosts, container platforms, and systems using XFRM/IPsec.
Restrict untrusted local shell or workload access where patching is delayed.
Monitor kernel logs for route warnings or ICMP/XFRM-related failures.
Validation and detection
Inventory Linux kernel versions across affected fleets.
Confirm vendor packages include the referenced stable kernel fixes.
Review whether XFRM/IPsec is enabled or used on exposed systems.
Check kernel logs for ip_rt_bug warnings or related call traces.
Validate remediation through approved regression testing, not public reproducer use.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-56647 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.