Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Critical

Out-of-bounds write in Dolby UDC DD+ decoder

IdentifiersCVE-2025-54957CWE-190· Integer Overflow or Wraparound

CVE-2025-54957 is a memory-corruption vulnerability in Dolby DDPlus Unified Decoder (UDC) versions 4.5 through 4.13. When the decoder processes Evolution/EMDF data from a specially crafted DD+ bitstream, code in evo_priv.c calculates the length for a buffer write using arithmetic that can overflow via integer wraparound. The wrapped value can cause the decoder to allocate a buffer that is smaller than required. A subsequent bounds check then becomes ineffective relative to the true amount of data written, resulting in an out-of-bounds write in the DD+ decoder process. Public reporting states that the issue is triggered by malformed but manually edited 'valid' DD+ bitstreams and has been shown to facilitate memory corruption and, on Android, code execution in the mediacodec context.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can crash the DD+ decoder process and corrupt adjacent memory. Because the flaw is an out-of-bounds write, impact can extend beyond denial of service to controlled memory corruption, including overwriting nearby structure members and pointers. Public reporting indicates this can be leveraged for arbitrary code execution in the Android mediacodec context. On Android, the risk is elevated because incoming audio content may be decoded automatically for transcription, making the bug reachable in a near-zero-click or zero-click scenario depending on the application and device behavior. On other platforms or devices, isolated exploitation may more commonly result in a media crash or device restart if not paired with additional exploitation primitives.

Mitigation

If you can’t patch tonight, do this now.

Until patched builds are fully deployed, reduce exposure to untrusted DD+ content and any workflows that automatically decode externally supplied audio. Where operationally feasible, restrict or disable automatic processing/transcription of incoming audio attachments, limit acceptance of untrusted media sources, and use defense-in-depth controls around media parsing components. Prioritize patching on devices where remotely delivered audio is decoded in privileged or automatically invoked media pipelines.

Remediation

Patch, then assume compromise.

Apply vendor patches that update Dolby UDC beyond affected versions 4.5 through 4.13. The content indicates Dolby issued a fix in 2025 and that Android incorporated fixes in Pixel updates in December 2025 and the broader Android January 2026 security update. Asset owners should deploy OEM/security-bulletin updates that include the Dolby decoder fix and verify devices are at the appropriate security patch level.
PUBLIC EXPLOITS

Exploits

No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.

VALID 0 / 1 TOTALView more in app

All candidate exploits were filtered out by Mallory's validation.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
DolbyUdcapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

42 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity31

Community discussion across Reddit, Mastodon, and other social sources.