ASoC: sti: initialize IRQ lock before requesting IRQ (CVE-2026-97909) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-97909

ASoC: sti: initialize IRQ lock before requesting IRQ

Answer in brief

CVE-2026-97909 records a Unknown severity vulnerability in ASoC: sti: initialize IRQ lock before requesting IRQ. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 25, 2026Updated Sep 25, 2026Source checked Sep 25, 2026First seen by HOL Sep 25, 2026Material review Sep 25, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=d05d862ead8eca5e7d4ccf82d39d9189579ee5b1 <f1e7b74512164314d0550ec5b62e3d40b95b0986 \|\| >=d05d862ead8eca5e7d4ccf82d39d9189579ee5b1 <998ca92f69bc43499705016d02ffaf0663126d57 \|\| >=d05d862ead8eca5e7d4ccf82d39d9189579ee5b1 <a42dd4dae4c9191caa017cf54cc40b6bb125be65 \|\| >=d05d862ead8eca5e7d4ccf82d39d9189579ee5b1 <04405aeef4f8d7bcac6dcb1947acafdb4420c2c3	f1e7b74512164314d0550ec5b62e3d40b95b0986, 998ca92f69bc43499705016d02ffaf0663126d57, a42dd4dae4c9191caa017cf54cc40b6bb125be65, 04405aeef4f8d7bcac6dcb1947acafdb4420c2c3
Linux/Linuxgeneric	4.11	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to f1e7b74512164314d0550ec5b62e3d40b95b0986 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 25, 2026

Sources and claim methodology

Upstream source description

In the Linux kernel, the following vulnerability has been resolved: ASoC: sti: initialize IRQ lock before requesting IRQ uni_reader_init() registers the shared IRQ before initializing reader->irq_lock. A pending interrupt can invoke the handler while the lock is still uninitialized. Initialize the lock before registering the IRQ so the interrupt path always sees valid lock state.

Quoted source text, attributed separately from HOL analysis.