CVE-2026-98437: Linux kernel · media: qcom: iris: fix runtime PM reference leaks
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in fff1ae8d0c8c97668e4cbcc6e1fd2cc740013795 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 12:55 UTC
Rated Low by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in fff1ae8d0c8c97668e4cbcc6e1fd2cc740013795, f87d7eda07fca21efe4b96169ae59007db46e60e, 7a52e76b63095e05d92f15f16f45421cab9789e1
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.
What to do
Upgrade Linux kernel to fff1ae8d0c8c97668e4cbcc6e1fd2cc740013795, f87d7eda07fca21efe4b96169ae59007db46e60e or 7a52e76b63095e05d92f15f16f45421cab9789e1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available in the Linux kernel commits identified by hashes fff1ae8d0c8c97668e4cbcc6e1fd2cc740013795, f87d7eda07fca21efe4b96169ae59007db46e60e, and 7a52e76b63095e05d92f15f16f45421cab9789e1. Users should update to a Linux kernel version that includes these fixes. No additional mitigation is indicated.
Description
A vulnerability in the Linux kernel's Qualcomm iris media driver caused runtime power management (PM) reference leaks due to improper handling of PM usage counts. The issue was fixed by ensuring proper use of pm_runtime_resume_and_get() and always calling pm_runtime_put_sync() to maintain balanced runtime PM references.