Answer in brief
CVE-2026-64381 records a Unknown severity vulnerability in smb: client: Fix next buffer leak in receive_encrypted_standard(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-64381 records a Unknown severity vulnerability in smb: client: Fix next buffer leak in receive_encrypted_standard(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=b24df3e30cbf48255db866720fb71f14bf9d2f39 <94e4f672db029414b9888b5137a7559f1febf2d8 || >=b24df3e30cbf48255db866720fb71f14bf9d2f39 <68fc0b6cc03ca58060c0f36454e169f5fe258974 || >=b24df3e30cbf48255db866720fb71f14bf9d2f39 <07e0ab81df1790afa35732a4e8e07ff831b29008 || >=b24df3e30cbf48255db866720fb71f14bf9d2f39 <9136a08dc29328edd9867f2545e73906ac9df93b || >=b24df3e30cbf48255db866720fb71f14bf9d2f39 <67097772df7791c53d608f04bd31c676ccf79b83 || >=b24df3e30cbf48255db866720fb71f14bf9d2f39 <297243e365fc9fe2f8e9b7dd535a65d922cd108b || >=b24df3e30cbf48255db866720fb71f14bf9d2f39 <927d4805aea0a287d36dd4f826ee24d69a2afee3 || >=b24df3e30cbf48255db866720fb71f14bf9d2f39 <1c6267a1d5cf4c73b656f8181b310cbbb3e4767b | 94e4f672db029414b9888b5137a7559f1febf2d8, 68fc0b6cc03ca58060c0f36454e169f5fe258974, 07e0ab81df1790afa35732a4e8e07ff831b29008, 9136a08dc29328edd9867f2545e73906ac9df93b, 67097772df7791c53d608f04bd31c676ccf79b83, 297243e365fc9fe2f8e9b7dd535a65d922cd108b, 927d4805aea0a287d36dd4f826ee24d69a2afee3, 1c6267a1d5cf4c73b656f8181b310cbbb3e4767b |
| Linux/Linuxgeneric | 4.19 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 11, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=b24df3e30cbf48255db866720fb71f14bf9d2f39 <94e4f672db029414b9888b5137a7559f1febf2d8 || >=b24df3e30cbf48255db866720fb71f14bf9d2f39 <68fc0b6cc03ca58060c0f36454e169f5fe258974 || >=b24df3e30cbf48255db866720fb71f14bf9d2f39 <07e0ab81df1790afa35732a4e8e07ff831b29008 || >=b24df3e30cbf48255db866720fb71f14bf9d2f39 <9136a08dc29328edd9867f2545e73906ac9df93b || >=b24df3e30cbf48255db866720fb71f14bf9d2f39 <67097772df7791c53d608f04bd31c676ccf79b83 || >=b24df3e30cbf48255db866720fb71f14bf9d2f39 <297243e365fc9fe2f8e9b7dd535a65d922cd108b || >=b24df3e30cbf48255db866720fb71f14bf9d2f39 <927d4805aea0a287d36dd4f826ee24d69a2afee3 || >=b24df3e30cbf48255db866720fb71f14bf9d2f39 <1c6267a1d5cf4c73b656f8181b310cbbb3e4767b | 94e4f672db029414b9888b5137a7559f1febf2d8, 68fc0b6cc03ca58060c0f36454e169f5fe258974, 07e0ab81df1790afa35732a4e8e07ff831b29008, 9136a08dc29328edd9867f2545e73906ac9df93b, 67097772df7791c53d608f04bd31c676ccf79b83, 297243e365fc9fe2f8e9b7dd535a65d922cd108b, 927d4805aea0a287d36dd4f826ee24d69a2afee3, 1c6267a1d5cf4c73b656f8181b310cbbb3e4767b |
| Linux/Linuxgeneric | 4.19 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 11, 2026
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.
Quoted source text, attributed separately from HOL analysis.