From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-93115: platform/mellanox: mlxbf-pmc: Check ACPI_COMPANION() against NULL
Date: Thu, 17 Sep 2026 17:16:32 +0100 [thread overview]
Message-ID: <2026091748-CVE-2026-93115-defe@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
platform/mellanox: mlxbf-pmc: Check ACPI_COMPANION() against NULL
Every platform driver can be forced to match a device that doesn't match
its list of device IDs because of device_match_driver_override(), so
platform drivers that rely on the existence of a device's ACPI companion
object need to verify its presence.
mlxbf_pmc_probe() passes the result of ACPI_COMPANION() to
acpi_device_hid(), which dereferences it, so force-binding the driver to
a device without an ACPI companion leads to a NULL pointer dereference.
Accordingly, add a requisite ACPI_COMPANION() check against NULL to the
mlxbf-pmc driver and return -ENODEV when the companion is missing.
The Linux kernel CVE team has assigned CVE-2026-93115 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.11 with commit 1a218d312e65ec396b2739056a8ea78493015f21 and fixed in 5.15.221 with commit 950d8e8375f3ff4787de51b7bdf8dd23a3ad6547
Issue introduced in 5.11 with commit 1a218d312e65ec396b2739056a8ea78493015f21 and fixed in 6.1.188 with commit fdfb736282b9665c0169df0c4152ec91fdea2767
Issue introduced in 5.11 with commit 1a218d312e65ec396b2739056a8ea78493015f21 and fixed in 6.6.157 with commit bf1e0cc5cc1d4e71b699fc98cc9198ead0ed53e0
Issue introduced in 5.11 with commit 1a218d312e65ec396b2739056a8ea78493015f21 and fixed in 6.12.110 with commit a75b84119e56fc34b0f1403f3b93d357a55dabb6
Issue introduced in 5.11 with commit 1a218d312e65ec396b2739056a8ea78493015f21 and fixed in 6.18.52 with commit 71ba8b6e28f7a83b724036f5de07e03bb5473286
Issue introduced in 5.11 with commit 1a218d312e65ec396b2739056a8ea78493015f21 and fixed in 7.2.6 with commit d25dd08268aeaceb485189aaa84aa6d68a460291
Issue introduced in 5.11 with commit 1a218d312e65ec396b2739056a8ea78493015f21 and fixed in 7.3-rc1 with commit c38cce70adef874c2a7b5132c14d6c221401deff
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-93115
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/platform/mellanox/mlxbf-pmc.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/950d8e8375f3ff4787de51b7bdf8dd23a3ad6547
https://git.kernel.org/stable/c/fdfb736282b9665c0169df0c4152ec91fdea2767
https://git.kernel.org/stable/c/bf1e0cc5cc1d4e71b699fc98cc9198ead0ed53e0
https://git.kernel.org/stable/c/a75b84119e56fc34b0f1403f3b93d357a55dabb6
https://git.kernel.org/stable/c/71ba8b6e28f7a83b724036f5de07e03bb5473286
https://git.kernel.org/stable/c/d25dd08268aeaceb485189aaa84aa6d68a460291
https://git.kernel.org/stable/c/c38cce70adef874c2a7b5132c14d6c221401deff
reply other threads:[~2026-09-17 16:39 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=2026091748-CVE-2026-93115-defe@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.