Microsoft · ASoC: sti: initialize IRQ lock before requesting IRQ
Affects MicrosoftSource GCVE Database
Not known to be exploited · fixed in f1e7b74512164314d0550ec5b62e3d40b95b0986 : update Microsoft when convenient.
Data as of 17 Nov 2026, 10:35 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- Patch
- Available – fixed in f1e7b74512164314d0550ec5b62e3d40b95b0986, a42dd4dae4c9191caa017cf54cc40b6bb125be65, 9128265f0fc8031a71775d70786052e5631aac54 +5
Exploitation evidence
Disclosed: evidence found.
CVE published 25 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 16 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Description
This vulnerability, identified as CVE-2026-97909, involves the initialization sequence of an IRQ lock before requesting an IRQ in Microsoft software versions 3.0 and 4.0. The description is minimal and does not provide details on the impact or exploitation. No CVSS score or detailed technical information is available.