CVE-2023-52845

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
Trending — 3 sources updated this week
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:

tipc: Change nla_policy for bearer-related names to NLA_NUL_STRING

syzbot reported the following uninit-value access issue [1]:

===================================================== BUG: KMSAN: uninit-value in strlen lib/string.c:418 [inline] BUG: KMSAN: uninit-value in strstr+0xb8/0x2f0 lib/string.c:756 strlen lib/string.c:418 [inline] strstr+0xb8/0x2f0 lib/string.c:756 tipc_nl_node_reset_link_stats+0x3ea/0xb50 net/tipc/node.c:2595 genl_family_rcv_msg_doit net/netlink/genetlink.c:971 [inline] genl_family_rcv_msg net/netlink/genetlink.c:1051 [inline] genl_rcv_msg+0x11ec/0x1290 net/netlink/genetlink.c:1066 netlink_rcv_skb+0x371/0x650 net/netlink/af_netlink.c:2545 genl_rcv+0x40/0x60 net/netlink/genetlink.c:1075 netlink_unicast_kernel net/netlink/af_netlink.c:1342 [inline] netlink_unicast+0xf47/0x1250 net/netlink/af_netlink.c:1368 netlink_sendmsg+0x1238/0x13d0 net/netlink/af_netlink.c:1910 sock_sendmsg_nosec net/socket.c:730 [inline] sock_sendmsg net/socket.c:753 [inline] ____sys_sendmsg+0x9c2/0xd60 net/socket.c:2541 ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2595 __sys_sendmsg net/socket.c:2624 [inline] __do_sys_sendmsg net/socket.c:2633 [inline] __se_sys_sendmsg net/socket.c:2631 [inline] __x64_sys_sendmsg+0x307/0x490 net/socket.c:2631 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd

Uninit was created at: slab_post_alloc_hook+0x12f/0xb70 mm/slab.h:767 slab_alloc_node mm/slub.c:3478 [inline] kmem_cache_alloc_node+0x577/0xa80 mm/slub.c:3523 kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:559 __alloc_skb+0x318/0x740 net/core/skbuff.c:650 alloc_skb include/linux/skbuff.h:1286 [inline] netlink_alloc_large_skb net/netlink/af_netlink.c:1214 [inline] netlink_sendmsg+0xb34/0x13d0 net/netlink/af_netlink.c:1885 sock_sendmsg_nosec net/socket.c:730 [inline] sock_sendmsg net/socket.c:753 [inline] ____sys_sendmsg+0x9c2/0xd60 net/socket.c:2541 ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2595 __sys_sendmsg net/socket.c:2624 [inline] __do_sys_sendmsg net/socket.c:2633 [inline] __se_sys_sendmsg net/socket.c:2631 [inline] __x64_sys_sendmsg+0x307/0x490 net/socket.c:2631 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd

TIPC bearer-related names including link names must be null-terminated strings. If a link name which is not null-terminated is passed through netlink, strstr() and similar functions can cause buffer overrun. This causes the above issue.

This patch changes the nla_policy for bearer-related names from NLA_STRING to NLA_NUL_STRING. This resolves the issue by ensuring that only null-terminated strings are accepted as bearer-related names.

syzbot reported similar uninit-value issue related to bearer names [2]. The root cause of this issue is that a non-null-terminated bearer name was passed. This patch also resolved this issue.

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-17). 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: 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.

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 (9)

Vendor Advisories for CVE-2023-52845(2)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
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
linuxKernel @ 4.14.330 (fixes >=3.19.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

(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
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 33× 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 195 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 102 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2023-52845?
CVE-2023-52845 is a medium-severity vulnerability; its CVE record was published on May 21, 2024. In the Linux kernel, the following vulnerability has been resolved: tipc: Change nlapolicy for bearer-related names to NLANUL_STRING syzbot reported the following uninit-value access issue [1]: ===================================================== BUG: KMSAN: uninit-value in strlen lib/string.c:418…
When was the CVE record for CVE-2023-52845 published?
The CVE record for CVE-2023-52845 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-52845 actively exploited?
CVE-2023-52845 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-52845?
CVE-2023-52845 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2023-52845?
A fix for CVE-2023-52845 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-52845 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-52845

Explore →

Is Your Infrastructure Affected by CVE-2023-52845?

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

Book a Demo →Browse All CVEs