CVE-2025-37748: Vulnerability in Linux Linux
In the Linux kernel, the following vulnerability has been resolved: iommu/mediatek: Fix NULL pointer deference in mtk_iommu_device_group Currently, mtk_iommu calls during probe iommu_device_register before the hw_list from driver data is initialized. Since iommu probing issue fix, it leads to NULL pointer dereference in mtk_iommu_device_group when hw_list is accessed with list_first_entry (not null safe). So, change the call order to ensure iommu_device_register is called after the driver data are initialized.
AI Analysis
Technical Summary
CVE-2025-37748 is a vulnerability identified in the Linux kernel specifically within the Mediatek IOMMU (Input-Output Memory Management Unit) driver code. The issue arises due to a NULL pointer dereference in the function mtk_iommu_device_group. During the probe phase, the driver calls iommu_device_register before the hardware list (hw_list) from the driver data is properly initialized. Since the hw_list is accessed using list_first_entry, which is not NULL-safe, this premature call order leads to dereferencing a NULL pointer. This can cause the kernel to crash or behave unpredictably, resulting in a denial of service (DoS) condition. The fix involves reordering the calls to ensure that iommu_device_register is invoked only after the driver data, including hw_list, is fully initialized. This vulnerability is specific to Linux kernel versions containing the affected Mediatek IOMMU driver code and does not currently have any known exploits in the wild. The vulnerability does not have an assigned CVSS score yet, but the technical details indicate it is a stability and availability risk rather than a direct confidentiality or integrity compromise.
Potential Impact
For European organizations, this vulnerability primarily poses a risk of system instability and denial of service on Linux systems running affected Mediatek IOMMU drivers. Systems using Mediatek SoCs with this IOMMU implementation, such as embedded devices, network equipment, or specialized industrial systems, could experience kernel panics or crashes if exploited. This could disrupt critical services, especially in sectors relying on embedded Linux devices like telecommunications, manufacturing automation, or IoT deployments. While this vulnerability does not directly lead to privilege escalation or data breaches, the resulting downtime or service interruptions could impact operational continuity and availability. Organizations with large-scale Linux deployments or those using Mediatek hardware in their infrastructure should be particularly cautious. The absence of known exploits reduces immediate risk, but the vulnerability's presence in kernel code means that attackers with local access could potentially trigger crashes, making it a concern for multi-tenant environments or shared hosting.
Mitigation Recommendations
To mitigate this vulnerability, European organizations should prioritize updating their Linux kernel to the patched version where the call order in the Mediatek IOMMU driver is corrected. Since the vulnerability is in the kernel driver code, applying vendor-provided kernel updates or patches is the most effective measure. For embedded or specialized devices, coordinate with hardware vendors or device manufacturers to obtain updated firmware or kernel images. Additionally, organizations should restrict local access to affected systems to trusted users only, minimizing the risk of malicious triggering of the NULL pointer dereference. Monitoring system logs for kernel crashes or unusual reboots can help detect exploitation attempts. In environments where immediate patching is not feasible, consider isolating affected devices or limiting their network exposure to reduce attack surface. Finally, maintain an inventory of devices using Mediatek SoCs and assess their exposure to this vulnerability to prioritize remediation efforts.
Affected Countries
Germany, France, United Kingdom, Italy, Spain, Netherlands, Poland, Sweden, Finland
CVE-2025-37748: Vulnerability in Linux Linux
Description
In the Linux kernel, the following vulnerability has been resolved: iommu/mediatek: Fix NULL pointer deference in mtk_iommu_device_group Currently, mtk_iommu calls during probe iommu_device_register before the hw_list from driver data is initialized. Since iommu probing issue fix, it leads to NULL pointer dereference in mtk_iommu_device_group when hw_list is accessed with list_first_entry (not null safe). So, change the call order to ensure iommu_device_register is called after the driver data are initialized.
AI-Powered Analysis
Technical Analysis
CVE-2025-37748 is a vulnerability identified in the Linux kernel specifically within the Mediatek IOMMU (Input-Output Memory Management Unit) driver code. The issue arises due to a NULL pointer dereference in the function mtk_iommu_device_group. During the probe phase, the driver calls iommu_device_register before the hardware list (hw_list) from the driver data is properly initialized. Since the hw_list is accessed using list_first_entry, which is not NULL-safe, this premature call order leads to dereferencing a NULL pointer. This can cause the kernel to crash or behave unpredictably, resulting in a denial of service (DoS) condition. The fix involves reordering the calls to ensure that iommu_device_register is invoked only after the driver data, including hw_list, is fully initialized. This vulnerability is specific to Linux kernel versions containing the affected Mediatek IOMMU driver code and does not currently have any known exploits in the wild. The vulnerability does not have an assigned CVSS score yet, but the technical details indicate it is a stability and availability risk rather than a direct confidentiality or integrity compromise.
Potential Impact
For European organizations, this vulnerability primarily poses a risk of system instability and denial of service on Linux systems running affected Mediatek IOMMU drivers. Systems using Mediatek SoCs with this IOMMU implementation, such as embedded devices, network equipment, or specialized industrial systems, could experience kernel panics or crashes if exploited. This could disrupt critical services, especially in sectors relying on embedded Linux devices like telecommunications, manufacturing automation, or IoT deployments. While this vulnerability does not directly lead to privilege escalation or data breaches, the resulting downtime or service interruptions could impact operational continuity and availability. Organizations with large-scale Linux deployments or those using Mediatek hardware in their infrastructure should be particularly cautious. The absence of known exploits reduces immediate risk, but the vulnerability's presence in kernel code means that attackers with local access could potentially trigger crashes, making it a concern for multi-tenant environments or shared hosting.
Mitigation Recommendations
To mitigate this vulnerability, European organizations should prioritize updating their Linux kernel to the patched version where the call order in the Mediatek IOMMU driver is corrected. Since the vulnerability is in the kernel driver code, applying vendor-provided kernel updates or patches is the most effective measure. For embedded or specialized devices, coordinate with hardware vendors or device manufacturers to obtain updated firmware or kernel images. Additionally, organizations should restrict local access to affected systems to trusted users only, minimizing the risk of malicious triggering of the NULL pointer dereference. Monitoring system logs for kernel crashes or unusual reboots can help detect exploitation attempts. In environments where immediate patching is not feasible, consider isolating affected devices or limiting their network exposure to reduce attack surface. Finally, maintain an inventory of devices using Mediatek SoCs and assess their exposure to this vulnerability to prioritize remediation efforts.
Affected Countries
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Linux
- Date Reserved
- 2025-04-16T04:51:23.936Z
- Cisa Enriched
- false
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d9832c4522896dcbe82f1
Added to database: 5/21/2025, 9:09:06 AM
Last enriched: 7/3/2025, 10:39:37 PM
Last updated: 1/7/2026, 4:15:18 AM
Views: 48
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-20893: Origin validation error in Fujitsu Client Computing Limited Fujitsu Security Solution AuthConductor Client Basic V2
HighCVE-2025-14891: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in ivole Customer Reviews for WooCommerce
MediumCVE-2025-14059: CWE-73 External Control of File Name or Path in roxnor EmailKit – Email Customizer for WooCommerce & WP
MediumCVE-2025-12648: CWE-552 Files or Directories Accessible to External Parties in cbutlerjr WP-Members Membership Plugin
MediumCVE-2025-14631: CWE-476 NULL Pointer Dereference in TP-Link Systems Inc. Archer BE400
HighActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.