[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"repo-stars":3,"vuln-DEBIAN-CVE-2025-40248":6},{"stargazers_count":4,"fetched_at":5},7,"2026-06-04T14:53:31.930Z",{"id":7,"descriptions":8,"cisa":9,"weaknesses":10,"exploits":11,"aliases":12,"duplicate_of":9,"upstream":13,"downstream":16,"duplicates":17,"related":18,"reserved_at":9,"published_at":19,"modified_at":20,"state":9,"summary":21,"references_raw":23,"kevs":30,"epss":9,"epss_history":31,"metrics":32,"affected":33},"DEBIAN-CVE-2025-40248","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/e07fd95c-9a38-4eea-9638-133e38c2ec9b@rbox.co/ [2]: https://lore.kernel.org/netdev/20250317-vsock-trans-signal-race-v4-0-fc8837f3f1d4@rbox.co/ [3]: https://lore.kernel.org/netdev/60f1b7db-3099-4f6a-875e-af9f6ef194f6@rbox.co/",null,[],[],[],[14],{"_key":15},"CVE-2025-40248",[],[],[],"2025-12-04T16:16:18.240Z","2026-04-28T20:30:09.633757Z",{"cisa_kev":22,"cisa_ransomware":22,"cisa_vendor":9,"epss_severity":9,"epss_score":9,"severity":9,"severity_score":9,"severity_version":9,"severity_source":9,"severity_vector":9,"severity_status":9},false,[24],{"url":25,"sources":26,"tags":28},"https://security-tracker.debian.org/tracker/CVE-2025-40248",[27],"osv_debian",[29],"Advisory",[],[],[],[34,55],{"ecosystem":35,"name":36,"vendor":37,"product":36,"cpe_part":9,"purl_type":38,"purl_namespace":37,"purl_name":36,"source":9,"versions":39},"Debian","linux","debian","deb",[40,46,49,52],{"version":41,"is_range":42,"range_type":43,"version_start":9,"version_start_type":9,"version_end":44,"version_end_type":45,"fixed_in":9},"lt5_10_247_1",true,"ecosystem","5.10.247-1","excluding",{"version":47,"is_range":42,"range_type":43,"version_start":9,"version_start_type":9,"version_end":48,"version_end_type":45,"fixed_in":9},"lt6_1_159_1","6.1.159-1",{"version":50,"is_range":42,"range_type":43,"version_start":9,"version_start_type":9,"version_end":51,"version_end_type":45,"fixed_in":9},"lt6_12_63_1","6.12.63-1",{"version":53,"is_range":42,"range_type":43,"version_start":9,"version_start_type":9,"version_end":54,"version_end_type":45,"fixed_in":9},"lt6_17_10_1","6.17.10-1",{"ecosystem":35,"name":56,"vendor":37,"product":56,"cpe_part":9,"purl_type":38,"purl_namespace":37,"purl_name":56,"source":9,"versions":57},"linux-6.1",[58],{"version":59,"is_range":42,"range_type":43,"version_start":9,"version_start_type":9,"version_end":60,"version_end_type":45,"fixed_in":9},"lt6_1_159_1~deb11u1","6.1.159-1~deb11u1"]