iio: chemical: sgp30: Handle IAQ thread creation failure
CVE-2026-89937 is fixed in 12 products on 1 platform, first by DEBIAN-CVE-2026-89937, released September 23, 2026. It is not reported as exploited. Patch Radar priority: Routine.
In the Linux kernel, the following vulnerability has been resolved: iio: chemical: sgp30: Handle IAQ thread creation failure kthread_run() can fail and return an error pointer, but sgp_probe() stores it and returns success, so the device is registered without its IAQ thread and sgp_remove() later passes the error pointer to kthread_stop(). Return the error from probe instead.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| kernel-64kb · sles 15.7 | 6.4.0-150700.53.90.1 | SUSE-SU-2026:5091-1 | Nov 7, 2026 |
| kernel-azure · sles 15.7 | 6.4.0-150700.53.90.1 | SUSE-SU-2026:5091-1 | Nov 7, 2026 |
| kernel-default · sles 15.7 | 6.4.0-150700.53.90.1 | SUSE-SU-2026:5091-1 | Nov 7, 2026 |
| kernel-default-base · sles 15.7 | 6.4.0-150700.53.90.1.150700.17.51.1 | SUSE-SU-2026:5091-1 | Nov 7, 2026 |
| kernel-docs · sles 15.7 | 6.4.0-150700.53.90.1 | SUSE-SU-2026:5091-1 | Nov 7, 2026 |
| kernel-livepatch-SLE15-SP7_Update_24 · sles 15.7 | 1-150700.15.3.1 | SUSE-SU-2026:5091-1 | Nov 7, 2026 |
| kernel-obs-build · sles 15.7 | 6.4.0-150700.53.90.1 | SUSE-SU-2026:5091-1 | Nov 7, 2026 |
| kernel-source · sles 15.7 | 6.4.0-150700.53.90.1 | SUSE-SU-2026:5091-1 | Nov 7, 2026 |
| kernel-syms · sles 15.7 | 6.4.0-150700.53.90.1 | SUSE-SU-2026:5091-1 | Nov 7, 2026 |
| kernel-zfcpdump · sles 15.7 | 6.4.0-150700.53.90.1 | SUSE-SU-2026:5091-1 | Nov 7, 2026 |
| linux · Debian 12.15 (bookworm) | 6.1.190-1 | DEBIAN-CVE-2026-89937 | Sep 23, 2026 |
| linux · Debian 13.5 (trixie) | 6.12.111-1 | DEBIAN-CVE-2026-89937 | Sep 23, 2026 |
| linux · Debian 14 | 7.2.6-1 | DEBIAN-CVE-2026-89937 | Sep 23, 2026 |
| linux-6.12 · Debian 12.15 (bookworm) | 6.12.111-1~deb12u1 | DEBIAN-CVE-2026-89937 | Sep 23, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.