The vulnerability is described as a reachable assertion in FFmpeg when processing a crafted AAC file, specifically related to commit N-113007-g8d24a28d06. The initial attempts to use this commit hash directly were misleading as it pointed to an unrelated change. By searching for the CVE (CVE-2025-22919) and associated Trac ticket (11385), I found a reference to the fixing commit: 1446e37d3d032e1452844778b3e6ba2c20f0c322.
The analysis of this fixing commit shows that the file libavfilter/buffersrc.c was modified, specifically the function init_audio. The patch added a validation check to ensure that s->sample_rate is greater than zero. The commit message explicitly states: "Fixes an assert in ffmpeg_enc.c that assumed a valid sample rate would be set. Fixes ticket #11385."
This indicates that init_audio was vulnerable because it failed to sanitize the sample_rate input, which could be controlled by a crafted AAC file. This unvalidated, potentially non-positive sample rate would then propagate to a function in ffmpeg_enc.c, which relied on a valid sample rate, triggering an assertion and causing a Denial of Service.
Therefore, init_audio is identified as a vulnerable function because it processed potentially malicious input (the sample rate) without proper validation, directly leading to the conditions for the assertion failure. While the assertion itself occurred in ffmpeg_enc.c, the exploitable flaw (lack of validation) that allowed this assertion to be reached via a crafted file was in init_audio.