All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2022-49358: netfilter: nf_tables: memleak flow rule from commit path
Date: Wed, 26 Feb 2025 03:10:32 +0100	[thread overview]
Message-ID: <2025022643-CVE-2022-49358-6cfd@gregkh> (raw)

Description
===========

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

netfilter: nf_tables: memleak flow rule from commit path

Abort path release flow rule object, however, commit path does not.
Update code to destroy these objects before releasing the transaction.

The Linux kernel CVE team has assigned CVE-2022-49358 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 5.3 with commit c9626a2cbdb20e26587b3fad99960520a023432b and fixed in 5.4.198 with commit 5b8d63489c3b701eb2a76f848ec94d8cbc9373b9
	Issue introduced in 5.3 with commit c9626a2cbdb20e26587b3fad99960520a023432b and fixed in 5.10.122 with commit 330c0c6cd2150a2d7f47af16aa590078b0d2f736
	Issue introduced in 5.3 with commit c9626a2cbdb20e26587b3fad99960520a023432b and fixed in 5.15.47 with commit e33d9bd563e71f6c6528b96008d65524a459c4dc
	Issue introduced in 5.3 with commit c9626a2cbdb20e26587b3fad99960520a023432b and fixed in 5.17.15 with commit 80de9ea1f5b808a6601e91111fae601df2b26369
	Issue introduced in 5.3 with commit c9626a2cbdb20e26587b3fad99960520a023432b and fixed in 5.18.4 with commit ab9f34a30c23f656e76f4c5b83125a4e7b53c86e
	Issue introduced in 5.3 with commit c9626a2cbdb20e26587b3fad99960520a023432b and fixed in 5.19 with commit 9dd732e0bdf538b1b76dc7c157e2b5e560ff30d3

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-2022-49358
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/netfilter/nf_tables_api.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/5b8d63489c3b701eb2a76f848ec94d8cbc9373b9
	https://git.kernel.org/stable/c/330c0c6cd2150a2d7f47af16aa590078b0d2f736
	https://git.kernel.org/stable/c/e33d9bd563e71f6c6528b96008d65524a459c4dc
	https://git.kernel.org/stable/c/80de9ea1f5b808a6601e91111fae601df2b26369
	https://git.kernel.org/stable/c/ab9f34a30c23f656e76f4c5b83125a4e7b53c86e
	https://git.kernel.org/stable/c/9dd732e0bdf538b1b76dc7c157e2b5e560ff30d3

                 reply	other threads:[~2025-02-26  2:13 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=2025022643-CVE-2022-49358-6cfd@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=cve@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.