CVE-2025-40176

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2025-11-12. the CNA's CVSS baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
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%CVSS: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

tls: wait for pending async decryptions if tls_strp_msg_hold fails

Async decryption calls tls_strp_msg_hold to create a clone of the input skb to hold references to the memory it uses. If we fail to allocate that clone, proceeding with async decryption can lead to various issues (UAF on the skb, writing into userspace memory after the recv() call has returned).

In this case, wait for all pending decryption requests.

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

Published

November 12, 2025

Last Modified

August 5, 2026

Advisory Details (5)

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

tls: wait for pending async decryptions if tls_strp_msg_hold fails - kernel/git/stable/linux.git - Linux kernel stable tree

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

tls: wait for pending async decryptions if tls_strp_msg_hold fails - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4fc109d0ab196bd943b7451276690fb6bb48c2e0
generic

tls: wait for pending async decryptions if tls_strp_msg_hold fails - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/39dec4ea3daf77f684308576baf483b55ca7f160
generic

tls: wait for pending async decryptions if tls_strp_msg_hold fails - kernel/git/stable/linux.git - Linux kernel stable tree

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

tls: wait for pending async decryptions if tls_strp_msg_hold fails - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9f83fd0c179e0f458e824e417f9d5ad53443f685

Patch Availability(23)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1051.57) @ noble2026-05-21ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-05-21ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1052.55+fips1) @ noble2026-05-21ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2040.41) @ noble2026-05-21ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1049.52.1) @ noble2026-05-21ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1050.53~22.04.1) @ jammy2026-05-21ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1052.58+fips1) @ noble2026-05-21ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1029.30) @ noble2026-05-21ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1045.46~22.04.1) @ jammy2026-05-21ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.17.0-14.14) @ questing2026-05-21ubuntu
ubuntulinux-tools-gcp-64k-6.17 (6.17.0-1007.7) @ questing2026-05-21ubuntu
ubuntulinux-tools-oracle-64k-6.17 (6.17.0-1007.7) @ questing2026-05-21ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1011.11) @ noble2026-05-21ubuntu
ubuntulinux-tools-azure-6.17 (6.17.0-1008.8) @ questing2026-05-21ubuntu
ubuntulinux-virtual-6.8 (6.8.0-106.106) @ noble2026-05-21ubuntu
redhatkernel-0:6.12.0-55.54.1.el10_02026-01-19redhat
redhatkernel-rt-0:5.14.0-284.152.1.rt14.437.el9_22026-01-14redhat
redhatkernel-0:5.14.0-284.152.1.el9_22026-01-14redhat
redhatkernel-0:5.14.0-427.106.1.el9_42026-01-13redhat
redhatkernel-0:5.14.0-570.77.1.el9_62026-01-12redhat
redhatkernel-0:6.12.0-124.27.1.el10_12026-01-12redhat
redhatkernel-0:5.14.0-611.16.1.el9_72025-12-17redhat
linuxKernel @ 6.1.158osv

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 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.153-1~deb11u1 (12 versions)6.1.158-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (44 versions)6.1.158-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.57-1~bpo12+1 (6 versions)6.12.57-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.17.5-1~exp1 (75 versions)6.17.6-1

Additional Vendor Advisories

(16)

Data Freshness Timeline

(refreshed 5× in last 7d / 27× 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 176 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2025-40176?
CVE-2025-40176 is a critical vulnerability published on November 12, 2025. In the Linux kernel, the following vulnerability has been resolved: tls: wait for pending async decryptions if tlsstrpmsg_hold fails Async decryption calls tlsstrpmsg_hold to create a clone of the input skb to hold references to the memory it uses. If we fail to allocate that clone, proceeding with…
When was CVE-2025-40176 disclosed?
CVE-2025-40176 was first published in the National Vulnerability Database on November 12, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-40176 actively exploited?
CVE-2025-40176 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 64.0% of all scored CVEs.
What is the CVSS score of CVE-2025-40176?
CVE-2025-40176 has a CVSS v4.0 base score of 9.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2025-40176?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-40176, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-40176

Explore →

Is Your Infrastructure Affected by CVE-2025-40176?

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