CVEvulnerability

CVE-2024-26654

7.0 HIGH Published 2024-04-01 Modified 2026-08-04 Official page ↗
Status
Modified
Published
2024-04-01
Last modified
2026-08-04
Assigner
416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS 3.1 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)
7.8 HIGH — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS 3.1 ([email protected])
7.0 HIGH — CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Weaknesses
CWE-416

Description

In the Linux kernel, the following vulnerability has been resolved: ALSA: sh: aica: reorder cleanup operations to avoid UAF bugs The dreamcastcard->timer could schedule the spu_dma_work and the spu_dma_work could also arm the dreamcastcard->timer. When the snd_pcm_substream is closing, the aica_channel will be deallocated. But it could still be dereferenced in the worker thread. The reason is that del_timer() will return directly regardless of whether the timer handler is running or not and the worker could be rescheduled in the timer handler. As a result, the UAF bug will happen. The racy situation is shown below: (Thread 1) | (Thread 2) snd_aicapcm_pcm_close() | ... | run_spu_dma() //worker | mod_timer() flush_work() | del_timer() | aica_period_elapsed() //timer kfree(dreamcastcard->channel) | schedule_work() | run_spu_dma() //worker ... | dreamcastcard->channel-> //USE In order to mitigate this bug and other possible corner cases, call mod_timer() conditionally in run_spu_dma(), then implement PCM sync_stop op to cancel both the timer and worker. The sync_stop op will be called from PCM core appropriately when needed.

Affected configurations

• linux linux kernel (>= 2.6.23 < 4.19.312) • linux linux kernel (>= 4.20 < 5.4.274) • linux linux kernel (>= 5.5 < 5.10.215) • linux linux kernel (>= 5.11 < 5.15.154) • linux linux kernel (>= 5.16 < 6.1.84) • linux linux kernel (>= 6.2 < 6.6.24) • linux linux kernel (>= 6.7 < 6.7.12) • linux linux kernel (>= 6.8 < 6.8.3) • linux linux kernel 6.9 • debian debian linux 10.0

Related

Weakness · CWE (1)

References