CVE-2026-68143

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

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

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

net: slip: serialize receive against buffer reallocation

sl_realloc_bufs() replaces rbuff and updates buffsize while holding sl->lock. slip_receive_buf() reads those fields and writes through rbuff without holding the lock.

An MTU change can therefore race with receive processing. An MTU shrink can expose the new smaller rbuff with the old larger bound, causing an out-of-bounds write. A receive callback which already loaded the old rbuff can instead continue writing after that buffer has been freed.

Serialize receive processing with sl_realloc_bufs() by holding sl->lock while consuming each receive batch.

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 19, 2026

Advisory Details (5)

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

net: slip: serialize receive against buffer reallocation - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: slip: serialize receive against buffer reallocation - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: slip: serialize receive against buffer reallocation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5d07b178bef511d69558cfc89fe1129258dc39f8
generic

net: slip: serialize receive against buffer reallocation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/44401f7dd9940ced7098930ef64f5a332f279fc2
generic

net: slip: serialize receive against buffer reallocation - kernel/git/stable/linux.git - Linux kernel stable tree

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

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

Frequently asked(5)

What is CVE-2026-68143?
CVE-2026-68143 is a high vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: net: slip: serialize receive against buffer reallocation slreallocbufs() replaces rbuff and updates buffsize while holding sl->lock. slipreceivebuf() reads those fields and writes through rbuff without holding the lock. An MTU…
When was CVE-2026-68143 disclosed?
CVE-2026-68143 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-68143 actively exploited?
CVE-2026-68143 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.4% of all scored CVEs.
What is the CVSS score of CVE-2026-68143?
CVE-2026-68143 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-68143?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68143, 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-68143

Explore →

Is Your Infrastructure Affected by CVE-2026-68143?

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