{"id":"DEBIAN-CVE-2024-49864","details":"In the Linux kernel, the following vulnerability has been resolved:  rxrpc: Fix a race between socket set up and I/O thread creation  In rxrpc_open_socket(), it sets up the socket and then sets up the I/O thread that will handle it.  This is a problem, however, as there's a gap between the two phases in which a packet may come into rxrpc_encap_rcv() from the UDP packet but we oops when trying to wake the not-yet created I/O thread.  As a quick fix, just make rxrpc_encap_rcv() discard the packet if there's no I/O thread yet.  A better, but more intrusive fix would perhaps be to rearrange things such that the socket creation is done by the I/O thread.","modified":"2026-09-15T09:03:13.781764209Z","published":"2024-10-21T18:15:06.203Z","upstream":["CVE-2024-49864"],"references":[{"type":"ADVISORY","url":"https://security-tracker.debian.org/tracker/CVE-2024-49864"}],"affected":[{"package":{"name":"linux","ecosystem":"Debian:13","purl":"pkg:deb/debian/linux?arch=source&distro=trixie"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.11.4-1"}]}],"ecosystem_specific":{"urgency":"not yet assigned"},"database_specific":{"source":"https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2024-49864.json"}},{"package":{"name":"linux","ecosystem":"Debian:14","purl":"pkg:deb/debian/linux?arch=source&distro=forky"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.11.4-1"}]}],"ecosystem_specific":{"urgency":"not yet assigned"},"database_specific":{"source":"https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2024-49864.json"}}],"schema_version":"1.9.0","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H"}]}