Kernel heap disclosure via partial debugfs write
Published Jun 18, 2025 · Updated May 11, 2026
Information disclosure in the wil6210 driver in Linux allows local users to expose kernel heap data through its WMI debugfs file. wil_write_file_wmi allocates an uninitialized buffer, then a nonzero file offset lets simple_write_to_buffer copy only a suffix before wmi_send transmits the full buffer. Reachability requires write access to debugfs, which is restricted to root by default, and an active wil6210 device; the leak is limited to stale heap bytes sent to that device.
Summary
What happened
Information disclosure in the wil6210 driver in Linux allows local users to expose kernel heap data through its WMI debugfs file. wil_write_file_wmi allocates an uninitialized buffer, then a nonzero file offset lets simple_write_to_buffer copy only a suffix before wmi_send transmits the full buffer. Reachability requires write access to debugfs, which is restricted to root by default, and an active wil6210 device; the leak is limited to stale heap bytes sent to that device.
The record
- CVE
- CVE-2022-50169
- Published
- Jun 18, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-909
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 18, 2025CVE 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=3.17
- Affected versionversion=ff974e4083341383d3dd4079e52ed30f57f376f0 <05ceda14ef7c73104e709c414c3680d8a59f51d4
- Affected versionversion=ff974e4083341383d3dd4079e52ed30f57f376f0 <074e865b37da55aa87baa16d68b96896f85f8adb
- Affected versionversion=ff974e4083341383d3dd4079e52ed30f57f376f0 <4615458db7793fadc6d546ac3564b36819e77a22
- Affected versionversion=ff974e4083341383d3dd4079e52ed30f57f376f0 <60c9983425167ec5073c628d83a6875760d18059
- Affected versionversion=ff974e4083341383d3dd4079e52ed30f57f376f0 <67470920cd3f3cb38699b1ad23234f96bead4d21
- Affected versionversion=ff974e4083341383d3dd4079e52ed30f57f376f0 <789edc1af9c1a2293956e8534bfef3d18d629de9
- Affected versionversion=ff974e4083341383d3dd4079e52ed30f57f376f0 <7a4836560a6198d245d5732e26f94898b12eb760
- Affected versionversion=ff974e4083341383d3dd4079e52ed30f57f376f0 <c1216e699a1ce83ea005510844bd7508d34c6cef
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.
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