Linux ACPI
 help / color / mirror / Atom feed
From: Artem Dinaburg <artem@trailofbits.com>
To: stable@vger.kernel.org
Cc: andriy.shevchenko@linux.intel.com, lenb@kernel.org,
	linux-acpi@vger.kernel.org, rafael.j.wysocki@intel.com,
	rafael@kernel.org
Subject: [6.18.y] Please pick ACPI platform parent lifetime fix
Date: Fri, 20 Nov 2026 14:23:36 -0500	[thread overview]
Message-ID: <20261120192336.26131-1-artem@trailofbits.com> (raw)

Hi,

Please pick commit a9ba4dd2f18bf3f439d9ef0d8f375f90360ba1bd ("ACPI:
platform: Use acpi_bus_get_primary_device()") for 6.18.y. It fixes
CVE-2026-100072.

acpi_create_platform_device() looks up the parent's physical device with
acpi_get_first_physical_node(), which does not take a reference, so in
theory that device may be freed while it is still in use. The fix takes
one reference with acpi_bus_get_primary_device() and holds it through
resource inspection and platform-device registration.

The fix is in 6.6.160, 6.12.114 and 7.2.6, and in mainline since 7.3.
6.18.y received only its prerequisite, upstream commit 72530e1f72b0
("ACPI: bus: Introduce acpi_bus_get_primary_device()"), in 6.18.57; the
fix itself did not apply to 6.18.y at that time. It applies unchanged
since 6.18.60, which picked up the ACPI scan changes f234fdaae1ca,
7617cc05df28 and ab06eb920401 that it depends on for context.

Compiled drivers/acpi/acpi_platform.o on 6.18.64 from a cumulative
x86_64 tree using allmodconfig. No kernel boot or runtime test was
performed.

An LLM was used to check applicability and stable-queue history and to
draft this request; I reviewed the result.

Thanks,
Artem Dinaburg

                 reply	other threads:[~2026-11-20 19:23 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=20261120192336.26131-1-artem@trailofbits.com \
    --to=artem@trailofbits.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rafael@kernel.org \
    --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