CVE-2024-56647: net: Fix icmp host relookup triggering ip_rt_bug
Telemetry drift only. No threshold crossed and no authority ruling changed.
CVE record, CISA KEV and EPSS as of 2026-10-18.
CVEs like this one computed, by meaning
What to do now held facts and links
- Upgrade to the fixed version for your release line, or later: 6.1.175; 6.6.140; 6.12.5; 6.13 CVE record
- Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
- Check your version against the ranges this record publishes.
What it is stated by the CNA
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…
- weakness
- Not named by the CNA.
- affected
- Linux
- published ranges
- linux kernel >= 2.6.25 < 6.12.5; linux kernel 6.13-rc1
- fixed in
- 6.1.175; 6.6.140; 6.12.5; 6.13
- fixed by package (from OSV advisories)
- Kernel (Linux): 6.1.175; 6.6.140; 6.12.5 CVE-2024-56647
- assigned by
- Linux
- published
- 2024-12-27
check us git.kernel.org git.kernel.org git.kernel.org git.kernel.org
Exploit code held, dated
- exploit code
- None held in the PoC-in-GitHub feed. A public repository changes this brief.
What moved held, dated
| date | EPSS | event |
|---|---|---|
| 28 Dec 2024 | 0.00043 | |
| 17 Mar 2025 | 0.00019 | scoring model v2025.03.14 |
| 28 Apr 2025 | 0.00026 | |
| 25 May 2025 | 0.00019 | |
| 22 May 2026 | 0.00016 | |
| 15 Jun 2026 | 0.00217 | scoring model v2026.06.15 |
| 11 Jul 2026 | 0.00218 | |
| 22 Jul 2026 | 0.00223 |
25 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.
Outside the record researched, cited
This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.
What would change this brief held, dated
- CISA KEV
- Not listed in the catalogue we hold. A listing changes this brief.
- exploit probability
- 0.00 on 2026-07-22 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
- fix
- Held: 6.1.175; 6.6.140; 6.12.5; 6.13. A newer fix from the CNA or OSV changes this brief.
How to check this
Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:
SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2024-56647', '2026-11-01T23:59:59.999999Z', now());