CVE-2023-54143

What it actually does

Improper error handling in vdec_msg_queue_init() leaves wdma_addr.size uninitialized or fails to release DMA resources on allocation failure, creating inconsistent state that can lead to use-after-free or memory corruption in the Mediatek video decoder path.

Why it matters to the business

Affected Linux systems performing media decoding may suffer kernel crashes, resource leaks, or local memory corruption; the issue is confined to specific hardware and error conditions with no observed in-the-wild exploitation or ransomware use.

How an attack unfolds

An attacker with local access forces repeated allocation failures during vdec_msg_queue_init() to hit the unhandled error paths, leaving the message queue in a partially initialized state that subsequent operations can leverage for corruption or information disclosure.

How to fix it

Apply the upstream fix by updating to a kernel containing commit 858322c409e0aba8f70810d23f35c482744f007c; rebuild and reboot with the corrected vcodec driver that properly sets wdma_addr.size=0 and uses goto mem_alloc_err on all error paths.

How to confirm the fix worked

Confirm the patched source contains the explicit msg_queue->wdma_addr.size=0 assignment before the first allocation failure return and that the two additional error paths now jump to mem_alloc_err; test by injecting allocation failures during queue init and verifying clean deinit.

Typical attack path

1. Obtain local code execution on a system with Mediatek video codec enabled
2. Trigger memory pressure or allocation failures to reach error paths in vdec_msg_queue_init()
3. Bypass the missing size=0 assignment and missing goto cleanup
4. Reuse the inconsistent msg_queue state in later decoder operations to corrupt kernel memory

How to detect it

Search kernel logs for oops or warnings mentioning vdec_msg_queue_init or mediatek vcodec around allocation failures; inspect for repeated DMA resource warnings without corresponding deinit messages.

What your security team should do

• Prioritize kernel updates on any systems using Mediatek video hardware within the next maintenance window
• Review kernel configuration to disable unused mediatek vcodec modules where possible
• Monitor vendor advisories for backported fixes in distribution kernels