CVE-2026-53078

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

bpf: Fix same-register dst/src OOB read and pointer leak in sock_ops

When a BPF sock_ops program accesses ctx fields with dst_reg == src_reg, the SOCK_OPS_GET_SK() and SOCK_OPS_GET_FIELD() macros fail to zero the destination register in the !fullsock / !locked_tcp_sock path.

Both macros borrow a temporary register to check is_fullsock / is_locked_tcp_sock when dst_reg == src_reg, because dst_reg holds the ctx pointer. When the check is false (e.g., TCP_NEW_SYN_RECV state with a request_sock), dst_reg should be zeroed but is not, leaving the stale ctx pointer:

  • SOCK_OPS_GET_SK: dst_reg retains the ctx pointer, passes NULL checks
as PTR_TO_SOCKET_OR_NULL, and can be used as a bogus socket pointer, leading to stack-out-of-bounds access in helpers like bpf_skc_to_tcp6_sock().
  • SOCK_OPS_GET_FIELD: dst_reg retains the ctx pointer which the
verifier believes is a SCALAR_VALUE, leaking a kernel pointer.

Fix both macros by:

  • Changing JMP_A(1) to JMP_A(2) in the fullsock path to skip the
added instruction.
  • Adding BPF_MOV64_IMM(si->dst_reg, 0) after the temp register
restore in the !fullsock path, placed after the restore because dst_reg == src_reg means we need src_reg intact to read ctx->temp.

CVSS v3
7.8
EG Score
7.8(high)
EPSS
1.6%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 28, 2026

Advisory Details (2)

Auto-updated Jun 28, 2026
No patch confirmed yet.
generic

bpf: Fix same-register dst/src OOB read and pointer leak in sock_ops - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/18e3ffde1822f0b48b1753bf34aa97ce839df1d8
generic

bpf: Fix same-register dst/src OOB read and pointer leak in sock_ops - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/10f86a2a5c91fc4c4d001960f1c21abe52545ef6

Vendor Advisories for CVE-2026-53078(2)

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

Data Freshness Timeline

(refreshed 32× in last 7d / 42× 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-07 01:06 UTCEG score recompute
  2. 2026-07-07 01:06 UTCGHSA enrichment
  3. 2026-07-06 13:23 UTCEG score recompute
  4. 2026-07-06 13:22 UTCGHSA enrichment
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-06 01:37 UTCEG score recompute
  8. 2026-07-06 01:37 UTCGHSA enrichment
  9. 2026-07-05 13:54 UTCEG score recompute
  10. 2026-07-05 13:54 UTCGHSA enrichment
  11. 2026-07-05 02:31 UTCEPSS rescore
  12. 2026-07-05 02:30 UTCEPSS rescore
  13. 2026-07-05 02:10 UTCEG score recompute
  14. 2026-07-05 02:10 UTCGHSA enrichment
  15. 2026-07-04 14:27 UTCEG score recompute
  16. 2026-07-04 14:27 UTCGHSA enrichment
  17. 2026-07-04 06:31 UTCEPSS rescore
  18. 2026-07-04 02:44 UTCEG score recompute
  19. 2026-07-04 02:43 UTCGHSA enrichment
  20. 2026-07-03 14:58 UTCEG score recompute
  21. 2026-07-03 14:58 UTCGHSA enrichment
  22. 2026-07-03 03:13 UTCEG score recompute
  23. 2026-07-03 03:13 UTCGHSA enrichment
  24. 2026-07-02 15:28 UTCEG score recompute
  25. 2026-07-02 15:28 UTCGHSA enrichment
Show 17 more
  1. 2026-07-02 03:44 UTCEG score recompute
  2. 2026-07-02 03:44 UTCGHSA enrichment
  3. 2026-07-01 16:01 UTCEG score recompute
  4. 2026-07-01 16:01 UTCGHSA enrichment
  5. 2026-07-01 04:18 UTCEG score recompute 7.80
  6. 2026-07-01 04:18 UTCGHSA enrichment
  7. 2026-06-30 23:22 UTCEPSS rescore
  8. 2026-06-28 14:07 UTCEPSS rescore
  9. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  10. 2026-06-28 04:56 UTCEPSS rescore
  11. 2026-06-28 04:56 UTCEPSS rescore
  12. 2026-06-27 23:16 UTCEG score recompute
  13. 2026-06-27 23:16 UTCGHSA enrichment
  14. 2026-06-27 03:08 UTCEPSS rescore
  15. 2026-06-25 13:49 UTCEPSS rescore
  16. 2026-06-24 18:14 UTCEG score recompute
  17. 2026-06-24 18:03 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-53078?
CVE-2026-53078 is a high vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: bpf: Fix same-register dst/src OOB read and pointer leak in sock_ops When a BPF sockops program accesses ctx fields with dstreg == src_reg, the SOCKOPSGETSK() and SOCKOPSGETFIELD() macros fail to zero the destination register in…
When was CVE-2026-53078 disclosed?
CVE-2026-53078 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on June 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53078 actively exploited?
CVE-2026-53078 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53078?
CVE-2026-53078 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-53078?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53078, 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-2026-53078

Explore →

Is Your Infrastructure Affected by CVE-2026-53078?

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