iio: light: gp2ap020a00f: drain irq_work after free_irq
- 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 6.6.160, 6.12.113, 6.18.56, 7.2.10
- 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: light: gp2ap020a00f: drain irq_work after free_irq The threaded IRQ handler queues data->work through irq_work_queue() so the trigger is polled from a per-CPU context. free_irq() does not flush an irq_work the handler already queued, so after gp2ap020a00f_remove() returns that work may still run and call iio_trigger_poll() on data->trig, which the devm cleanup has already freed, causing a use-after-free. Add irq_work_sync(&data->work) after free_irq() in remove() and in the probe error path, mirroring commit 78601726d4a5 ("iio: trigger: sysfs: fix use-after-free on remove"). Found by an in-house static analysis tool, confirmed by manual review.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From bf29fbeaa13d3350ca71df70c705d8b883c45692 · fixed in 85c20d1cf3f01a506605a16c2f9ce23b9c8b114f; From bf29fbeaa13d3350ca71df70c705d8b883c45692 · fixed in a36814b9fe00970116d30c3143d81e7425c4d334; From bf29fbeaa13d3350ca71df70c705d8b883c45692 · fixed in cc71400bc965c0d3894a38ead3d71243400c2d5e; From bf29fbeaa13d3350ca71df70c705d8b883c45692 · fixed in a1769877ff52a4f1bfb9ca535d1b5113808bd602; From bf29fbeaa13d3350ca71df70c705d8b883c45692 · fixed in 63213927b141085b6c8719b8037dab3074b7e0fe
- Linux Linux
3.13
- KernelLinux
From 3.13.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