Description
In the Linux kernel, the following vulnerability has been resolved: smb: server: 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. This fixes regression Namjae reported with the 6.18 release.
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
89b021a72663c4d96d8a8b85272bb42d991a1c6f to < 66c082e3d4651e8629a393a9e182b01eb50fb0a3affected89b021a72663c4d96d8a8b85272bb42d991a1c6f to < 809cbd31aa4f87a1b889532244c9cf30eb022385affected89b021a72663c4d96d8a8b85272bb42d991a1c6f to < 26ad87a2cfb8c1384620d1693a166ed87303046eaffected
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