Nixpkgs security tracker

Login with GitHub
⚠️ You are using a production deployment that is still only suitable for demo purposes. Any work done in this might be wiped later without notice.

Suggestion detail

Dismissed
(max. allowed matches exceeded)
created 3 weeks, 3 days ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
wifi: rt2x00: avoid full teardown before work setup in probe

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 products

Linux
  • <eb7474d0253bb2de4793e1d3ce833e8564bbe732
  • =<5.10.*
  • <2.6.39
  • =<*
  • =<6.6.*
  • <56994852d704535ea354a4627ca667b1b4fa0deb
  • <536fb3d739d75a03cb318c0c6fe799425cfea501
  • <3c0427d719bddb33caf18ff4ffb77cb47de7eb00
  • <8b58d1f1356df6a7d2de3f55bb665b18b04ffda0
  • =<6.18.*
  • =<6.12.*
  • <816559409e340acaa5c9d868291dab30d8c80263
  • =<7.1.*
  • <66bd9b1a72de7c2f5141b02d796048aafaed8a49
  • =<5.15.*
  • <59afe6148927395cf86f9429900e029a48b1d42b
  • =<6.1.*
  • ==2.6.39