Unspecified local impact via owner-field multiplication
Published Apr 12, 2020 · Updated May 29, 2026
Incorrect type conversion in Linux kernel 5.6.3 and earlier allows local users to cause unspecified impact through ALSA controls. snd_ctl_elem_add assigns info->owner to count, which then controls a private_size-by-count allocation-size multiplication. Kernel engineers dispute exploitability because both existing ioctl callers intentionally encode safe non-owner data in that field; relevance requires an unfamiliar new caller.
Summary
What happened
Incorrect type conversion in Linux kernel 5.6.3 and earlier allows local users to cause unspecified impact through ALSA controls. snd_ctl_elem_add assigns info->owner to count, which then controls a private_size-by-count allocation-size multiplication. Kernel engineers dispute exploitability because both existing ioctl callers intentionally encode safe non-owner data in that field; relevance requires an unfamiliar new caller.
The record
- CVE
- CVE-2020-11725
- Published
- Apr 12, 2020
- Updated
- May 29, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-704
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 12, 2020CVE publishedPublication date reported by the CVE source.
- May 29, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo