CVE-2025-38043

What it actually does

The missing dma_mask initialization on FFA devices causes dma_alloc_attrs to emit warnings at kernel/dma/mapping.c:597 when device pointers are used for DMA buffer allocation.

Why it matters to the business

Systems running affected Linux kernels on Arm platforms may experience noisy kernel logs and diagnostic noise; low operational risk given negligible exploitation probability and absence from known campaigns.

How an attack unfolds

No practical end-to-end exploitation path exists; the issue manifests as a kernel warning rather than memory corruption or privilege escalation, and no threat actors have been observed leveraging it.

How to fix it

Upgrade to a kernel containing commit 97bab02f0b64ba6bcdf6a8fae561db07f509aee9 or later; for claws-mail on Mageia 5 apply package 3.11.1-3.mga5 or newer. Reboot after kernel update.

How to confirm the fix worked

Confirm the commit 97bab02f0b64ba6bcdf6a8fae561db07f509aee9 is present in the running kernel source or binary; verify absence of the dma_alloc_attrs warning when FFA devices are initialized.

How to detect it

Search kernel logs and dmesg for the exact warning string from dma_alloc_attrs involving FFA devices; no post-exploitation artifacts are expected.

What your security team should do

• Apply the referenced kernel commit or distribution update at the next maintenance window
• Monitor kernel logs for the dma_alloc_attrs warning on Arm systems until patched
• Prioritize updates on production Arm servers and embedded devices using FFA