cbcvebase.
CVE-2026-31613
published 2026-04-24

CVE-2026-31613: In the Linux kernel, the following vulnerability has been resolved: smb: client: fix OOB reads parsing symlink error response When a CREATE returns…

PriorityP341high8.1CVSS 3.1
AVNACLPRNUIRSUCHINAH
EPSS
0.38%
30.5th percentile
In the Linux kernel, the following vulnerability has been resolved: smb: client: fix OOB reads parsing symlink error response When a CREATE returns STATUS_STOPPED_ON_SYMLINK, smb2_check_message() returns success without any length validation, leaving the symlink parsers as the only defense against an untrusted server. symlink_data() walks SMB 3.1.1 error contexts with the loop test "p ErrorId at offset 4 and p->ErrorDataLength at offset 0. When the server-controlled ErrorDataLength advances p to within 1-7 bytes of end, the next iteration will read past it. When the matching context is found, sym->SymLinkErrorTag is read at offset 4 from p->ErrorContextData with no check that the symlink header itself fits. smb2_parse_symlink_response() then bounds-checks the substitute name using SMB2_SYMLINK_STRUCT_SIZE as the offset of PathBuffer from iov_base. That value is computed as sizeof(smb2_err_rsp) + sizeof(smb2_symlink_err_rsp), which is correct only when ErrorContextCount == 0. With at least one error context the symlink data sits 8 bytes deeper, and each skipped non-matching context shifts it further by 8 + ALIGN(ErrorDataLength, 8). The check is too short, allowing the substitute name read to run past iov_len. The out-of-bound heap bytes are UTF-16-decoded into the symlink target and returned to userspace via readlink(2). Fix this all up by making the loops test require the full context header to fit, rejecting sym if its header runs past end, and bound the substitute name against the actual position of sym->PathBuffer rather than a fixed offset. Because sub_offs and sub_len are 16bits, the pointer math will not overflow here with the new greater-than.

Affected

40 ranges· showing 25
VendorProductVersion rangeFixed in
linuxlinux
linuxlinux
linuxlinux>= 6.0.16 < 6.16.1
linuxlinux>= 76894f3e2f71177747b8b4763fb180e800279585 < 043834e72337ee7b4e9685859888623ba1504ac7043834e72337ee7b4e9685859888623ba1504ac7
linuxlinux>= 76894f3e2f71177747b8b4763fb180e800279585 < d65a64755a3df68a2fd19d2a81395e9f723aca23d65a64755a3df68a2fd19d2a81395e9f723aca23
linuxlinux>= 76894f3e2f71177747b8b4763fb180e800279585 < 20ac98f0eb6047edb73c9a27af782bdde08b375720ac98f0eb6047edb73c9a27af782bdde08b3757
linuxlinux>= 76894f3e2f71177747b8b4763fb180e800279585 < e0dd90d14cbbf318157ea8e3fb62ee68a28655ede0dd90d14cbbf318157ea8e3fb62ee68a28655ed
linuxlinux>= 76894f3e2f71177747b8b4763fb180e800279585 < 781902e069f4ecb6c3b83502f181972c1446110a781902e069f4ecb6c3b83502f181972c1446110a
linuxlinux>= 76894f3e2f71177747b8b4763fb180e800279585 < a66ef2e7ed837325c5600f8617d5ee0a0a149fdda66ef2e7ed837325c5600f8617d5ee0a0a149fdd
linuxlinux>= 76894f3e2f71177747b8b4763fb180e800279585 < 3df690bba28edec865cf7190be10708ad0ddd67e3df690bba28edec865cf7190be10708ad0ddd67e
linuxlinux_kernel
linuxlinux_kernel>= 6.1 < 6.18.246.18.24
linuxlinux_kernel>= 6.19 < 6.19.146.19.14
linuxlinux_kernel>= 7.0 < 7.0.17.0.1
ubuntulinux
ubuntulinux-aws
ubuntulinux-azure
ubuntulinux-azure-6.8
ubuntulinux-azure-fde
ubuntulinux-azure-fde-6.8
ubuntulinux-azure-fips
ubuntulinux-fips
ubuntulinux-gcp
ubuntulinux-gcp-6.8
ubuntulinux-gcp-fips

CVSS provenance

nvdv3.18.1HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H
vendor_redhat7.0HIGH
vendor_ubuntu2.0LOW
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.