CVE-2023-52745

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-59464 (ENISA EUVD) · GHSA-p4g6-hq7c-h438 (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.3%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

IB/IPoIB: Fix legacy IPoIB due to wrong number of queues

The cited commit creates child PKEY interfaces over netlink will multiple tx and rx queues, but some devices doesn't support more than 1 tx and 1 rx queues. This causes to a crash when traffic is sent over the PKEY interface due to the parent having a single queue but the child having multiple queues.

This patch fixes the number of queues to 1 for legacy IPoIB at the earliest possible point in time.

BUG: kernel NULL pointer dereference, address: 000000000000036b PGD 0 P4D 0 Oops: 0000 [#1] SMP CPU: 4 PID: 209665 Comm: python3 Not tainted 6.1.0_for_upstream_min_debug_2022_12_12_17_02 #1 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:kmem_cache_alloc+0xcb/0x450 Code: ce 7e 49 8b 50 08 49 83 78 10 00 4d 8b 28 0f 84 cb 02 00 00 4d 85 ed 0f 84 c2 02 00 00 41 8b 44 24 28 48 8d 4a 01 49 8b 3c 24 <49> 8b 5c 05 00 4c 89 e8 65 48 0f c7 0f 0f 94 c0 84 c0 74 b8 41 8b RSP: 0018:ffff88822acbbab8 EFLAGS: 00010202 RAX: 0000000000000070 RBX: ffff8881c28e3e00 RCX: 00000000064f8dae RDX: 00000000064f8dad RSI: 0000000000000a20 RDI: 0000000000030d00 RBP: 0000000000000a20 R08: ffff8882f5d30d00 R09: ffff888104032f40 R10: ffff88810fade828 R11: 736f6d6570736575 R12: ffff88810081c000 R13: 00000000000002fb R14: ffffffff817fc865 R15: 0000000000000000 FS: 00007f9324ff9700(0000) GS:ffff8882f5d00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000000000000036b CR3: 00000001125af004 CR4: 0000000000370ea0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: skb_clone+0x55/0xd0 ip6_finish_output2+0x3fe/0x690 ip6_finish_output+0xfa/0x310 ip6_send_skb+0x1e/0x60 udp_v6_send_skb+0x1e5/0x420 udpv6_sendmsg+0xb3c/0xe60 ? ip_mc_finish_output+0x180/0x180 ? __switch_to_asm+0x3a/0x60 ? __switch_to_asm+0x34/0x60 sock_sendmsg+0x33/0x40 __sys_sendto+0x103/0x160 ? _copy_to_user+0x21/0x30 ? kvm_clock_get_cycles+0xd/0x10 ? ktime_get_ts64+0x49/0xe0 __x64_sys_sendto+0x25/0x30 do_syscall_64+0x3d/0x90 entry_SYSCALL_64_after_hwframe+0x46/0xb0 RIP: 0033:0x7f9374f1ed14 Code: 42 41 f8 ff 44 8b 4c 24 2c 4c 8b 44 24 20 89 c5 44 8b 54 24 28 48 8b 54 24 18 b8 2c 00 00 00 48 8b 74 24 10 8b 7c 24 08 0f 05 <48> 3d 00 f0 ff ff 77 34 89 ef 48 89 44 24 08 e8 68 41 f8 ff 48 8b RSP: 002b:00007f9324ff7bd0 EFLAGS: 00000293 ORIG_RAX: 000000000000002c RAX: ffffffffffffffda RBX: 00007f9324ff7cc8 RCX: 00007f9374f1ed14 RDX: 00000000000002fb RSI: 00007f93000052f0 RDI: 0000000000000030 RBP: 0000000000000000 R08: 00007f9324ff7d40 R09: 000000000000001c R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000000 R13: 000000012a05f200 R14: 0000000000000001 R15: 00007f9374d57bdc

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.3% × 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.3%
EPSS %ILE
18th
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.3% 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

August 5, 2026

References (5)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 5.4.232 (fixes >=5.4.229)—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 (25 versions)
  • every version up to 5.10.178-1: fixed in 5.10.178-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.12-1: fixed in 6.1.12-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.12-1: fixed in 6.1.12-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.12-1: fixed in 6.1.12-1
—

Weakness Classification(1)

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

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 93 of 207 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. 7 repeat rows among the latest 100 are merged into the row they repeat. The 114 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2023-52745?
CVE-2023-52745 is a medium-severity vulnerability; its CVE record was published on May 21, 2024. In the Linux kernel, the following vulnerability has been resolved: IB/IPoIB: Fix legacy IPoIB due to wrong number of queues The cited commit creates child PKEY interfaces over netlink will multiple tx and rx queues, but some devices doesn't support more than 1 tx and 1 rx queues. This causes to a…
When was the CVE record for CVE-2023-52745 published?
The CVE record for CVE-2023-52745 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 August 5, 2026; the record at its source may have been updated since.
Is CVE-2023-52745 actively exploited?
CVE-2023-52745 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (18th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-52745?
CVE-2023-52745 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2023-52745?
A fix for CVE-2023-52745 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-52745

Explore →

Is Your Infrastructure Affected by CVE-2023-52745?

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

Book a Demo →Browse All CVEs