Bug 2482558 (CVE-2026-46185)

Summary:	CVE-2026-46185 kernel: smb/client: fix out-of-bounds read in symlink_data()
Product:	[Other] Security Response	Reporter:	OSIDB Bzimport <bzimport>
Component:	vulnerability	Assignee:	Product Security DevOps Team <prodsec-dev>
Status:	NEW ---	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	rhel-process-autobot, watson-tool-maintainers
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:	A flaw was found in the Linux kernel's Server Message Block (SMB) client. This vulnerability arises from insufficient length validation in the `smb2_check_message()` function when processing symlink error responses. A remote attacker could exploit this by sending a specially crafted symlink error response, which may lead to an out-of-bounds read in the `symlink_data()` function. This could potentially result in information disclosure or a denial of service.	Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-05-28 11:03:11 UTC

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

smb/client: fix out-of-bounds read in symlink_data()

Since smb2_check_message() returns success without length validation for
the symlink error response, in symlink_data() it is possible for
iov->iov_len to be smaller than sizeof(struct smb2_err_rsp). If the buffer
only contains the base SMB2 header (64 bytes), accessing
err->ErrorContextCount (at offset 66) or err->ByteCount later in
symlink_data() will cause an out-of-bounds read.

Comment 1 Keith Grant 2026-05-28 14:25:12 UTC

Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2026052830-CVE-2026-46185-42df@gregkh/T

Comment 5 errata-xmlrpc 2026-08-20 05:22:21 UTC

This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:57251 https://access.redhat.com/errata/RHSA-2026:57251

Comment 6 errata-xmlrpc 2026-09-04 00:52:51 UTC

This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:63129 https://access.redhat.com/errata/RHSA-2026:63129