Cloudanix VulnDB

CVE-2025-25467

Critical · 9.8

CVSS

9.8

EPSS

0.7%

Published

Feb 18, 2025

CISA due date

—

Cloudanix analysis

Next patch cycle SSVC: Track

A flaw in a widely used video encoding library lets attackers take over devices simply by getting them to open a specially made audio file.

Exploitation
Remote Unauthenticated
Attacker needs
None
Complexity
Low
Impact
Remote Code Execution
Component
Library
Class
Memory Corruption
Remediation
Upgrade
Effort
Medium
Patch risk
Low

What it actually does

Insufficient tracking and releasing of allocated memory in libx264 leads to memory corruption that can be leveraged for arbitrary code execution when processing specially crafted input.

Why it matters to the business

Attackers can gain full control of systems that process untrusted media files, resulting in data theft, ransomware deployment, or persistent compromise across media-handling applications and devices.

How an attack unfolds

An attacker creates a malicious AAC file that triggers improper memory handling in libx264; when the file is decoded on an affected system the corruption allows shellcode to be executed with the privileges of the processing application.

How to fix it

Update libx264 to the fixed versions released in Pixel-family specific updates dated 2023-12-05; rebuild and redeploy any applications that statically link or bundle the library; replace affected Android images with patched builds.

How to confirm the fix worked

Verify that the installed libx264 library reports a build date on or after 2023-12-05, run regression tests with crafted AAC samples, and confirm memory sanitizers no longer report leaks or use-after-free conditions on the vulnerable code paths.

Typical attack path

  1. Craft a malicious AAC file that exploits the memory tracking flaw
  2. Deliver the file to the target via email, web download, or media sharing
  3. Induce the victim application or device to process the file with libx264
  4. Trigger memory corruption to execute attacker-controlled code

How to detect it

Review application logs and media-processing service telemetry for crashes or unexpected terminations when handling AAC files; inspect process memory dumps for signs of heap corruption around libx264 decode routines.

What your security team should do

  • Immediately apply the 2023-12-05 Pixel-family updates to all affected Android devices
  • Inventory all applications and services that depend on libx264 and schedule library upgrades
  • Block or sandbox untrusted AAC and other media processing until patches are deployed
  • Monitor EPSS and exploit maturity indicators for any rise in weaponization

The record

Insufficient tracking and releasing of allocated used memory in libx264 git master allows attackers to execute arbitrary code via creating a crafted AAC file.

Affected packages

Ecosystem Package Introduced Fixed
Debian:11 x264 0 No fix
Debian:12 x264 0 No fix
Debian:13 x264 0 No fix

Related vulnerabilities