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.
References
Configurations
Configuration 1 (hide)
|
History
11 Nov 2026, 23:10
| Type | Values Removed | Values Added |
|---|---|---|
| Summary |
|
19 Oct 2026, 19:17
| Type | Values Removed | Values Added |
|---|---|---|
| CWE | CWE-362 |
Information
Published : 2026-04-24 15:16
Updated : 2026-11-11 23:10
NVD link : CVE-2026-31539
Mitre link : CVE-2026-31539
CVE.ORG link : CVE-2026-31539
JSON object : View
Products Affected
linux
- linux_kernel
CWE
NVD-CWE-noinfo
CWE-362
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
