From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-64076: netfilter: bridge: eb_tables: close module init race
Date: Sun, 19 Jul 2026 17:38:58 +0200 [thread overview]
Message-ID: <2026071914-CVE-2026-64076-4346@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
netfilter: bridge: eb_tables: close module init race
sashiko reports for unrelated patch:
Does the core ebtables initialization in ebtables.c suffer from a similar race?
Once nf_register_sockopt() completes, the sockopts are exposed globally.
sockopt has to be registered last, just like in ip/ip6/arptables.
The Linux kernel CVE team has assigned CVE-2026-64076 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.13 with commit 5b53951cfc85329d29df9d07b1e905f4563546a5 and fixed in 6.18.34 with commit c647e2a21bbbaceda6cdb8a44a56f44d231dc4b4
Issue introduced in 5.13 with commit 5b53951cfc85329d29df9d07b1e905f4563546a5 and fixed in 7.0.11 with commit 02d999dc69b3918dba2414932b5d95f1f75c76cb
Issue introduced in 5.13 with commit 5b53951cfc85329d29df9d07b1e905f4563546a5 and fixed in 7.1 with commit 27414ff1b287ea9a2a11675149ec28e05539f3cc
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-64076
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/bridge/netfilter/ebtables.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/c647e2a21bbbaceda6cdb8a44a56f44d231dc4b4
https://git.kernel.org/stable/c/02d999dc69b3918dba2414932b5d95f1f75c76cb
https://git.kernel.org/stable/c/27414ff1b287ea9a2a11675149ec28e05539f3cc
reply other threads:[~2026-07-19 15:42 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=2026071914-CVE-2026-64076-4346@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