Answer in brief
CVE-2026-98450 records a Unknown severity vulnerability in smb: client: close completed creates on compound wait errors. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=e0bba0b8548179b696e86c158ea8f45f2ef6ad14 <2cb07d1a6a30283dbfc809c8036bc1fd103d59fa || >=e0bba0b8548179b696e86c158ea8f45f2ef6ad14 <224b56b7c02b2bfb1f5bee18d5f56ae6b052be44 || >=e0bba0b8548179b696e86c158ea8f45f2ef6ad14 <253612499ce9b4cd7bb922fe507ec204bddd9313 || >=e0bba0b8548179b696e86c158ea8f45f2ef6ad14 <6c5c547f037bc18f0b8d0b5db5a648f8f630ce85 | 2cb07d1a6a30283dbfc809c8036bc1fd103d59fa, 224b56b7c02b2bfb1f5bee18d5f56ae6b052be44, 253612499ce9b4cd7bb922fe507ec204bddd9313, 6c5c547f037bc18f0b8d0b5db5a648f8f630ce85 |
| Linux/Linuxgeneric | 4.19 | Not reported |
| Linux/Linuxgeneric | >=e0bba0b8548179b696e86c158ea8f45f2ef6ad14 <8afc80156b1d9e2cfd02d42c255305fad95b59fc || >=e0bba0b8548179b696e86c158ea8f45f2ef6ad14 <2cb07d1a6a30283dbfc809c8036bc1fd103d59fa || >=e0bba0b8548179b696e86c158ea8f45f2ef6ad14 <224b56b7c02b2bfb1f5bee18d5f56ae6b052be44 || >=e0bba0b8548179b696e86c158ea8f45f2ef6ad14 <253612499ce9b4cd7bb922fe507ec204bddd9313 || >=e0bba0b8548179b696e86c158ea8f45f2ef6ad14 <6c5c547f037bc18f0b8d0b5db5a648f8f630ce85 | 8afc80156b1d9e2cfd02d42c255305fad95b59fc, 2cb07d1a6a30283dbfc809c8036bc1fd103d59fa, 224b56b7c02b2bfb1f5bee18d5f56ae6b052be44, 253612499ce9b4cd7bb922fe507ec204bddd9313, 6c5c547f037bc18f0b8d0b5db5a648f8f630ce85 |
Published upstream
Oct 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 18, 2026
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.
Quoted source text, attributed separately from HOL analysis.