CVE-2026-53262

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. 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:

l2tp: pppol2tp: hold reference to session in pppol2tp_ioctl()

pppol2tp_ioctl() read sock->sk->sk_user_data directly without any locks or reference counting. If a controllable sleep was induced during copy_from_user() (e.g. via a userfaultfd page fault sleep), a concurrent socket close could trigger pppol2tp_session_close() asynchronously. This frees the l2tp_session structure via the l2tp_session_del_work workqueue. Upon resuming, the ioctl thread dereferences the stale session pointer, resulting in a Use-After-Free (UAF).

Fix this by securely fetching the session reference using the RCU-safe, refcounted helper pppol2tp_sock_to_session(sk) on entry. This locks the session's refcount across the sleep. We structured the function to exit via standard err breaks, guaranteeing that l2tp_session_put() is cleanly called on all return paths to drop the reference.

To preserve existing behavior we validate the session and its magic signature only for the specific L2TP commands that require it. This ensures that generic/unknown ioctls called on an unconnected socket still return -ENOIOCTLCMD and correctly fall back to generic handlers (e.g. in sock_do_ioctl()).

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

Published

June 25, 2026

Last Modified

June 30, 2026

Advisory Details (4)

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

l2tp: pppol2tp: hold reference to session in pppol2tp_ioctl() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e251d4cdfc725c9e7d686161e3b775a0e7d95053
generic

l2tp: pppol2tp: hold reference to session in pppol2tp_ioctl() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a213a8950414c684999dcf03edeea6c46ede172e
generic

l2tp: pppol2tp: hold reference to session in pppol2tp_ioctl() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/78cdfdca88cbf731a92f3b9ee5427c633dd94e28
generic

l2tp: pppol2tp: hold reference to session in pppol2tp_ioctl() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/62f327e287cf7b595ae3f73ba72f5cd2a9e9f39f

Vendor Advisories for CVE-2026-53262(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 31× in last 7d / 49× 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 03:58 UTCEG score recompute
  2. 2026-07-07 03:58 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 14:46 UTCEG score recompute
  6. 2026-07-06 14:46 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-06 01:52 UTCEG score recompute
  10. 2026-07-06 01:52 UTCGHSA enrichment
  11. 2026-07-05 13:04 UTCEG score recompute
  12. 2026-07-05 13:04 UTCGHSA enrichment
  13. 2026-07-05 00:16 UTCEG score recompute
  14. 2026-07-05 00:16 UTCGHSA enrichment
  15. 2026-07-04 11:28 UTCEG score recompute
  16. 2026-07-04 11:28 UTCGHSA enrichment
  17. 2026-07-03 22:40 UTCEG score recompute
  18. 2026-07-03 22:40 UTCGHSA enrichment
  19. 2026-07-03 09:52 UTCEG score recompute
  20. 2026-07-03 09:52 UTCGHSA enrichment
  21. 2026-07-02 21:03 UTCEG score recompute
  22. 2026-07-02 21:03 UTCGHSA enrichment
  23. 2026-07-02 08:16 UTCEG score recompute
  24. 2026-07-02 08:16 UTCGHSA enrichment
  25. 2026-07-01 19:28 UTCEG score recompute
Show 24 more
  1. 2026-07-01 19:27 UTCGHSA enrichment
  2. 2026-07-01 15:07 UTCEPSS rescore
  3. 2026-07-01 06:39 UTCEG score recompute
  4. 2026-07-01 06:39 UTCGHSA enrichment
  5. 2026-06-30 17:51 UTCEG score recompute
  6. 2026-06-30 17:51 UTCGHSA enrichment
  7. 2026-06-30 05:03 UTCEG score recompute
  8. 2026-06-30 05:03 UTCGHSA enrichment
  9. 2026-06-29 16:15 UTCEG score recompute
  10. 2026-06-29 16:15 UTCGHSA enrichment
  11. 2026-06-29 14:06 UTCEPSS rescore
  12. 2026-06-29 14:06 UTCEPSS rescore
  13. 2026-06-29 03:28 UTCEG score recompute
  14. 2026-06-29 03:28 UTCGHSA enrichment
  15. 2026-06-28 14:40 UTCEG score recompute 7.80
  16. 2026-06-28 14:40 UTCGHSA enrichment
  17. 2026-06-28 14:07 UTCEPSS rescore
  18. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  19. 2026-06-28 04:56 UTCEPSS rescore
  20. 2026-06-28 04:56 UTCEPSS rescore
  21. 2026-06-27 03:08 UTCEPSS rescore
  22. 2026-06-25 13:49 UTCEPSS rescore
  23. 2026-06-25 10:03 UTCEG score recompute
  24. 2026-06-25 10:02 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-53262?
CVE-2026-53262 is a high vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: l2tp: pppol2tp: hold reference to session in pppol2tp_ioctl() pppol2tpioctl() read sock->sk->skuser_data directly without any locks or reference counting. If a controllable sleep was induced during copyfromuser() (e.g. via a…
When was CVE-2026-53262 disclosed?
CVE-2026-53262 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53262 actively exploited?
CVE-2026-53262 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53262?
CVE-2026-53262 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-53262?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53262, 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-53262

Explore →

Is Your Infrastructure Affected by CVE-2026-53262?

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