CVE-2025-37972: Vulnerability in Linux Linux
In the Linux kernel, the following vulnerability has been resolved: Input: mtk-pmic-keys - fix possible null pointer dereference In mtk_pmic_keys_probe, the regs parameter is only set if the button is parsed in the device tree. However, on hardware where the button is left floating, that node will most likely be removed not to enable that input. In that case the code will try to dereference a null pointer. Let's use the regs struct instead as it is defined for all supported platforms. Note that it is ok setting the key reg even if that latter is disabled as the interrupt won't be enabled anyway.
AI Analysis
Technical Summary
CVE-2025-37972 is a vulnerability identified in the Linux kernel specifically related to the mtk-pmic-keys driver, which handles power management integrated circuit (PMIC) key inputs on certain MediaTek platforms. The root cause of the vulnerability is a possible null pointer dereference in the function mtk_pmic_keys_probe. This function attempts to set up input keys based on device tree configurations. However, on hardware where the button input is left floating or disabled, the corresponding device tree node is typically removed to prevent enabling that input. In such cases, the regs parameter, which should point to the register structure, remains unset (null). The vulnerable code then attempts to dereference this null pointer, leading to a potential kernel crash or denial of service. The fix involves using a regs struct that is defined for all supported platforms regardless of the device tree node presence. This approach avoids dereferencing a null pointer by always referencing a valid structure, even if the key register is disabled and its interrupt is not enabled. This vulnerability is specific to certain Linux kernel versions identified by the commit hash b581acb49aec5c3b0af9ab1c537fb73481b79069 and affects systems using the MediaTek PMIC keys driver. No known exploits are currently reported in the wild, and no CVSS score has been assigned yet. The vulnerability primarily risks system stability by causing kernel crashes due to null pointer dereference, which can be triggered without authentication or user interaction if the affected driver is loaded and the hardware configuration matches the described scenario.
Potential Impact
For European organizations, the impact of CVE-2025-37972 centers on system availability and reliability. Systems running vulnerable Linux kernel versions on MediaTek platforms with the mtk-pmic-keys driver could experience kernel panics or crashes, leading to denial of service conditions. This could disrupt critical infrastructure, embedded devices, or enterprise systems that rely on these platforms. Although the vulnerability does not directly expose confidentiality or integrity risks, the resulting downtime could affect operational continuity, especially in sectors like telecommunications, manufacturing, or IoT deployments where MediaTek hardware is prevalent. The lack of known exploits reduces immediate risk, but unpatched systems remain vulnerable to potential future exploitation. European organizations with embedded Linux devices or servers using affected kernels should be aware of this threat to prevent unexpected outages. The vulnerability's exploitation does not require user interaction or authentication, increasing the risk if vulnerable devices are exposed or accessible within internal networks.
Mitigation Recommendations
To mitigate CVE-2025-37972, European organizations should: 1) Identify all Linux systems running the affected kernel versions, particularly those using MediaTek hardware with the mtk-pmic-keys driver. 2) Apply the official Linux kernel patches or updates that address this null pointer dereference vulnerability as soon as they become available. 3) For embedded or IoT devices where kernel updates may be delayed, consider disabling the mtk-pmic-keys driver if the hardware configuration does not require it, thereby eliminating the vulnerable code path. 4) Implement monitoring for kernel crashes or unexpected reboots that could indicate exploitation attempts or trigger conditions. 5) Restrict network access to vulnerable devices to reduce exposure, especially from untrusted networks. 6) Engage with hardware and software vendors to ensure timely updates and support for affected platforms. These steps go beyond generic advice by focusing on hardware-specific driver management and proactive system inventory and monitoring.
Affected Countries
Germany, France, United Kingdom, Italy, Spain, Netherlands, Poland, Sweden, Finland
CVE-2025-37972: Vulnerability in Linux Linux
Description
In the Linux kernel, the following vulnerability has been resolved: Input: mtk-pmic-keys - fix possible null pointer dereference In mtk_pmic_keys_probe, the regs parameter is only set if the button is parsed in the device tree. However, on hardware where the button is left floating, that node will most likely be removed not to enable that input. In that case the code will try to dereference a null pointer. Let's use the regs struct instead as it is defined for all supported platforms. Note that it is ok setting the key reg even if that latter is disabled as the interrupt won't be enabled anyway.
AI-Powered Analysis
Technical Analysis
CVE-2025-37972 is a vulnerability identified in the Linux kernel specifically related to the mtk-pmic-keys driver, which handles power management integrated circuit (PMIC) key inputs on certain MediaTek platforms. The root cause of the vulnerability is a possible null pointer dereference in the function mtk_pmic_keys_probe. This function attempts to set up input keys based on device tree configurations. However, on hardware where the button input is left floating or disabled, the corresponding device tree node is typically removed to prevent enabling that input. In such cases, the regs parameter, which should point to the register structure, remains unset (null). The vulnerable code then attempts to dereference this null pointer, leading to a potential kernel crash or denial of service. The fix involves using a regs struct that is defined for all supported platforms regardless of the device tree node presence. This approach avoids dereferencing a null pointer by always referencing a valid structure, even if the key register is disabled and its interrupt is not enabled. This vulnerability is specific to certain Linux kernel versions identified by the commit hash b581acb49aec5c3b0af9ab1c537fb73481b79069 and affects systems using the MediaTek PMIC keys driver. No known exploits are currently reported in the wild, and no CVSS score has been assigned yet. The vulnerability primarily risks system stability by causing kernel crashes due to null pointer dereference, which can be triggered without authentication or user interaction if the affected driver is loaded and the hardware configuration matches the described scenario.
Potential Impact
For European organizations, the impact of CVE-2025-37972 centers on system availability and reliability. Systems running vulnerable Linux kernel versions on MediaTek platforms with the mtk-pmic-keys driver could experience kernel panics or crashes, leading to denial of service conditions. This could disrupt critical infrastructure, embedded devices, or enterprise systems that rely on these platforms. Although the vulnerability does not directly expose confidentiality or integrity risks, the resulting downtime could affect operational continuity, especially in sectors like telecommunications, manufacturing, or IoT deployments where MediaTek hardware is prevalent. The lack of known exploits reduces immediate risk, but unpatched systems remain vulnerable to potential future exploitation. European organizations with embedded Linux devices or servers using affected kernels should be aware of this threat to prevent unexpected outages. The vulnerability's exploitation does not require user interaction or authentication, increasing the risk if vulnerable devices are exposed or accessible within internal networks.
Mitigation Recommendations
To mitigate CVE-2025-37972, European organizations should: 1) Identify all Linux systems running the affected kernel versions, particularly those using MediaTek hardware with the mtk-pmic-keys driver. 2) Apply the official Linux kernel patches or updates that address this null pointer dereference vulnerability as soon as they become available. 3) For embedded or IoT devices where kernel updates may be delayed, consider disabling the mtk-pmic-keys driver if the hardware configuration does not require it, thereby eliminating the vulnerable code path. 4) Implement monitoring for kernel crashes or unexpected reboots that could indicate exploitation attempts or trigger conditions. 5) Restrict network access to vulnerable devices to reduce exposure, especially from untrusted networks. 6) Engage with hardware and software vendors to ensure timely updates and support for affected platforms. These steps go beyond generic advice by focusing on hardware-specific driver management and proactive system inventory and monitoring.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Linux
- Date Reserved
- 2025-04-16T04:51:23.975Z
- Cisa Enriched
- false
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682cd0f71484d88663aeae39
Added to database: 5/20/2025, 6:59:03 PM
Last enriched: 7/3/2025, 7:11:27 PM
Last updated: 8/18/2025, 11:32:18 PM
Views: 11
Related Threats
CVE-2025-8453: CWE-269 Improper Privilege Management in Schneider Electric Saitel DR RTU
HighCVE-2025-54175: CWE-79 Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') in OpenSolution Quick.CMS.EXT
MediumCVE-2025-54174: CWE-352 Cross-Site Request Forgery (CSRF) in OpenSolution Quick.CMS
MediumCVE-2025-54172: CWE-79 Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') in OpenSolution Quick.CMS
MediumCVE-2025-43749: CWE-552 Files or Directories Accessible to External Parties in Liferay Portal
MediumActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.