wifi: rt2x00: avoid full teardown before work setup in probe
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 0439f5367c8d8bb2ebaca8d7329f51f3148b2fb2 · fixed in 8b58d1f1356df6a7d2de3f55bb665b18b04ffda0; From 0439f5367c8d8bb2ebaca8d7329f51f3148b2fb2 · fixed in 59afe6148927395cf86f9429900e029a48b1d42b; From 0439f5367c8d8bb2ebaca8d7329f51f3148b2fb2 · fixed in 3c0427d719bddb33caf18ff4ffb77cb47de7eb00; From 0439f5367c8d8bb2ebaca8d7329f51f3148b2fb2 · fixed in eb7474d0253bb2de4793e1d3ce833e8564bbe732; From 0439f5367c8d8bb2ebaca8d7329f51f3148b2fb2 · fixed in 66bd9b1a72de7c2f5141b02d796048aafaed8a49; From 0439f5367c8d8bb2ebaca8d7329f51f3148b2fb2 · fixed in 816559409e340acaa5c9d868291dab30d8c80263; From 0439f5367c8d8bb2ebaca8d7329f51f3148b2fb2 · fixed in 56994852d704535ea354a4627ca667b1b4fa0deb; From 0439f5367c8d8bb2ebaca8d7329f51f3148b2fb2 · fixed in 536fb3d739d75a03cb318c0c6fe799425cfea501
- Linux Linux
2.6.39
- KernelLinux
From 2.6.39 · fixed in 5.10.261; From 5.11.0 · fixed in 5.15.212; From 5.16.0 · fixed in 6.1.178; From 6.2.0 · fixed in 6.6.145; From 6.7.0 · fixed in 6.12.97; From 6.13.0 · fixed in 6.18.40; From 6.19.0 · fixed in 7.1.5
References 8
git.kernel.org
- stable/c/8b58d1f1356df6a7d2de3f55bb665b18b04ffda0
- stable/c/59afe6148927395cf86f9429900e029a48b1d42b
- stable/c/3c0427d719bddb33caf18ff4ffb77cb47de7eb00
- stable/c/eb7474d0253bb2de4793e1d3ce833e8564bbe732
- stable/c/66bd9b1a72de7c2f5141b02d796048aafaed8a49
- stable/c/816559409e340acaa5c9d868291dab30d8c80263
- stable/c/56994852d704535ea354a4627ca667b1b4fa0deb
- stable/c/536fb3d739d75a03cb318c0c6fe799425cfea501