Description
In the Linux kernel, the following vulnerability has been resolved: smb: client: make use of smbdirect_socket.recv_io.credits.available The logic off managing recv credits by counting posted recv_io and granted credits is racy. That's because the peer might already consumed a credit, but between receiving the incoming recv at the hardware and processing the completion in the 'recv_done' functions we likely have a window where we grant credits, which don't really exist. So we better have a decicated counter for the available credits, which will be incremented when we posted new recv buffers and drained when we grant the credits to the peer.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
5fb9b459b3686e366640edd4e62805ef7b4de927 to < f664e6e8a81103cb45c8802a9bc7499e0902c458affected5fb9b459b3686e366640edd4e62805ef7b4de927 to < be8845ad5d6558703d20567d8702155598325db8affected5fb9b459b3686e366640edd4e62805ef7b4de927 to < 9911b1ed187a770a43950bf51f340ad4b7beecbaaffected
Linux Linux
Default version status: affected
6.18affected0 to < 6.18unaffected6.18.11 to ≤ 6.18.*unaffected6.19.1 to ≤ 6.19.*unaffected7.0 to ≤ *unaffected