Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 32 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 88% of all CVEs (13 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 1a218d312e65ec396b2739056a8ea78493015f21 – < 950d8e8375f3ff4787de51b7bdf8dd23a3ad6547
    • affected 1a218d312e65ec396b2739056a8ea78493015f21 – < fdfb736282b9665c0169df0c4152ec91fdea2767
    • affected 1a218d312e65ec396b2739056a8ea78493015f21 – < bf1e0cc5cc1d4e71b699fc98cc9198ead0ed53e0
    • affected 1a218d312e65ec396b2739056a8ea78493015f21 – < a75b84119e56fc34b0f1403f3b93d357a55dabb6
    • affected 1a218d312e65ec396b2739056a8ea78493015f21 – < 71ba8b6e28f7a83b724036f5de07e03bb5473286
    • affected 1a218d312e65ec396b2739056a8ea78493015f21 – < d25dd08268aeaceb485189aaa84aa6d68a460291
    • affected 1a218d312e65ec396b2739056a8ea78493015f21 – < c38cce70adef874c2a7b5132c14d6c221401deff
  • Linux · Linux

    • affected 5.11
    • unaffected < 5.11
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-93115 badge
[![CVE-2026-93115](https://cveledger.app/badge/CVE-2026-93115.svg)](https://cveledger.app/cve/CVE-2026-93115)

Record last updated .