CVE-2026-74493

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-15. 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: 0.7%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

net/smc: fix socket use-after-free during link group termination

__smc_lgr_terminate() drops conns_lock after finding a connection in lgr->conns_all, but before taking a reference on its socket. The connection is embedded in the socket, and its registration reference protects it only while the connection remains in the tree.

A concurrent close can unregister the connection and drop that reference, freeing the socket before the termination worker reaches sock_hold().

The race is reachable when close overlaps link group termination. Local stress testing reproduced the use-after-free and KASAN reported:

BUG: KASAN: slab-use-after-free in __smc_lgr_terminate.part.0 [smc] Write of size 4 by task kworker/3:3 Workqueue: events smc_lgr_terminate_work [smc] __smc_lgr_terminate.part.0 [smc]

The socket was allocated by smc_create(), freed through slab_free_after_rcu_debug(), and was followed by:

refcount_t: addition on 0; use-after-free. __smc_lgr_terminate.part.0 [smc]

Take the socket reference while conns_lock still protects the tree entry. The unregister path then cannot drop the last reference until termination has finished using the socket.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
49
EG Risk 49/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
Severity98% × 45%
Exploitation1% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
52nd
KEV
Not listed

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

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact total (CVSS ≥ 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

August 15, 2026

Last Modified

August 19, 2026

Advisory Details (8)

Auto-updated Sep 30, 2026
Patch available.
generic

net/smc: fix socket use-after-free during link group termination - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/smc: fix socket use-after-free during link group termination - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/smc: fix socket use-after-free during link group termination - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/smc: fix socket use-after-free during link group termination - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/smc: fix socket use-after-free during link group termination - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/smc: fix socket use-after-free during link group termination - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/smc: fix socket use-after-free during link group termination - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/smc: fix socket use-after-free during link group termination - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/281c103a8eaed59001ce952f231df1b07674215a

Vendor Advisories for CVE-2026-74493(2)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1035.38) @ noble2026-10-05ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). 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 (56 versions)
  • every version up to 6.1.187-1: fixed in 6.1.187-1
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1
  • every version up to 6.12.107-1~deb12u1: fixed in 6.12.107-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (33 versions)
  • every version up to 6.12.105-1: fixed in 6.12.105-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (165 versions)
  • every version up to 7.1.8-1: fixed in 7.1.8-1
—

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 56× in last 7d / 287× 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.

Showing the most recent 100 of 447 total refreshes for this CVE.

  1. 2026-10-05 06:45 UTCVendor advisory
  2. 2026-10-05 06:45 UTCGHSA enrichment
  3. 2026-10-05 02:23 UTCEG score recompute
  4. 2026-10-05 02:23 UTCVendor advisory
  5. 2026-10-05 02:23 UTCGHSA enrichment
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-04 21:55 UTCVendor advisory
  8. 2026-10-04 21:55 UTCGHSA enrichment
  9. 2026-10-04 16:27 UTCVendor advisory
  10. 2026-10-04 16:27 UTCGHSA enrichment
  11. 2026-10-04 12:01 UTCVendor advisory
  12. 2026-10-04 12:01 UTCGHSA enrichment
  13. 2026-10-04 07:29 UTCVendor advisory
  14. 2026-10-04 07:29 UTCGHSA enrichment
  15. 2026-10-04 03:24 UTCVendor advisory
  16. 2026-10-04 03:24 UTCGHSA enrichment
  17. 2026-10-03 19:29 UTCEG score recompute
  18. 2026-10-03 19:29 UTCVendor advisory
  19. 2026-10-03 19:29 UTCGHSA enrichment
  20. 2026-10-03 14:26 UTCEPSS rescore
  21. 2026-10-03 00:47 UTCVendor advisory
  22. 2026-10-03 00:47 UTCGHSA enrichment
  23. 2026-10-02 19:57 UTCEG score recompute
  24. 2026-10-02 19:57 UTCVendor advisory
  25. 2026-10-02 19:57 UTCGHSA enrichment
Show 75 more
  1. 2026-10-02 15:50 UTCVendor advisory
  2. 2026-10-02 15:50 UTCGHSA enrichment
  3. 2026-10-02 07:02 UTCVendor advisory
  4. 2026-10-02 07:02 UTCGHSA enrichment
  5. 2026-10-02 01:59 UTCEG score recompute
  6. 2026-10-02 01:59 UTCVendor advisory
  7. 2026-10-02 01:59 UTCGHSA enrichment
  8. 2026-10-01 19:50 UTCEPSS rescore
  9. 2026-10-01 14:02 UTCVendor advisory
  10. 2026-10-01 14:02 UTCGHSA enrichment
  11. 2026-10-01 09:56 UTCVendor advisory
  12. 2026-10-01 09:56 UTCGHSA enrichment
  13. 2026-10-01 05:50 UTCVendor advisory
  14. 2026-10-01 05:50 UTCGHSA enrichment
  15. 2026-10-01 01:33 UTCVendor advisory
  16. 2026-10-01 01:33 UTCGHSA enrichment
  17. 2026-09-30 20:56 UTCEG score recompute
  18. 2026-09-30 20:56 UTCVendor advisory
  19. 2026-09-30 20:56 UTCGHSA enrichment
  20. 2026-09-29 15:24 UTCEPSS rescore
  21. 2026-09-29 07:51 UTCVendor advisory
  22. 2026-09-29 07:51 UTCGHSA enrichment
  23. 2026-09-29 03:46 UTCVendor advisory
  24. 2026-09-29 03:46 UTCGHSA enrichment
  25. 2026-09-28 23:37 UTCEG score recompute
  26. 2026-09-28 23:37 UTCVendor advisory
  27. 2026-09-28 23:37 UTCGHSA enrichment
  28. 2026-09-28 15:21 UTCEG score recompute
  29. 2026-09-28 15:21 UTCVendor advisory
  30. 2026-09-28 15:21 UTCGHSA enrichment
  31. 2026-09-28 13:52 UTCEPSS rescore
  32. 2026-09-28 10:55 UTCVendor advisory
  33. 2026-09-28 10:55 UTCGHSA enrichment
  34. 2026-09-28 06:49 UTCVendor advisory
  35. 2026-09-28 06:49 UTCGHSA enrichment
  36. 2026-09-28 02:43 UTCVendor advisory
  37. 2026-09-28 02:43 UTCGHSA enrichment
  38. 2026-09-27 22:36 UTCVendor advisory
  39. 2026-09-27 22:36 UTCGHSA enrichment
  40. 2026-09-27 16:43 UTCEG score recompute
  41. 2026-09-27 16:43 UTCVendor advisory
  42. 2026-09-27 16:43 UTCGHSA enrichment
  43. 2026-09-27 13:48 UTCEPSS rescore
  44. 2026-09-27 12:30 UTCVendor advisory
  45. 2026-09-27 12:30 UTCGHSA enrichment
  46. 2026-09-27 08:24 UTCEG score recompute
  47. 2026-09-27 08:24 UTCVendor advisory
  48. 2026-09-27 08:24 UTCGHSA enrichment
  49. 2026-09-26 15:59 UTCEPSS rescore
  50. 2026-09-26 00:28 UTCEPSS rescore
  51. 2026-09-25 11:52 UTCVendor advisory
  52. 2026-09-25 11:52 UTCGHSA enrichment
  53. 2026-09-25 06:32 UTCVendor advisory
  54. 2026-09-25 06:32 UTCGHSA enrichment
  55. 2026-09-25 02:27 UTCVendor advisory
  56. 2026-09-25 02:27 UTCGHSA enrichment
  57. 2026-09-24 17:02 UTCEG score recompute
  58. 2026-09-24 17:02 UTCVendor advisory
  59. 2026-09-24 17:02 UTCGHSA enrichment
  60. 2026-09-24 14:04 UTCEPSS rescore
  61. 2026-09-24 12:55 UTCVendor advisory
  62. 2026-09-24 12:55 UTCGHSA enrichment
  63. 2026-09-24 08:49 UTCVendor advisory
  64. 2026-09-24 08:49 UTCGHSA enrichment
  65. 2026-09-24 04:44 UTCVendor advisory
  66. 2026-09-24 04:44 UTCGHSA enrichment
  67. 2026-09-24 00:37 UTCVendor advisory
  68. 2026-09-24 00:37 UTCGHSA enrichment
  69. 2026-09-23 20:31 UTCEG score recompute
  70. 2026-09-23 20:31 UTCVendor advisory
  71. 2026-09-23 20:31 UTCGHSA enrichment
  72. 2026-09-23 17:54 UTCEPSS rescore
  73. 2026-09-23 13:09 UTCVendor advisory
  74. 2026-09-23 13:09 UTCGHSA enrichment
  75. 2026-09-23 09:03 UTCVendor advisory

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-74493?
CVE-2026-74493 is a critical vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: net/smc: fix socket use-after-free during link group termination smclgrterminate() drops conns_lock after finding a connection in lgr->conns_all, but before taking a reference on its socket. The connection is embedded in the…
When was CVE-2026-74493 disclosed?
CVE-2026-74493 was first published on August 15, 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-74493 actively exploited?
CVE-2026-74493 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (52nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-74493?
CVE-2026-74493 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-74493?
A fix for CVE-2026-74493 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-74493 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-74493

Explore →

Is Your Infrastructure Affected by CVE-2026-74493?

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

Book a Demo →Browse All CVEs