CVE-2026-31535
N/A
Summary
In 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.
Affected Software
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| Linux | Linux | 5fb9b459b3686e366640edd4e62805ef7b4de927 < f664e6e8a81103cb45c8802a9bc7499e0902c458 | affected |
| Linux | Linux | 5fb9b459b3686e366640edd4e62805ef7b4de927 < be8845ad5d6558703d20567d8702155598325db8 | affected |
| Linux | Linux | 5fb9b459b3686e366640edd4e62805ef7b4de927 < 9911b1ed187a770a43950bf51f340ad4b7beecba | 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/f664e6e8a81103cb45c8802a9bc7499e0902c458
- https://git.kernel.org/stable/c/be8845ad5d6558703d20567d8702155598325db8
- https://git.kernel.org/stable/c/9911b1ed187a770a43950bf51f340ad4b7beecba
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.