CVE-2026-99529 in Linuxinfo

Summary

by MITRE • 11/19/2026

In the Linux kernel, the following vulnerability has been resolved:

wifi: b43: fix use-after-free in b43_bcma_remove()

b43_one_core_detach() frees the struct b43_wldev it is given the bus device of. b43_bcma_remove() then reads wldev->dev again to free the bus device, which is a read of freed memory.

b43_ssb_remove() does not have the problem: it takes a copy of wldev->dev at the start. Do the same here.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Analysis

by VulDB Data Team • 11/19/2026

The Linux kernel vulnerability identified in the b43 wireless driver involves a critical use-after-free error within the bcma bus removal routine, specifically located in the function b43_bcma_remove(). This flaw arises from an improper handling of memory pointers during device detachment sequences. The root cause lies in the sequence of operations performed when removing a core associated with this legacy Broadcom wireless hardware interface. During the cleanup process, the helper function b43_one_core_detach is invoked to release resources associated with a specific wireless LAN device structure, denoted as struct b43_wldev. Crucially, this detachment routine frees the memory allocated for the wldev structure itself, including its embedded bus device pointer.

Following the execution of b43_one_core_detach, the control flow proceeds to access members of the now-deallocated wldev object. Specifically, the code attempts to read the dev field from the freed struct b43_wldev in order to subsequently free the associated bus device resource. Because the memory containing this pointer has already been returned to the system allocator and potentially overwritten by other allocations, accessing it constitutes a use-after-free condition. This type of error falls under CWE-416, which describes referencing memory after it has been freed, leading to unpredictable behavior such as kernel panics, data corruption, or potential privilege escalation if an attacker can control the contents of the reclaimed memory region.

The operational impact of this vulnerability is significant for system stability and security. In a local context, triggering this code path through device removal events could cause immediate kernel crashes, resulting in denial-of-service conditions that disrupt network connectivity and require a system reboot. From a remote exploitation perspective, if an attacker can influence the timing or state of wireless interface operations, they might leverage the use-after-free to execute arbitrary code within the kernel space by manipulating what gets allocated into the freed memory slot before it is accessed again. This aligns with ATT&CK technique T1059, specifically command and script interpretation via system-level APIs, although in this case, the immediate vector is a local privilege escalation through kernel exploitation rather than direct user-space execution.

A comparative analysis reveals that the similar removal routine for SSB bus devices, b43_ssb_remove(), does not suffer from this flaw because it employs a defensive programming pattern. That function creates an early copy of the wldev->dev pointer at the beginning of its execution, ensuring that even if subsequent operations free or modify the original structure, the copied reference remains valid for cleanup purposes. The resolution applied to b43_bcma_remove() mirrors this established best practice by capturing a local copy of the device pointer before any detachment logic is executed. This ensures that the final deallocation step operates on a stable, independent reference rather than relying on data within a structure that may no longer exist in memory.

Mitigation strategies for organizations running affected Linux kernels involve applying vendor-provided security patches as soon as they become available. Since this vulnerability exists in core kernel networking drivers, it is not easily mitigated through application-level controls or network segmentation alone. Administrators should prioritize patching systems with Broadcom wireless hardware that utilize the b43 driver stack. Additionally, enabling Kernel Self-Protection Project features such as KASLR and SLUB debugging can help mitigate exploitation attempts by randomizing memory layouts and detecting invalid accesses during development phases, though these are not substitutes for applying the code fix itself. Regular auditing of kernel logs for oops or panic messages related to b43 devices may also aid in identifying systems where this vulnerability has been triggered inadvertently through hardware removal events.

Responsible

Linux

Reservation

09/25/2026

Disclosure

11/19/2026

Moderation

accepted

CPE

ready

EPSS

0.00174

KEV

no

Activities

very low

Sources

Interested in the pricing of exploits?

See the underground prices here!