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@kernel.org>
Subject: CVE-2026-74525: net: sxgbe: free TX rings on RX allocation failure
Date: Sat, 15 Aug 2026 21:26:46 +0900	[thread overview]
Message-ID: <2026081545-CVE-2026-74525-47b2@gregkh> (raw)

From: Greg Kroah-Hartman <gregkh@kernel.org>

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

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

net: sxgbe: free TX rings on RX allocation failure

When RX descriptor ring allocation fails, init_dma_desc_rings() only
frees the partially allocated RX rings and returns. The TX rings that
were allocated earlier in the same function are leaked.

Rearrange error labels to clean up TX rings upon RX failures.

The Linux kernel CVE team has assigned CVE-2026-74525 to this issue.


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

	Issue introduced in 3.15 with commit 1edb9ca69e8a7988900fc0283e10550b5592164d and fixed in 6.6.151 with commit 3563e2486dcd50a751dbcbc1de37e5186646dce6
	Issue introduced in 3.15 with commit 1edb9ca69e8a7988900fc0283e10550b5592164d and fixed in 6.12.103 with commit b33644a4f6d8f127c62d7b39f24114d3d2499204
	Issue introduced in 3.15 with commit 1edb9ca69e8a7988900fc0283e10550b5592164d and fixed in 6.18.44 with commit 42b87cfd9666ef156637c90ff3f6f6dd9a5ad4cb
	Issue introduced in 3.15 with commit 1edb9ca69e8a7988900fc0283e10550b5592164d and fixed in 7.1.8 with commit f2e5bb9fb710553e76a3be9097b448b4e73d8c92
	Issue introduced in 3.15 with commit 1edb9ca69e8a7988900fc0283e10550b5592164d and fixed in 7.2-rc6 with commit c870f7e2890b9f78ac84515a9809cc5c183c975e

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-74525
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:
	drivers/net/ethernet/samsung/sxgbe/sxgbe_main.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/3563e2486dcd50a751dbcbc1de37e5186646dce6
	https://git.kernel.org/stable/c/b33644a4f6d8f127c62d7b39f24114d3d2499204
	https://git.kernel.org/stable/c/42b87cfd9666ef156637c90ff3f6f6dd9a5ad4cb
	https://git.kernel.org/stable/c/f2e5bb9fb710553e76a3be9097b448b4e73d8c92
	https://git.kernel.org/stable/c/c870f7e2890b9f78ac84515a9809cc5c183c975e

                 reply	other threads:[~2026-08-15 12:31 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=2026081545-CVE-2026-74525-47b2@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 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.