CVE-2026-68431
Last modified
CVE-2026-68431 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: ksmbd: validate minimum PDU size for transform requests The receive path applies the minimum SMB2 PDU size check only when ProtocolId is SMB2_PROTO_NUMBER. A packet carrying SMB2_TRANSFORM_PROTO_NUM bypasses the check even when the negotiated dialect does not provide transform handling. On an SMB 2.1 connection, a short transform packet therefore reaches init_smb2_rsp_hdr(), which interprets the request as a full SMB2 header and reads beyond the request allocation.
Description
In the Linux kernel, the following vulnerability has been resolved: ksmbd: validate minimum PDU size for transform requests The receive path applies the minimum SMB2 PDU size check only when ProtocolId is SMB2_PROTO_NUMBER. A packet carrying SMB2_TRANSFORM_PROTO_NUM bypasses the check even when the negotiated dialect does not provide transform handling. On an SMB 2.1 connection, a short transform packet therefore reaches init_smb2_rsp_hdr(), which interprets the request as a full SMB2 header and reads beyond the request allocation. The copied fields can then be returned to the unauthenticated client. Compression transforms are converted to ordinary SMB2 messages before protocol validation. After that conversion, validate ordinary SMB2 requests against SMB2_MIN_SUPPORTED_PDU_SIZE and require encryption transform requests to contain both a transform header and an SMB2 header. This rejects truncated requests before work allocation.
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 368ba06881c395f1c9a7ba22203cf8d78b4addc0, < b62c510f59803f82f9b4c76ead2a56833b2984c7; >= 368ba06881c395f1c9a7ba22203cf8d78b4addc0, < cfc0b8e5080aec87700774e8568765eaa4b7b92b; df3a4518aee64f21bcafa891105b468413f27431; 543c12c2644e772caa6880662c2a852cfdc5a10c; e9cb7be2fcbaee9e808b729e92948d38d52e5add; >= 5.15.145, < 5.16; >= 6.1.34, < 6.2; >= 6.3.8, < 6.4 |
| Linux | Linux | 6.4 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-68431?
How severe is CVE-2026-68431?
How do I fix CVE-2026-68431?
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-68426In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68427In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68428In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68429In the Linux kernel, the following vulnerability has been re…
- CVE-2026-6843A flaw was found in nano. A local user could exploit a forma…5.5
- CVE-2026-68430In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68432In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68433In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68434In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68435In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68436In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68437In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-68431?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
