CVE-2026-74631

HIGHPre-NVD 8.48.4
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
8.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.4Exploit: 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: smc: fix splice entry lifetime imbalance in smc_rx_splice

smc_rx_splice() passes pages to splice_to_pipe() before taking the references that cover the lifetime of each splice entry. In the VM-backed RMB path, splice_to_pipe() may drop unqueued entries through smc_rx_spd_release(), while queued entries are released later via the pipe buffer callback.

The old post-splice accounting also derives the number of queued VM pages from an offset mutated while building the descriptor, and a multi-page splice pairs one sock_hold() with multiple sock_put() calls.

Take the page and socket references for every candidate entry before splice_to_pipe(), and drop the matching private state, page reference, and socket reference from smc_rx_spd_release() for entries that never get queued. This fixes a refcount imbalance that can underflow page refcounts and trigger a use-after-free.

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

Published

August 22, 2026

Last Modified

August 25, 2026

Advisory Details (8)

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

net: smc: fix splice entry lifetime imbalance in smc_rx_splice - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: smc: fix splice entry lifetime imbalance in smc_rx_splice - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4515c78f4d9fd577270f012efeb062ea58b3682d
generic

net: smc: fix splice entry lifetime imbalance in smc_rx_splice - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0b7d54cedea5cb158e21925ae0c6c2f5c87ed2a0
generic

net: smc: fix splice entry lifetime imbalance in smc_rx_splice - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: smc: fix splice entry lifetime imbalance in smc_rx_splice - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: smc: fix splice entry lifetime imbalance in smc_rx_splice - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: smc: fix splice entry lifetime imbalance in smc_rx_splice - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/07ad246529d136d5ef441d5ab4c305d132ff3090
generic

net: smc: fix splice entry lifetime imbalance in smc_rx_splice - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7ddc7af2ae7fc5a0c0635b245c0824c8b76de5cb

Vendor Advisories for CVE-2026-74631(1)

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 29× in last 7d / 32× 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-30 01:22 UTCEPSS rescore
  2. 2026-08-29 22:53 UTCGHSA enrichment
  3. 2026-08-29 11:54 UTCGHSA enrichment
  4. 2026-08-29 00:52 UTCEG score recompute
  5. 2026-08-29 00:52 UTCGHSA enrichment
  6. 2026-08-28 21:42 UTCEPSS rescore
  7. 2026-08-28 11:28 UTCGHSA enrichment
  8. 2026-08-28 00:27 UTCEG score recompute
  9. 2026-08-28 00:27 UTCGHSA enrichment
  10. 2026-08-27 14:25 UTCEPSS rescore
  11. 2026-08-27 13:25 UTCGHSA enrichment
  12. 2026-08-27 02:26 UTCGHSA enrichment
  13. 2026-08-26 15:27 UTCEG score recompute
  14. 2026-08-26 15:27 UTCGHSA enrichment
  15. 2026-08-26 14:47 UTCEPSS rescore
  16. 2026-08-26 04:27 UTCGHSA enrichment
  17. 2026-08-25 17:28 UTCEG score recompute
  18. 2026-08-25 17:28 UTCGHSA enrichment
  19. 2026-08-25 13:49 UTCEPSS rescore
  20. 2026-08-25 06:29 UTCEG score recompute
  21. 2026-08-25 06:29 UTCGHSA enrichment
  22. 2026-08-25 05:56 UTCEG score recompute 8.40
  23. 2026-08-25 05:56 UTCGHSA enrichment
  24. 2026-08-25 05:55 UTCMITRE cvelistV5CVSS v3 → 8.4 · severity → HIGH
  25. 2026-08-24 14:18 UTCEPSS rescore
Show 7 more
  1. 2026-08-23 13:19 UTCGHSA enrichment
  2. 2026-08-23 13:19 UTCNVD update
  3. 2026-08-23 13:06 UTCGHSA enrichment
  4. 2026-08-23 13:05 UTCMITRE cvelistV5
  5. 2026-08-22 16:24 UTCNVD update
  6. 2026-08-22 15:42 UTCEG score recompute
  7. 2026-08-22 15:35 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74631?
CVE-2026-74631 is a high vulnerability published on August 22, 2026. In the Linux kernel, the following vulnerability has been resolved: net: smc: fix splice entry lifetime imbalance in smcrxsplice smcrxsplice() passes pages to splicetopipe() before taking the references that cover the lifetime of each splice entry. In the VM-backed RMB path, splicetopipe() may drop…
When was CVE-2026-74631 disclosed?
CVE-2026-74631 was first published in the National Vulnerability Database on August 22, 2026, with the most recent update on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74631 actively exploited?
CVE-2026-74631 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.5% of all scored CVEs.
What is the CVSS score of CVE-2026-74631?
CVE-2026-74631 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2026-74631?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74631, 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-74631

Explore →

Is Your Infrastructure Affected by CVE-2026-74631?

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