From: GitHub issues - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: [Security]FPE in alsa-utils axfer `wave_parser_pre_process
Date: Sun, 5 Jul 2026 13:21:24 +0200 (CEST) [thread overview]
Message-ID: <18bf60dd6695ef00-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <18bf60dd6688f500-webhooks-bot@alsa-project.org>
alsa-project/alsa-utils issue #332 was opened from eglonnnn:
### Description
A floating point exception vulnerability in alsa-utils v1.2.15.2. When `axfer`'s WAVE container parser processes a crafted WAVE file missing the `fmt` chunk, `samples_per_frame` and `frames_per_second` remain zero, causing a division-by-zero in `wave_parser_pre_process()`.
### Impact
- Denial-of-service via process crash
- Any user processing untrusted WAVE files with axfer is affected
### Reproduction
All materials are available in my research repository:
https://github.com/eglonnnn/opensource-fuzz-vulnerability-research/tree/main/FPE%20in%20alsa-utils%20axfer%20wave_parser_pre_process
Issue URL : https://github.com/alsa-project/alsa-utils/issues/332
Repository URL: https://github.com/alsa-project/alsa-utils
parent reply other threads:[~2026-07-05 11:22 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <18bf60dd6688f500-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=18bf60dd6695ef00-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