CVE-2026-72005

published 15 Aug 2026 · updated 19 Nov 2026

wifi: rt2x00: avoid full teardown before work setup in probe

7.8HighCVSS 7.8EPSS 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 eb7474d0253bb2de4793e1d3ce833e8564bbe732, Kernel 3c0427d719bddb33caf18ff4ffb77cb47de7eb00, Kernel 536fb3d739d75a03cb318c0c6fe799425cfea501 and 12 more.

In the Linux kernel, the following vulnerability has been resolved: wifi: rt2x00: avoid full teardown before work setup in probe rt2x00lib_probe_dev() uses the full rt2x00lib_remove_dev() teardown for all probe failures. However, drv_data allocation and workqueue allocation can fail before intf_work, autowakeup_work and sleep_work have been initialized. Do not enter the full remove path until the probe has reached the point where those work items are set up. Return directly for drv_data allocation failure, and use a small early cleanup path for workqueue allocation failure. This issue was found by our static analysis tool and then confirmed by manual review of rt2x00lib_probe_dev() and rt2x00lib_remove_dev(). The early probe exits should not call a common teardown path that assumes the later work setup has already completed. A QEMU PoC forced alloc_ordered_workqueue() to fail before the work initializers are reached. The resulting fail path entered rt2x00lib_remove_dev(), and DEBUG_OBJECTS reported invalid work drains with rt2x00lib_probe_dev() and rt2x00lib_remove_dev() in the stack.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=0439f5367c8d8bb2ebaca8d7329f51f3148b2fb2 <eb7474d0253bb2de4793e1d3ce833e8564bbe732, >=0439f5367c8d8bb2ebaca8d7329f51f3148b2fb2 <3c0427d719bddb33caf18ff4ffb77cb47de7eb00, >=0439f5367c8d8bb2ebaca8d7329f51f3148b2fb2 <536fb3d739d75a03cb318c0c6fe799425cfea501, >=0439f5367c8d8bb2ebaca8d7329f51f3148b2fb2 <56994852d704535ea354a4627ca667b1b4fa0deb, >=0439f5367c8d8bb2ebaca8d7329f51f3148b2fb2 <59afe6148927395cf86f9429900e029a48b1d42b, >=0439f5367c8d8bb2ebaca8d7329f51f3148b2fb2 <66bd9b1a72de7c2f5141b02d796048aafaed8a49, >=0439f5367c8d8bb2ebaca8d7329f51f3148b2fb2 <816559409e340acaa5c9d868291dab30d8c80263, >=0439f5367c8d8bb2ebaca8d7329f51f3148b2fb2 <8b58d1f1356df6a7d2de3f55bb665b18b04ffda0, =2.6.39eb7474d0253bb2de4793e1d3ce833e8564bbe732, 3c0427d719bddb33caf18ff4ffb77cb47de7eb00, 536fb3d739d75a03cb318c0c6fe799425cfea501, 56994852d704535ea354a4627ca667b1b4fa0deb, 59afe6148927395cf86f9429900e029a48b1d42b, 66bd9b1a72de7c2f5141b02d796048aafaed8a49, 816559409e340acaa5c9d868291dab30d8c80263, 8b58d1f1356df6a7d2de3f55bb665b18b04ffda0
linux-kernel: Kernel>=5.11.0 <5.15.212, >=5.16.0 <6.1.178, >=6.13.0 <6.18.40, >=6.19.0 <7.1.5, >=6.2.0 <6.6.145, >=6.7.0 <6.12.97, >=2.6.39 <5.10.2615.15.212, 6.1.178, 6.18.40, 7.1.5, 6.6.145, 6.12.97, 5.10.261

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-2026-72005 severity on Zeptric[![CVE-2026-72005](https://zeptric.io/badge/cve/CVE-2026-72005.svg)](https://zeptric.io/cve/CVE-2026-72005)