From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-43378: smb: server: fix use-after-free in smb2_open()
Date: Fri, 8 May 2026 16:21:47 +0200 [thread overview]
Message-ID: <2026050832-CVE-2026-43378-d7e3@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
smb: server: fix use-after-free in smb2_open()
The opinfo pointer obtained via rcu_dereference(fp->f_opinfo) is
dereferenced after rcu_read_unlock(), creating a use-after-free
window.
The Linux kernel CVE team has assigned CVE-2026-43378 to this issue.
Affected and fixed versions
===========================
Fixed in 6.1.167 with commit e1b21e6066615e7d3d3a7aa2677e415e563fd7cc
Fixed in 6.6.130 with commit b720c84087cb547f23ce03eab93568c1769e4556
Fixed in 6.12.78 with commit 54b48ae83de8bb06e65079d96368efe359d4909c
Fixed in 6.18.19 with commit 8f5b1a7cb009a93c48e9e334a2f59a660f9afc07
Fixed in 6.19.9 with commit 190e5f808e8058640b408ccfed25440b441a718a
Fixed in 7.0 with commit 1e689a56173827669a35da7cb2a3c78ed5c53680
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-43378
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/smb2pdu.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/e1b21e6066615e7d3d3a7aa2677e415e563fd7cc
https://git.kernel.org/stable/c/b720c84087cb547f23ce03eab93568c1769e4556
https://git.kernel.org/stable/c/54b48ae83de8bb06e65079d96368efe359d4909c
https://git.kernel.org/stable/c/8f5b1a7cb009a93c48e9e334a2f59a660f9afc07
https://git.kernel.org/stable/c/190e5f808e8058640b408ccfed25440b441a718a
https://git.kernel.org/stable/c/1e689a56173827669a35da7cb2a3c78ed5c53680
reply other threads:[~2026-05-08 14:23 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=2026050832-CVE-2026-43378-d7e3@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox