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.
References
Configurations
Configuration 1 (hide)
|
History
No history.
Information
Published : 2026-04-24 15:16
Updated : 2026-06-17 10:33
NVD link : CVE-2026-31535
Mitre link : CVE-2026-31535
CVE.ORG link : CVE-2026-31535
JSON object : View
Products Affected
linux
- linux_kernel
CWE
CWE-367
Time-of-check Time-of-use (TOCTOU) Race Condition
