Skip to main content
VulnerabilityPublished Updated

CVE-2025-37972: Linux kernel · Input: mtk-pmic-keys – fix possible null pointer dereference

Affects Linux kernelSource GCVE Database

0
Compare

Not known to be exploited.

Data as of 10 Nov 2026, 14:35 UTC

Severity
Medium

Rated Medium by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 May 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 10 Nov 2026.

What to do

AI-suggested

A fix has been implemented in the Linux kernel to address this issue by modifying the mtk_pmic_keys_probe function to use a consistently defined regs struct. Users should update to the fixed kernel version once available. No additional mitigation steps are specified.

Description

A null pointer dereference vulnerability was identified and fixed in the Linux kernel's mtk-pmic-keys input driver. The issue occurs when the device tree does not define a button node, causing the code to dereference a null pointer. The fix involves using a regs struct that is always defined for supported platforms to avoid this dereference.

References

Community reviews

Loading reviews…