Menu

Star on GitHub · 3.2k

CVE-2026-31705

9.8 · CRITICAL

In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix out-of-bounds write in smb2_get_ea() EA alignment smb2_get_ea() applies 4-byte alignment padding via memset() after…

Published May 1, 2026CWE-787EPSS 0.40%

Overview

CVE-2026-31705 is a critical-severity vulnerability. It was published on May 1, 2026 and has a CVSS 3.1 base score of 9.8 (CRITICAL).

This vulnerability has a CVSS 3.1 base score of 9.8, rated CRITICAL. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

ksmbd: fix out-of-bounds write in smb2_get_ea() EA alignment

smb2_get_ea() applies 4-byte alignment padding via memset() after

writing each EA entry. The bounds check on buf_free_len is performed

before the value memcpy, but the alignment memset fires unconditionally

afterward with no check on remaining space.

When the EA value exactly fills the remaining buffer (buf_free_len == 0

after value subtraction), the alignment memset writes 1-3 NUL bytes

past the buf_free_len boundary. In compound requests where the response

buffer is shared across commands, the first command (e.g., READ) can

consume most of the buffer, leaving a tight remainder for the QUERY_INFO

EA response. The alignment memset then overwrites past the physical

kvmalloc allocation into adjacent kernel heap memory.

Add a bounds check before the alignment memset to ensure buf_free_len

can accommodate the padding bytes.

This is the same bug pattern fixed

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-31705?

CVE-2026-31705 is a critical-severity vulnerability. It was published on May 1, 2026 and has a CVSS 3.1 base score of 9.8 (CRITICAL).

How severe is CVE-2026-31705?

This vulnerability has a CVSS 3.1 base score of 9.8, rated CRITICAL. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2026-31705?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-31705?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-31705 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related CRITICAL CVEs from 2026

View all