CVE-2026-99291
ksmbd: fix SMB2 CREATE response buffer overflow
No exploitation reported by the sources we read.
- Published2026-11-16
- Fixed in7.3.2 · 7.3
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 SMB2 CREATE response buffer overflow smb2_allocate_rsp_buf() uses the MAX_CIFS_SMALL_BUFFER_SIZE (448-byte) buffer for a single SMB2_CREATE response. That buffer also holds a 4-byte length field, which only leaves 444 bytes for the SMB2 body. The AAPL response made this buffer too small. After 8f1b796ff113, a request with AAPL response contexts may need at least 456 bytes. In the 456-byte case, create_aapl_rsp_buf() is appended last, clears 128 bytes, and writes 12 bytes past the allocation. KASAN reports: BUG: KASAN: slab-out-of-bounds in create_aapl_rsp_buf+0x31/0x6e0 Write of size 128 at addr ffff88800370954c by task kworker/0:0/9 ... create_aapl_rsp_buf+0x31/0x6e0 smb2_open+0x58f9/0xef10 ... smb2_allocate_rsp_buf+0x19d/0x370 ... The buggy address is located 332 bytes inside of allocated 448-byte region [ffff888003709400, ffff8880037095c0) Reserve enough space for any fixed CREATE response KSMBD can build. Store the required allocation size in the per-dialect values table. This keeps the small buffer for other commands and avoids using the max transaction buffer for every CREATE.
Timeline
dates in UTC- 2026-11-1609:59CVE publishedCNA
Versions per branch
OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 7.3 | ≥ 7.3.0, < 7.3.2 | 7.3.2 | OSV |
| 7.x | ≥ 7.2.6, < 7.3 | 7.3 | 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- ≥ 8f1b796ff1135f5660e1889973359331c61b78a0, < 824a572c0f909ca51fdb7e18e4eee33ca7896c7afixed in 824a572c0f909ca51fdb7e18e4eee33ca7896c7agit
- ≥ 8f1b796ff1135f5660e1889973359331c61b78a0, < 713c31a3a225b6239a37ac7fbfb394567f8b3519fixed in 713c31a3a225b6239a37ac7fbfb394567f8b3519git
- = bbeefd3e96645ea4951520aea66a010ce87927afno fix statedgit
- ≥ 7.2.6, < 7.3fixed in 7.3semver
- Linuxother versions: affected
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected- = 7.3no fix stated
Not affected < 7.3 · ≥ 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
- linuxDebian:14all versions · fixed in 7.3.3-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-realtime-6.14Ubuntu:Pro:Realtime:24.04:LTSall versions · no fixed version listedand 1 other package
- linux-riscvUbuntu:24.04:LTSall versions · no fixed version listedand 28 other packages
- linux-riscvUbuntu:22.04:LTSall versions · no fixed version listedand 32 other packages
1 more package range on OSV.dev
Fix
- Update Linux kernel to 7.3.2 · 7.3
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.18.82026-11-19
- FIRST EPSSEPSS score0.2 %2026-11-18
- OSVaffected packages—
- GitHub Advisoriesadvisory—
Identifiers
- EUVD-2026-126197same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-phxc-ww8f-9c6wsame flawGitHub Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/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-phxc-ww8f-9c6w
Frequently asked questions
What is CVE-2026-99291?
Is CVE-2026-99291 actively exploited?
What is the CVSS score for CVE-2026-99291?
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-phxc-ww8f-9c6w
- 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