smb: smbdirect: introduce smbdirect_socket.recv_io.credits.available
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.18.11, 6.19.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 5fb9b459b3686e366640edd4e62805ef7b4de927 · fixed in e811e60e1cc79923c4388146eb1fa26a7482731e; From 5fb9b459b3686e366640edd4e62805ef7b4de927 · fixed in f99996870222b598914a1f49d7375dc23752c237; From 5fb9b459b3686e366640edd4e62805ef7b4de927 · fixed in 6e3c5052f9686192e178806e017b7377155f4bab
- Linux Linux
6.18
- KernelLinux
From 6.18.0 · fixed in 6.18.11; From 6.19.0 · fixed in 6.19.1