---
id: CVE-2026-97909
title: |-
  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
summary: |-
  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 th…
severity: none
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= d05d862ead8eca5e7d4ccf82d39d9189579ee5b1 <
    f1e7b74512164314d0550ec5b62e3d40b95b0986
  - >-
    Linux >= d05d862ead8eca5e7d4ccf82d39d9189579ee5b1 <
    998ca92f69bc43499705016d02ffaf0663126d57
  - >-
    Linux >= d05d862ead8eca5e7d4ccf82d39d9189579ee5b1 <
    a42dd4dae4c9191caa017cf54cc40b6bb125be65
  - >-
    Linux >= d05d862ead8eca5e7d4ccf82d39d9189579ee5b1 <
    04405aeef4f8d7bcac6dcb1947acafdb4420c2c3
  - Linux 4.11
published: '2026-09-25'
updated: '2026-09-25'
sourceUpdated: '2026-09-25T11:17:17.847'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-97909'
references:
  - url: 'https://git.kernel.org/stable/c/04405aeef4f8d7bcac6dcb1947acafdb4420c2c3'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/998ca92f69bc43499705016d02ffaf0663126d57'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/a42dd4dae4c9191caa017cf54cc40b6bb125be65'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/f1e7b74512164314d0550ec5b62e3d40b95b0986'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
  - cve.org
ingestedAt: '2026-09-25T11:06:38.892Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.