Skip to main content

CVE-2024-56751: Vulnerability in Linux Linux

High
VulnerabilityCVE-2024-56751cvecve-2024-56751
Published: Sun Dec 29 2024 (12/29/2024, 11:30:16 UTC)
Source: CVE
Vendor/Project: Linux
Product: Linux

Description

In the Linux kernel, the following vulnerability has been resolved: ipv6: release nexthop on device removal The CI is hitting some aperiodic hangup at device removal time in the pmtu.sh self-test: unregister_netdevice: waiting for veth_A-R1 to become free. Usage count = 6 ref_tracker: veth_A-R1@ffff888013df15d8 has 1/5 users at dst_init+0x84/0x4a0 dst_alloc+0x97/0x150 ip6_dst_alloc+0x23/0x90 ip6_rt_pcpu_alloc+0x1e6/0x520 ip6_pol_route+0x56f/0x840 fib6_rule_lookup+0x334/0x630 ip6_route_output_flags+0x259/0x480 ip6_dst_lookup_tail.constprop.0+0x5c2/0x940 ip6_dst_lookup_flow+0x88/0x190 udp_tunnel6_dst_lookup+0x2a7/0x4c0 vxlan_xmit_one+0xbde/0x4a50 [vxlan] vxlan_xmit+0x9ad/0xf20 [vxlan] dev_hard_start_xmit+0x10e/0x360 __dev_queue_xmit+0xf95/0x18c0 arp_solicit+0x4a2/0xe00 neigh_probe+0xaa/0xf0 While the first suspect is the dst_cache, explicitly tracking the dst owing the last device reference via probes proved such dst is held by the nexthop in the originating fib6_info. Similar to commit f5b51fe804ec ("ipv6: route: purge exception on removal"), we need to explicitly release the originating fib info when disconnecting a to-be-removed device from a live ipv6 dst: move the fib6_info cleanup into ip6_dst_ifdown(). Tested running: ./pmtu.sh cleanup_ipv6_exception in a tight loop for more than 400 iterations with no spat, running an unpatched kernel I observed a splat every ~10 iterations.

AI-Powered Analysis

AILast updated: 06/28/2025, 07:41:37 UTC

Technical Analysis

CVE-2024-56751 is a vulnerability identified in the Linux kernel related to the IPv6 networking stack, specifically concerning the handling of nexthop references during device removal. The issue arises when an IPv6 network device is removed, and the kernel fails to properly release the nexthop references held by the originating fib6_info structure. This improper cleanup leads to a hang or deadlock condition during device removal, as demonstrated by the pmtu.sh self-test where the kernel waits indefinitely for a network device (e.g., veth_A-R1) to become free due to lingering usage counts. The root cause is that the dst_cache, which tracks destination entries, holds references to nexthops that are not released timely. The fix involves moving the fib6_info cleanup into the ip6_dst_ifdown() function, ensuring that when a device is disconnected, the associated fib6_info is explicitly released, preventing the kernel from hanging. This vulnerability manifests as aperiodic kernel hangups or crashes during network device removal, impacting system stability and availability. It does not appear to be exploitable for privilege escalation or data leakage but can cause denial of service (DoS) by making the kernel unresponsive or causing system crashes during routine network device management operations. The vulnerability affects Linux kernel versions identified by the commit hash f88d8ea67fbdbac7a64bfa6ed9a2ba27bb822f74 and was published on December 29, 2024. No known exploits are currently reported in the wild, and no CVSS score has been assigned yet.

Potential Impact

For European organizations, this vulnerability primarily poses a risk to system availability and operational continuity. Organizations relying on Linux-based infrastructure with IPv6 enabled, especially those using virtual Ethernet devices (veth) or complex network topologies involving dynamic device removal (e.g., cloud providers, data centers, telecom operators, and enterprises with containerized environments), may experience system hangs or crashes during network device removal. This can disrupt critical services, lead to downtime, and increase operational costs due to system instability. The impact is more pronounced in environments with frequent network device reconfiguration or automated orchestration systems that dynamically add and remove network interfaces. While this vulnerability does not directly compromise confidentiality or integrity, the denial of service effect can indirectly affect business operations, compliance with service level agreements (SLAs), and incident response capabilities. Given the widespread use of Linux in European IT infrastructure, the potential for disruption is significant, especially in sectors such as finance, healthcare, and telecommunications where high availability is essential.

Mitigation Recommendations

1. Apply the official Linux kernel patch that addresses CVE-2024-56751 as soon as it becomes available from trusted sources or Linux distributions. 2. For organizations using custom or long-term support (LTS) kernels, backport the fix into their kernel versions after thorough testing. 3. Monitor kernel updates and subscribe to security advisories from Linux vendors and distributions to ensure timely patching. 4. Implement robust change management and testing procedures for network device removal operations, particularly in virtualized or containerized environments, to detect and mitigate hangs early. 5. Use kernel crash dump and logging tools to capture detailed information if hangs occur, facilitating faster diagnosis and remediation. 6. Where possible, schedule network device removals during maintenance windows to minimize operational impact. 7. Consider temporarily disabling or limiting dynamic network device removal in critical production environments until patches are applied. 8. Engage with Linux vendor support channels for guidance on patch deployment and mitigation strategies tailored to specific environments.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Linux
Date Reserved
2024-12-29T11:26:39.759Z
Cisa Enriched
false
Cvss Version
null
State
PUBLISHED

Threat ID: 682d9822c4522896dcbde712

Added to database: 5/21/2025, 9:08:50 AM

Last enriched: 6/28/2025, 7:41:37 AM

Last updated: 8/15/2025, 9:03:11 AM

Views: 17

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats