7.8
CVE-2022-48787
- EPSS 0.02%
- Published 16.07.2024 12:15:03
- Last modified 21.11.2024 07:34:01
- Source 416baaa9-dc9f-4396-8d5f-8c081f
- CVE-Watchlists
- Open
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.
Data is provided by the National Vulnerability Database (NVD)
Linux ≫ Linux Kernel Version >= 4.14.263 < 4.14.268
Linux ≫ Linux Kernel Version >= 4.19.226 < 4.19.231
Linux ≫ Linux Kernel Version >= 5.4.174 < 5.4.181
Linux ≫ Linux Kernel Version >= 5.10.94 < 5.10.102
Linux ≫ Linux Kernel Version >= 5.15.17 < 5.15.25
Linux ≫ Linux Kernel Version >= 5.16.3 < 5.16.11
| Type | Source | Score | Percentile |
|---|---|---|---|
| EPSS | FIRST.org | 0.02% | 0.024 |
| Source | Base Score | Exploit Score | Impact Score | Vector string |
|---|---|---|---|---|
| nvd@nist.gov | 7.8 | 1.8 | 5.9 |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
|
CWE-416 Use After Free
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.