From: GitHub issues - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: [Security] Segmentation Fault DoS in snd_config_load_string via corrupted linked list pointer
Date: Sat, 4 Jul 2026 14:07:38 +0200 (CEST) [thread overview]
Message-ID: <18bf14cee52c5a00-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <18bf14cee505bb00-webhooks-bot@alsa-project.org>
alsa-project/alsa-lib issue #514 was opened from eglonnnn:
### Description
A segmentation fault vulnerability in alsa-lib v1.2.15.3. When `snd_config_load_string()` parses a crafted ALSA configuration text, the parser produces an inconsistent linked-list state during array/composite node handling, causing `list_del()` to access an uninitialized pointer and trigger a SEGV.
### Impact
- Denial-of-service via process crash
- Any application processing untrusted ALSA configuration text is affected
### Reproduction
All materials are available in my research repository:
https://github.com/eglonnnn/opensource-fuzz-vulnerability-research/tree/main/SEGV%20in%20alsa-lib%20snd_config_load_string
Issue URL : https://github.com/alsa-project/alsa-lib/issues/514
Repository URL: https://github.com/alsa-project/alsa-lib
parent reply other threads:[~2026-07-04 12:08 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <18bf14cee505bb00-webhooks-bot@alsa-project.org>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=18bf14cee52c5a00-webhooks-bot@alsa-project.org \
--to=github@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox