CVE-2022-49123: ath11k: Fix frames flush failure caused by deadlock
In the Linux kernel, the following vulnerability has been resolved:
ath11k: Fix frames flush failure caused by deadlock
We are seeing below warnings:
kernel: [25393.301506] ath11kpci 0000:01:00.0: failed to flush mgmt transmit queue 0 kernel: [25398.421509] ath11kpci 0000:01:00.0: failed to flush mgmt transmit queue 0 kernel: [25398.421831] ath11kpci 0000:01:00.0: dropping mgmt frame for vdev 0, isstarted 0
this means ath11k fails to flush mgmt. frames because wmimgmttxwork has no chance to run in 5 seconds.
By setting /proc/sys/kernel/hungtasktimeoutsecs to 20 and increasing ATH11KFLUSHTIMEOUT to 50 we get below warnings:
kernel: [ 120.763160] INFO: task wpasupplicant:924 blocked for more than 20 seconds. kernel: [ 120.763169] Not tainted 5.10.90 #12 kernel: [ 120.763177] "echo 0 > /proc/sys/kernel/hungtasktimeoutsecs" disables this message. kernel: [ 120.763186] task:wpasupplicant state:D stack: 0 pid: 924 ppid: 1 flags:0x000043a0 kernel: [ 120.763201] Call Trace: kernel: [ 120.763214] schedule+0x785/0x12fa kernel: [ 120.763224] ? lockdephardirqsonprepare+0xe2/0x1bb kernel: [ 120.763242] schedule+0x7e/0xa1 kernel: [ 120.763253] scheduletimeout+0x98/0xfe kernel: [ 120.763266] ? runlocaltimers+0x4a/0x4a kernel: [ 120.763291] ath11kmacflushtxcomplete+0x197/0x2b1 [ath11k 13c3a9bf37790f4ac8103b3decf7ab4008ac314a] kernel: [ 120.763306] ? initwaitentry+0x2e/0x2e kernel: [ 120.763343] ieee80211flushqueues+0x167/0x21f [mac80211 335da900954f1c5ea7f1613d92088ce83342042c] kernel: [ 120.763378] ieee80211recalcidle+0x105/0x125 [mac80211 335da900954f1c5ea7f1613d92088ce83342042c] kernel: [ 120.763411] ieee80211recalcidle+0x14/0x27 [mac80211 335da900954f1c5ea7f1613d92088ce83342042c] kernel: [ 120.763441] ieee80211freechanctx+0x77/0xa2 [mac80211 335da900954f1c5ea7f1613d92088ce83342042c] kernel: [ 120.763473] ieee80211vifreleasechannel+0x100/0x131 [mac80211 335da900954f1c5ea7f1613d92088ce83342042c] kernel: [ 120.763540] ieee80211vifreleasechannel+0x66/0x81 [mac80211 335da900954f1c5ea7f1613d92088ce83342042c] kernel: [ 120.763572] ieee80211destroyauthdata+0xa3/0xe6 [mac80211 335da900954f1c5ea7f1613d92088ce83342042c] kernel: [ 120.763612] ieee80211mgddeauth+0x178/0x29b [mac80211 335da900954f1c5ea7f1613d92088ce83342042c] kernel: [ 120.763654] cfg80211mlmedeauth+0x1a8/0x22c [cfg80211 8945aa5bc2af5f6972336665d8ad6f9c191ad5be] kernel: [ 120.763697] nl80211deauthenticate+0xfa/0x123 [cfg80211 8945aa5bc2af5f6972336665d8ad6f9c191ad5be] kernel: [ 120.763715] genlrcvmsg+0x392/0x3c2 kernel: [ 120.763750] ? nl80211associate+0x432/0x432 [cfg80211 8945aa5bc2af5f6972336665d8ad6f9c191ad5be] kernel: [ 120.763782] ? nl80211associate+0x432/0x432 [cfg80211 8945aa5bc2af5f6972336665d8ad6f9c191ad5be] kernel: [ 120.763802] ? genlrcv+0x36/0x36 kernel: [ 120.763814] netlinkrcvskb+0x89/0xf7 kernel: [ 120.763829] genlrcv+0x28/0x36 kernel: [ 120.763840] netlinkunicast+0x179/0x24b kernel: [ 120.763854] netlinksendmsg+0x393/0x401 kernel: [ 120.763872] socksendmsg+0x72/0x76 kernel: [ 120.763886] syssendmsg+0x170/0x1e6 kernel: [ 120.763897] ? copymsghdrfromuser+0x7a/0xa2 kernel: [ 120.763914] syssendmsg+0x95/0xd1 kernel: [ 120.763940] syssendmsg+0x85/0xbf kernel: [ 120.763956] dosyscall64+0x43/0x55 kernel: [ 120.763966] entrySYSCALL64afterhwframe+0x44/0xa9 kernel: [ 120.763977] RIP: 0033:0x79089f3fcc83 kernel: [ 120.763986] RSP: 002b:00007ffe604f0508 EFLAGS: 00000246 ORIGRAX: 000000000000002e kernel: [ 120.763997] RAX: ffffffffffffffda RBX: 000059b40e987690 RCX: 000079089f3fcc83 kernel: [ 120.764006] RDX: 0000000000000000 RSI: 00007ffe604f0558 RDI: 0000000000000009 kernel: [ 120.764014] RBP: 00007ffe604f0540 R08: 0000000000000004 R09: 0000000000400000 kernel: [ 120.764023] R10: 00007ffe604f0638 R11: 0000000000000246 R12: 000059b40ea04980 kernel: [ 120.764032] R13: 00007ffe604 ---truncated---
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2022-49123?
CVE-2022-49123 is considered to have a moderate severity due to the potential for deadlock in the ath11k driver affecting wireless management frames.
How do I fix CVE-2022-49123?
To fix CVE-2022-49123, update your Linux kernel to version 5.17.4 or later, where the vulnerability has been resolved.
What systems are affected by CVE-2022-49123?
CVE-2022-49123 affects systems using the Linux kernel and specifically those utilizing the ath11k driver for Wi-Fi management.
What does CVE-2022-49123 impact in a system's operation?
CVE-2022-49123 can lead to management frame transmission issues resulting in deadlock, impacting network connectivity.
When was CVE-2022-49123 disclosed?
CVE-2022-49123 was disclosed in January 2023 after being identified in the Linux kernel.