CVE-2025-40342

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

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

nvme-fc: use lock accessing port_state and rport state

nvme_fc_unregister_remote removes the remote port on a lport object at any point in time when there is no active association. This races with with the reconnect logic, because nvme_fc_create_association is not taking a lock to check the port_state and atomically increase the active count on the rport.

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

Published

December 9, 2025

Last Modified

August 5, 2026

Advisory Details (7)

Auto-updated Jul 30, 2026
No patch confirmed yet.
generic

nvme-fc: use lock accessing port_state and rport state - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/891cdbb162ccdb079cd5228ae43bdeebce8597ad
generic

nvme-fc: use lock accessing port_state and rport state - kernel/git/stable/linux.git - Linux kernel stable tree

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

nvme-fc: use lock accessing port_state and rport state - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9950af4303942081dc8c7a5fdc3688c17c7eb6c0
generic

nvme-fc: use lock accessing port_state and rport state - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/25f4bf1f7979a7871974fd36c79d69ff1cf4b446
generic

nvme-fc: use lock accessing port_state and rport state - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4253e0a4546138a2bf9cb6acf66b32fee677fc7c
generic

nvme-fc: use lock accessing port_state and rport state - kernel/git/stable/linux.git - Linux kernel stable tree

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

nvme-fc: use lock accessing port_state and rport state - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/de3d91af47bc015031e7721b100a29989f6498a5

Vendor Advisories for CVE-2025-40342(1)

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

Patch Availability(26)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (6.17.0-14.14) @ questing2026-07-30ubuntu
ubuntulinux-tools-gcp-64k-6.17 (6.17.0-1007.7) @ questing2026-07-30ubuntu
ubuntulinux-tools-oracle-64k-6.17 (6.17.0-1007.7) @ questing2026-07-30ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1011.11) @ noble2026-07-30ubuntu
ubuntulinux-virtual-6.8 (6.8.0-106.106) @ noble2026-07-30ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1067 (5.15.0-1067.71) @ jammy2026-07-30ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1049.52.1) @ noble2026-07-30ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1052.55+fips1) @ noble2026-07-30ubuntu
ubuntulinux-tools-gcp-fips-5.15 (5.15.0.1103.93) @ jammy2026-07-30ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1045.46) @ noble2026-07-30ubuntu
ubuntulinux-tools-gke-5.15 (5.15.0.1099.98) @ jammy2026-07-30ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-07-30ubuntu
ubuntulinux-tools-azure-6.17 (6.17.0-1008.8) @ questing2026-07-30ubuntu
ubuntulinux-tools-realtime-5.15 (5.15.0.1102.106) @ jammy2026-07-30ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1094.98) @ jammy2026-07-30ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1050.53~22.04.1) @ jammy2026-07-30ubuntu
ubuntulinux-tools-nvidia-tegra-igx-rt-5.15 (5.15.0.1044.46) @ jammy2026-07-30ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1051.57) @ noble2026-07-30ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2040.41) @ noble2026-07-30ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1097.95) @ jammy2026-07-30ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1109.94) @ jammy2026-07-30ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1052.58+fips1) @ noble2026-07-30ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1109.107) @ jammy2026-07-30ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1110.119~20.04.1) @ focal2026-07-30ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1029.30) @ noble2026-07-30ubuntu
linuxKernel @ 5.10.247osv

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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (47 versions)5.10.247-1
linux-6.16.1.106-3~deb11u1 ... 6.1.158-1~deb11u1 (13 versions)6.1.159-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (45 versions)6.1.159-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.63-1~bpo12+1 (8 versions)6.12.63-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.17.8-1~bpo13+1 (79 versions)6.17.8-1

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

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 186 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2025-40342?
CVE-2025-40342 is a high vulnerability published on December 9, 2025. In the Linux kernel, the following vulnerability has been resolved: nvme-fc: use lock accessing port_state and rport state nvmefcunregister_remote removes the remote port on a lport object at any point in time when there is no active association. This races with with the reconnect logic, because…
When was CVE-2025-40342 disclosed?
CVE-2025-40342 was first published in the National Vulnerability Database on December 9, 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-40342 actively exploited?
CVE-2025-40342 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 69.6% of all scored CVEs.
What is the CVSS score of CVE-2025-40342?
CVE-2025-40342 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2025-40342?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-40342, 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-40342

Explore →

Is Your Infrastructure Affected by CVE-2025-40342?

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