CVE-2026-31535
smb: client: make use of smbdirect_socket.recv_io.credits.available
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.
Fixes and workarounds
No remediation reported in collected sources.
Missing remediation information is not evidence that no patch exists.
Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| Linux Linux |
≥ 5fb9b459b3686e366640edd4e62805ef7b4de927; < f664e6e8a81103cb45c8802a9bc7499e0902c458 (affected, git) ≥ 5fb9b459b3686e366640edd4e62805ef7b4de927; < be8845ad5d6558703d20567d8702155598325db8 (affected, git) ≥ 5fb9b459b3686e366640edd4e62805ef7b4de927; < 9911b1ed187a770a43950bf51f340ad4b7beecba (affected, git) Other versions: unaffected |
CNA: Linux |
| Linux Linux |
6.18 (affected) ≥ 0; < 6.18 (unaffected, semver) ≥ 6.18.11; ≤ 6.18.* (unaffected, semver) ≥ 6.19.1; ≤ 6.19.* (unaffected, semver) ≥ 7.0; ≤ * (unaffected, original_commit_for_fix) Other versions: affected |
CNA: Linux |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
No CVSS assessment reported. An unscored record is not a low-severity determination.
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.