Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2024-56751— ipv6: release nexthop on device removal

Quick assessment

Affected
Linux Linux
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞，该漏洞源于ipv6模块中设备移除时nexthop的释放。

AI Predicted 4.3 Difficulty: Moderate EPSS 0.22% · P12

Possible ATT&CK Techniques 1 AI

T1499.002 · Service Exhaustion Flood

Affected Version Matrix 14

VendorProduct Version RangeStatus
Linux Linux f88d8ea67fbdbac7a64bfa6ed9a2ba27bb822f74< 77aa9855a878fb43f547ddfbda3127a1e88ad31a affected
f88d8ea67fbdbac7a64bfa6ed9a2ba27bb822f74< b2f26a27ea3f72f75d18330f76f5d1007c791848 affected
f88d8ea67fbdbac7a64bfa6ed9a2ba27bb822f74< 43e25adc80269f917d2a195f0d59f74cdd182955 affected
f88d8ea67fbdbac7a64bfa6ed9a2ba27bb822f74< a3c3f8a4d025acc8c857246ec2b812c59102487a affected
f88d8ea67fbdbac7a64bfa6ed9a2ba27bb822f74< 0e4c6faaef8a24b762a24ffb767280e263ef8e10 affected
f88d8ea67fbdbac7a64bfa6ed9a2ba27bb822f74< eb02688c5c45c3e7af7e71f036a7144f5639cbfe affected
5.3 affected
< 5.3 unaffected
… +6 more rows
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2024-56751

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
ipv6: release nexthop on device removal
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
N/A
Source: CVE Program / CVE List V5
Vulnerability Type
N/A
Source: CVE Program / CVE List V5
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞，该漏洞源于ipv6模块中设备移除时nexthop的释放。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
Linux Linux f88d8ea67fbdbac7a64bfa6ed9a2ba27bb822f74 ~ 77aa9855a878fb43f547ddfbda3127a1e88ad31a -
Linux Linux 5.3 -

II. Public POCs for CVE-2024-56751

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2024-56751

请登录查看更多情报信息。

Patches & Fixes for CVE-2024-56751 (5)

Other References for CVE-2024-56751 (1)

Same Patch Batch · Linux · 2024-12-29 · 39 CVEs total

CVE-2024-56719 10.0 CRITICAL net: stmmac: fix TSO DMA API usage causing oops
CVE-2024-56718 9.8 CRITICAL net/smc: protect link down work from execute after lgr freed
CVE-2024-56720 7.8 HIGH bpf, sockmap: Several fixes to bpf_msg_pop_data
CVE-2024-56740 7.8 HIGH nfs/localio: must clear res.replen in nfs_local_read_done
CVE-2024-56709 7.8 HIGH io_uring: check if iowq is killed before queuing
CVE-2024-56715 7.8 HIGH ionic: Fix netdev notifier unregister on failure
CVE-2024-56717 7.5 HIGH net: mscc: ocelot: fix incorrect IFH SRC_PORT field in ocelot_ifh_set_basic()
CVE-2024-56749 7.5 HIGH dlm: fix dlm_recover_members refcount on error
CVE-2024-56721 7.1 HIGH x86/CPU/AMD: Terminate the erratum_1386_microcode array
CVE-2024-56747 scsi: qedi: Fix a possible memory leak in qedi_alloc_and_init_sb()
CVE-2024-56756 nvme-pci: fix freeing of the HMB descriptor table
CVE-2024-56742 vfio/mlx5: Fix an unwind issue in mlx5vf_add_migration_pages()
CVE-2024-56743 nfs_common: must not hold RCU while calling nfsd_file_put_local
CVE-2024-56755 netfs/fscache: Add a memory barrier for FSCACHE_VOLUME_CREATING
CVE-2024-56745 PCI: Fix reset_method_store() memory leak
CVE-2024-56744 f2fs: fix to avoid potential deadlock in f2fs_record_stop_reason()
CVE-2024-56746 fbdev: sh7760fb: Fix a possible memory leak in sh7760fb_alloc_mem()
CVE-2024-56748 scsi: qedf: Fix a possible memory leak in qedf_alloc_and_init_sb()
CVE-2024-56727 octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_flows.c
CVE-2024-56754 crypto: caam - Fix the pointer passed to caam_qi_shutdown()

Showing top 20 of 39 CVEs. View all on vendor page &rarr; →

IV. Related Vulnerabilities

Same product: Linux
Same vendor: Linux

V. Comments for CVE-2024-56751

No comments yet

Leave a comment