CVE-2026-99290
ksmbd: fix use-after-free after a failed durable reconnect
No exploitation reported by the sources we read.
- Published2026-11-16
- Fixed in7.3.2 · 6.18.61 · 6.12.117 · 6.7
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free after a failed durable reconnect ksmbd_reopen_durable_fd() republishes a detached durable handle in the reconnecting session's file table and takes no reference for that entry. If smb2_open() then fails, cleanup relies on the final ksmbd_fd_put() to remove the volatile id. Two reconnects of the same handle can both take a lookup reference before either attaches it. If the one that reopens first then fails and drops its references first, the other request makes the final put through ksmbd_put_durable_fd(). That frees the handle without removing the first session's table entry, so tearing that session down writes to freed memory. BUG: KASAN: slab-use-after-free in __close_file_table_ids+0x14d/0x740 [ksmbd] Call Trace: __close_file_table_ids+0x14d/0x740 [ksmbd] ksmbd_destroy_file_table+0x76/0x100 [ksmbd] ksmbd_session_destroy+0xf8/0x480 [ksmbd] ksmbd_dispose_sessions+0x13e/0x200 [ksmbd] ksmbd_conn_sessions_cleanup+0x4c3/0x6d0 [ksmbd] Freed by task 1030: __ksmbd_close_fd+0x97d/0x1000 [ksmbd] smb2_open+0x14eb/0xd9f0 [ksmbd] Commit 3515503322f4 ("ksmbd: fix durable reconnect error path file lifetime") handles a final put made by the reconnecting request, but not one made by another holder. Remove the volatile id under the file-table lock on this error path, before the references are dropped, as ksmbd_close_fd() does on the request_open path just above. Removal then no longer depends on which holder makes the final put. The stale comment in the reconnect cleanup is updated to match. A successful reconnect is unchanged.
Timeline
dates in UTC- 2026-11-1609:59CVE publishedCNA
Versions per branch
OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 7.3 | ≥ 6.19.0, < 7.3.2 | 7.3.2 | OSV |
| 6.x | ≥ 6.13.0, < 6.18.61 | 6.18.61 | OSV |
| 6.x | ≥ 6.9.0, < 6.12.117 | 6.12.117 | OSV |
| 6.x | ≥ 6.6.32, < 6.7 | 6.7 | OSV |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Products declared by the CNA2 products
As Linux, the CNA that assigned this CVE, declared them in the CVE record; versions as written.
- Linuxother versions: not affected
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected- ≥ c8efcc786146a951091588e5fa7e3c754850cb3c, < 5078a4e41b29acdf6be52e4a7cc8a59c2a72a471fixed in 5078a4e41b29acdf6be52e4a7cc8a59c2a72a471git
- ≥ c8efcc786146a951091588e5fa7e3c754850cb3c, < bd47ee501b6ac4a26ae41f780a43b7967302a269fixed in bd47ee501b6ac4a26ae41f780a43b7967302a269git
- ≥ c8efcc786146a951091588e5fa7e3c754850cb3c, < edacf65866a9f397438d5b9ff9f43312b29b4b3cfixed in edacf65866a9f397438d5b9ff9f43312b29b4b3cgit
- ≥ c8efcc786146a951091588e5fa7e3c754850cb3c, < 248b5819591c577727930e4e255a455235fab50afixed in 248b5819591c577727930e4e255a455235fab50agit
- = 8df4bcdb0a4232192b2445256c39b787d58ef14dno fix statedgit
- ≥ 6.6.32, < 6.7fixed in 6.7semver
- Linuxother versions: affected
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected- = 6.9no fix stated
Not affected < 6.9 · ≥ 6.12.117, ≤ 6.12.* · ≥ 6.18.61, ≤ 6.18.* · ≥ 7.3.2, ≤ 7.3.* · ≥ 7.4-rc1
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-11-16
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Packages
- linuxUbuntu:26.10all versions · no fixed version listedand 8 other packages
- linuxUbuntu:26.04:LTSall versions · no fixed version listedand 14 other packages
- linuxDebian:14all versions · fixed in 7.3.3-1
- linuxDebian:13all versions · fixed in 6.12.117-1
- linux-aws-fipsUbuntu:Pro:FIPS-updates:22.04:LTSall versions · no fixed version listed
- linux-azureUbuntu:18.04:LTSall versions · no fixed version listedand 14 other packages
- linux-hwe-edgeUbuntu:16.04:LTSall versions · no fixed version listed
- linux-ltsAlpaquita:streamfrom 6.18.58-r0 · fixed in 6.18.62-r0
5 more package ranges on OSV.dev
Fix
- Update Linux kernel to 7.3.2 · 6.18.61 · 6.12.117 · 6.7
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- PoC-in-GitHubno public repository identifiedread 2026-11-19
- Metasploit modules
- none listed Metasploit Framework
Sources
- NVDCVE recordread 2026-11-19
- CNACVSS 3.17.52026-11-19
- FIRST EPSSEPSS score0.2 %2026-11-18
- OSVaffected packages—
- GitHub Advisoriesadvisory—
Identifiers
- EUVD-2026-126196same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-jj2j-7jrj-28q3same flawGitHub Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
- Published
- 2026-11-16
- Last Modified
- 2026-11-19
- NVD status
- Received
- GitHub Advisory
- GHSA-jj2j-7jrj-28q3
Frequently asked questions
What is CVE-2026-99290?
Is CVE-2026-99290 actively exploited?
What is the CVSS score for CVE-2026-99290?
Running Linux kernel? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-jj2j-7jrj-28q3
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- OpenCVE · OpenCVE terms of service · terms restrict redistribution
- OSV.dev · Per record, as its publisher states it: each row carries the label in sourceLicense when one is served