CVE-2023-53585

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2025-10-04. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 0

A fix is available — apply it.

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

bpf: reject unhashed sockets in bpf_sk_assign

The semantics for bpf_sk_assign are as follows:

sk = some_lookup_func() bpf_sk_assign(skb, sk) bpf_sk_release(sk)

That is, the sk is not consumed by bpf_sk_assign. The function therefore needs to make sure that sk lives long enough to be consumed from __inet_lookup_skb. The path through the stack for a TCPv4 packet is roughly:

netif_receive_skb_core: takes RCU read lock __netif_receive_skb_core: sch_handle_ingress: tcf_classify: bpf_sk_assign() deliver_ptype_list_skb: deliver_skb: ip_packet_type->func == ip_rcv: ip_rcv_core: ip_rcv_finish_core: dst_input: ip_local_deliver: ip_local_deliver_finish: ip_protocol_deliver_rcu: tcp_v4_rcv: __inet_lookup_skb: skb_steal_sock

The existing helper takes advantage of the fact that everything happens in the same RCU critical section: for sockets with SOCK_RCU_FREE set bpf_sk_assign never takes a reference. skb_steal_sock then checks SOCK_RCU_FREE again and does sock_put if necessary.

This approach assumes that SOCK_RCU_FREE is never set on a sk between bpf_sk_assign and skb_steal_sock, but this invariant is violated by unhashed UDP sockets. A new UDP socket is created in TCP_CLOSE state but without SOCK_RCU_FREE set. That flag is only added in udp_lib_get_port() which happens when a socket is bound.

When bpf_sk_assign was added it wasn't possible to access unhashed UDP sockets from BPF, so this wasn't a problem. This changed in commit 0c48eefae712 ("sock_map: Lift socket state restriction for datagram sockets"), but the helper wasn't adjusted accordingly. The following sequence of events will therefore lead to a refcount leak:

  • Add socket(AF_INET, SOCK_DGRAM) to a sockmap.
  • Pull socket out of sockmap and bpf_sk_assign it. Since
SOCK_RCU_FREE is not set we increment the refcount.
  • bind() or connect() the socket, setting SOCK_RCU_FREE.
  • skb_steal_sock will now set refcounted = false due to
SOCK_RCU_FREE.
  • tcp_v4_rcv() skips sock_put().

Fix the problem by rejecting unhashed sockets in bpf_sk_assign(). This matches the behaviour of __inet_lookup_skb which is ultimately the goal of bpf_sk_assign().

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
EPSS
4.4%
KEV
Not listed

Published

October 4, 2025

Last Modified

March 23, 2026

Vendor Advisories for CVE-2023-53585(2)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:5.14.0-427.13.1.el9_42024-04-30redhat
redhatkernel-0:4.18.0-240.el82020-11-04redhat

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.

Data Freshness Timeline

(refreshed 12× in last 7d / 40× 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.

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

Frequently asked(5)

What is CVE-2023-53585?
CVE-2023-53585 is a medium vulnerability published on October 4, 2025. In the Linux kernel, the following vulnerability has been resolved: bpf: reject unhashed sockets in bpfskassign The semantics for bpfskassign are as follows: sk = somelookupfunc() bpfskassign(skb, sk) bpfskrelease(sk) That is, the sk is not consumed by bpfskassign. The function therefore needs to…
When was CVE-2023-53585 disclosed?
CVE-2023-53585 was first published in the National Vulnerability Database on October 4, 2025, with the most recent update on March 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-53585 actively exploited?
CVE-2023-53585 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2023-53585?
CVE-2023-53585 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2023-53585?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-53585, 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-2023-53585

Explore →

Is Your Infrastructure Affected by CVE-2023-53585?

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