Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-40248vsock: Ignore signal/timeout on connect() if already established

Description

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 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. 2. 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. 3. 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]/

Timeline

  1. ID reserved

    By Linux

  2. · 8 months later

    Published

  3. · 8 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-40248, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Deferred3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (14 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected d021c344051af91f42c5ba9fdedc176740cbd238 – < 3f71753935d648082a8279a97d30efe6b85be680
    • affected d021c344051af91f42c5ba9fdedc176740cbd238 – < da664101fb4a0de5cb70d2bae6a650df954df2af
    • affected d021c344051af91f42c5ba9fdedc176740cbd238 – < 67432915145848658149683101104e32f9fd6559
    • affected d021c344051af91f42c5ba9fdedc176740cbd238 – < eeca93f06df89be5a36305b7b9dae1ed65550dfc
    • affected d021c344051af91f42c5ba9fdedc176740cbd238 – < 5998da5a8208ae9ad7838ba322bccb2bdcd95e81
    • affected d021c344051af91f42c5ba9fdedc176740cbd238 – < f1c170cae285e4b8f61be043bb17addc3d0a14b5
    • affected d021c344051af91f42c5ba9fdedc176740cbd238 – < ab6b19f690d89ae4709fba73a3c4a7911f495b7a
    • affected d021c344051af91f42c5ba9fdedc176740cbd238 – < 002541ef650b742a198e4be363881439bb9d86b4
  • Linux · Linux

    • affected 3.9
    • unaffected < 3.9
    • unaffected 5.4.302 – ≤ 5.4.*
    • unaffected 5.10.247 – ≤ 5.10.*
    • unaffected 5.15.197 – ≤ 5.15.*
    • unaffected 6.1.159 – ≤ 6.1.*
    • unaffected 6.6.118 – ≤ 6.6.*
    • unaffected 6.12.60 – ≤ 6.12.*
    • unaffected 6.17.10 – ≤ 6.17.*
    • unaffected 6.18 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-40248 badge
[![CVE-2025-40248](https://cveledger.app/badge/CVE-2025-40248.svg)](https://cveledger.app/cve/CVE-2025-40248)

Record last updated .