Vulnerability · Published Dec 9, 2025 · Assigned by Linux
CVE-2022-50660wifi: ipw2200: fix memory leak in ipw_wdev_init()
Unrated
In plain English
A security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 16% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Severity (CVSS )–Not rated
Exploit odds (30 days)0.2%top 83.5% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known
Official description
In the Linux kernel, the following vulnerability has been resolved: wifi: ipw2200: fix memory leak in ipw_wdev_init() In the error path of ipw_wdev_init(), exception value is returned, and the memory applied for in the function is not released. Also the memory is not released in ipw_pci_probe(). As a result, memory leakage occurs. So memory release needs to be added to the error path of ipw_wdev_init().
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.20-1 | DEBIAN-CVE-2022-50660 |
| Debian:13 | linux | 6.1.20-1 | DEBIAN-CVE-2022-50660 |
| Debian:14 | linux | 6.1.20-1 | DEBIAN-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux | 5.15.0-75.82 | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1038.43 | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1040.47 | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1041.48.1 | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1036.44 | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1036.41 | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1022.27 | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1032.35 | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1033.38 | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1035.40 | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-75.82 | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1027.27 | UBUNTU-CVE-2022-50660 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1015.15 | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1037.43 | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1032.35 | UBUNTU-CVE-2022-50660 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2022-50660 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2022-50660 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | a3caa99e6c68f466c13cfea74097f6fb01b45e25 – before 75d20ba9506eb90d92e660e04dd887ff1495fcc3a3caa99e6c68f466c13cfea74097f6fb01b45e25 – before fb3517b92a45c8004ac26250ae041a24eb23fef1a3caa99e6c68f466c13cfea74097f6fb01b45e25 – before 112c1af02b8f535baf42ef9d807aea963705ef15a3caa99e6c68f466c13cfea74097f6fb01b45e25 – before 8a2eb9d9d0c1535bc8e22840193bff4cdcac878ba3caa99e6c68f466c13cfea74097f6fb01b45e25 – before 9424ea9d557ef41d86eb40b6349ae991c3dcff89a3caa99e6c68f466c13cfea74097f6fb01b45e25 – before 62ec7e8bf42f1542f966dda687c654aae81718c8a3caa99e6c68f466c13cfea74097f6fb01b45e25 – before 1f590fb3d14e5db3a9e06ee141b1685c429278cea3caa99e6c68f466c13cfea74097f6fb01b45e25 – before 9fe21dc626117fb44a8eb393713a86a620128ce3 |
| Linux | Linux | 2.6.33 |
References
- https://git.kernel.org/stable/c/75d20ba9506eb90d92e660e04dd887ff1495fcc3
- https://git.kernel.org/stable/c/fb3517b92a45c8004ac26250ae041a24eb23fef1
- https://git.kernel.org/stable/c/112c1af02b8f535baf42ef9d807aea963705ef15
- https://git.kernel.org/stable/c/8a2eb9d9d0c1535bc8e22840193bff4cdcac878b
- https://git.kernel.org/stable/c/9424ea9d557ef41d86eb40b6349ae991c3dcff89
- https://git.kernel.org/stable/c/62ec7e8bf42f1542f966dda687c654aae81718c8
- https://git.kernel.org/stable/c/1f590fb3d14e5db3a9e06ee141b1685c429278ce
- https://git.kernel.org/stable/c/9fe21dc626117fb44a8eb393713a86a620128ce3