Kernel memory corruption via stale DAI link pointer
Published Sep 17, 2026 · Updated Sep 18, 2026
Memory corruption in affected Linux 4.19 and later kernels allows attackers to read or corrupt kernel memory during Meson ASoC probing. If the first DAI-link krealloc moves its allocation and the following private-data krealloc fails, meson_card_reallocate_links leaves card->dai_link pointing to freed memory; cleanup dereferences and frees it again. The path requires an Amlogic device tree with an AXG sound card and TDM playback link plus the two-step allocation outcome; no OS account or user interaction is required.
Summary
What happened
Memory corruption in affected Linux 4.19 and later kernels allows attackers to read or corrupt kernel memory during Meson ASoC probing. If the first DAI-link krealloc moves its allocation and the following private-data krealloc fails, meson_card_reallocate_links leaves card->dai_link pointing to freed memory; cleanup dereferences and frees it again. The path requires an Amlogic device tree with an AXG sound card and TDM playback link plus the two-step allocation outcome; no OS account or user interaction is required.
The record
- CVE
- CVE-2026-93039
- Published
- Sep 17, 2026
- Updated
- Sep 18, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.19
- Affected versionversion=7864a79f37b55769b817d5e6c5ae0ca4bfdba93b <0b30fbe6bf7cf6499b19dd886f466e7c9e820089
- Affected versionversion=7864a79f37b55769b817d5e6c5ae0ca4bfdba93b <1c1485343b7c1c39dab7ecb9cd16ba49fd0ce642
- Affected versionversion=7864a79f37b55769b817d5e6c5ae0ca4bfdba93b <2aaa41cf974f83a6fb105422bac4e2f107150774
- Affected versionversion=7864a79f37b55769b817d5e6c5ae0ca4bfdba93b <41e92e0caa1fe3df2efaca346bfcaeb7fb9826ab
- Affected versionversion=7864a79f37b55769b817d5e6c5ae0ca4bfdba93b <5ed1b048527bebe4529eb6e01c34dcc5d97ba5fe
- Affected versionversion=7864a79f37b55769b817d5e6c5ae0ca4bfdba93b <8db0a0fc84e80aa9924e0833aef6cc95df94e5a7
- Affected versionversion=7864a79f37b55769b817d5e6c5ae0ca4bfdba93b <8fec16898f184e5f8f8fdd09ff1ced2bd7ffc13d
- Affected versionversion=7864a79f37b55769b817d5e6c5ae0ca4bfdba93b <de33afc57f24538186bccf4c4f6c65dd38634fd8
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started