CVE-2026-98450: smb: client: close completed creates on compound wait errors
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- Fixed version: Linux Linux 224b56b7c02b2bfb1f5bee18d5f56ae6b052be44, 253612499ce9b4cd7bb922fe507ec204bddd9313, 2cb07d1a6a30283dbfc809c8036bc1fd103d59fa; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
Low priority for now. Upgrade to Linux Linux 224b56b7c02b2bfb1f5bee18d5f56ae6b052be44, 253612499ce9b4cd7bb922fe507ec204bddd9313, 2cb07d1a6a30283dbfc809c8036bc1fd103d59fa; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 18, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.19affected
- e0bba0b8548179b696e86c158ea8f45f2ef6ad14 and later · before da83fed81241b03fd0e7ccf0091b051cf420d8d2affected · git
- e0bba0b8548179b696e86c158ea8f45f2ef6ad14 and later · before e94370cf2b76e913a997e9a633ab521a45029284affected · git
- e0bba0b8548179b696e86c158ea8f45f2ef6ad14 and later · before c8c6c7e665af4dba75a02f4c9bad3ae2ce341619affected · git
- e0bba0b8548179b696e86c158ea8f45f2ef6ad14 and later · before 8afc80156b1d9e2cfd02d42c255305fad95b59fcaffected · git
- e0bba0b8548179b696e86c158ea8f45f2ef6ad14 and later · before 2cb07d1a6a30283dbfc809c8036bc1fd103d59faaffected · git
- e0bba0b8548179b696e86c158ea8f45f2ef6ad14 and later · before 224b56b7c02b2bfb1f5bee18d5f56ae6b052be44affected · git
- e0bba0b8548179b696e86c158ea8f45f2ef6ad14 and later · before 253612499ce9b4cd7bb922fe507ec204bddd9313affected · git
- e0bba0b8548179b696e86c158ea8f45f2ef6ad14 and later · before 6c5c547f037bc18f0b8d0b5db5a648f8f630ce85affected · git
- before 4.19not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:12 | linux-6.12 | before 6.12.113-1~deb12u1 | 6.12.113-1~deb12u1 |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.9-1 | 7.2.9-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-98448Oct 18, 2026 · xfs: release orphanage dir inode if chown fails0Monitor
- ← EarlierCVE-2026-98449Oct 18, 2026 · smb: client: delete compound mids on send failure before unlock0Monitor
- Later →CVE-2026-98451Oct 18, 2026 · smb: client: use finish_no_open() for non-regular inodes35Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 224b56b7c02b2bfb1f5bee18d5f56ae6b052be44 | Vendor (CNA) |
| Linux Linux | 253612499ce9b4cd7bb922fe507ec204bddd9313 | Vendor (CNA) |
| Linux Linux | 2cb07d1a6a30283dbfc809c8036bc1fd103d59fa | Vendor (CNA) |
| Linux Linux | 6c5c547f037bc18f0b8d0b5db5a648f8f630ce85 | Vendor (CNA) |
| Linux Linux | 8afc80156b1d9e2cfd02d42c255305fad95b59fc | Vendor (CNA) |
| Linux Linux | c8c6c7e665af4dba75a02f4c9bad3ae2ce341619 | Vendor (CNA) |
| Linux Linux | da83fed81241b03fd0e7ccf0091b051cf420d8d2 | Vendor (CNA) |
| Linux Linux | e94370cf2b76e913a997e9a633ab521a45029284 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.113-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.113-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayOct 31, 2026+13 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/253612499ce9b4cd7bb922fe507ec204bddd9313
- git.kernel.org/stable/c/2cb07d1a6a30283dbfc809c8036bc1fd103d59fa
- git.kernel.org/stable/c/6c5c547f037bc18f0b8d0b5db5a648f8f630ce85
- git.kernel.org/stable/c/8afc80156b1d9e2cfd02d42c255305fad95b59fc
- git.kernel.org/stable/c/c8c6c7e665af4dba75a02f4c9bad3ae2ce341619
- git.kernel.org/stable/c/da83fed81241b03fd0e7ccf0091b051cf420d8d2
- git.kernel.org/stable/c/e94370cf2b76e913a997e9a633ab521a45029284
Vendor advisories and official records. Exploit/PoC links are deliberately left out.