Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
High

Out-of-bounds read in Linux kernel SMB client symlink error response parsing

IdentifiersCVE-2026-31613CWE-125· Out-of-bounds Read

CVE-2026-31613 is an out-of-bounds read vulnerability in the Linux kernel SMB client code when parsing SMB 3.1.1 symlink error responses from an untrusted server. The issue is triggered on the CREATE error path when the server returns STATUS_STOPPED_ON_SYMLINK. In that path, smb2_check_message() returns success without performing length validation, leaving subsequent symlink parsing logic to process attacker-controlled response data. In symlink_data(), SMB 3.1.1 error contexts are iterated with a loop condition of "p < end", but the parser reads fields from the current context header without first ensuring the full header fits in bounds. A server-controlled ErrorDataLength can advance the parser pointer to within 1-7 bytes of the end of the buffer, causing the next iteration to read past the end. Additionally, when a matching context is found, the code reads SymLinkErrorTag from ErrorContextData without verifying that the symlink header itself is fully present. A second bounds error exists in smb2_parse_symlink_response(), which validates the substitute name using a fixed SMB2_SYMLINK_STRUCT_SIZE offset from iov_base. That offset is only correct when ErrorContextCount is zero; when one or more error contexts are present, the actual symlink data is deeper in the buffer and may be shifted further by skipped contexts. As a result, substitute-name parsing can run past iov_len and consume out-of-bounds heap data.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

A malicious or compromised SMB server can cause the Linux kernel SMB client to read beyond the end of the received response buffer. The resulting out-of-bounds heap bytes may be UTF-16 decoded into the symlink target and returned to userspace via readlink(2), creating an information disclosure condition. Available advisory text also indicates the flaw may contribute to denial-of-service impact due to invalid memory access during parsing, but the specifically documented consequence is leakage of kernel heap data to userspace.

Mitigation

If you can’t patch tonight, do this now.

Until patched, reduce exposure by avoiding connections to untrusted SMB servers and limiting use of the kernel SMB client against attacker-controlled or unverified endpoints. Where operationally feasible, restrict outbound SMB client access to trusted servers only. No content provided describes a complete workaround short of applying a fixed kernel.

Remediation

Patch, then assume compromise.

Upgrade to a Linux kernel release containing the upstream fix for CVE-2026-31613. The fix hardens SMB symlink error-response parsing by requiring that the full SMB error-context header fit before each iteration, rejecting symlink structures whose headers extend past the end of the buffer, and validating the substitute name against the actual position of sym->PathBuffer rather than a fixed structure offset. Vendor advisories indicate fixed kernels have been shipped across multiple stable and enterprise distributions; apply the vendor-provided kernel update for the affected platform and reboot as required.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
LinuxLinux Kerneloperating_system
Rocky LinuxKerneloperating_system
Rocky LinuxKernel-Rtoperating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity2

Community discussion across Reddit, Mastodon, and other social sources.