CVE-2026-98449smb: client: delete compound mids on send failure before unlock
- —Not scoredno CVSS score yet
- 0.18%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: smb: client: delete compound mids on send failure before unlock When sending a compound request fails, smb_send_rqst() kicks off a reconnect. compound_send_recv() still has those mids on pending_mid_q, but it unlocks the server without removing them first. During reconnect, cifs_abort_connection() walks pending_mid_q and runs each mid callback. With no response yet, those callbacks return credits and drop in_flight. Then compound_send_recv()'s send-error path returns the same credits again. in_flight ends up decremented twice and smb2_add_credits() WARNs. syzbot hits this during SMB2_negotiate when the socket send fails. cifs_call_async() already calls delete_mid() before unlock on send failure. Do the same for compound chains and set cancelled_mid[] so the out: path does not delete them again.
Timeline
ID reserved
By Linux
- 23 days later
· 23 days later
Published
- 23 days later
· 23 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.18% · top 93% of all CVEs (14 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected ee258d79159afed52ca9372aeb9c1a51e89b32ee – < 36a2ba21d38a86bae84441e4c8d5b10653ef341a
- affected ee258d79159afed52ca9372aeb9c1a51e89b32ee – < 59d30bdc3dd6fd3a8990f59bc7a137b1cbb3ed4e
- affected ee258d79159afed52ca9372aeb9c1a51e89b32ee – < 70783946f3b5d0c06ec7df0f5e7bec2bfad24efb
- affected ee258d79159afed52ca9372aeb9c1a51e89b32ee – < 8f6f8a48399f82f4a83f7b9f25b9707e0062a4f9
- affected 3c57a0be487088b08d9c88998f911eb4a7ba36e4
- affected 4.20.11 – < 4.21
- affected 5.0
- unaffected < 5.0
- unaffected 6.12.117 – ≤ 6.12.*
- unaffected 6.18.61 – ≤ 6.18.*
- unaffected 7.2.9 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References4
- https://git.kernel.org/stable/c/36a2ba21d38a86bae84441e4c8d5b10653ef341a (opens in a new tab)
- https://git.kernel.org/stable/c/59d30bdc3dd6fd3a8990f59bc7a137b1cbb3ed4e (opens in a new tab)
- https://git.kernel.org/stable/c/70783946f3b5d0c06ec7df0f5e7bec2bfad24efb (opens in a new tab)
- https://git.kernel.org/stable/c/8f6f8a48399f82f4a83f7b9f25b9707e0062a4f9 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-103689 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-98449)Record last updated .