PT-2026-116669 · Linux · Linux
CVE-2026-98450
·
Published
2026-10-18
·
Updated
2026-10-18
None
No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
In the Linux kernel, the following vulnerability has been resolved:
smb: client: close completed creates on compound wait errors
compound send recv() waits for responses in order. If a later wait is
interrupted, or if a later MID fails during response synchronization, an
earlier CREATE may already have opened a remote handle. The earlier mid
is then released without invoking handle cancelled mid(), leaving the
remote handle open because no FID was copied to the caller.
Mark completed earlier mids as cancelled when a compound wait or MID
synchronization aborts. Keep their response buffers attached while the
MIDs are synchronized, and transfer them only after synchronization of
the processed responses, so the release path can inspect successful
CREATE responses and queue SMB2 close() after a later failure. Account for
a remote open only after the close work is allocated and before it is
queued, since the caller has not yet updated num remote opens. Mark the
create+close compound used by smb2 unlink() so it is not closed again.
Non-CREATE responses and compounds that already include a close keep their
existing behavior.
Found an issue in the description? Have something to add? Feel free to write us 👾
Related Identifiers
Affected Products
Linux