CVE-2024-56647: net: Fix icmp host relookup triggering ip_rt_bug
First published: Fri Dec 27 2024(Updated: )
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.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel | >=2.6.25<6.12.5 | |
| Linux Kernel | =6.13-rc1 | |
| debian/linux | <=5.10.223-1<=5.10.234-1<=6.1.129-1<=6.1.133-1 | 6.12.22-1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/9545011e7b2a8fc0cbd6e387a09f12cd41d7d82f
- https://git.kernel.org/stable/c/c44daa7e3c73229f7ac74985acb8c7fb909c4e0a
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-56647
- https://nvd.nist.gov/vuln/detail/CVE-2024-56647
- https://launchpad.net/bugs/cve/CVE-2024-56647
- https://security-tracker.debian.org/tracker/CVE-2024-56647
- https://ubuntu.com/security/CVE-2024-56647
- https://git.kernel.org/linus/c44daa7e3c73229f7ac74985acb8c7fb909c4e0a
Frequently Asked Questions
What is the severity of CVE-2024-56647?
The severity level of CVE-2024-56647 is currently classified as moderate.
How do I fix CVE-2024-56647?
To fix CVE-2024-56647, it is recommended to update the Linux kernel to a version that incorporates the patch, specifically versions newer than 6.12.5 or 6.13-rc1.
What software is affected by CVE-2024-56647?
CVE-2024-56647 affects multiple versions of the Linux kernel from version 2.6.25 up to 6.12.5, as well as 6.13-rc1.
What is the impact of CVE-2024-56647?
The impact of CVE-2024-56647 may result in a kernel warning indicating an IP routing bug, which could potentially affect network stability.
Who is responsible for addressing CVE-2024-56647?
The responsibility for addressing CVE-2024-56647 lies with the Linux kernel maintainers and those deploying affected versions.
- agent/title
- agent/type
- agent/first-publish-date
- agent/author
- agent/remedy
- agent/severity
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/usn-cve
- source/Ubuntu
- collector/launchpad-cve
- source/Launchpad
- agent/references
- agent/description
- agent/source
- agent/softwarecombine
- agent/tags
- agent/event
- collector/security-tracker-debian
- source/Debian
- collector/nvd-cve
- vendor/linux
- canonical/linux kernel
- version/linux kernel/2.6.25
- version/linux kernel/6.13-rc1
- package-manager/debian