MEDIUM 5.5

CVE-2026-53105: Linux Kernel MT7925 WiFi Driver Null Pointer Dereference DoS

A flaw in the Linux kernel's WiFi driver for MediaTek MT7925 chipsets can cause the system to crash if the driver attempts to process network transmission without proper initialization. The vulnerability exists because the code tries to access data from an uninitialized network interface object without first checking whether that object exists. An attacker with local access to a system running the affected driver could trigger this crash, causing a denial of service.

Source data · NVD / CISA · public domain

CVSS
3.1 · 5.5 MEDIUM · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weaknesses (CWE)
CWE-476
Affected products
1 configuration(s)
Published / Modified
2026-06-24 / 2026-07-23

NVD description (verbatim)

In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: mt7925: prevent NULL vif dereference in mt7925_mac_write_txwi Check for a NULL `vif` before accessing `ieee80211_vif_is_mld(vif)` to avoid a potential kernel panic in scenarios where `vif` might not be initialized.

4 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-53105 is a null pointer dereference vulnerability (CWE-476) in the mt7925_mac_write_txwi function within the Linux kernel's mt76 WiFi driver. The flaw occurs when the function attempts to call ieee80211_vif_is_mld() on a vif (virtual interface) pointer without validating that the pointer is non-null first. In scenarios where a vif is not properly initialized, this results in a kernel panic. The vulnerability requires local access and unprivileged execution context to exploit, making it a lower-privilege attack surface compared to remote network-based exploits.

Business impact

Systems running affected Linux kernel versions with MT7925 wireless hardware face localized availability risk. A local, unprivileged user can force a kernel panic, temporarily rendering the device unreachable over the network or unusable for its primary function. In enterprise environments with shared Linux systems, this could be weaponized by a lower-privileged account holder to disrupt service. However, the impact is containable through standard system restart procedures; no data confidentiality or integrity compromise occurs.

Affected systems

This vulnerability affects the Linux kernel across all maintained versions that include the mt76 driver with MT7925 chipset support. Systems using Mediatek MT7925 WiFi cards—commonly found in laptops, embedded systems, and network appliances—are in scope. You can verify your system's inclusion by checking kernel version and confirming mt7925 is loaded via lsmod or reviewing your device's wireless hardware specifications. Verify against your kernel release notes and vendor advisory for the exact versions addressed by upstream Linux kernel patches.

Exploitability

Exploitation requires local system access and unprivileged user privileges. An authenticated local user can craft conditions to invoke mt7925_mac_write_txwi with a null vif pointer, triggering the panic. No network interaction, authentication bypass, or privilege escalation is required as a prerequisite. The barrier to exploitation is low for anyone with shell access, but the impact is non-persistent denial of service only. No known public exploits are referenced in active threat tracking databases.

Remediation

Apply the upstream Linux kernel patch that adds null-pointer validation to mt7925_mac_write_txwi before the ieee80211_vif_is_mld() call. Most Linux distributions derive patches from upstream kernel development; check your vendor's security advisory for the specific kernel version containing this fix. Systems should be updated to the earliest patched kernel version available for your distribution. Kernel module recompilation or driver rebuild may be necessary if you maintain a custom kernel configuration.

Patch guidance

Identify your current Linux kernel version using `uname -r`. Cross-reference your kernel version against your distribution's security advisory or the upstream Linux kernel security database to determine if a patched version is available. For RHEL, Ubuntu, Debian, and other major distributions, kernel security updates are typically delivered as standard patch packages. Install the updated kernel package and reboot. Verify the fix by confirming the new kernel is running post-reboot and that mt7925 loads without additional errors in dmesg.

Detection guidance

Monitor system logs for kernel panic messages or oops events involving mt7925_mac_write_txwi, particularly those referencing null pointer dereferences. On systems where syslog or journalctl are active, search for entries like 'NULL pointer dereference at' combined with mt7925 or mt76 driver context. Kernel crash dumps, if available, will show the exact stack trace. Proactive detection is difficult without instrumentation; focus detection efforts on systems where the vulnerability window is known (unpatched kernel versions with MT7925 driver). Consider host-based monitoring that flags unexpected kernel panics correlating with wireless driver activity.

Why prioritize this

While the CVSS score of 5.5 (Medium) reflects limited scope and unprivileged access requirement, this vulnerability merits prompt attention because kernel-level denial-of-service flaws in wireless drivers are operationally disruptive in any environment. For organizations with remote workers using affected laptops or for edge devices relying on MT7925 connectivity, a single exploitation event forces a full system restart and service interruption. Prioritize patching any systems where MT7925 is the primary or sole wireless interface, and where local user access is a realistic threat model.

Risk score, explained

The CVSS 3.1 score of 5.5 reflects a local attack vector (AV:L), low complexity (AC:L), unprivileged user requirement (PR:L), and no user interaction needed (UI:N). The scope is unchanged (S:U), and the impact is high availability loss (A:H) with no confidentiality or integrity impact. This is a straightforward DoS without escalation or multi-stage requirements, placing it solidly in the Medium severity range. The score accurately captures that while impact is severe (system unavailability), the attack is bounded by local-only access.

Frequently asked questions

Do I need to check if my Linux system uses MT7925 wireless hardware?

Yes. You can check by running `lspci | grep -i mediatek` or `lsusb | grep -i mediatek` to identify MT7925 devices. If MT7925 is not present, this vulnerability does not apply to your system. Systems using different WiFi chipsets (e.g., Intel, Qualcomm) are unaffected.

If I'm running Linux in a VM with passed-through MT7925 hardware, am I vulnerable?

Yes. Any Linux kernel instance that loads the mt76 driver and registers MT7925 hardware is vulnerable until patched, regardless of whether it runs on bare metal or as a virtual machine with hardware passthrough.

What are the signs that someone has exploited this vulnerability on my system?

Exploitation manifests as unexpected kernel panics or system reboots. Check syslog or journalctl for stack traces mentioning mt7925_mac_write_txwi and NULL pointer dereference. Unlike many exploits, this one does not leave malware artifacts; the system simply crashes and reboots.

Are there any temporary mitigations if I cannot patch immediately?

Restrict local user shell access to trusted accounts only, as exploitation requires local authentication. Disabling the mt7925 driver entirely (if an alternative wireless interface exists) eliminates the attack surface but sacrifices functionality. The most practical mitigation is to prioritize kernel patching.

This analysis is based on vulnerability data published as of the last update and does not represent real-time threat intelligence. Patch availability and timelines vary by Linux distribution; consult your vendor's advisory for specific version recommendations. CVSS scores and severity assessments are subject to change as threat context evolves. No exploit code is provided or recommended. Organizations should conduct internal validation of patches before production deployment. Source: NVD (public-domain), retrieved 2026-08-01. Analysis generated by SEC.co (claude-haiku-4-5).