Kernel stack corruption via stale WMI callback
Published Oct 22, 2025 · Updated Oct 22, 2025
Stack out-of-bounds write in the Linux kernel allows local users to corrupt kernel stack memory after a timed-out ath9k WMI command. The ath9k WMI response callback copies a late response into wmi->cmd_rsp_buf after ath9k_wmi_cmd returns and its stack buffer is no longer valid. Exploitation requires low-privileged local access, a high-complexity timeout race, and the affected ath9k WMI driver; the write occurs in kernel context.
Summary
What happened
Stack out-of-bounds write in the Linux kernel allows local users to corrupt kernel stack memory after a timed-out ath9k WMI command. The ath9k WMI response callback copies a late response into wmi->cmd_rsp_buf after ath9k_wmi_cmd returns and its stack buffer is no longer valid. Exploitation requires low-privileged local access, a high-complexity timeout race, and the affected ath9k WMI driver; the write occurs in kernel context.
The record
- CVE
- CVE-2023-53717
- Published
- Oct 22, 2025
- Updated
- Oct 22, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 22, 2025CVE publishedPublication date reported by the CVE source.
- Oct 22, 2025Record 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=2.6.35
- Affected versionversion=fb9987d0f748c983bb795a86f47522313f701a08 <1af7eacfad45149c54893a8a9df9e92ef89f0a90
- Affected versionversion=fb9987d0f748c983bb795a86f47522313f701a08 <554048a72d7ecfdd58cc1bfb56e0a1864e64e82c
- Affected versionversion=fb9987d0f748c983bb795a86f47522313f701a08 <78b56b0a613a87b61290b95be497fdfe2fe58aa6
- Affected versionversion=fb9987d0f748c983bb795a86f47522313f701a08 <89a33c3c847b19b19205cde1d924df2a6c70d8eb
- Affected versionversion=fb9987d0f748c983bb795a86f47522313f701a08 <8a2f35b9830692f7a616f2f627f943bc748af13a
- Affected versionversion=fb9987d0f748c983bb795a86f47522313f701a08 <8f28513d9520184059530c01a9f928a1b3809d3f
- Affected versionversion=fb9987d0f748c983bb795a86f47522313f701a08 <ae4933b4f17de8e2b7ff6f91b17d3b0099a6d6bc
- Affected versionversion=fb9987d0f748c983bb795a86f47522313f701a08 <bf6dc175a2b53098a69db1236d9d53982f4b1bc0
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
No sourced classifications are available.
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