Bug 2555132 (CVE-2026-98656) - CVE-2026-98656 kernel: iio: trigger: cancel reenable_work before freeing trigger
Summary: CVE-2026-98656 kernel: iio: trigger: cancel reenable_work before freeing trigger
Keywords:
Status: NEW
Alias: CVE-2026-98656
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-10-18 15:56 UTC by OSIDB Bzimport
Modified: 2026-10-21 21:04 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-10-18 15:56:16 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.