Bug 2444313 - CVE-2026-29022 dosbox-staging: dr_libs: Heap buffer overflow via crafted WAV files [fedora-42]
Summary: CVE-2026-29022 dosbox-staging: dr_libs: Heap buffer overflow via crafted WAV ...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: dosbox-staging
Version: 42
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Yaakov Selkowitz
QA Contact:
URL:
Whiteboard: {"flaws": ["239c750c-7ae9-4870-a8e3-d...
Depends On:
Blocks: CVE-2026-29022
TreeView+ depends on / blocked
 
Reported: 2026-03-04 05:32 UTC by Vipul Nair
Modified: 2026-06-11 10:33 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-06-11 10:33:17 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Vipul Nair 2026-03-04 05:32:19 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

Comment 1 Ben Beasley 2026-03-04 06:12:16 UTC
Let me supply the details that are missing here.

The CVE report is here: https://www.cve.org/CVERecord?id=CVE-2026-29022

The bug is in dr_wav, and is fixed in 0.14.5 via https://github.com/mackron/dr_libs/commit/8a7258cc66b49387ad58cc5b81568982a3560d49. Unfortunately, the bundled dr_wav here is 0.13.11, and there are significant API changes in all three dr_* libs from dr_flac 0.12.x to 0.13.x, dr_mp3 0.6.x to 0.7.x, and dr_wav 0.13.x. If I remember correctly, this is why dosbox-staging is bundling dr_libs rather than using the system package.

I found that the fix for this particular issue was easy enough to cherry-pick to dr_wav 0.13.17, at least; see https://src.fedoraproject.org/rpms/dr_libs/c/0ee60144d4480605bb152bd6094680630775b98a?branch=f42. I just had to omit the version number and changelog parts of the diff. So you could, if you like, try using that as a downstream patch for your bundled dr_wav header.

This is not the only potentially security-relevant issue fixed since dr_flac 0.12.x / dr_mp3 0.6.x / dr_wav 0.13.x. It is just the only one that has been assigned a CVE, as far as I know. In the long run, dosbox-staging upstream ought to be encouraged to upgrade their vendored dr_libs headers and fix any API incompatibilities with the latest versions.

Comment 2 Fedora Release Engineering 2026-05-06 16:21:04 UTC
This message is a reminder that Fedora Linux 42 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-05-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '42'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 42 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 3 Aoife Moloney 2026-06-11 10:33:17 UTC
Fedora Linux 42 entered end-of-life (EOL) status on 2026-05-27.

Fedora Linux 42 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.