Back
CVE-2022-50169
wifi: wil6210: debugfs: fix info leak in wil_write_file_wmi()
High7.1EPSS 0.26%
- Published
- Updated
- Reserved
- Assigned by
- Linux
Description
In the Linux kernel, the following vulnerability has been resolved: wifi: wil6210: debugfs: fix info leak in wil_write_file_wmi() The simple_write_to_buffer() function will succeed if even a single byte is initialized. However, we need to initialize the whole buffer to prevent information leaks. Just use memdup_user().
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | High7.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.26% · top 82% of all CVEs (6 Nov 2026)
Loading the EPSS history…
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.1.
Weakness
Affected products
- affected ff974e4083341383d3dd4079e52ed30f57f376f0 – < c1216e699a1ce83ea005510844bd7508d34c6cef
- affected ff974e4083341383d3dd4079e52ed30f57f376f0 – < 4615458db7793fadc6d546ac3564b36819e77a22
- affected ff974e4083341383d3dd4079e52ed30f57f376f0 – < 60c9983425167ec5073c628d83a6875760d18059
- affected ff974e4083341383d3dd4079e52ed30f57f376f0 – < 05ceda14ef7c73104e709c414c3680d8a59f51d4
- affected ff974e4083341383d3dd4079e52ed30f57f376f0 – < 074e865b37da55aa87baa16d68b96896f85f8adb
- affected ff974e4083341383d3dd4079e52ed30f57f376f0 – < 789edc1af9c1a2293956e8534bfef3d18d629de9
- affected ff974e4083341383d3dd4079e52ed30f57f376f0 – < 67470920cd3f3cb38699b1ad23234f96bead4d21
- affected ff974e4083341383d3dd4079e52ed30f57f376f0 – < 7a4836560a6198d245d5732e26f94898b12eb760
- affected 3.17
- unaffected < 3.17
- unaffected 4.14.291 – ≤ 4.14.*
- unaffected 4.19.256 – ≤ 4.19.*
- unaffected 5.4.211 – ≤ 5.4.*
- unaffected 5.10.137 – ≤ 5.10.*
- unaffected 5.15.61 – ≤ 5.15.*
- unaffected 5.18.18 – ≤ 5.18.*
- unaffected 5.19.2 – ≤ 5.19.*
- unaffected 6.0 – ≤ *
References (8)
- https://git.kernel.org/stable/c/c1216e699a1ce83ea005510844bd7508d34c6cef (opens in a new tab)
- https://git.kernel.org/stable/c/4615458db7793fadc6d546ac3564b36819e77a22 (opens in a new tab)
- https://git.kernel.org/stable/c/60c9983425167ec5073c628d83a6875760d18059 (opens in a new tab)
- https://git.kernel.org/stable/c/05ceda14ef7c73104e709c414c3680d8a59f51d4 (opens in a new tab)
- https://git.kernel.org/stable/c/074e865b37da55aa87baa16d68b96896f85f8adb (opens in a new tab)
- https://git.kernel.org/stable/c/789edc1af9c1a2293956e8534bfef3d18d629de9 (opens in a new tab)
- https://git.kernel.org/stable/c/67470920cd3f3cb38699b1ad23234f96bead4d21 (opens in a new tab)
- https://git.kernel.org/stable/c/7a4836560a6198d245d5732e26f94898b12eb760 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://trackcve.app/cve/CVE-2022-50169)Record last updated .