CVE-2026-99291
Last modified
CVE-2026-99291 is a vulnerability of currently unknown severity. 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.
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.
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 8f1b796ff1135f5660e1889973359331c61b78a0, < 824a572c0f909ca51fdb7e18e4eee33ca7896c7a; >= 8f1b796ff1135f5660e1889973359331c61b78a0, < 713c31a3a225b6239a37ac7fbfb394567f8b3519; bbeefd3e96645ea4951520aea66a010ce87927af; >= 7.2.6, < 7.3 |
| Linux | Linux | 7.3 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-99291?
How severe is CVE-2026-99291?
How do I fix CVE-2026-99291?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-99286In the Linux kernel, the following vulnerability has been re…
- CVE-2026-99287In the Linux kernel, the following vulnerability has been re…
- CVE-2026-99288In the Linux kernel, the following vulnerability has been re…
- CVE-2026-99289In the Linux kernel, the following vulnerability has been re…
- CVE-2026-9929Inappropriate implementation in WebGL in Google Chrome on An…4.3
- CVE-2026-99290In the Linux kernel, the following vulnerability has been re…
- CVE-2026-99292In the Linux kernel, the following vulnerability has been re…
- CVE-2026-99293In the Linux kernel, the following vulnerability has been re…
- CVE-2026-99294In the Linux kernel, the following vulnerability has been re…
- CVE-2026-99295In the Linux kernel, the following vulnerability has been re…
- CVE-2026-99296In the Linux kernel, the following vulnerability has been re…
- CVE-2026-99297In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-99291?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
