From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-52967: smb/client: fix possible infinite loop and oob read in symlink_data()
Date: Wed, 24 Jun 2026 17:29:51 +0100 [thread overview]
Message-ID: <2026062438-CVE-2026-52967-0fd6@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
smb/client: fix possible infinite loop and oob read in symlink_data()
On 32-bit architectures, the infinite loop is as follows:
len = p->ErrorDataLength == 0xfffffff8
u8 *next = p->ErrorContextData + len
next == p
On 32-bit architectures, the out-of-bounds read is as follows:
len = p->ErrorDataLength == 0xfffffff0
u8 *next = p->ErrorContextData + len
next == (u8 *)p - 8
The Linux kernel CVE team has assigned CVE-2026-52967 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.1 with commit 76894f3e2f71177747b8b4763fb180e800279585 and fixed in 6.1.175 with commit 1cfa2d59f669db28d6292d10ff87ca6837c781b0
Issue introduced in 6.1 with commit 76894f3e2f71177747b8b4763fb180e800279585 and fixed in 6.6.141 with commit b41598bf54b3fe528994e573df6008f8f4d0a4f4
Issue introduced in 6.1 with commit 76894f3e2f71177747b8b4763fb180e800279585 and fixed in 6.12.91 with commit cd4b9b662f0fb9aa97ee6bf9034eca76fc6cab23
Issue introduced in 6.1 with commit 76894f3e2f71177747b8b4763fb180e800279585 and fixed in 6.18.33 with commit 97a05b0ae9ea5ec052be2eef0f9cc7ce03501bbb
Issue introduced in 6.1 with commit 76894f3e2f71177747b8b4763fb180e800279585 and fixed in 7.0.10 with commit 1b9331b16b0ed9414dcf7583d8134bdfeb117aae
Issue introduced in 6.1 with commit 76894f3e2f71177747b8b4763fb180e800279585 and fixed in 7.1 with commit 7d9a7f1f96cd617ee9e75bb22217c709038e26b8
Issue introduced in 6.0.16 with commit 2d046892a493d9760c35fdaefc3017f27f91b621
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-52967
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
fs/smb/client/smb2file.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/1cfa2d59f669db28d6292d10ff87ca6837c781b0
https://git.kernel.org/stable/c/b41598bf54b3fe528994e573df6008f8f4d0a4f4
https://git.kernel.org/stable/c/cd4b9b662f0fb9aa97ee6bf9034eca76fc6cab23
https://git.kernel.org/stable/c/97a05b0ae9ea5ec052be2eef0f9cc7ce03501bbb
https://git.kernel.org/stable/c/1b9331b16b0ed9414dcf7583d8134bdfeb117aae
https://git.kernel.org/stable/c/7d9a7f1f96cd617ee9e75bb22217c709038e26b8
reply other threads:[~2026-06-24 16:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026062438-CVE-2026-52967-0fd6@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.