CVE-2022-50187: ath11k: fix netdev open race
In the Linux kernel, the following vulnerability has been resolved:
ath11k: fix netdev open race
Make sure to allocate resources needed before registering the device.
This specifically avoids having a racing open() trigger a BUGON() in modtimer() when ath11kmacopstart() is called before the monreaptimer as been set up.
I did not see this issue with next-20220310, but I hit it on every probe with next-20220511. Perhaps some timing changed in between.
Here's the backtrace:
[ 51.346947] kernel BUG at kernel/time/timer.c:990! [ 51.346958] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ... [ 51.578225] Call trace: [ 51.583293] modtimer+0x298/0x390 [ 51.589518] modtimer+0x14/0x20 [ 51.595368] ath11kmacopstart+0x41c/0x4a0 [ath11k] [ 51.603165] drvstart+0x38/0x60 [mac80211] [ 51.610110] ieee80211doopen+0x29c/0x7d0 [mac80211] [ 51.617945] ieee80211open+0x60/0xb0 [mac80211] [ 51.625311] devopen+0x100/0x1c0 [ 51.631420] devchangeflags+0x194/0x210 [ 51.638214] devchangeflags+0x24/0x70 [ 51.644646] dosetlink+0x228/0xdb0 [ 51.650723] rtnlnewlink+0x460/0x830 [ 51.657162] rtnlnewlink+0x4c/0x80 [ 51.663229] rtnetlinkrcvmsg+0x124/0x390 [ 51.669917] netlinkrcvskb+0x58/0x130 [ 51.676314] rtnetlinkrcv+0x18/0x30 [ 51.682460] netlinkunicast+0x250/0x310 [ 51.688960] netlinksendmsg+0x19c/0x3e0 [ 51.695458] syssendmsg+0x220/0x290 [ 51.701938] syssendmsg+0x7c/0xc0 [ 51.708148] syssendmsg+0x68/0xd0 [ 51.714254] arm64syssendmsg+0x28/0x40 [ 51.720900] invokesyscall+0x48/0x120
Tested-on: WCN6855 hw2.0 PCI WLAN.HSP.1.1-03125-QCAHSPSWPLV1V2SILICONZLITE-3
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/linux-aws-5.15to a version that resolves this vulnerability.Fixed in 5.15.0-1023.27~20.04.1 - Upgrade
Upgrade
ubuntu/linux-azure-5.15to a version that resolves this vulnerability.Fixed in 5.15.0-1023.29~20.04.1 - Upgrade
Upgrade
ubuntu/linux-gcp-5.15to a version that resolves this vulnerability.Fixed in 5.15.0-1022.29~20.04.1 - Upgrade
Upgrade
ubuntu/linux-hwe-5.15to a version that resolves this vulnerability.Fixed in 5.15.0-53.59~20.04.1 - Upgrade
Upgrade
ubuntu/linux-intel-iotg-5.15to a version that resolves this vulnerability.Fixed in 5.15.0-1018.23~20.04.1 - Upgrade
Upgrade
ubuntu/linux-lowlatency-hwe-5.15to a version that resolves this vulnerability.Fixed in 5.15.0-53.59~20.04.1 - Upgrade
Upgrade
ubuntu/linux-oracle-5.15to a version that resolves this vulnerability.Fixed in 5.15.0-1022.28~20.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-5.15to a version that resolves this vulnerability.Fixed in 5.15.0-1023.27~20.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 5.15.0-53.59 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 5.15.0-1023.27 - Upgrade
Upgrade
ubuntu/linux-azureto a version that resolves this vulnerability.Fixed in 5.15.0-1023.29 - Upgrade
Upgrade
ubuntu/linux-azure-fdeto a version that resolves this vulnerability.Fixed in 5.15.0-1024.30.1 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 5.15.0-1022.29 - Upgrade
Upgrade
ubuntu/linux-gketo a version that resolves this vulnerability.Fixed in 5.15.0-1020.25 - Upgrade
Upgrade
ubuntu/linux-gkeopto a version that resolves this vulnerability.Fixed in 5.15.0-1008.12 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 5.15.0-1018.21 - Upgrade
Upgrade
ubuntu/linux-intel-iotgto a version that resolves this vulnerability.Fixed in 5.15.0-1018.23 - Upgrade
Upgrade
ubuntu/linux-kvmto a version that resolves this vulnerability.Fixed in 5.15.0-1021.26 - Upgrade
Upgrade
ubuntu/linux-lowlatencyto a version that resolves this vulnerability.Fixed in 5.15.0-53.59 - Upgrade
Upgrade
ubuntu/linux-nvidiato a version that resolves this vulnerability.Fixed in 5.15.0-1015.15 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 5.15.0-1022.28 - Upgrade
Upgrade
ubuntu/linux-raspito a version that resolves this vulnerability.Fixed in 5.15.0-1018.20 - Upgrade
Upgrade
ubuntu/linux-realtimeto a version that resolves this vulnerability.Fixed in 5.15.0-1025.28 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.0.2-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.192-2Fixed in 6.12.107-1Fixed in 6.12.117-1Fixed in 7.3.4-1Fixed in 7.3.5-1 - Compensating control
In ath11k, allocate the resources needed for the device before registering it, ensuring mon_reap_timer is set up before ath11k_mac_op_start() can be called.
Event History
Frequently Asked Questions
What is the severity of CVE-2022-50187?
CVE-2022-50187 has a moderate severity rating, indicating it could lead to instability under certain conditions.
How do I fix CVE-2022-50187?
To mitigate CVE-2022-50187, ensure you update your Linux kernel to the latest version that includes the fix.
What systems are affected by CVE-2022-50187?
CVE-2022-50187 affects the Linux kernel version from next-20220511 onwards.
What does CVE-2022-50187 address?
CVE-2022-50187 addresses a race condition during device registration in the ath11k driver.
Who is responsible for fixing CVE-2022-50187?
The responsibility for addressing CVE-2022-50187 lies with the Linux kernel developers and system administrators who manage the affected systems.