Skip to content
statance
MenuClose
unknown

CVE-2026-98449

smb: client: delete compound mids on send failure before unlock

Published 18 Oct 2026 · Source updated 10 Nov 2026 · Retrieved 2026-11-19 04:33 UTC

Monitor this CVE ↗Full CVE monitoring on Pro and Business

What happened?

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.

Description supplied by CVE Program. Formatting is simplified; follow the original advisory for full details.

Affected software and versions

Source-provided software and version information
SoftwareVersion informationFixed version
LinuxLinuxaffected: ee258d79159afed52ca9372aeb9c1a51e89b32ee to < 36a2ba21d38a86bae84441e4c8d5b10653ef341a; affected: ee258d79159afed52ca9372aeb9c1a51e89b32ee to < 59d30bdc3dd6fd3a8990f59bc7a137b1cbb3ed4e; affected: ee258d79159afed52ca9372aeb9c1a51e89b32ee to < 70783946f3b5d0c06ec7df0f5e7bec2bfad24efb; affected: ee258d79159afed52ca9372aeb9c1a51e89b32ee to < 8f6f8a48399f82f4a83f7b9f25b9707e0062a4f9; affected: 3c57a0be487088b08d9c88998f911eb4a7ba36e4; affected: 4.20.11 to < 4.21See vendor advisory
LinuxLinuxaffected: 5.0; unaffected: 0 to < 5.0; unaffected: 6.12.117 to ≤ 6.12.*; unaffected: 6.18.61 to ≤ 6.18.*; unaffected: 7.2.9 to ≤ 7.2.*; unaffected: 7.3 to ≤ *See vendor advisory

Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.

Is it being exploited?

This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.

CISA data retrieved 2026-11-19 21:16 UTC. Check CISA ↗

How to respond

  1. Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
  2. Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
  3. Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.

Sources and remediation references

This public advisory does not determine whether a particular server is affected. Records are refreshed as sources change; verify urgent decisions against the original advisory.

← Browse the public CVE feed