Skip to main content
VulnerabilityPublished Updated

CVE-2026-93115: Linux kernel · platform/mellanox: mlxbf-pmc: Check ACPI_COMPANION() against NULL

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in fdfb736282b9665c0169df0c4152ec91fdea2767 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 12:55 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in fdfb736282b9665c0169df0c4152ec91fdea2767, d25dd08268aeaceb485189aaa84aa6d68a460291, c38cce70adef874c2a7b5132c14d6c221401deff +4

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 1a218d312e65ec396b2739056a8ea78493015f21, < fdfb736282b9665c0169df0c4152ec91fdea2767
Fixed in
  • fdfb736282b9665c0169df0c4152ec91fdea2767
LinuxLinuxAffected
  • ≥ 1a218d312e65ec396b2739056a8ea78493015f21, < d25dd08268aeaceb485189aaa84aa6d68a460291
Fixed in
  • d25dd08268aeaceb485189aaa84aa6d68a460291
LinuxLinuxAffected
  • ≥ 1a218d312e65ec396b2739056a8ea78493015f21, < c38cce70adef874c2a7b5132c14d6c221401deff
Fixed in
  • c38cce70adef874c2a7b5132c14d6c221401deff
LinuxLinuxAffected
  • ≥ 1a218d312e65ec396b2739056a8ea78493015f21, < bf1e0cc5cc1d4e71b699fc98cc9198ead0ed53e0
Fixed in
  • bf1e0cc5cc1d4e71b699fc98cc9198ead0ed53e0
LinuxLinuxAffected
  • ≥ 1a218d312e65ec396b2739056a8ea78493015f21, < a75b84119e56fc34b0f1403f3b93d357a55dabb6
Fixed in
  • a75b84119e56fc34b0f1403f3b93d357a55dabb6
LinuxLinuxAffected
  • ≥ 1a218d312e65ec396b2739056a8ea78493015f21, < 950d8e8375f3ff4787de51b7bdf8dd23a3ad6547
Fixed in
  • 950d8e8375f3ff4787de51b7bdf8dd23a3ad6547

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.

References

Community reviews

Loading reviews…