Answer in brief
CVE-2026-31432 records a High severity (CVSS 8.8) vulnerability in ksmbd: fix OOB write in QUERY_INFO for compound requests. 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.
CVSS is 8.8. 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 | >=e2b76ab8b5c9327ab2dae6da05d0752eb2f4771d <850452af77f55d185f9445e1f7a1db53c5e4aad4 || >=e2b76ab8b5c9327ab2dae6da05d0752eb2f4771d <d48c64fb80ad78b3dd29fb7d79b6ec7bd72bfc09 || >=e2b76ab8b5c9327ab2dae6da05d0752eb2f4771d <075ea208c648cc2bcd616295b711d3637c61de45 || >=e2b76ab8b5c9327ab2dae6da05d0752eb2f4771d <515c2daab46021221bdf406bef19bc90a44ec617 || >=e2b76ab8b5c9327ab2dae6da05d0752eb2f4771d <fda9522ed6afaec45cabc198d8492270c394c7bc || f2283680a80571ca82d710bc6ecd8f8beac67d63 || 9f297df20d93411c0b4ddad7f88ba04a7cd36e77 || >=5.15.145 <5.16 || >=6.1.71 <6.2 | 850452af77f55d185f9445e1f7a1db53c5e4aad4, d48c64fb80ad78b3dd29fb7d79b6ec7bd72bfc09, 075ea208c648cc2bcd616295b711d3637c61de45, 515c2daab46021221bdf406bef19bc90a44ec617, fda9522ed6afaec45cabc198d8492270c394c7bc, 5.16, 6.2 |
| Linux/Linuxgeneric | 6.6 | Not reported |
Published upstream
Apr 22, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jun 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 19, 2026
In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix OOB write in QUERY_INFO for compound requests When a compound request such as READ + QUERY_INFO(Security) is received, and the first command (READ) consumes most of the response buffer, ksmbd could write beyond the allocated buffer while building a security descriptor. The root cause was that smb2_get_info_sec() checked buffer space using ppntsd_size from xattr, while build_sec_desc() often synthesized a significantly larger descriptor from POSIX ACLs. This patch introduces smb_acl_sec_desc_scratch_len() to accurately compute the final descriptor size beforehand, performs proper buffer checking with smb2_calc_max_out_buf_len(), and uses exact-sized allocation + iov pinning.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-31432 records a High severity (CVSS 8.8) vulnerability in ksmbd: fix OOB write in QUERY_INFO for compound requests. 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.
CVSS is 8.8. 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 | >=e2b76ab8b5c9327ab2dae6da05d0752eb2f4771d <850452af77f55d185f9445e1f7a1db53c5e4aad4 || >=e2b76ab8b5c9327ab2dae6da05d0752eb2f4771d <d48c64fb80ad78b3dd29fb7d79b6ec7bd72bfc09 || >=e2b76ab8b5c9327ab2dae6da05d0752eb2f4771d <075ea208c648cc2bcd616295b711d3637c61de45 || >=e2b76ab8b5c9327ab2dae6da05d0752eb2f4771d <515c2daab46021221bdf406bef19bc90a44ec617 || >=e2b76ab8b5c9327ab2dae6da05d0752eb2f4771d <fda9522ed6afaec45cabc198d8492270c394c7bc || f2283680a80571ca82d710bc6ecd8f8beac67d63 || 9f297df20d93411c0b4ddad7f88ba04a7cd36e77 || >=5.15.145 <5.16 || >=6.1.71 <6.2 | 850452af77f55d185f9445e1f7a1db53c5e4aad4, d48c64fb80ad78b3dd29fb7d79b6ec7bd72bfc09, 075ea208c648cc2bcd616295b711d3637c61de45, 515c2daab46021221bdf406bef19bc90a44ec617, fda9522ed6afaec45cabc198d8492270c394c7bc, 5.16, 6.2 |
| Linux/Linuxgeneric | 6.6 | Not reported |
Published upstream
Apr 22, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jun 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 19, 2026
In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix OOB write in QUERY_INFO for compound requests When a compound request such as READ + QUERY_INFO(Security) is received, and the first command (READ) consumes most of the response buffer, ksmbd could write beyond the allocated buffer while building a security descriptor. The root cause was that smb2_get_info_sec() checked buffer space using ppntsd_size from xattr, while build_sec_desc() often synthesized a significantly larger descriptor from POSIX ACLs. This patch introduces smb_acl_sec_desc_scratch_len() to accurately compute the final descriptor size beforehand, performs proper buffer checking with smb2_calc_max_out_buf_len(), and uses exact-sized allocation + iov pinning.
Quoted source text, attributed separately from HOL analysis.