CVE-2025-40248

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

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

vsock: Ignore signal/timeout on connect() if already established

During connect(), acting on a signal/timeout by disconnecting an already established socket leads to several issues:

  • connect() invoking vsock_transport_cancel_pkt() ->
virtio_transport_purge_skbs() may race with sendmsg() invoking virtio_transport_get_credit(). This results in a permanently elevated vvs->bytes_unsent. Which, in turn, confuses the SOCK_LINGER handling.
  • connect() resetting a connected socket's state may race with socket
being placed in a sockmap. A disconnected socket remaining in a sockmap breaks sockmap's assumptions. And gives rise to WARNs.
  • connect() transitioning SS_CONNECTED -> SS_UNCONNECTED allows for a
transport change/drop after TCP_ESTABLISHED. Which poses a problem for any simultaneous sendmsg() or connect() and may result in a use-after-free/null-ptr-deref.

Do not disconnect socket on signal/timeout. Keep the logic for unconnected sockets: they don't linger, can't be placed in a sockmap, are rejected by sendmsg().

[1]: https://lore.kernel.org/netdev/[email protected]/ [2]: https://lore.kernel.org/netdev/[email protected]/ [3]: https://lore.kernel.org/netdev/[email protected]/

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

Published

December 4, 2025

Last Modified

August 5, 2026

Advisory Details (9)

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

SSA-253495

https://cert-portal.siemens.com/productcert/html/ssa-253495.html
generic

vsock: Ignore signal/timeout on connect() if already established - kernel/git/stable/linux.git - Linux kernel stable tree

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

vsock: Ignore signal/timeout on connect() if already established - kernel/git/stable/linux.git - Linux kernel stable tree

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

vsock: Ignore signal/timeout on connect() if already established - kernel/git/stable/linux.git - Linux kernel stable tree

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

vsock: Ignore signal/timeout on connect() if already established - kernel/git/stable/linux.git - Linux kernel stable tree

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

vsock: Ignore signal/timeout on connect() if already established - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/67432915145848658149683101104e32f9fd6559
generic

vsock: Ignore signal/timeout on connect() if already established - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5998da5a8208ae9ad7838ba322bccb2bdcd95e81
generic

vsock: Ignore signal/timeout on connect() if already established - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3f71753935d648082a8279a97d30efe6b85be680
generic

vsock: Ignore signal/timeout on connect() if already established - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/002541ef650b742a198e4be363881439bb9d86b4

Vendor Advisories for CVE-2025-40248(15)

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

Patch Availability(24)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1052.58+fips1) @ noble2026-05-21ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1109.94) @ jammy2026-05-21ubuntu
ubuntulinux-tools-raspi-6.17 (6.17.0-1010.10) @ questing2026-05-21ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.17.0-19.19) @ questing2026-05-21ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1067 (5.15.0-1067.71) @ jammy2026-05-21ubuntu
redhatkpatch-patch2026-03-09redhat
redhatkernel-0:5.14.0-284.155.1.el9_22026-02-04redhat
redhatkernel-0:5.14.0-427.109.1.el9_42026-02-04redhat
redhatkernel-rt-0:5.14.0-284.155.1.rt14.440.el9_22026-02-04redhat
redhatkernel-0:4.18.0-305.184.1.el8_42026-02-04redhat
redhatkernel-rt-0:3.10.0-1160.146.1.rt56.1298.el72026-02-02redhat
redhatkernel-0:5.14.0-570.84.1.el9_62026-02-02redhat
redhatkernel-0:6.12.0-55.58.1.el10_02026-02-02redhat
redhatkernel-0:6.12.0-124.31.1.el10_12026-02-02redhat
redhatkernel-0:3.10.0-1160.146.1.el72026-01-29redhat
redhatkernel-0:4.18.0-477.126.1.el8_82026-01-28redhat
redhatkernel-0:4.18.0-193.183.1.el8_22026-01-28redhat
redhatkernel-0:4.18.0-372.177.1.el8_62026-01-28redhat
redhatkernel-0:5.14.0-70.163.1.el9_02026-01-28redhat
redhatkernel-rt-0:5.14.0-70.163.1.rt21.235.el9_02026-01-28redhat
redhatkernel-0:5.14.0-611.26.1.el9_72026-01-26redhat
redhatkernel-0:4.18.0-553.97.1.el8_102026-01-26redhat
redhatkernel-rt-0:4.18.0-553.97.1.rt7.438.el8_102026-01-26redhat
linuxKernel @ 5.4.302—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

(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.9-1 (78 versions)6.17.10-1—

Additional Vendor Advisories

(11)

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 4× in last 7d / 25× 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 174 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2025-40248?
CVE-2025-40248 is a high vulnerability published on December 4, 2025. In the Linux kernel, the following vulnerability has been resolved: vsock: Ignore signal/timeout on connect() if already established During connect(), acting on a signal/timeout by disconnecting an already established socket leads to several issues: 1. connect() invoking vsocktransportcancel_pkt()…
When was CVE-2025-40248 disclosed?
CVE-2025-40248 was first published in the National Vulnerability Database on December 4, 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-40248 actively exploited?
CVE-2025-40248 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 94.8% of all scored CVEs.
What is the CVSS score of CVE-2025-40248?
CVE-2025-40248 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2025-40248?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-40248, 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-40248

Explore →

Is Your Infrastructure Affected by CVE-2025-40248?

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

Start Free Scan →Browse All CVEs