CVE-2026-90057

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-81918 (ENISA EUVD) · GHSA-45fm-hw2m-668x (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
5th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 17, 2026

Last Modified

October 19, 2026

Advisory Details (6)

Auto-updated Sep 18, 2026
Patch available.
Web page

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
Web page

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
Web page

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
Web page

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
Web page

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
Web page

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

Patch Availability(14)

These rows come from Ubuntu. Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (57 versions)
  • every version up to 6.1.190-1: fixed in 6.1.190-1
—
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 (180 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

All Vendor Advisories

(14)

Data Freshness Timeline

(refreshed 9× in last 7d / 35× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 159 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 59 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-21 16:42 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  2. 2026-11-20 16:39 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  3. 2026-11-19 16:36 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  4. 2026-11-18 16:36 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  5. 2026-11-17 17:33 UTCEchelonGraph re-scored
  6. 2026-11-17 17:33 UTCVendor advisory
  7. 2026-11-17 17:33 UTCGHSA enrichmentGHSA-45fm-hw2m-668x · GitHub severity HIGH · GitHub CVSS 7.8
  8. 2026-11-17 16:36 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  9. 2026-11-16 16:53 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  10. 2026-11-15 17:03 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  11. 2026-11-14 16:42 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  12. 2026-11-13 16:58 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  13. 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  14. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  15. 2026-11-10 16:51 UTCEchelonGraph re-scored
  16. 2026-11-10 16:51 UTCGHSA enrichmentGHSA-45fm-hw2m-668x · GitHub severity HIGH · GitHub CVSS 7.8
  17. 2026-11-10 16:46 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  18. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  19. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  20. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  21. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  22. 2026-11-05 16:39 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  23. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  24. 2026-11-03 17:43 UTCEchelonGraph re-scored
  25. 2026-11-03 17:43 UTCGHSA enrichmentGHSA-45fm-hw2m-668x · GitHub severity HIGH · GitHub CVSS 7.8
Show 75 more
  1. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  2. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  3. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  4. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  5. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  6. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  7. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  8. 2026-10-27 17:48 UTCEchelonGraph re-scored
  9. 2026-10-27 17:48 UTCGHSA enrichmentGHSA-45fm-hw2m-668x · GitHub severity HIGH · GitHub CVSS 7.8
  10. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  11. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  12. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  13. 2026-10-25 13:52 UTCEchelonGraph re-scored
  14. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  15. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  16. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  17. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  18. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  19. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  20. 2026-10-19 09:35 UTCEchelonGraph re-scored
  21. 2026-10-19 09:35 UTCGHSA enrichmentGHSA-45fm-hw2m-668x · GitHub severity HIGH · GitHub CVSS 7.8
  22. 2026-10-19 09:12 UTCEchelonGraph re-scored
  23. 2026-10-19 09:12 UTCGHSA enrichmentGHSA-45fm-hw2m-668x · GitHub severity HIGH · GitHub CVSS 7.8
  24. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  25. 2026-10-18 03:01 UTCEchelonGraph re-scored
  26. 2026-10-17 18:36 UTCEchelonGraph re-scored
  27. 2026-10-17 18:36 UTCGHSA enrichmentGHSA-45fm-hw2m-668x · GitHub severity HIGH · GitHub CVSS 7.8
  28. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  29. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  30. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  31. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  32. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  33. 2026-10-13 04:49 UTCEchelonGraph re-scored
  34. 2026-10-13 04:49 UTCGHSA enrichmentGHSA-45fm-hw2m-668x · GitHub severity HIGH · GitHub CVSS 7.8
  35. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  36. 2026-10-12 14:47 UTCEchelonGraph re-scored
  37. 2026-10-12 01:55 UTCGHSA enrichmentGHSA-45fm-hw2m-668x · GitHub severity HIGH · GitHub CVSS 7.8
  38. 2026-10-11 19:14 UTCEchelonGraph re-scored
  39. 2026-10-11 16:31 UTCEchelonGraph re-scored
  40. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  41. 2026-10-11 13:46 UTCEchelonGraph re-scored
  42. 2026-10-11 11:24 UTCEchelonGraph re-scored
  43. 2026-10-11 11:24 UTCGHSA enrichmentGHSA-45fm-hw2m-668x · GitHub severity HIGH · GitHub CVSS 7.8
  44. 2026-10-10 22:23 UTCEchelonGraph re-scored
  45. 2026-10-10 22:23 UTCGHSA enrichmentGHSA-45fm-hw2m-668x · GitHub severity HIGH · GitHub CVSS 7.8
  46. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  47. 2026-10-10 08:37 UTCEchelonGraph re-scored
  48. 2026-10-10 08:37 UTCGHSA enrichmentGHSA-45fm-hw2m-668x · GitHub severity HIGH · GitHub CVSS 7.8
  49. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  50. 2026-10-09 19:46 UTCGHSA enrichmentGHSA-45fm-hw2m-668x · GitHub severity HIGH · GitHub CVSS 7.8
  51. 2026-10-09 06:54 UTCGHSA enrichmentGHSA-45fm-hw2m-668x · GitHub severity HIGH · GitHub CVSS 7.8
  52. 2026-10-08 18:02 UTCEchelonGraph re-scored
  53. 2026-10-08 18:02 UTCGHSA enrichmentGHSA-45fm-hw2m-668x · GitHub severity HIGH · GitHub CVSS 7.8
  54. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  55. 2026-10-08 03:18 UTCEchelonGraph re-scored
  56. 2026-10-08 03:18 UTCGHSA enrichmentGHSA-45fm-hw2m-668x · GitHub severity HIGH · GitHub CVSS 7.8
  57. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  58. 2026-10-07 14:26 UTCGHSA enrichmentGHSA-45fm-hw2m-668x · GitHub severity HIGH · GitHub CVSS 7.8
  59. 2026-10-07 00:55 UTCEchelonGraph re-scored
  60. 2026-10-07 00:55 UTCGHSA enrichmentGHSA-45fm-hw2m-668x · GitHub severity HIGH · GitHub CVSS 7.8
  61. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  62. 2026-10-06 11:36 UTCGHSA enrichmentGHSA-45fm-hw2m-668x · GitHub severity HIGH · GitHub CVSS 7.8
  63. 2026-10-05 22:45 UTCEchelonGraph re-scored
  64. 2026-10-05 22:45 UTCGHSA enrichmentGHSA-45fm-hw2m-668x · GitHub severity HIGH · GitHub CVSS 7.8
  65. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  66. 2026-10-05 09:55 UTCEchelonGraph re-scored
  67. 2026-10-05 09:54 UTCGHSA enrichmentGHSA-45fm-hw2m-668x · GitHub severity HIGH · GitHub CVSS 7.8
  68. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  69. 2026-10-04 21:03 UTCGHSA enrichmentGHSA-45fm-hw2m-668x · GitHub severity HIGH · GitHub CVSS 7.8
  70. 2026-10-04 08:05 UTCGHSA enrichmentGHSA-45fm-hw2m-668x · GitHub severity HIGH · GitHub CVSS 7.8
  71. 2026-10-03 19:14 UTCEchelonGraph re-scored
  72. 2026-10-03 19:14 UTCGHSA enrichmentGHSA-45fm-hw2m-668x · GitHub severity HIGH · GitHub CVSS 7.8
  73. 2026-10-03 06:24 UTCEchelonGraph re-scored
  74. 2026-10-03 06:24 UTCGHSA enrichmentGHSA-45fm-hw2m-668x · GitHub severity HIGH · GitHub CVSS 7.8
  75. 2026-10-02 17:33 UTCGHSA enrichmentGHSA-45fm-hw2m-668x · GitHub severity HIGH · GitHub CVSS 7.8

Frequently asked(5)

What is CVE-2026-90057?
CVE-2026-90057 is a high-severity vulnerability; its CVE record was published on September 17, 2026. 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…
When was the CVE record for CVE-2026-90057 published?
The CVE record for CVE-2026-90057 was published on September 17, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 19, 2026; the record at its source may have been updated since.
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?
A fix for CVE-2026-90057 is available: update to the fixed version the vendor names in its advisory. 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.