Description
In the Linux kernel, the following vulnerability has been resolved: smb: smbdirect: introduce 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.
Product status
5fb9b459b3686e366640edd4e62805ef7b4de927 (git) before e811e60e1cc79923c4388146eb1fa26a7482731e
5fb9b459b3686e366640edd4e62805ef7b4de927 (git) before f99996870222b598914a1f49d7375dc23752c237
5fb9b459b3686e366640edd4e62805ef7b4de927 (git) before 6e3c5052f9686192e178806e017b7377155f4bab
6.18
Any version before 6.18
6.18.11 (semver)
6.19.1 (semver)
7.0 (original_commit_for_fix)
References
git.kernel.org/...c/e811e60e1cc79923c4388146eb1fa26a7482731e
git.kernel.org/...c/f99996870222b598914a1f49d7375dc23752c237
git.kernel.org/...c/6e3c5052f9686192e178806e017b7377155f4bab