From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-64138: ksmbd: validate SID in parent security descriptor during ACL inheritance
Date: Sun, 19 Jul 2026 17:40:00 +0200 [thread overview]
Message-ID: <2026071928-CVE-2026-64138-e6dd@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: validate SID in parent security descriptor during ACL inheritance
Introduce smb_validate_ntsd_sid() helper to safely validate Owner SID
and Group SID inside the NT Security Descriptor (smb_ntsd) retrieved
from the parent directory.
The Linux kernel CVE team has assigned CVE-2026-64138 to this issue.
Affected and fixed versions
===========================
Fixed in 6.12.92 with commit f0e5c9c663badc9982e6941322eef1cb17de0f11
Fixed in 6.18.34 with commit 18d8db24b0a5b7be4829238dd4022236df02d421
Fixed in 7.0.11 with commit 1c9d0646a9959752f11ca1080dc1ff26bd1756cb
Fixed in 7.1 with commit 69f030cf95488ae1186c72ac8c66fd279664ea7f
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-64138
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/server/smbacl.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/f0e5c9c663badc9982e6941322eef1cb17de0f11
https://git.kernel.org/stable/c/18d8db24b0a5b7be4829238dd4022236df02d421
https://git.kernel.org/stable/c/1c9d0646a9959752f11ca1080dc1ff26bd1756cb
https://git.kernel.org/stable/c/69f030cf95488ae1186c72ac8c66fd279664ea7f
reply other threads:[~2026-07-19 15:45 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=2026071928-CVE-2026-64138-e6dd@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.