Back
CVE-2022-48787
iwlwifi: fix use-after-free
High7.8EPSS 0.24%
- Published
- Updated
- Reserved
- Assigned by
- Linux
Description
In the Linux kernel, the following vulnerability has been resolved: iwlwifi: fix use-after-free If no firmware was present at all (or, presumably, all of the firmware files failed to parse), we end up unbinding by calling device_release_driver(), which calls remove(), which then in iwlwifi calls iwl_drv_stop(), freeing the 'drv' struct. However the new code I added will still erroneously access it after it was freed. Set 'failure=false' in this case to avoid the access, all data was already freed anyway.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.24% · top 84% of all CVEs (6 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Weakness
Affected products
- affected 8e10749fa1a454c1e7214f36cec83241f5a36ef1 – < d3b98fe36f8a06ce654049540773256ab59cb53d
- affected 1d7cc54137a4f28506dc7beac235b240b08f4e59 – < 7d6475179b85a83186ccce59cdc359d4f07d0bcb
- affected 0446cafa843e6db4982731c167e11c80d42be7e2 – < 494de920d98f125b099f27a2d274850750aff957
- affected febab6b60d61d13cd9f30a2991deea56df39567d – < 008508c16af0087cda0394e1ac6f0493b01b6063
- affected e23f075d77987de4215c8e0696f28bcc707506f7 – < ddd46059f7d99119b62d44c519df7a79f2e6a515
- affected 6b5ad4bd0d78fef6bbe0ecdf96e09237c9c52cc1 – < 9958b9cbb22145295ee1ffaea0904c383da2c05d
- affected ab07506b0454bea606095951e19e72c282bfbb42 – < bea2662e7818e15d7607d17d57912ac984275d94
- affected 4.14.263 – < 4.14.268
- affected 4.19.226 – < 4.19.231
- affected 5.4.174 – < 5.4.181
- affected 5.10.94 – < 5.10.102
- affected 5.15.17 – < 5.15.25
- affected 5.16.3 – < 5.16.11
References (7)
- https://git.kernel.org/stable/c/d3b98fe36f8a06ce654049540773256ab59cb53d (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/7d6475179b85a83186ccce59cdc359d4f07d0bcb (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/494de920d98f125b099f27a2d274850750aff957 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/008508c16af0087cda0394e1ac6f0493b01b6063 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/ddd46059f7d99119b62d44c519df7a79f2e6a515 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/9958b9cbb22145295ee1ffaea0904c383da2c05d (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/bea2662e7818e15d7607d17d57912ac984275d94 (opens in a new tab)x_transferred
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-48787)Record last updated .