smb: client: make use of smbdirect_socket.recv_io.credits.available
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.18.116.19.17.0In 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.
From the CVE record · Linux
The Linux kernel SMB client has a race in how it counts available receive credits. A network peer may be granted credits that are not actually available when a receive arrives before its completion is processed. The input does not specify authentication requirements, user interaction, or a further impact.
Engineers running the Linux kernel SMB client should check their kernel version; affected versions are not specified.