From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-64005: net/smc: Do not re-initialize smc hashtables
Date: Sun, 19 Jul 2026 16:57:45 +0200 [thread overview]
Message-ID: <2026071907-CVE-2026-64005-594b@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
net/smc: Do not re-initialize smc hashtables
INIT_HLIST_HEAD(&smc_v*_hashinfo.ht) are called after smc_nl_init(),
proto_register() and sock_register(). This can lead to smc_v*_hashinfo.ht
being reset even though hash entries already exist and are being used,
possibly resulting in a corrupted list.
Remove unnecessary and dangerous re-initialisation of smc_v*_hashinfo.ht in
smc_init(); it is implicitly initialised to zero anyhow. Add
HLIST_HEAD_INIT to the definitions for clarity.
The Linux kernel CVE team has assigned CVE-2026-64005 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.11 with commit f16a7dd5cf27eeda187425c9c7d96802a549f9c4 and fixed in 5.10.259 with commit cdc79c05cc375f68ae87b0c74fdaac1a5c93155a
Issue introduced in 4.11 with commit f16a7dd5cf27eeda187425c9c7d96802a549f9c4 and fixed in 5.15.210 with commit 2006605006e5a4a11d93e1ebdbbe95764d24276f
Issue introduced in 4.11 with commit f16a7dd5cf27eeda187425c9c7d96802a549f9c4 and fixed in 6.1.176 with commit 64c96e497d5ada0b90e99bf58f893aa2b73dcfbc
Issue introduced in 4.11 with commit f16a7dd5cf27eeda187425c9c7d96802a549f9c4 and fixed in 6.6.143 with commit ed7a758313011885347b854e97cb95903ef3c3f7
Issue introduced in 4.11 with commit f16a7dd5cf27eeda187425c9c7d96802a549f9c4 and fixed in 6.12.93 with commit 0cc9d0ac22d02f1ba1884de5d6de9eaf8b45d82d
Issue introduced in 4.11 with commit f16a7dd5cf27eeda187425c9c7d96802a549f9c4 and fixed in 6.18.35 with commit 55cba6b883b41e5922c00ba9d4e3262131f46f1b
Issue introduced in 4.11 with commit f16a7dd5cf27eeda187425c9c7d96802a549f9c4 and fixed in 7.0.12 with commit 5ec939367e700722ffbb1b7cacccbb1a3cf0ebd1
Issue introduced in 4.11 with commit f16a7dd5cf27eeda187425c9c7d96802a549f9c4 and fixed in 7.1 with commit 9e4389b0038781f19f97895186ed941ff8ac1678
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-64005
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:
net/smc/af_smc.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/cdc79c05cc375f68ae87b0c74fdaac1a5c93155a
https://git.kernel.org/stable/c/2006605006e5a4a11d93e1ebdbbe95764d24276f
https://git.kernel.org/stable/c/64c96e497d5ada0b90e99bf58f893aa2b73dcfbc
https://git.kernel.org/stable/c/ed7a758313011885347b854e97cb95903ef3c3f7
https://git.kernel.org/stable/c/0cc9d0ac22d02f1ba1884de5d6de9eaf8b45d82d
https://git.kernel.org/stable/c/55cba6b883b41e5922c00ba9d4e3262131f46f1b
https://git.kernel.org/stable/c/5ec939367e700722ffbb1b7cacccbb1a3cf0ebd1
https://git.kernel.org/stable/c/9e4389b0038781f19f97895186ed941ff8ac1678
reply other threads:[~2026-07-19 15:03 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=2026071907-CVE-2026-64005-594b@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;
as well as URLs for NNTP newsgroup(s).