CVE-2026-31538
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Summary
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 Software
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| Linux | Linux | 89b021a72663c4d96d8a8b85272bb42d991a1c6f < 66c082e3d4651e8629a393a9e182b01eb50fb0a3 | affected |
| Linux | Linux | 89b021a72663c4d96d8a8b85272bb42d991a1c6f < 809cbd31aa4f87a1b889532244c9cf30eb022385 | affected |
| Linux | Linux | 89b021a72663c4d96d8a8b85272bb42d991a1c6f < 26ad87a2cfb8c1384620d1693a166ed87303046e | affected |
| Linux | Linux | 6.18 | affected |
| Linux | Linux | 0 < 6.18 | unaffected |
| Linux | Linux | 6.18.11 <= 6.18.* | unaffected |
| Linux | Linux | 6.19.1 <= 6.19.* | unaffected |
| Linux | Linux | 7.0 <= * | unaffected |
Weaknesses
References
- https://git.kernel.org/stable/c/66c082e3d4651e8629a393a9e182b01eb50fb0a3
- https://git.kernel.org/stable/c/809cbd31aa4f87a1b889532244c9cf30eb022385
- https://git.kernel.org/stable/c/26ad87a2cfb8c1384620d1693a166ed87303046e
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.