VulnerabilityPublished 18 Oct 2026Updated 21 Oct 2026

CVE-2026-98677: Linux kernel · iio: adc: ad_sigma_delta: fix use-after-free on unbind

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in f20b94a7dc1ff9ade191ce839c984210fdbdc653 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 14:18 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in f20b94a7dc1ff9ade191ce839c984210fdbdc653, 84500ae0d976995a6870cb1dca2d124b6b2d6e5a, 5663c72bf400231e90777982216797191887a6b9 +2

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 8bea9af887de4c99a95f93f2ce400ef63e8b4e9b, < f20b94a7dc1ff9ade191ce839c984210fdbdc653	Fixed in f20b94a7dc1ff9ade191ce839c984210fdbdc653
LinuxLinux	Affected ≥ 8bea9af887de4c99a95f93f2ce400ef63e8b4e9b, < 84500ae0d976995a6870cb1dca2d124b6b2d6e5a	Fixed in 84500ae0d976995a6870cb1dca2d124b6b2d6e5a
LinuxLinux	Affected ≥ 8bea9af887de4c99a95f93f2ce400ef63e8b4e9b, < 5663c72bf400231e90777982216797191887a6b9	Fixed in 5663c72bf400231e90777982216797191887a6b9
LinuxLinux	Affected ≥ 8bea9af887de4c99a95f93f2ce400ef63e8b4e9b, < 975b09bc680acc60903777b766cdb53b0bf9c9f6	Fixed in 975b09bc680acc60903777b766cdb53b0bf9c9f6
LinuxLinux	Affected ≥ 8bea9af887de4c99a95f93f2ce400ef63e8b4e9b, < 9ee8306121495d2a25aa5d1bfd519f2748786b83	Fixed in 9ee8306121495d2a25aa5d1bfd519f2748786b83
LinuxLinux	Affected =5.19	Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: iio: adc: ad_sigma_delta: fix use-after-free on unbind ad_sd_buffer_postenable() allocates sigma_delta->samples_buf with devm_krealloc() at runtime, so its devres entry sits after all probe-time entries of the driver. devm resources are released in reverse allocation order, which means unbind frees samples_buf before iio_device_unregister() disables the buffers and detaches the trigger pollfunc. The data ready IRQ is still enabled at that point, so ad_sd_trigger_handler() can still run and memcpy() incoming samples into the freed samples_buf. Fix this by preallocating the buffer in devm_ad_sd_setup_buffer_and_trigger(), before the triggered buffer and the IRQ are set up, so it is freed only after iio_device_unregister() has drained the trigger handler via free_irq(). Size it for the worst case of all sequencer slots being active; ad_sd_validate_scan_mask() already caps the number of active channels at num_slots. This issue was found by an in-house static analysis tool.

References

Community reviews

Loading reviews…