Vulnerability · Published Apr 17, 2024 · Assigned by Linux
CVE-2024-26896wifi: wfx: fix memory leak when starting AP
Medium 5.5
In plain English
A medium-severity out-of-bounds read 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 13% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
In the Linux kernel, the following vulnerability has been resolved: wifi: wfx: fix memory leak when starting AP Kmemleak reported this error: unreferenced object 0xd73d1180 (size 184): comm "wpa_supplicant", pid 1559, jiffies 13006305 (age 964.245s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 1e 00 01 00 00 00 00 00 ................ backtrace: [<5ca11420>] kmem_cache_alloc+0x20c/0x5ac [<127bdd74>] __alloc_skb+0x144/0x170 [<fb8a5e38>] __netdev_alloc_skb+0x50/0x180 [<0f9fa1d5>] __ieee80211_beacon_get+0x290/0x4d4 [mac80211] [<7accd02d>] ieee80211_beacon_get_tim+0x54/0x18c [mac80211] [<41e25cc3>] wfx_start_ap+0xc8/0x234 [wfx] [<93a70356>] ieee80211_start_ap+0x404/0x6b4 [mac80211] [<a4a661cd>] nl80211_start_ap+0x76c/0x9e0 [cfg80211] [<47bd8b68>] genl_rcv_msg+0x198/0x378 [<453ef796>] netlink_rcv_skb+0xd0/0x130 [<6b7c977a>] genl_rcv+0x34/0x44 [<66b2d04d>] netlink_unicast+0x1b4/0x258 [<f965b9b6>] netlink_sendmsg+0x1e8/0x428 [<aadb8231>] ____sys_sendmsg+0x1e0/0x274 [<d2b5212d>] ___sys_sendmsg+0x80/0xb4 [<69954f45>] __sys_sendmsg+0x64/0xa8 unreferenced object 0xce087000 (size 1024): comm "wpa_supplicant", pid 1559, jiffies 13006305 (age 964.246s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 10 00 07 40 00 00 00 00 00 00 00 00 00 00 00 00 ...@............ backtrace: [<9a993714>] __kmalloc_track_caller+0x230/0x600 [<f83ea192>] kmalloc_reserve.constprop.0+0x30/0x74 [<a2c61343>] __alloc_skb+0xa0/0x170 [<fb8a5e38>] __netdev_alloc_skb+0x50/0x180 [<0f9fa1d5>] __ieee80211_beacon_get+0x290/0x4d4 [mac80211] [<7accd02d>] ieee80211_beacon_get_tim+0x54/0x18c [mac80211] [<41e25cc3>] wfx_start_ap+0xc8/0x234 [wfx] [<93a70356>] ieee80211_start_ap+0x404/0x6b4 [mac80211] [<a4a661cd>] nl80211_start_ap+0x76c/0x9e0 [cfg80211] [<47bd8b68>] genl_rcv_msg+0x198/0x378 [<453ef796>] netlink_rcv_skb+0xd0/0x130 [<6b7c977a>] genl_rcv+0x34/0x44 [<66b2d04d>] netlink_unicast+0x1b4/0x258 [<f965b9b6>] netlink_sendmsg+0x1e8/0x428 [<aadb8231>] ____sys_sendmsg+0x1e0/0x274 [<d2b5212d>] ___sys_sendmsg+0x80/0xb4 However, since the kernel is build optimized, it seems the stack is not accurate. It appears the issue is related to wfx_set_mfp_ap(). The issue is obvious in this function: memory allocated by ieee80211_beacon_get() is never released. Fixing this leak makes kmemleak happy.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.85-1 | DEBIAN-CVE-2024-26896 |
| Debian:13 | linux | 6.7.12-1 | DEBIAN-CVE-2024-26896 |
| Debian:14 | linux | 6.7.12-1 | DEBIAN-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux | 5.15.0-160.170 | USN-7829-1 |
| Ubuntu:22.04:LTS | linux | 5.15.0-160.170 | UBUNTU-CVE-2024-26896 |
| Ubuntu:24.04:LTS | linux | 6.8.0-35.35 | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1095.102 | USN-7829-1 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1095.102 | UBUNTU-CVE-2024-26896 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1009.9 | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1098.107 | USN-7829-3 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1098.107 | UBUNTU-CVE-2024-26896 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1008.8 | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1098.107.1 | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1095.104 | USN-7829-1 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1095.104 | UBUNTU-CVE-2024-26896 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1008.9 | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1091.97 | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1091.97 | USN-7829-1 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1004.7 | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1078.86 | USN-7829-1 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1078.86 | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1089.92 | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1089.92 | USN-7829-1 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1006.6 | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1090.96 | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1090.96 | USN-7829-5 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1089.94 | USN-7933-1 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1089.94 | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-160.170 | USN-7829-1 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-160.170 | UBUNTU-CVE-2024-26896 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-35.35.1 | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1090.91 | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1090.91 | USN-7829-1 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1047.47 | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1047.47 | USN-7829-6 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1036.36 | USN-7829-6 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1036.36 | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2024-26896 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | 6.8.0-1006.6 | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1092.98 | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1092.98 | USN-7829-1 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1006.6 | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1089.92 | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1089.92 | USN-7829-6 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1005.5 | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2024-26896 |
| Ubuntu:24.04:LTS | linux-riscv | 6.8.0-35.35.1 | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2024-26896 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1059.63 | USN-7829-1 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1059.63 | UBUNTU-CVE-2024-26896 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 268bceec1684932e194ae87877dcc73f534d921c – before a1f57a0127b89a6b6620514564aa7eaec16d9af3268bceec1684932e194ae87877dcc73f534d921c – before 3a71ec74e5e3478d202a1874f085ca3ef40be49b268bceec1684932e194ae87877dcc73f534d921c – before 12f00a367b2b62756e0396f14b54c2c15524e1c3268bceec1684932e194ae87877dcc73f534d921c – before dadbb5d29d6c5f571a50272fce8c1505a9559487268bceec1684932e194ae87877dcc73f534d921c – before b8cfb7c819dd39965136a66fe3a7fde688d976fc |
| Linux | Linux | 5.10 |
Weakness: CWE-125
References
- https://git.kernel.org/stable/c/a1f57a0127b89a6b6620514564aa7eaec16d9af3
- https://git.kernel.org/stable/c/3a71ec74e5e3478d202a1874f085ca3ef40be49b
- https://git.kernel.org/stable/c/12f00a367b2b62756e0396f14b54c2c15524e1c3
- https://git.kernel.org/stable/c/dadbb5d29d6c5f571a50272fce8c1505a9559487
- https://git.kernel.org/stable/c/b8cfb7c819dd39965136a66fe3a7fde688d976fc