CVE-2026-31535
Description
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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
OS impact
| OS | Version | Status | Fixed in |
|---|---|---|---|
| sles | affected | | |
| debian | bookworm | fixed | 0 |
| debian | bullseye | fixed | 0 |
| debian | forky | fixed | 6.18.12-1 |
| debian | sid | fixed | 6.18.12-1 |
| debian | trixie | fixed | 0 |
| linux-kernel | affected | 6.18.11 |
References
- https://git.kernel.org/stable/c/9911b1ed187a770a43950bf51f340ad4b7beecba
- https://git.kernel.org/stable/c/be8845ad5d6558703d20567d8702155598325db8
- https://git.kernel.org/stable/c/f664e6e8a81103cb45c8802a9bc7499e0902c458
- https://www.suse.com/security/cve/CVE-2026-31535.html
- https://security-tracker.debian.org/tracker/CVE-2026-31535
CWEs
CWE-367
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.