CVE-2026-93039 ASoC: meson: Keep link pointers valid on realloc failure
A use-after-free vulnerability in the Linux kernel's Meson audio driver allows attackers to potentially execute code or escalate privileges via a double free error during memory reallocation failures.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-93039?
CVE-2026-93039 is a high-severity use after free vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
In the Linux kernel, the following vulnerability has been resolved:
ASoC: meson: Keep link pointers valid on realloc failure
meson_card_reallocate_links() grows the DAI link and private data arrays with two consecutive krealloc() calls and updates the owner pointers only after both calls have succeeded.
A successful krealloc() may move the data: it frees the old block and returns a new one. When that happens for the link array and the second krealloc() then fails, card->dai_link still points to the block that krealloc() already freed, and the error path frees the new block too. The probe error path then calls meson_card_clean_references(), which dereferences card->dai_link and kfree()s it again, resulting in a use-after-free and a double free.
Commit card->dai_link and card->num_links right after the first krealloc() succeeds, so the pointer always refers to a valid allocation that meson_card_clean_references() can walk and free. krealloc() with __GFP_ZERO zero-initializes the added entries, so walking them on the error path is safe. With both failure paths reduced to a plain return, drop the goto labels and the error message.
Which versions are affected by CVE-2026-93039?
How do I fix CVE-2026-93039?
Apply the vendor's patch.
Upgrade to the fixed version. These bugs are found with fuzzing and sanitisers and avoided by memory-safe languages. More about Use after free.
Is CVE-2026-93039 being exploited?
There is no known exploitation of CVE-2026-93039 in the wild and no public exploit code.
Sources
Also known as AZL-102126, BELL-CVE-2026-93039, DEBIAN-CVE-2026-93039, GHSA-w65f-8rhv-gqvr, UBUNTU-CVE-2026-93039.