Kernel panic via uninitialized widget count
Published Nov 19, 2024 · Updated May 11, 2026
Bounds-checking failure in Linux 6.7 through 6.11.6 allows local users to trigger a kernel panic through ASoC DAPM. The dapm_widget_list_create function fills the widgets array before initializing num_widgets, although __counted_by uses that value to enforce the array bound. Linux 6.12-rc1 through 6.12-rc5 is also affected, and a panic requires CONFIG_UBSAN_TRAP; otherwise the bounds sanitizer issues a warning.
Summary
What happened
Bounds-checking failure in Linux 6.7 through 6.11.6 allows local users to trigger a kernel panic through ASoC DAPM. The dapm_widget_list_create function fills the widgets array before initializing num_widgets, although __counted_by uses that value to enforce the array bound. Linux 6.12-rc1 through 6.12-rc5 is also affected, and a panic requires CONFIG_UBSAN_TRAP; otherwise the bounds sanitizer issues a warning.
The record
- CVE
- CVE-2024-53045
- Published
- Nov 19, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 19, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 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=6.7
- Affected versionversion=80e698e2df5ba2124bdeca37f1e589de58a4d514 <2ef9439f7a19fd3d43b288d38b1c6e55b668a4fe
- Affected versionversion=80e698e2df5ba2124bdeca37f1e589de58a4d514 <c549cb66e8de0ba1936fc97a59f0156741d3492a
What conditions does exploitation require?
What is affected?
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