CVE-2026-64381
Last modified
CVE-2026-64381 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: smb: client: Fix next buffer leak in receive_encrypted_standard() receive_encrypted_standard() allocates next_buffer before checking whether the number of compound PDUs already reached MAX_COMPOUND. If the limit check fails, the function returns immediately and the newly allocated next_buffer is not assigned to server->smallbuf/server->bigbuf, making it leaked. Move the MAX_COMPOUND check before allocating next_buffer.. EPSS estimates a 0.18% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: smb: client: Fix next buffer leak in receive_encrypted_standard() receive_encrypted_standard() allocates next_buffer before checking whether the number of compound PDUs already reached MAX_COMPOUND. If the limit check fails, the function returns immediately and the newly allocated next_buffer is not assigned to server->smallbuf/server->bigbuf, making it leaked. Move the MAX_COMPOUND check before allocating next_buffer.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= b24df3e30cbf48255db866720fb71f14bf9d2f39, < 94e4f672db029414b9888b5137a7559f1febf2d8; >= b24df3e30cbf48255db866720fb71f14bf9d2f39, < 68fc0b6cc03ca58060c0f36454e169f5fe258974; >= b24df3e30cbf48255db866720fb71f14bf9d2f39, < 07e0ab81df1790afa35732a4e8e07ff831b29008; >= b24df3e30cbf48255db866720fb71f14bf9d2f39, < 9136a08dc29328edd9867f2545e73906ac9df93b; >= b24df3e30cbf48255db866720fb71f14bf9d2f39, < 67097772df7791c53d608f04bd31c676ccf79b83; >= b24df3e30cbf48255db866720fb71f14bf9d2f39, < 297243e365fc9fe2f8e9b7dd535a65d922cd108b; >= b24df3e30cbf48255db866720fb71f14bf9d2f39, < 927d4805aea0a287d36dd4f826ee24d69a2afee3; >= b24df3e30cbf48255db866720fb71f14bf9d2f39, < 1c6267a1d5cf4c73b656f8181b310cbbb3e4767b |
| Linux | Linux | 4.19 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-64381?
How severe is CVE-2026-64381?
How do I fix CVE-2026-64381?
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-64375In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64376In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64377In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64378In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64379In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-64380In the Linux kernel, the following vulnerability has been re…8.2
- CVE-2026-64382In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-64383In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-64384In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-64385In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-64386In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-64387In the Linux kernel, the following vulnerability has been re…9.8
Are you affected by CVE-2026-64381?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST