platform/mellanox: mlxbf-pmc: Check ACPI_COMPANION() against NULL
Summary
| CVE | CVE-2026-93115 |
|---|
| State | PUBLISHED |
|---|
| Assigner | Linux |
|---|
| Source Priority | CVE Program / NVD first with legacy fallback |
|---|
| Published | 2026-09-17 17:18:06 UTC |
|---|
| Updated | 2026-09-17 17:18:06 UTC |
|---|
| 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. |
|---|
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 1a218d312e65ec396b2739056a8ea78493015f21 950d8e8375f3ff4787de51b7bdf8dd23a3ad6547 git |
Not specified |
| CNA |
Linux |
Linux |
affected 1a218d312e65ec396b2739056a8ea78493015f21 fdfb736282b9665c0169df0c4152ec91fdea2767 git |
Not specified |
| CNA |
Linux |
Linux |
affected 1a218d312e65ec396b2739056a8ea78493015f21 bf1e0cc5cc1d4e71b699fc98cc9198ead0ed53e0 git |
Not specified |
| CNA |
Linux |
Linux |
affected 1a218d312e65ec396b2739056a8ea78493015f21 a75b84119e56fc34b0f1403f3b93d357a55dabb6 git |
Not specified |
| CNA |
Linux |
Linux |
affected 1a218d312e65ec396b2739056a8ea78493015f21 71ba8b6e28f7a83b724036f5de07e03bb5473286 git |
Not specified |
| CNA |
Linux |
Linux |
affected 1a218d312e65ec396b2739056a8ea78493015f21 d25dd08268aeaceb485189aaa84aa6d68a460291 git |
Not specified |
| CNA |
Linux |
Linux |
affected 1a218d312e65ec396b2739056a8ea78493015f21 c38cce70adef874c2a7b5132c14d6c221401deff git |
Not specified |
| CNA |
Linux |
Linux |
affected 5.11 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.11 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.15.221 5.15.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.1.188 6.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.157 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.110 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.52 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2.6 7.2.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.3-rc1 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/950d8e8375f3ff4787de51b7bdf8dd23a3ad6547 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/fdfb736282b9665c0169df0c4152ec91fdea2767 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/d25dd08268aeaceb485189aaa84aa6d68a460291 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/bf1e0cc5cc1d4e71b699fc98cc9198ead0ed53e0 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/71ba8b6e28f7a83b724036f5de07e03bb5473286 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/c38cce70adef874c2a7b5132c14d6c221401deff |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/a75b84119e56fc34b0f1403f3b93d357a55dabb6 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.