CVE-2023-52784

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-05-21. 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-2023-59501 (ENISA EUVD) · GHSA-r5hp-gwxj-3824 (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.2%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: stop the device in bond_setup_by_slave()

Commit 9eed321cde22 ("net: lapbether: only support ethernet devices") has been able to keep syzbot away from net/lapb, until today.

In the following splat [1], the issue is that a lapbether device has been created on a bonding device without members. Then adding a non ARPHRD_ETHER member forced the bonding master to change its type.

The fix is to make sure we call dev_close() in bond_setup_by_slave() so that the potential linked lapbether devices (or any other devices having assumptions on the physical device) are removed.

A similar bug has been addressed in commit 40baec225765 ("bonding: fix panic on non-ARPHRD_ETHER enslave failure")

[1] skbuff: skb_under_panic: text:ffff800089508810 len:44 put:40 head:ffff0000c78e7c00 data:ffff0000c78e7bea tail:0x16 end:0x140 dev:bond0 kernel BUG at net/core/skbuff.c:192 ! Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP Modules linked in: CPU: 0 PID: 6007 Comm: syz-executor383 Not tainted 6.6.0-rc3-syzkaller-gbf6547d8715b #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/04/2023 pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : skb_panic net/core/skbuff.c:188 [inline] pc : skb_under_panic+0x13c/0x140 net/core/skbuff.c:202 lr : skb_panic net/core/skbuff.c:188 [inline] lr : skb_under_panic+0x13c/0x140 net/core/skbuff.c:202 sp : ffff800096a06aa0 x29: ffff800096a06ab0 x28: ffff800096a06ba0 x27: dfff800000000000 x26: ffff0000ce9b9b50 x25: 0000000000000016 x24: ffff0000c78e7bea x23: ffff0000c78e7c00 x22: 000000000000002c x21: 0000000000000140 x20: 0000000000000028 x19: ffff800089508810 x18: ffff800096a06100 x17: 0000000000000000 x16: ffff80008a629a3c x15: 0000000000000001 x14: 1fffe00036837a32 x13: 0000000000000000 x12: 0000000000000000 x11: 0000000000000201 x10: 0000000000000000 x9 : cb50b496c519aa00 x8 : cb50b496c519aa00 x7 : 0000000000000001 x6 : 0000000000000001 x5 : ffff800096a063b8 x4 : ffff80008e280f80 x3 : ffff8000805ad11c x2 : 0000000000000001 x1 : 0000000100000201 x0 : 0000000000000086 Call trace: skb_panic net/core/skbuff.c:188 [inline] skb_under_panic+0x13c/0x140 net/core/skbuff.c:202 skb_push+0xf0/0x108 net/core/skbuff.c:2446 ip6gre_header+0xbc/0x738 net/ipv6/ip6_gre.c:1384 dev_hard_header include/linux/netdevice.h:3136 [inline] lapbeth_data_transmit+0x1c4/0x298 drivers/net/wan/lapbether.c:257 lapb_data_transmit+0x8c/0xb0 net/lapb/lapb_iface.c:447 lapb_transmit_buffer+0x178/0x204 net/lapb/lapb_out.c:149 lapb_send_control+0x220/0x320 net/lapb/lapb_subr.c:251 __lapb_disconnect_request+0x9c/0x17c net/lapb/lapb_iface.c:326 lapb_device_event+0x288/0x4e0 net/lapb/lapb_iface.c:492 notifier_call_chain+0x1a4/0x510 kernel/notifier.c:93 raw_notifier_call_chain+0x3c/0x50 kernel/notifier.c:461 call_netdevice_notifiers_info net/core/dev.c:1970 [inline] call_netdevice_notifiers_extack net/core/dev.c:2008 [inline] call_netdevice_notifiers net/core/dev.c:2022 [inline] __dev_close_many+0x1b8/0x3c4 net/core/dev.c:1508 dev_close_many+0x1e0/0x470 net/core/dev.c:1559 dev_close+0x174/0x250 net/core/dev.c:1585 lapbeth_device_event+0x2e4/0x958 drivers/net/wan/lapbether.c:466 notifier_call_chain+0x1a4/0x510 kernel/notifier.c:93 raw_notifier_call_chain+0x3c/0x50 kernel/notifier.c:461 call_netdevice_notifiers_info net/core/dev.c:1970 [inline] call_netdevice_notifiers_extack net/core/dev.c:2008 [inline] call_netdevice_notifiers net/core/dev.c:2022 [inline] __dev_close_many+0x1b8/0x3c4 net/core/dev.c:1508 dev_close_many+0x1e0/0x470 net/core/dev.c:1559 dev_close+0x174/0x250 net/core/dev.c:1585 bond_enslave+0x2298/0x30cc drivers/net/bonding/bond_main.c:2332 bond_do_ioctl+0x268/0xc64 drivers/net/bonding/bond_main.c:4539 dev_ifsioc+0x754/0x9ac dev_ioctl+0x4d8/0xd34 net/core/dev_ioctl.c:786 sock_do_ioctl+0x1d4/0x2d0 net/socket.c:1217 sock_ioctl+0x4e8/0x834 net/socket.c:1322 vfs_ioctl fs/ioctl.c:51 [inline] __do_ ---truncated---

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.2% × 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.2%
EPSS %ILE
15th
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.2% 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

May 21, 2024

Last Modified

September 25, 2025

Patch Availability(7)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:5.14.0-427.65.1.el9_42025-04-16redhat
redhatkernel-0:5.14.0-503.11.1.el9_52024-11-12redhat
redhatkernel-0:4.18.0-477.74.1.el8_82024-09-24redhat
redhatkernel-rt-0:4.18.0-553.16.1.rt7.357.el8_102024-08-08redhat
redhatkernel-0:4.18.0-553.16.1.el8_102024-08-08redhat
redhatkernel-0:4.18.0-372.113.1.el8_62024-07-29redhat
linuxKernel @ 5.4.262 (fixes >=2.6.24)—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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (35 versions)
  • every version up to 5.10.205-1: fixed in 5.10.205-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.55-1~bpo11+1 (11 versions)
  • every version up to 6.1.64-1: fixed in 6.1.64-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.6.8-1: fixed in 6.6.8-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.6.8-1: fixed in 6.6.8-1
—

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2023-52784?
CVE-2023-52784 is a medium-severity vulnerability; its CVE record was published on May 21, 2024. In the Linux kernel, the following vulnerability has been resolved: bonding: stop the device in bond_setup_by_slave() Commit 9eed321cde22 ("net: lapbether: only support ethernet devices") has been able to keep syzbot away from net/lapb, until today. In the following splat [1], the issue is that a…
When was the CVE record for CVE-2023-52784 published?
The CVE record for CVE-2023-52784 was published on May 21, 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 September 25, 2025; the record at its source may have been updated since.
Is CVE-2023-52784 actively exploited?
CVE-2023-52784 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (15th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-52784?
CVE-2023-52784 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2023-52784?
A fix for CVE-2023-52784 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-52784 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-2023-52784

Explore →

Is Your Infrastructure Affected by CVE-2023-52784?

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