CVE-2024-56703

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 5.5 from GitHub Security Advisory published 2024-12-28. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2024-53351 (ENISA EUVD) · GHSA-r654-x82p-f2p7 (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

ipv6: Fix soft lockups in fib6_select_path under high next hop churn

Soft lockups have been observed on a cluster of Linux-based edge routers located in a highly dynamic environment. Using the bird service, these routers continuously update BGP-advertised routes due to frequently changing nexthop destinations, while also managing significant IPv6 traffic. The lockups occur during the traversal of the multipath circular linked-list in the fib6_select_path function, particularly while iterating through the siblings in the list. The issue typically arises when the nodes of the linked list are unexpectedly deleted concurrently on a different core—indicated by their 'next' and 'previous' elements pointing back to the node itself and their reference count dropping to zero. This results in an infinite loop, leading to a soft lockup that triggers a system panic via the watchdog timer.

Apply RCU primitives in the problematic code sections to resolve the issue. Where necessary, update the references to fib6_siblings to annotate or use the RCU APIs.

Include a test script that reproduces the issue. The script periodically updates the routing table while generating a heavy load of outgoing IPv6 traffic through multiple iperf3 clients. It consistently induces infinite soft lockups within a couple of minutes.

Kernel log:

0 [ffffbd13003e8d30] machine_kexec at ffffffff8ceaf3eb 1 [ffffbd13003e8d90] __crash_kexec at ffffffff8d0120e3 2 [ffffbd13003e8e58] panic at ffffffff8cef65d4 3 [ffffbd13003e8ed8] watchdog_timer_fn at ffffffff8d05cb03 4 [ffffbd13003e8f08] __hrtimer_run_queues at ffffffff8cfec62f 5 [ffffbd13003e8f70] hrtimer_interrupt at ffffffff8cfed756 6 [ffffbd13003e8fd0] __sysvec_apic_timer_interrupt at ffffffff8cea01af 7 [ffffbd13003e8ff0] sysvec_apic_timer_interrupt at ffffffff8df1b83d -- -- 8 [ffffbd13003d3708] asm_sysvec_apic_timer_interrupt at ffffffff8e000ecb [exception RIP: fib6_select_path+299] RIP: ffffffff8ddafe7b RSP: ffffbd13003d37b8 RFLAGS: 00000287 RAX: ffff975850b43600 RBX: ffff975850b40200 RCX: 0000000000000000 RDX: 000000003fffffff RSI: 0000000051d383e4 RDI: ffff975850b43618 RBP: ffffbd13003d3800 R8: 0000000000000000 R9: ffff975850b40200 R10: 0000000000000000 R11: 0000000000000000 R12: ffffbd13003d3830 R13: ffff975850b436a8 R14: ffff975850b43600 R15: 0000000000000007 ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018 9 [ffffbd13003d3808] ip6_pol_route at ffffffff8ddb030c 10 [ffffbd13003d3888] ip6_pol_route_input at ffffffff8ddb068c 11 [ffffbd13003d3898] fib6_rule_lookup at ffffffff8ddf02b5 12 [ffffbd13003d3928] ip6_route_input at ffffffff8ddb0f47 13 [ffffbd13003d3a18] ip6_rcv_finish_core.constprop.0 at ffffffff8dd950d0 14 [ffffbd13003d3a30] ip6_list_rcv_finish.constprop.0 at ffffffff8dd96274 15 [ffffbd13003d3a98] ip6_sublist_rcv at ffffffff8dd96474 16 [ffffbd13003d3af8] ipv6_list_rcv at ffffffff8dd96615 17 [ffffbd13003d3b60] __netif_receive_skb_list_core at ffffffff8dc16fec 18 [ffffbd13003d3be0] netif_receive_skb_list_internal at ffffffff8dc176b3 19 [ffffbd13003d3c50] napi_gro_receive at ffffffff8dc565b9 20 [ffffbd13003d3c80] ice_receive_skb at ffffffffc087e4f5 [ice] 21 [ffffbd13003d3c90] ice_clean_rx_irq at ffffffffc0881b80 [ice] 22 [ffffbd13003d3d20] ice_napi_poll at ffffffffc088232f [ice] 23 [ffffbd13003d3d80] __napi_poll at ffffffff8dc18000 24 [ffffbd13003d3db8] net_rx_action at ffffffff8dc18581 25 [ffffbd13003d3e40] __do_softirq at ffffffff8df352e9 26 [ffffbd13003d3eb0] run_ksoftirqd at ffffffff8ceffe47 27 [ffffbd13003d3ec0] smpboot_thread_fn at ffffffff8cf36a30 28 [ffffbd13003d3ee8] kthread at ffffffff8cf2b39f 29 [ffffbd13003d3f28] ret_from_fork at ffffffff8ce5fa64 30 [ffffbd13003d3f50] ret_from_fork_asm at ffffffff8ce03cbb

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
42nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

December 28, 2024

Last Modified

October 15, 2026

Advisory Details (7)

Auto-updated Jul 17, 2026
Patch available.
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4076-1] linux-6.1 security update

https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html
Web page

ipv6: Fix soft lockups in fib6_select_path under high next hop churn - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d9ccb18f83ea2bb654289b6ecf014fd267cc988b
Web page

ipv6: Fix soft lockups in fib6_select_path under high next hop churn - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d0ec61c9f3583b76aebdbb271f5c0d3fcccd48b2
Web page

ipv6: Fix soft lockups in fib6_select_path under high next hop churn - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/52da02521ede55fb86546c3fffd9377b3261b91f
Web page

ipv6: Fix soft lockups in fib6_select_path under high next hop churn - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/34a949e7a0869dfa31a40416d2a56973fae1807b
Web page

ipv6: Fix soft lockups in fib6_select_path under high next hop churn - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/11edcd026012ac18acee0f1514db3ed1b160fc6f

Vendor Advisories for CVE-2024-56703(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(13)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (498 versions)
  • every version on: no fix on record
—
linux-6.16.1.106-3~deb11u1, 6.1.106-3~deb11u2, 6.1.106-3~deb11u3, 6.1.112-1~deb11u1, 6.1.119-1~deb11u1
  • every version up to 6.1.128-1~deb11u1: fixed in 6.1.128-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (34 versions)
  • every version up to 6.1.128-1: fixed in 6.1.128-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.3-1: fixed in 6.12.3-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.3-1: fixed in 6.12.3-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(12)

Data Freshness Timeline

(refreshed 8× in last 7d / 39× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 95 of 218 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 123 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:41 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  2. 2026-11-01 16:32 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  3. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  4. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  5. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  6. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  7. 2026-10-27 17:25 UTCOSV refresh
  8. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  9. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  10. 2026-10-25 16:54 UTCEG score recompute
  11. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  12. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  13. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  14. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  15. 2026-10-21 16:30 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  16. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  17. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  18. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  19. 2026-10-18 05:58 UTCEG score recompute
  20. 2026-10-17 16:31 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  21. 2026-10-16 16:37 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  22. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  23. 2026-10-15 02:55 UTCGHSA enrichmentGHSA-r654-x82p-f2p7 · GitHub CVSS 5.5
  24. 2026-10-15 02:04 UTCEG score recompute
  25. 2026-10-15 02:04 UTCGHSA enrichmentGHSA-r654-x82p-f2p7 · GitHub CVSS 5.5
Show 70 more
  1. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  2. 2026-10-13 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  3. 2026-10-12 17:37 UTCEG score recompute
  4. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  5. 2026-10-11 21:03 UTCEG score recompute
  6. 2026-10-11 15:54 UTCEG score recompute
  7. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  8. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  9. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  10. 2026-10-08 17:08 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  11. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  12. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  13. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  14. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  15. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  16. 2026-10-02 16:25 UTCEG score recompute
  17. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  18. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  19. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  20. 2026-09-28 02:02 UTCOSV refresh
  21. 2026-09-27 13:44 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  22. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  23. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  24. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  25. 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  26. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  27. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  28. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  29. 2026-09-16 05:12 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  30. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  31. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  32. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  33. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  34. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  35. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  36. 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  37. 2026-09-08 09:55 UTCEG score recompute
  38. 2026-09-08 09:55 UTCVendor advisory
  39. 2026-09-08 09:55 UTCGHSA enrichmentGHSA-r654-x82p-f2p7 · GitHub CVSS 5.5
  40. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  41. 2026-09-07 13:18 UTCOSV refresh
  42. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  43. 2026-09-04 13:59 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  44. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  45. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  46. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  47. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  48. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  49. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  50. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  51. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  52. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  53. 2026-08-24 14:15 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  54. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  55. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  56. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  57. 2026-08-20 22:31 UTCOSV refresh
  58. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  59. 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  60. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  61. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  62. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  63. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  64. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  65. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  66. 2026-08-11 13:41 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  67. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  68. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  69. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  70. 2026-08-07 16:26 UTCEPSS rescoreEPSS 0.5% · 39th percentile

Frequently asked(5)

What is CVE-2024-56703?
CVE-2024-56703 is a medium-severity vulnerability; its CVE record was published on December 28, 2024. In the Linux kernel, the following vulnerability has been resolved: ipv6: Fix soft lockups in fib6_select_path under high next hop churn Soft lockups have been observed on a cluster of Linux-based edge routers located in a highly dynamic environment. Using the bird service, these routers…
When was the CVE record for CVE-2024-56703 published?
The CVE record for CVE-2024-56703 was published on December 28, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 15, 2026; the record at its source may have been updated since.
Is CVE-2024-56703 actively exploited?
CVE-2024-56703 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-56703?
CVE-2024-56703 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-56703?
A fix for CVE-2024-56703 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-56703 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-56703

Explore →

Is Your Infrastructure Affected by CVE-2024-56703?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.