Case · DiggingBeagle record

vLLM Phi-4 audio attention allocations exhausted GPU memory on valid input

Phi-4 multimodal audio attention materialized full layer-by-layer attention matrices for long waveforms in vLLM instead of using a bounded streaming form. A legal ten-minute WAV was enough in the reproduction to exhaust roughly 24 GiB of GPU memory and terminate the engine.

Scope

The issue requires the affected Phi-4 audio encoder and a long permitted audio input on an inadequately provisioned worker. The failure is a model-specific resource exhaustion condition, not proof of a malformed-file exploit or data theft.

Assessment profile

Assessment method
Setting
research demonstration
Exploitation
demonstrated
Evidence
Grade B
Remediation
patch available
AI role
AGAINST AI
Basis and provenance

The cited primary technical report or advisory supports the stated mechanism within its reported scope. The assessment does not infer a production breach, a victim count or a comparable impact score from a laboratory result. A maintainer or advisory names a patched release; that does not prove every deployed instance has updated. Boundary: Resource exhaustion here comes from a legal input length paired with an eager attention implementation that retains a large number of intermediate matrices across layers.

Assessed Oct 29, 2026 using diggingbeagle.assessment/1.

At a glance

Mechanism and trust boundary

  1. 01

    Step

  2. 02

    Step

  3. 03

    Step

Claims & evidence

CLM-ENRICH-20261029-38The vLLM Phi-4 audio advisory reproduces GPU memory exhaustion from a permitted long WAV input because eager attention tensors are retained across the encoder’s layers.supported

Basis: reported finding

Link to claim
CLM-CP23-VLLM-PHI4-AUDIO-OOM-1Phi-4 multimodal audio attention materialized full layer-by-layer attention matrices for long waveforms in vLLM instead of using a bounded streaming form. The issue requires the affected Phi-4 audio encoder and a long permitted audio input on an inadequately provisioned worker. A legal ten-minute WAV was enough in the reproduction to exhaust roughly 24 GiB of GPU memory and terminate the engine.supported

Basis: reported finding

Link to claim

Implications

A legal ten-minute WAV was enough in the reproduction to exhaust roughly 24 GiB of GPU memory and terminate the engine.

Controls and mitigations

  • Upgrade to vLLM 0.32.0 and use bounded attention implementations plus per-request memory limits.

Unknowns and contradictions

  • The failure is a model-specific resource exhaustion condition, not proof of a malformed-file exploit or data theft.

Sources and citation

Material revision history

  1. Oct 29, 2026 · Canonical change recorded · new in release · revision 202