CVE-2025-40168

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2025-11-12. a secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
8.1EG
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.1Exploit: None knownExposed: 0

A fix is available — apply it.

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

smc: Use __sk_dst_get() and dst_dev_rcu() in smc_clc_prfx_match().

smc_clc_prfx_match() is called from smc_listen_work() and not under RCU nor RTNL.

Using sk_dst_get(sk)->dev could trigger UAF.

Let's use __sk_dst_get() and dst_dev_rcu().

Note that the returned value of smc_clc_prfx_match() is not used in the caller.

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

Published

November 12, 2025

Last Modified

September 2, 2026

Advisory Details (2)

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

smc: Use __sk_dst_get() and dst_dev_rcu() in smc_clc_prfx_match(). - kernel/git/stable/linux.git - Linux kernel stable tree

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

smc: Use __sk_dst_get() and dst_dev_rcu() in smc_clc_prfx_match(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/235f81045c008169cc4e1955b4a64e118eebe61b

Vendor Advisories for CVE-2025-40168(12)

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

Patch Availability(16)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (6.17.0-14.14) @ questing2026-07-30ubuntu
ubuntulinux-tools-oracle-64k-6.17 (6.17.0-1007.7) @ questing2026-07-30ubuntu
ubuntulinux-tools-azure-6.17 (6.17.0-1008.8) @ questing2026-07-30ubuntu
ubuntulinux-tools-gcp-64k-6.17 (6.17.0-1007.7) @ questing2026-07-30ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1011.11) @ noble2026-07-30ubuntu
redhatkernel-0:5.14.0-570.123.1.el9_62026-06-22redhat
redhatkernel-0:4.18.0-193.195.1.el8_22026-04-22redhat
redhatkernel-0:4.18.0-372.188.1.el8_62026-04-22redhat
redhatkernel-0:4.18.0-305.189.1.el8_42026-04-22redhat
redhatkernel-0:4.18.0-477.135.1.el8_82026-04-08redhat
redhatkernel-0:6.12.0-55.63.1.el10_02026-03-09redhat
redhatkernel-0:5.14.0-611.36.1.el9_72026-03-02redhat
redhatkernel-0:6.12.0-124.39.1.el10_12026-02-25redhat
redhatkernel-rt-0:4.18.0-553.105.1.rt7.446.el8_102026-02-17redhat
redhatkernel-0:4.18.0-553.105.1.el8_102026-02-16redhat
linuxKernel @ 6.17.3—osv

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
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (56 versions)6.1.187-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (176 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.17.5-1~exp1 (75 versions)6.17.6-1—

Additional Vendor Advisories

(5)

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 6× 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.

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

  1. 2026-09-18 19:27 UTCEPSS rescore
  2. 2026-09-17 19:29 UTCEPSS rescore
  3. 2026-09-16 14:07 UTCEPSS rescore
  4. 2026-09-16 05:14 UTCEPSS rescore
  5. 2026-09-13 16:46 UTCEPSS rescore
  6. 2026-09-12 15:00 UTCEPSS rescore
  7. 2026-09-11 14:52 UTCEPSS rescore
  8. 2026-09-11 09:35 UTCEPSS rescore
  9. 2026-09-10 09:33 UTCEPSS rescore
  10. 2026-09-08 21:59 UTCEPSS rescore
  11. 2026-09-07 16:00 UTCEPSS rescore
  12. 2026-09-06 13:46 UTCEPSS rescore
  13. 2026-09-04 05:05 UTCEPSS rescore
  14. 2026-09-02 14:11 UTCEPSS rescore
  15. 2026-09-02 13:45 UTCEG score recompute
  16. 2026-09-02 13:45 UTCVendor advisory
  17. 2026-09-02 13:45 UTCGHSA enrichment
  18. 2026-09-02 12:56 UTCEG score recompute
  19. 2026-09-02 12:56 UTCVendor advisory
  20. 2026-09-02 12:56 UTCGHSA enrichment
  21. 2026-09-01 13:53 UTCEPSS rescore
  22. 2026-09-01 04:38 UTCEPSS rescore
  23. 2026-08-30 19:16 UTCEPSS rescore
  24. 2026-08-30 01:21 UTCEPSS rescore
  25. 2026-08-28 21:40 UTCEPSS rescore
Show 75 more
  1. 2026-08-27 14:24 UTCEPSS rescore
  2. 2026-08-26 14:45 UTCEPSS rescore
  3. 2026-08-25 13:48 UTCEPSS rescore
  4. 2026-08-23 00:18 UTCEPSS rescore
  5. 2026-08-21 23:48 UTCEPSS rescore
  6. 2026-08-20 22:54 UTCEPSS rescore
  7. 2026-08-20 20:31 UTCOSV refresh
  8. 2026-08-19 17:03 UTCEPSS rescore
  9. 2026-08-19 17:03 UTCEPSS rescore
  10. 2026-08-18 13:47 UTCEPSS rescore
  11. 2026-08-17 13:46 UTCEPSS rescore
  12. 2026-08-16 14:55 UTCEPSS rescore
  13. 2026-08-16 02:13 UTCEPSS rescore
  14. 2026-08-15 01:29 UTCEPSS rescore
  15. 2026-08-13 21:59 UTCEPSS rescore
  16. 2026-08-12 13:50 UTCEPSS rescore
  17. 2026-08-09 13:46 UTCEPSS rescore
  18. 2026-08-08 16:36 UTCEPSS rescore
  19. 2026-08-07 16:26 UTCEPSS rescore
  20. 2026-08-06 13:46 UTCEPSS rescore
  21. 2026-08-05 12:52 UTCEG score recompute
  22. 2026-08-05 12:52 UTCVendor advisory
  23. 2026-08-05 12:52 UTCGHSA enrichment
  24. 2026-08-04 15:09 UTCEPSS rescore
  25. 2026-08-04 10:37 UTCEPSS rescore
  26. 2026-08-02 02:26 UTCEPSS rescore
  27. 2026-08-01 04:15 UTCEPSS rescore
  28. 2026-07-30 16:27 UTCEPSS rescore
  29. 2026-07-30 06:27 UTCEG score recompute▲ 8.10
  30. 2026-07-30 06:27 UTCVendor advisory
  31. 2026-07-30 06:27 UTCGHSA enrichment
  32. 2026-07-30 06:18 UTCMITRE cvelistV5CVSS v3 → 8.1 · severity → HIGH
  33. 2026-07-30 01:29 UTCEPSS rescore
  34. 2026-07-28 15:35 UTCEPSS rescore
  35. 2026-07-27 07:09 UTCOSV refresh
  36. 2026-07-26 14:54 UTCEPSS rescore
  37. 2026-07-25 14:17 UTCEPSS rescore
  38. 2026-07-25 14:17 UTCEPSS rescore
  39. 2026-07-24 14:17 UTCEPSS rescore
  40. 2026-07-23 02:55 UTCEG score recompute
  41. 2026-07-22 14:07 UTCEPSS rescore
  42. 2026-07-22 14:07 UTCEPSS rescore
  43. 2026-07-21 15:24 UTCEPSS rescore
  44. 2026-07-20 17:07 UTCEPSS rescore
  45. 2026-07-19 14:30 UTCEPSS rescore
  46. 2026-07-19 14:30 UTCEPSS rescore
  47. 2026-07-19 02:28 UTCEPSS rescore
  48. 2026-07-19 02:28 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 01:47 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-04 06:30 UTCEPSS rescore
  70. 2026-07-01 15:06 UTCEPSS rescore
  71. 2026-07-01 15:06 UTCEPSS rescore
  72. 2026-06-30 23:22 UTCEPSS rescore
  73. 2026-06-30 23:22 UTCEPSS rescore
  74. 2026-06-29 14:06 UTCEPSS rescore
  75. 2026-06-29 14:06 UTCEPSS rescore

Related CVEs(same product + same vendor)

Frequently asked(5)

What is CVE-2025-40168?
CVE-2025-40168 is a high vulnerability published on November 12, 2025. In the Linux kernel, the following vulnerability has been resolved: smc: Use skdstget() and dstdevrcu() in smcclcprfx_match(). smcclcprfxmatch() is called from smclisten_work() and not under RCU nor RTNL. Using skdstget(sk)->dev could trigger UAF. Let's use skdstget() and dstdevrcu(). Note that the…
When was CVE-2025-40168 disclosed?
CVE-2025-40168 was first published in the National Vulnerability Database on November 12, 2025, with the most recent update on September 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-40168 actively exploited?
CVE-2025-40168 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 66.9% of all scored CVEs.
What is the CVSS score of CVE-2025-40168?
CVE-2025-40168 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2025-40168?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-40168, 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-40168

Explore →

Is Your Infrastructure Affected by CVE-2025-40168?

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

Start Free Scan →Browse All CVEs