archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <>
Cc: Greg Kroah-Hartman <>
Subject: CVE-2024-26925: netfilter: nf_tables: release mutex after nft_gc_seq_end from abort path
Date: Wed, 24 Apr 2024 14:49:21 -0700	[thread overview]
Message-ID: <2024042421-CVE-2024-26925-7c19@gregkh> (raw)


In the Linux kernel, the following vulnerability has been resolved:

netfilter: nf_tables: release mutex after nft_gc_seq_end from abort path

The commit mutex should not be released during the critical section
between nft_gc_seq_begin() and nft_gc_seq_end(), otherwise, async GC
worker could collect expired objects and get the released commit lock
within the same GC sequence.

nf_tables_module_autoload() temporarily releases the mutex to load
module dependencies, then it goes back to replay the transaction again.
Move it at the end of the abort phase after nft_gc_seq_end() is called.

The Linux kernel CVE team has assigned CVE-2024-26925 to this issue.

Affected and fixed versions

	Issue introduced in 5.4.262 with commit 4b6346dc1edf and fixed in 5.4.274 with commit 61ac7284346c
	Issue introduced in 5.10.198 with commit 23292bdfda5f and fixed in 5.10.215 with commit 2cee2ff7f8cc
	Issue introduced in 5.15.134 with commit b44a459c6561 and fixed in 5.15.155 with commit eb769ff4e281
	Issue introduced in 6.1.56 with commit 5d319f7a8143 and fixed in 6.1.86 with commit 8d3a58af50e4
	Issue introduced in 6.5 with commit 720344340fb9 and fixed in 6.6.26 with commit 8038ee3c3e5b
	Issue introduced in 6.5 with commit 720344340fb9 and fixed in 6.8.5 with commit a34ba4bdeec0
	Issue introduced in 6.5 with commit 720344340fb9 and fixed in 6.9-rc3 with commit 0d459e2ffb54
	Issue introduced in 6.4.13 with commit e07e68823116

Please see 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
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:


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:

                 reply	other threads:[~2024-04-24 21:49 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2024042421-CVE-2024-26925-7c19@gregkh \ \ \ \ \

* 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).