CVE-2024-56717

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

net: mscc: ocelot: fix incorrect IFH SRC_PORT field in ocelot_ifh_set_basic()

Packets injected by the CPU should have a SRC_PORT field equal to the CPU port module index in the Analyzer block (ocelot->num_phys_ports).

The blamed commit copied the ocelot_ifh_set_basic() call incorrectly from ocelot_xmit_common() in net/dsa/tag_ocelot.c. Instead of calling with "x", it calls with BIT_ULL(x), but the field is not a port mask, but rather a single port index.

[ side note: this is the technical debt of code duplication :( ]

The error used to be silent and doesn't appear to have other user-visible manifestations, but with new changes in the packing library, it now fails loudly as follows:

------------[ cut here ]------------ Cannot store 0x40 inside bits 46-43 - will truncate sja1105 spi2.0: xmit timed out WARNING: CPU: 1 PID: 102 at lib/packing.c:98 __pack+0x90/0x198 sja1105 spi2.0: timed out polling for tstamp CPU: 1 UID: 0 PID: 102 Comm: felix_xmit Tainted: G W N 6.13.0-rc1-00372-gf706b85d972d-dirty #2605 Call trace: __pack+0x90/0x198 (P) __pack+0x90/0x198 (L) packing+0x78/0x98 ocelot_ifh_set_basic+0x260/0x368 ocelot_port_inject_frame+0xa8/0x250 felix_port_deferred_xmit+0x14c/0x258 kthread_worker_fn+0x134/0x350 kthread+0x114/0x138

The code path pertains to the ocelot switchdev driver and to the felix secondary DSA tag protocol, ocelot-8021q. Here seen with ocelot-8021q.

The messenger (packing) is not really to blame, so fix the original commit instead.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
25(Track)
EG Risk 25/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
37%
KEV
Not listed

Published

December 29, 2024

Last Modified

August 5, 2026

Advisory Details (4)

Auto-updated Aug 5, 2026
No patch confirmed yet.
generic

net: mscc: ocelot: fix incorrect IFH SRC_PORT field in ocelot_ifh_set_basic() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2d5df3a680ffdaf606baa10636bdb1daf757832e
generic

net: mscc: ocelot: fix incorrect IFH SRC_PORT field in ocelot_ifh_set_basic() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a8836eae3288c351acd3b2743d2fad2a4ee2bd56
generic

net: mscc: ocelot: fix incorrect IFH SRC_PORT field in ocelot_ifh_set_basic() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2f3c62ffe88116cd2a39cd73e01103535599970f
generic

net: mscc: ocelot: fix incorrect IFH SRC_PORT field in ocelot_ifh_set_basic() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/59c4ca8d8d7918eb6e2df91d2c254827264be309

Patch Availability(17)

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.

All Vendor Advisories

(17)

Data Freshness Timeline

(refreshed 14× in last 7d / 46× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 128 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2024-56717?
CVE-2024-56717 is a medium vulnerability published on December 29, 2024. In the Linux kernel, the following vulnerability has been resolved: net: mscc: ocelot: fix incorrect IFH SRCPORT field in ocelotifhsetbasic() Packets injected by the CPU should have a SRC_PORT field equal to the CPU port module index in the Analyzer block (ocelot->numphysports). The blamed commit…
When was CVE-2024-56717 disclosed?
CVE-2024-56717 was first published in the National Vulnerability Database on December 29, 2024, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-56717 actively exploited?
CVE-2024-56717 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 63.3% of all scored CVEs.
What is the CVSS score of CVE-2024-56717?
CVE-2024-56717 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-56717?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-56717, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2024-56717

Explore →

Is Your Infrastructure Affected by CVE-2024-56717?

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