CVE-2026-31539
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.
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/6e3c5052f9686192e178806e017b7377155f4bab
- https://git.kernel.org/stable/c/e811e60e1cc79923c4388146eb1fa26a7482731e
- https://git.kernel.org/stable/c/f99996870222b598914a1f49d7375dc23752c237
- https://www.suse.com/security/cve/CVE-2026-31539.html
- https://security-tracker.debian.org/tracker/CVE-2026-31539
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.