CVE-2023-53601

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 (severity: MODERATE) published 2025-10-04. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2025-32275 (ENISA EUVD) · GHSA-cqg2-m42r-rqrx (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.1%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

bonding: do not assume skb mac_header is set

Drivers must not assume in their ndo_start_xmit() that skbs have their mac_header set. skb->data is all what is needed.

bonding seems to be one of the last offender as caught by syzbot:

WARNING: CPU: 1 PID: 12155 at include/linux/skbuff.h:2907 skb_mac_offset include/linux/skbuff.h:2913 [inline] WARNING: CPU: 1 PID: 12155 at include/linux/skbuff.h:2907 bond_xmit_hash drivers/net/bonding/bond_main.c:4170 [inline] WARNING: CPU: 1 PID: 12155 at include/linux/skbuff.h:2907 bond_xmit_3ad_xor_slave_get drivers/net/bonding/bond_main.c:5149 [inline] WARNING: CPU: 1 PID: 12155 at include/linux/skbuff.h:2907 bond_3ad_xor_xmit drivers/net/bonding/bond_main.c:5186 [inline] WARNING: CPU: 1 PID: 12155 at include/linux/skbuff.h:2907 __bond_start_xmit drivers/net/bonding/bond_main.c:5442 [inline] WARNING: CPU: 1 PID: 12155 at include/linux/skbuff.h:2907 bond_start_xmit+0x14ab/0x19d0 drivers/net/bonding/bond_main.c:5470 Modules linked in: CPU: 1 PID: 12155 Comm: syz-executor.3 Not tainted 6.1.30-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023 RIP: 0010:skb_mac_header include/linux/skbuff.h:2907 [inline] RIP: 0010:skb_mac_offset include/linux/skbuff.h:2913 [inline] RIP: 0010:bond_xmit_hash drivers/net/bonding/bond_main.c:4170 [inline] RIP: 0010:bond_xmit_3ad_xor_slave_get drivers/net/bonding/bond_main.c:5149 [inline] RIP: 0010:bond_3ad_xor_xmit drivers/net/bonding/bond_main.c:5186 [inline] RIP: 0010:__bond_start_xmit drivers/net/bonding/bond_main.c:5442 [inline] RIP: 0010:bond_start_xmit+0x14ab/0x19d0 drivers/net/bonding/bond_main.c:5470 Code: 8b 7c 24 30 e8 76 dd 1a 01 48 85 c0 74 0d 48 89 c3 e8 29 67 2e fe e9 15 ef ff ff e8 1f 67 2e fe e9 10 ef ff ff e8 15 67 2e fe <0f> 0b e9 45 f8 ff ff e8 09 67 2e fe e9 dc fa ff ff e8 ff 66 2e fe RSP: 0018:ffffc90002fff6e0 EFLAGS: 00010283 RAX: ffffffff835874db RBX: 000000000000ffff RCX: 0000000000040000 RDX: ffffc90004dcf000 RSI: 00000000000000b5 RDI: 00000000000000b6 RBP: ffffc90002fff8b8 R08: ffffffff83586d16 R09: ffffffff83586584 R10: 0000000000000007 R11: ffff8881599fc780 R12: ffff88811b6a7b7e R13: 1ffff110236d4f6f R14: ffff88811b6a7ac0 R15: 1ffff110236d4f76 FS: 00007f2e9eb47700(0000) GS:ffff8881f6b00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000001b2e421000 CR3: 000000010e6d4000 CR4: 00000000003526e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace:

[] netdev_start_xmit include/linux/netdevice.h:4925 [inline] [] __dev_direct_xmit+0x4ef/0x850 net/core/dev.c:4380 [] dev_direct_xmit include/linux/netdevice.h:3043 [inline] [] packet_direct_xmit+0x18b/0x300 net/packet/af_packet.c:284 [] packet_snd net/packet/af_packet.c:3112 [inline] [] packet_sendmsg+0x4a22/0x64d0 net/packet/af_packet.c:3143 [] sock_sendmsg_nosec net/socket.c:716 [inline] [] sock_sendmsg net/socket.c:736 [inline] [] __sys_sendto+0x472/0x5f0 net/socket.c:2139 [] __do_sys_sendto net/socket.c:2151 [inline] [] __se_sys_sendto net/socket.c:2147 [inline] [] __x64_sys_sendto+0xe5/0x100 net/socket.c:2147 [] do_syscall_x64 arch/x86/entry/common.c:50 [inline] [] do_syscall_64+0x2f/0x50 arch/x86/entry/common.c:80 [] entry_SYSCALL_64_after_hwframe+0x63/0xcd

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.1% × 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.1%
EPSS %ILE
4th
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.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-05). 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

October 4, 2025

Last Modified

November 5, 2026

References (5)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 5.15.121 (fixes >=5.12.0)—osv

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.38-4~bpo11+1 (8 versions)
  • every version up to 6.1.52-1: fixed in 6.1.52-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.4.4-1: fixed in 6.4.4-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.4.4-1: fixed in 6.4.4-1
—

Data Freshness Timeline

(refreshed 9× in last 7d / 38× 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 94 of 194 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. 6 repeat rows among the latest 100 are merged into the row they repeat. The 100 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2023-53601?
CVE-2023-53601 is a medium-severity vulnerability; its CVE record was published on October 4, 2025. In the Linux kernel, the following vulnerability has been resolved: bonding: do not assume skb mac_header is set Drivers must not assume in their ndo_start_xmit() that skbs have their mac_header set. skb->data is all what is needed. bonding seems to be one of the last offender as caught by syzbot:…
When was the CVE record for CVE-2023-53601 published?
The CVE record for CVE-2023-53601 was published on October 4, 2025. 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 November 5, 2026; the record at its source may have been updated since.
Is CVE-2023-53601 actively exploited?
CVE-2023-53601 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-53601?
CVE-2023-53601 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2023-53601?
A fix for CVE-2023-53601 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-53601

Explore →

Is Your Infrastructure Affected by CVE-2023-53601?

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

Book a Demo →Browse All CVEs