CVE-2026-90057

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-17. 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.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

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

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

slip: remove slip_hangup() to fix use-after-free in slip_receive_buf()

Jaeyoung Chung and Eulgyu Kim reported a slab-use-after-free read in slip_receive_buf() when racing against tty hangup.

tty_ldisc_hangup() calls ld->ops->hangup() while holding only a read lock on tty->ldisc_sem (via tty_ldisc_ref()). Because slip_hangup() simply called slip_close(), it ran concurrently with reader functions such as slip_receive_buf().

slip_close() unregisters and frees the net device and its private struct slip, causing concurrent reader threads in slip_receive_buf() to dereference freed memory.

Line discipline close() is already guaranteed to be called under the write lock of tty->ldisc_sem during hangup processing (in tty_ldisc_reinit() or tty_ldisc_kill()).

Remove slip_hangup() so teardown is serialized cleanly by slip_close().

CVSS v3
7.8
EG Score
7.8HIGHhigh confidence
EG Risk
40
EG Risk 40/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
5th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 17, 2026

Last Modified

September 18, 2026

Advisory Details (6)

Auto-updated Sep 18, 2026
No patch confirmed yet.
generic

slip: remove slip_hangup() to fix use-after-free in slip_receive_buf() - kernel/git/stable/linux.git - Linux kernel stable tree

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

slip: remove slip_hangup() to fix use-after-free in slip_receive_buf() - kernel/git/stable/linux.git - Linux kernel stable tree

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

slip: remove slip_hangup() to fix use-after-free in slip_receive_buf() - kernel/git/stable/linux.git - Linux kernel stable tree

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

slip: remove slip_hangup() to fix use-after-free in slip_receive_buf() - kernel/git/stable/linux.git - Linux kernel stable tree

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

slip: remove slip_hangup() to fix use-after-free in slip_receive_buf() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9a3b1edff1ecb47d323f2506b3ffc22178acd1c6
generic

slip: remove slip_hangup() to fix use-after-free in slip_receive_buf() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/23c53269f2baaedf2d92784290cb9ef6db2a3bce

Vendor Advisories for CVE-2026-90057(1)

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

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (179 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 24× in last 7d / 67× 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-10-04 23:22 UTCEPSS rescore
  2. 2026-10-04 21:03 UTCGHSA enrichment
  3. 2026-10-04 08:05 UTCGHSA enrichment
  4. 2026-10-03 19:14 UTCEG score recompute
  5. 2026-10-03 19:14 UTCGHSA enrichment
  6. 2026-10-03 06:24 UTCEG score recompute
  7. 2026-10-03 06:24 UTCGHSA enrichment
  8. 2026-10-02 17:33 UTCGHSA enrichment
  9. 2026-10-02 04:42 UTCEG score recompute
  10. 2026-10-02 04:42 UTCGHSA enrichment
  11. 2026-10-01 19:51 UTCEPSS rescore
  12. 2026-10-01 15:50 UTCGHSA enrichment
  13. 2026-10-01 02:59 UTCEG score recompute
  14. 2026-10-01 02:59 UTCGHSA enrichment
  15. 2026-09-30 15:04 UTCEPSS rescore
  16. 2026-09-30 14:06 UTCGHSA enrichment
  17. 2026-09-30 01:15 UTCEG score recompute
  18. 2026-09-30 01:14 UTCGHSA enrichment
  19. 2026-09-29 12:22 UTCGHSA enrichment
  20. 2026-09-28 23:31 UTCEG score recompute
  21. 2026-09-28 23:31 UTCGHSA enrichment
  22. 2026-09-28 13:52 UTCEPSS rescore
  23. 2026-09-28 13:52 UTCEPSS rescore
  24. 2026-09-28 10:40 UTCGHSA enrichment
  25. 2026-09-27 21:48 UTCEG score recompute
Show 42 more
  1. 2026-09-27 21:48 UTCGHSA enrichment
  2. 2026-09-27 13:49 UTCEPSS rescore
  3. 2026-09-27 08:56 UTCGHSA enrichment
  4. 2026-09-26 20:05 UTCEG score recompute
  5. 2026-09-26 20:04 UTCGHSA enrichment
  6. 2026-09-26 15:59 UTCEPSS rescore
  7. 2026-09-26 07:13 UTCEG score recompute
  8. 2026-09-26 07:13 UTCGHSA enrichment
  9. 2026-09-25 18:22 UTCGHSA enrichment
  10. 2026-09-25 04:40 UTCGHSA enrichment
  11. 2026-09-24 15:49 UTCEG score recompute
  12. 2026-09-24 15:49 UTCGHSA enrichment
  13. 2026-09-24 14:04 UTCEPSS rescore
  14. 2026-09-24 02:57 UTCEG score recompute
  15. 2026-09-24 02:57 UTCGHSA enrichment
  16. 2026-09-23 17:54 UTCEPSS rescore
  17. 2026-09-23 14:06 UTCGHSA enrichment
  18. 2026-09-23 01:16 UTCEG score recompute
  19. 2026-09-23 01:16 UTCGHSA enrichment
  20. 2026-09-22 16:01 UTCEPSS rescore
  21. 2026-09-22 12:25 UTCGHSA enrichment
  22. 2026-09-21 23:34 UTCEG score recompute
  23. 2026-09-21 23:34 UTCGHSA enrichment
  24. 2026-09-21 21:09 UTCEPSS rescore
  25. 2026-09-21 10:44 UTCGHSA enrichment
  26. 2026-09-20 21:54 UTCEG score recompute
  27. 2026-09-20 21:54 UTCGHSA enrichment
  28. 2026-09-20 20:16 UTCEPSS rescore
  29. 2026-09-20 09:03 UTCGHSA enrichment
  30. 2026-09-19 20:12 UTCEG score recompute
  31. 2026-09-19 20:12 UTCGHSA enrichment
  32. 2026-09-19 07:21 UTCEG score recompute
  33. 2026-09-19 07:21 UTCGHSA enrichment
  34. 2026-09-18 19:28 UTCEPSS rescore
  35. 2026-09-18 18:31 UTCEG score recompute
  36. 2026-09-18 18:31 UTCGHSA enrichment
  37. 2026-09-18 18:07 UTCEG score recompute▲ 7.80
  38. 2026-09-18 18:06 UTCGHSA enrichment
  39. 2026-09-18 17:59 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  40. 2026-09-17 17:23 UTCNVD update
  41. 2026-09-17 16:53 UTCEG score recompute
  42. 2026-09-17 16:19 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-90057?
CVE-2026-90057 is a high vulnerability published on September 17, 2026. In the Linux kernel, the following vulnerability has been resolved: slip: remove sliphangup() to fix use-after-free in slipreceive_buf() Jaeyoung Chung and Eulgyu Kim reported a slab-use-after-free read in slipreceivebuf() when racing against tty hangup. ttyldischangup() calls ld->ops->hangup()…
When was CVE-2026-90057 disclosed?
CVE-2026-90057 was first published on September 17, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-90057 actively exploited?
CVE-2026-90057 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-90057?
CVE-2026-90057 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-90057?
No fix for CVE-2026-90057 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-90057 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-90057

Explore →

Is Your Infrastructure Affected by CVE-2026-90057?

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

Book a Demo →Browse All CVEs