Skip to main content
VulnerabilityPublished Updated

CVE-2026-98450: Linux kernel · smb: client: close completed creates on compound wait errors

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in 253612499ce9b4cd7bb922fe507ec204bddd9313 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:07 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 253612499ce9b4cd7bb922fe507ec204bddd9313, 224b56b7c02b2bfb1f5bee18d5f56ae6b052be44, 8afc80156b1d9e2cfd02d42c255305fad95b59fc +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ e0bba0b8548179b696e86c158ea8f45f2ef6ad14, < 253612499ce9b4cd7bb922fe507ec204bddd9313
Fixed in
  • 253612499ce9b4cd7bb922fe507ec204bddd9313
LinuxLinuxAffected
  • ≥ e0bba0b8548179b696e86c158ea8f45f2ef6ad14, < 224b56b7c02b2bfb1f5bee18d5f56ae6b052be44
Fixed in
  • 224b56b7c02b2bfb1f5bee18d5f56ae6b052be44
LinuxLinuxAffected
  • ≥ e0bba0b8548179b696e86c158ea8f45f2ef6ad14, < 8afc80156b1d9e2cfd02d42c255305fad95b59fc
Fixed in
  • 8afc80156b1d9e2cfd02d42c255305fad95b59fc
LinuxLinuxAffected
  • ≥ e0bba0b8548179b696e86c158ea8f45f2ef6ad14, < 6c5c547f037bc18f0b8d0b5db5a648f8f630ce85
Fixed in
  • 6c5c547f037bc18f0b8d0b5db5a648f8f630ce85
LinuxLinuxAffected
  • ≥ e0bba0b8548179b696e86c158ea8f45f2ef6ad14, < 2cb07d1a6a30283dbfc809c8036bc1fd103d59fa
Fixed in
  • 2cb07d1a6a30283dbfc809c8036bc1fd103d59fa
LinuxLinuxAffected
  • =4.19
Fixed in–

Description

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.

References

Community reviews

Loading reviews…