| From bippy-5f407fcff5a0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2024-56647: net: Fix icmp host relookup triggering ip_rt_bug |
| |
| Description |
| =========== |
| |
| 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. |
| |
| The Linux kernel CVE team has assigned CVE-2024-56647 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 2.6.25 with commit 8b7817f3a959ed99d7443afc12f78a7e1fcc2063 and fixed in 6.12.5 with commit 9545011e7b2a8fc0cbd6e387a09f12cd41d7d82f |
| Issue introduced in 2.6.25 with commit 8b7817f3a959ed99d7443afc12f78a7e1fcc2063 and fixed in 6.13 with commit c44daa7e3c73229f7ac74985acb8c7fb909c4e0a |
| |
| Please see https://www.kernel.org for a full list of currently supported |
| kernel versions by the kernel community. |
| |
| Unaffected versions might change over time as fixes are backported to |
| older supported kernel versions. The official CVE entry at |
| https://cve.org/CVERecord/?id=CVE-2024-56647 |
| will be updated if fixes are backported, please check that for the most |
| up to date information about this issue. |
| |
| |
| Affected files |
| ============== |
| |
| The file(s) affected by this issue are: |
| net/ipv4/icmp.c |
| |
| |
| Mitigation |
| ========== |
| |
| The Linux kernel CVE team recommends that you update to the latest |
| stable kernel version for this, and many other bugfixes. Individual |
| changes are never tested alone, but rather are part of a larger kernel |
| release. Cherry-picking individual commits is not recommended or |
| supported by the Linux kernel community at all. If however, updating to |
| the latest release is impossible, the individual changes to resolve this |
| issue can be found at these commits: |
| https://git.kernel.org/stable/c/9545011e7b2a8fc0cbd6e387a09f12cd41d7d82f |
| https://git.kernel.org/stable/c/c44daa7e3c73229f7ac74985acb8c7fb909c4e0a |
