vsock/bpf: return early if transport is not assigned
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 58e586c30d0b6f5dc0174a41026f2b0a48c9aab6, Kernel 6771e1279dadf1d92a72e1465134257d9e6f2459 and Kernel f6abafcd32f9cfc4b1a2f820ecea70773e26d423.
In the Linux kernel, the following vulnerability has been resolved: vsock/bpf: return early if transport is not assigned Some of the core functions can only be called if the transport has been assigned. As Michal reported, a socket might have the transport at NULL, for example after a failed connect(), causing the following trace: BUG: kernel NULL pointer dereference, address: 00000000000000a0 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 12faf8067 P4D 12faf8067 PUD 113670067 PMD 0 Oops: Oops: 0000 [#1] PREEMPT SMP NOPTI CPU: 15 UID: 0 PID: 1198 Comm: a.out Not tainted 6.13.0-rc2+ RIP: 0010:vsock_connectible_has_data+0x1f/0x40 Call Trace: vsock_bpf_recvmsg+0xca/0x5e0 sock_recvmsg+0xb9/0xc0 __sys_recvfrom+0xb3/0x130 __x64_sys_recvfrom+0x20/0x30 do_syscall_64+0x93/0x180 entry_SYSCALL_64_after_hwframe+0x76/0x7e So we need to check the `vsk->transport` in vsock_bpf_recvmsg(), especially for connected sockets (stream/seqpacket) as we already do in __vsock_connectible_recvmsg().
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.4, >=634f1a7110b439c65fd8a809171c1d2d28bcea6f <58e586c30d0b6f5dc0174a41026f2b0a48c9aab6, >=634f1a7110b439c65fd8a809171c1d2d28bcea6f <6771e1279dadf1d92a72e1465134257d9e6f2459, >=634f1a7110b439c65fd8a809171c1d2d28bcea6f <f6abafcd32f9cfc4b1a2f820ecea70773e26d423 | 58e586c30d0b6f5dc0174a41026f2b0a48c9aab6, 6771e1279dadf1d92a72e1465134257d9e6f2459, f6abafcd32f9cfc4b1a2f820ecea70773e26d423 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket