CVE-2026-68144

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-10. a secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 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:

phonet: pep: fix use-after-free in pep_get_sb()

pep_get_sb() doesn't consider that pskb_may_pull() might have relocated the skb data, and continue to access the older pointer, causing UAF.

Reproduced under KASAN:

BUG: KASAN: slab-use-after-free in pep_get_sb+0x234/0x3b0 Read of size 1 at addr ff11000105510f50 by task repro/157 pep_get_sb+0x234/0x3b0 pipe_handler_do_rcv+0x5f7/0xa10 pep_do_rcv+0x203/0x410 __sk_receive_skb+0x471/0x4a0 phonet_rcv+0x5b3/0x6c0 __netif_receive_skb+0xcc/0x1d0

Refetch the header with skb_header_pointer() after pskb_may_pull(), so the possibly stale pointer is no longer dereferenced. There are better ways to solve this, but, this is the less instrusive one.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
43%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 19, 2026

Advisory Details (7)

Auto-updated Aug 19, 2026
No patch confirmed yet.
generic

phonet: pep: fix use-after-free in pep_get_sb() - kernel/git/stable/linux.git - Linux kernel stable tree

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

phonet: pep: fix use-after-free in pep_get_sb() - kernel/git/stable/linux.git - Linux kernel stable tree

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

phonet: pep: fix use-after-free in pep_get_sb() - kernel/git/stable/linux.git - Linux kernel stable tree

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

phonet: pep: fix use-after-free in pep_get_sb() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8d931a75a38b9bb584a4071f5ebbd52755fc35ee
generic

phonet: pep: fix use-after-free in pep_get_sb() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/25e3641beb51333bfbb155af2fd2573a61113af2
generic

phonet: pep: fix use-after-free in pep_get_sb() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/17f78c0c0d41d738ee236eb6e841e39395188054
generic

phonet: pep: fix use-after-free in pep_get_sb() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0f71f852a96af9685858ce59fda34ecbf85c283d

Vendor Advisories for CVE-2026-68144(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 57× in last 7d / 71× 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-08-21 04:44 UTCVendor advisory
  2. 2026-08-21 04:44 UTCGHSA enrichment
  3. 2026-08-21 00:20 UTCEG score recompute
  4. 2026-08-21 00:20 UTCGHSA enrichment
  5. 2026-08-20 22:56 UTCEPSS rescore
  6. 2026-08-20 19:56 UTCGHSA enrichment
  7. 2026-08-20 15:31 UTCGHSA enrichment
  8. 2026-08-20 11:03 UTCGHSA enrichment
  9. 2026-08-20 06:38 UTCGHSA enrichment
  10. 2026-08-20 02:14 UTCGHSA enrichment
  11. 2026-08-19 21:50 UTCGHSA enrichment
  12. 2026-08-19 17:26 UTCEG score recompute
  13. 2026-08-19 17:26 UTCGHSA enrichment
  14. 2026-08-19 17:04 UTCEPSS rescore
  15. 2026-08-19 16:55 UTCEG score recompute
  16. 2026-08-19 16:55 UTCGHSA enrichment
  17. 2026-08-19 16:19 UTCGHSA enrichment
  18. 2026-08-19 11:46 UTCGHSA enrichment
  19. 2026-08-19 07:22 UTCGHSA enrichment
  20. 2026-08-19 02:58 UTCGHSA enrichment
  21. 2026-08-18 22:14 UTCGHSA enrichment
  22. 2026-08-18 17:51 UTCEG score recompute
  23. 2026-08-18 17:50 UTCGHSA enrichment
  24. 2026-08-18 13:48 UTCEPSS rescore
  25. 2026-08-18 13:03 UTCGHSA enrichment
Show 46 more
  1. 2026-08-18 08:38 UTCGHSA enrichment
  2. 2026-08-18 04:12 UTCGHSA enrichment
  3. 2026-08-17 23:45 UTCGHSA enrichment
  4. 2026-08-17 19:21 UTCGHSA enrichment
  5. 2026-08-17 14:28 UTCEG score recompute
  6. 2026-08-17 14:28 UTCGHSA enrichment
  7. 2026-08-17 13:47 UTCEPSS rescore
  8. 2026-08-17 10:04 UTCGHSA enrichment
  9. 2026-08-17 05:40 UTCEG score recompute
  10. 2026-08-17 05:40 UTCGHSA enrichment
  11. 2026-08-17 05:11 UTCEG score recompute
  12. 2026-08-17 05:11 UTCGHSA enrichment
  13. 2026-08-17 02:50 UTCGHSA enrichment
  14. 2026-08-16 22:26 UTCGHSA enrichment
  15. 2026-08-16 18:02 UTCEG score recompute
  16. 2026-08-16 18:02 UTCGHSA enrichment
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 13:38 UTCGHSA enrichment
  19. 2026-08-16 09:14 UTCGHSA enrichment
  20. 2026-08-16 04:51 UTCEG score recompute
  21. 2026-08-16 04:51 UTCGHSA enrichment
  22. 2026-08-16 00:28 UTCGHSA enrichment
  23. 2026-08-15 20:04 UTCGHSA enrichment
  24. 2026-08-15 15:40 UTCGHSA enrichment
  25. 2026-08-15 11:16 UTCGHSA enrichment
  26. 2026-08-15 06:52 UTCGHSA enrichment
  27. 2026-08-15 01:51 UTCEG score recompute
  28. 2026-08-15 01:51 UTCGHSA enrichment
  29. 2026-08-15 01:30 UTCEPSS rescore
  30. 2026-08-14 21:27 UTCGHSA enrichment
  31. 2026-08-14 17:04 UTCGHSA enrichment
  32. 2026-08-14 12:40 UTCGHSA enrichment
  33. 2026-08-14 08:17 UTCGHSA enrichment
  34. 2026-08-14 03:53 UTCEG score recompute
  35. 2026-08-14 03:53 UTCGHSA enrichment
  36. 2026-08-13 23:30 UTCEG score recompute
  37. 2026-08-13 23:30 UTCGHSA enrichment
  38. 2026-08-13 22:46 UTCEG score recompute▲ 9.80
  39. 2026-08-13 22:45 UTCGHSA enrichment
  40. 2026-08-13 22:44 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  41. 2026-08-13 14:26 UTCEG score recompute
  42. 2026-08-13 14:26 UTCGHSA enrichment
  43. 2026-08-12 13:51 UTCEPSS rescore
  44. 2026-08-10 13:24 UTCNVD update
  45. 2026-08-10 12:21 UTCEG score recompute
  46. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-68144?
CVE-2026-68144 is a critical vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: phonet: pep: fix use-after-free in pepgetsb() pepgetsb() doesn't consider that pskbmaypull() might have relocated the skb data, and continue to access the older pointer, causing UAF. Reproduced under KASAN: BUG: KASAN:…
When was CVE-2026-68144 disclosed?
CVE-2026-68144 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68144 actively exploited?
CVE-2026-68144 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 56.7% of all scored CVEs.
What is the CVSS score of CVE-2026-68144?
CVE-2026-68144 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-68144?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68144, 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-68144

Explore →

Is Your Infrastructure Affected by CVE-2026-68144?

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

Start Free Scan →Browse All CVEs