CVE-2025-38513

published 16 Aug 2025 · updated 11 May 2026

wifi: zd1211rw: Fix potential NULL pointer dereference in zd_mac_tx_to_dev()

5.5MediumCVSS 5.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 014c34dc132015c4f918ada4982e952947ac1047, Kernel 5420de65efbeb6503bcf1d43451c9df67ad60298, Kernel 602b4eb2f25668de15de69860ec99caf65b3684d and 5 more.

In the Linux kernel, the following vulnerability has been resolved: wifi: zd1211rw: Fix potential NULL pointer dereference in zd_mac_tx_to_dev() There is a potential NULL pointer dereference in zd_mac_tx_to_dev(). For example, the following is possible: T0 T1 zd_mac_tx_to_dev() /* len == skb_queue_len(q) */ while (len > ZD_MAC_MAX_ACK_WAITERS) { filter_ack() spin_lock_irqsave(&q->lock, flags); /* position == skb_queue_len(q) */ for (i=1; i<position; i++) skb = __skb_dequeue(q) if (mac->type == NL80211_IFTYPE_AP) skb = __skb_dequeue(q); spin_unlock_irqrestore(&q->lock, flags); skb_dequeue() -> NULL Since there is a small gap between checking skb queue length and skb being unconditionally dequeued in zd_mac_tx_to_dev(), skb_dequeue() can return NULL. Then the pointer is passed to zd_mac_tx_status() where it is dereferenced. In order to avoid potential NULL pointer dereference due to situations like above, check if skb is not NULL before passing it to zd_mac_tx_status(). Found by Linux Verification Center (linuxtesting.org) with SVACE.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=2.6.25, >=459c51ad6e1fc19e91a53798358433d3c08cd09d <014c34dc132015c4f918ada4982e952947ac1047, >=459c51ad6e1fc19e91a53798358433d3c08cd09d <5420de65efbeb6503bcf1d43451c9df67ad60298, >=459c51ad6e1fc19e91a53798358433d3c08cd09d <602b4eb2f25668de15de69860ec99caf65b3684d, >=459c51ad6e1fc19e91a53798358433d3c08cd09d <74b1ec9f5d627d2bdd5e5b6f3f81c23317657023, >=459c51ad6e1fc19e91a53798358433d3c08cd09d <adf08c96b963c7cd7ec1ee1c0c556228d9bedaae, >=459c51ad6e1fc19e91a53798358433d3c08cd09d <b24f65c184540dfb967479320ecf7e8c2e9220dc, >=459c51ad6e1fc19e91a53798358433d3c08cd09d <c1958270de947604cc6de05fc96dbba256b49cf0, >=459c51ad6e1fc19e91a53798358433d3c08cd09d <fcd9c923b58e86501450b9b442ccc7ce4a8d0fda014c34dc132015c4f918ada4982e952947ac1047, 5420de65efbeb6503bcf1d43451c9df67ad60298, 602b4eb2f25668de15de69860ec99caf65b3684d, 74b1ec9f5d627d2bdd5e5b6f3f81c23317657023, adf08c96b963c7cd7ec1ee1c0c556228d9bedaae, b24f65c184540dfb967479320ecf7e8c2e9220dc, c1958270de947604cc6de05fc96dbba256b49cf0, fcd9c923b58e86501450b9b442ccc7ce4a8d0fda

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2025-38513 severity on Zeptric[![CVE-2025-38513](https://zeptric.io/badge/cve/CVE-2025-38513.svg)](https://zeptric.io/cve/CVE-2025-38513)