CVE-2026-53034

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 2026-06-24. 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 — 4 sources updated this week

Also known asEUVD-2026-38902 (ENISA EUVD) · GHSA-pwx6-fvf4-6686 (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:

bpf, sockmap: Fix af_unix null-ptr-deref in proto update

unix_stream_connect() sets sk_state (WRITE_ONCE(sk->sk_state, TCP_ESTABLISHED)) _before_ it assigns a peer (unix_peer(sk) = newsk). sk_state == TCP_ESTABLISHED makes sock_map_sk_state_allowed() believe that socket is properly set up, which would include having a defined peer. IOW, there's a window when unix_stream_bpf_update_proto() can be called on socket which still has unix_peer(sk) == NULL.

CPU0 bpf CPU1 connect -------- ------------

WRITE_ONCE(sk->sk_state, TCP_ESTABLISHED) sock_map_sk_state_allowed(sk) ... sk_pair = unix_peer(sk) sock_hold(sk_pair) sock_hold(newsk) smp_mb__after_atomic() unix_peer(sk) = newsk

BUG: kernel NULL pointer dereference, address: 0000000000000080 RIP: 0010:unix_stream_bpf_update_proto+0xa0/0x1b0 Call Trace: sock_map_link+0x564/0x8b0 sock_map_update_common+0x6e/0x340 sock_map_update_elem_sys+0x17d/0x240 __sys_bpf+0x26db/0x3250 __x64_sys_bpf+0x21/0x30 do_syscall_64+0x6b/0x3a0 entry_SYSCALL_64_after_hwframe+0x76/0x7e

Initial idea was to move peer assignment _before_ the sk_state update[1], but that involved an additional memory barrier, and changing the hot path was rejected. Then a NULL check during proto update in unix_stream_bpf_update_proto() was considered[2], but the follow-up discussion[3] focused on the root cause, i.e. sockmap update taking a wrong lock. Or, more specifically, missing unix_state_lock()[4]. In the end it was concluded that teaching sockmap about the af_unix locking would be unnecessarily complex[5]. Complexity aside, since BPF_PROG_TYPE_SCHED_CLS and BPF_PROG_TYPE_SCHED_ACT are allowed to update sockmaps, sock_map_update_elem() taking the unix lock, as it is currently implemented in unix_state_lock(): spin_lock(&unix_sk(s)->lock), would be problematic. unix_state_lock() taken in a process context, followed by a softirq-context TC BPF program attempting to take the same spinlock -- deadlock[6]. This way we circled back to the peer check idea[2].

[1]: https://lore.kernel.org/netdev/[email protected]/ [2]: https://lore.kernel.org/netdev/[email protected]/ [3]: https://lore.kernel.org/netdev/[email protected]/ [4]: https://lore.kernel.org/netdev/CAAVpQUA+8GL_j63CaKb8hbxoL21izD58yr1NvhOhU=j+35+3og@mail.gmail.com/ [5]: https://lore.kernel.org/bpf/CAAVpQUAHijOMext28Gi10dSLuMzGYh+jK61Ujn+fZ-wvcODR2A@mail.gmail.com/ [6]: https://lore.kernel.org/bpf/[email protected]/

Summary of scenarios where af_unix/stream connect() may race a sockmap update:

  • connect() vs. bpf(BPF_MAP_UPDATE_ELEM), i.e. sock_map_update_elem_sys()

Implemented NULL check is sufficient. Once assigned, socket peer won't be released until socket fd is released. And that's not an issue because sock_map_update_elem_sys() bumps fd refcnf.

  • connect() vs BPF program doing update

Update restricted per verifier.c:may_update_sockmap() to

BPF_PROG_TYPE_TRACING/BPF_TRACE_ITER BPF_PROG_TYPE_SOCK_OPS (bpf_sock_map_update() only) BPF_PROG_TYPE_SOCKET_FILTER BPF_PROG_TYPE_SCHED_CLS BPF_PROG_TYPE_SCHED_ACT BPF_PROG_TYPE_XDP BPF_PROG_TYPE_SK_REUSEPORT BPF_PROG_TYPE_FLOW_DISSECTOR BPF_PROG_TYPE_SK_LOOKUP

Plus one more race to consider:

CPU0 bpf CPU1 connect -------- ------------

WRITE_ONCE(sk->sk_state, TCP_ESTABLISHED) sock_map_sk_state_allowed(sk) sock_hold(newsk) smp_mb__after_atomic() ---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.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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
2nd
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-10-24). 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 low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 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 low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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)14 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's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

June 24, 2026

Last Modified

July 15, 2026

Advisory Details (6)

Auto-updated Jul 16, 2026
Patch available.
Web page

bpf, sockmap: Fix af_unix null-ptr-deref in proto update - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/dca38b7734d2ea00af4818ff3ae836fab33d5d5a
Web page

bpf, sockmap: Fix af_unix null-ptr-deref in proto update - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a94d3dd78ee8b63e6b8ad629081c952c93ee5a10
Web page

bpf, sockmap: Fix af_unix null-ptr-deref in proto update - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/75b7d3b3f8bd4e59eb3af1b11a43c64c0c2db6f4
Web page

bpf, sockmap: Fix af_unix null-ptr-deref in proto update - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4913c94a3adcdbb64c552110c0c243cb1fdbb317
Web page

bpf, sockmap: Fix af_unix null-ptr-deref in proto update - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/37bfcd164161b47d00b1c3bd20adc816a6977ce0
Web page

bpf, sockmap: Fix af_unix null-ptr-deref in proto update - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/041eb6348d73ee5e15fc8161f1eac5a6e8289ca0

Vendor Advisories for CVE-2026-53034(2)

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

Patch Availability(26)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-10-22ubuntu
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-10-22ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-10-22ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-10-22ubuntu
ubuntulinux-tools-oracle-edge (7.0.0-1011.11~24.04.1) @ noble2026-10-22ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-10-22ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-10-22ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-10-22ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-10-22ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-10-22ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-10-22ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-10-22ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-10-22ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-10-22ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-10-22ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-10-22ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-10-22ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-10-22ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-10-22ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-10-22ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-10-22ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-10-22ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-10-22ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-10-22ubuntu
ubuntulinux-tools-azure-edge (7.0.0-1014.14~24.04.1) @ noble2026-10-22ubuntu
linuxKernel @ 6.1.175 (fixes >=5.15.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
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)
  • every version up to 6.1.176-1~deb11u1: fixed in 6.1.176-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)
  • every version up to 6.1.176-1: fixed in 6.1.176-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)
  • every version up to 6.12.94-1: fixed in 6.12.94-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (141 versions)
  • every version up to 7.0.10-1: fixed in 7.0.10-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(24)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 11× 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 100 of 245 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. None are among the latest 100 rows. The 145 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-53034?
CVE-2026-53034 is a medium-severity vulnerability; its CVE record was published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: bpf, sockmap: Fix af_unix null-ptr-deref in proto update unixstreamconnect() sets skstate (WRITEONCE(sk->sk_state, TCPESTABLISHED)) before it assigns a peer (unixpeer(sk) = newsk). skstate == TCPESTABLISHED makes…
When was the CVE record for CVE-2026-53034 published?
The CVE record for CVE-2026-53034 was published on June 24, 2026. 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 July 15, 2026; the record at its source may have been updated since.
Is CVE-2026-53034 actively exploited?
CVE-2026-53034 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53034?
CVE-2026-53034 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53034?
A fix for CVE-2026-53034 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53034 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-2026-53034

Explore →

Is Your Infrastructure Affected by CVE-2026-53034?

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

Book a Demo →Browse All CVEs