CVE-2025-21854
- Source
- https://nvd.nist.gov/vuln/detail/CVE-2025-21854
- Import Source
- https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2025-21854.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/CVE-2025-21854
- Downstream
- Related
- Published
- 2025-03-12T09:42:08Z
- Modified
- 2025-10-10T07:20:30.257030Z
- Severity
-
- 5.5 (Medium) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H CVSS Calculator
- Summary
- sockmap, vsock: For connectible sockets allow only connected
- Details
-
In the Linux kernel, the following vulnerability has been resolved:
sockmap, vsock: For connectible sockets allow only connected
sockmap expects all vsocks to have a transport assigned, which is expressed in vsockproto::psockupdateskprot(). However, there is an edge case where an unconnected (connectible) socket may lose its previously assigned transport. This is handled with a NULL check in the vsock/BPF recv path.
Another design detail is that listening vsocks are not supposed to have any transport assigned at all. Which implies they are not supported by the sockmap. But this is complicated by the fact that a socket, before switching to TCP_LISTEN, may have had some transport assigned during a failed connect() attempt. Hence, we may end up with a listening vsock in a sockmap, which blows up quickly:
KASAN: null-ptr-deref in range [0x0000000000000120-0x0000000000000127] CPU: 7 UID: 0 PID: 56 Comm: kworker/7:0 Not tainted 6.14.0-rc1+ Workqueue: vsock-loopback vsockloopbackwork RIP: 0010:vsockreadskb+0x4b/0x90 Call Trace: skpsockverdictdataready+0xa4/0x2e0 virtiotransportrecvpkt+0x1ca8/0x2acc vsockloopbackwork+0x27d/0x3f0 processonework+0x846/0x1420 workerthread+0x5b3/0xf80 kthread+0x35a/0x700 retfromfork+0x2d/0x70 retfromfork_asm+0x1a/0x30
For connectible sockets, instead of relying solely on the state of vsk->transport, tell sockmap to only allow those representing established connections. This aligns with the behaviour for AFINET and AFUNIX.
- References
-
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- https://git.kernel.org/stable/c/22b683217ad2112791a708693cb236507abd637a
- https://git.kernel.org/stable/c/8fb5bb169d17cdd12c2dcc2e96830ed487d77a0f
- https://git.kernel.org/stable/c/cc9a7832ede53ade1ba9991f0e27314caa4029d8
- https://git.kernel.org/stable/c/f7b473e35986835cc2813fef7b9d40336a09247e
Affected packages
Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected ranges
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced634f1a7110b439c65fd8a809171c1d2d28bcea6fFixedcc9a7832ede53ade1ba9991f0e27314caa4029d8
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced634f1a7110b439c65fd8a809171c1d2d28bcea6fFixed22b683217ad2112791a708693cb236507abd637a
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced634f1a7110b439c65fd8a809171c1d2d28bcea6fFixedf7b473e35986835cc2813fef7b9d40336a09247e
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced634f1a7110b439c65fd8a809171c1d2d28bcea6fFixed8fb5bb169d17cdd12c2dcc2e96830ed487d77a0f