mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Artem Dinaburg <artem@trailofbits.com>
To: stable@vger.kernel.org
Cc: abdun.nihaal@gmail.com, christian.gromm@microchip.com,
	error27@gmail.com, gregkh@linuxfoundation.org, johan@kernel.org,
	knavaneeth786@gmail.com, linux-kernel@vger.kernel.org,
	parthiban.veerasooran@microchip.com
Subject: [PATCH 6.6.y 0/2] CVE-2025-71272, CVE-2026-43317: backport fix series
Date: Wed, 14 Oct 2026 15:14:50 -0400	[thread overview]
Message-ID: <20261014191452.23814-1-artem@trailofbits.com> (raw)

Hi,

Please consider this backport series for CVE-2025-71272, CVE-2026-43317 to
6.6.y.

Apply the patches in this order:
1. most: core: fix resource leak in most_register_interface error paths (fix)
2. most: core: fix leak on early registration failure (fix)

Patch 1 initializes the interface device before ID allocation and releases
the device, ID and private storage on registration failures.

Patch 2 moves callback and channel-count validation after device
initialization so those early failures also release the device. The code
changes in both patches are identical to upstream.

The complete fix is already present in 6.12.y, 6.18.y and 7.2.y.

Build-tested only as part of a cumulative 6.6.y series: x86_64 objects
(allmodconfig, CONFIG_WERROR=y); no runtime testing.

An LLM assisted with preparing these backports.

Thanks,
Artem Dinaburg

             reply	other threads:[~2026-10-14 19:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-14 19:14 Artem Dinaburg [this message]
2026-10-14 19:14 ` [PATCH 6.6.y 1/2] most: core: fix resource leak in most_register_interface error paths Artem Dinaburg
2026-10-14 19:14 ` [PATCH 6.6.y 2/2] most: core: fix leak on early registration failure Artem Dinaburg

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=20261014191452.23814-1-artem@trailofbits.com \
    --to=artem@trailofbits.com \
    --cc=abdun.nihaal@gmail.com \
    --cc=christian.gromm@microchip.com \
    --cc=error27@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=johan@kernel.org \
    --cc=knavaneeth786@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=parthiban.veerasooran@microchip.com \
    --cc=stable@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
all inboxes | Powered by JetHome®