CVE-2023-54229
Typo-Induced Registration Failure in Linux ath11k 6GHz PHY
Publication date: 2025-12-30
Last updated on: 2025-12-30
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a bug in the Linux kernel's ath11k wireless driver related to the registration of 6GHz-only physical wireless devices (phys). Due to what appears to be a typo, if the device's Board Data File (BDF) does not allow the 7115MHz channel, the 6GHz-only phy fails to register properly, causing errors and preventing the wireless hardware from being correctly initialized.
How can this vulnerability impact me? :
The impact of this vulnerability is that a 6GHz-only wireless device may fail to register and initialize on affected Linux kernels. This means the wireless hardware will not function correctly, potentially causing loss of wireless connectivity or inability to use the 6GHz wireless band on affected devices.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking the system logs for specific error messages related to the ath11k driver failing to register the 6GHz-only phy. Look for warnings or errors such as 'ieee80211 registration failed: -22' or 'failed register the radio with mac80211: -22' in the kernel log. You can use the command 'dmesg | grep ath11k' or 'journalctl -k | grep ath11k' to find these messages.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where this issue is fixed, as the vulnerability is due to a typo in the ath11k driver code causing registration failure of the 6GHz-only phy. Until an update is applied, you may consider disabling the affected wireless device or avoiding use of 6GHz-only channels to prevent triggering the issue.