smb: client: fix double-free in SMB2_flush() replay
- 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.6.145, 6.12.96, 6.18.39, 7.1.4
- 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: total
Summary
In the Linux kernel, the following vulnerability has been resolved: smb: client: fix double-free in SMB2_flush() replay SMB2_flush() keeps its response buffer bookkeeping across replay attempts. If a replayable flush response is received and the retry then fails before cifs_send_recv() stores a replacement response, flush_exit will free the stale response pointer a second time. Reinitialize resp_buftype and rsp_iov at the top of the replay loop so cleanup only acts on response state produced by the current attempt. This fixes a double-free without changing replay handling for successful requests.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 433042a91f9373241307725b52de573933ffedbf · fixed in 6e27f40b682a5e42a2daae3ce6d96f0e0e16dedb; From 4f1fffa2376922f3d1d506e49c0fd445b023a28e · fixed in 878757163eea684750107a31ea134c103863515d; From 4f1fffa2376922f3d1d506e49c0fd445b023a28e · fixed in 3407240cde132a4b72d6429a2625a09a2f78adaf; From 4f1fffa2376922f3d1d506e49c0fd445b023a28e · fixed in 013a9a3da46c5dabcf18f65ea6a47874ba12a15d; From 4f1fffa2376922f3d1d506e49c0fd445b023a28e · fixed in 4be31c943a3a27a5a0251dbb8f5cb89059ec3d5a; From 6.6.32 · fixed in 6.6.145
- Linux Linux
6.8
- KernelLinux
fixed in 6.6.145; From 6.7.0 · fixed in 6.12.96; From 6.8.0 · fixed in 6.18.39; From 6.13.0 · fixed in 7.1.4