iio: trigger: cancel reenable_work before freeing trigger
- 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.16, 5.17, 6.6.160, 6.12.113, 6.18.56, and 1 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
Summary
In the Linux kernel, the following vulnerability has been resolved: iio: trigger: cancel reenable_work before freeing trigger iio_trigger_notify_done_atomic() defers ->reenable() into trig->reenable_work on the system workqueue, and the worker dereferences the owning trigger through container_of(). Nothing cancels this work before iio_trig_release() frees the trigger, so a worker armed by the last in-flight IRQ can outlive the free and touch freed memory. Cancel it at the top of iio_trig_release(), which every free path reaches through the device core's final put_device(). Found by an in-house static analysis tool.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 9020ef659885f2622cfb386cc229b6d618362895 · fixed in ac5d26a46c90ff61fd574eff4e8f0d71c905828a; From 9020ef659885f2622cfb386cc229b6d618362895 · fixed in cf513df1a2c75566cdc802d9da47f62e8d6cfd18; From 9020ef659885f2622cfb386cc229b6d618362895 · fixed in e64703280ce7a23a43c27efebeb7da457c88bf5c; From 9020ef659885f2622cfb386cc229b6d618362895 · fixed in 882d0011c59ff8ac15188ec9ce071399ecfa10ad; From 9020ef659885f2622cfb386cc229b6d618362895 · fixed in 2a57b9246cecd5dd797a42eb310d6c8816f26d9e; From 5.15.17 · fixed in 5.16; From 5.16.3 · fixed in 5.17
- Linux Linux
5.17
- KernelLinux
From 5.17.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.113; From 6.13.0 · fixed in 6.18.56; From 6.19.0 · fixed in 7.2.10