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.
Fix
Patch, vendor advisory and mitigation references on NVD 3
- https://git.kernel.org/stable/c/6e3c5052f9686192e178806e017b7377155f4bab Patch
- https://git.kernel.org/stable/c/e811e60e1cc79923c4388146eb1fa26a7482731e Patch
- https://git.kernel.org/stable/c/f99996870222b598914a1f49d7375dc23752c237 Patch
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 3
- CwesCWE-362NVD modified 2026-10-19 19:17
- StatusAnalyzed → ModifiedNVD modified 2026-10-19 19:17
- First seenCVSS 7.5 · linuxNVD modified 2026-10-16 16:17
Affected (CPE criteria) 1
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*