Vulnerability · Published May 21, 2024 · Assigned by Linux
CVE-2023-52769wifi: ath12k: fix htt mlo-offset event locking
High 8.8
In plain English
A high-severity 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.3% (higher than 27% 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: ath12k: fix htt mlo-offset event locking The ath12k active pdevs are protected by RCU but the htt mlo-offset event handling code calling ath12k_mac_get_ar_by_pdev_id() was not marked as a read-side critical section. Mark the code in question as an RCU read-side critical section to avoid any potential use-after-free issues. Compile tested only.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:13 | linux | 6.6.8-1 | DEBIAN-CVE-2023-52769 |
| Debian:14 | linux | 6.6.8-1 | DEBIAN-CVE-2023-52769 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2023-52769 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2023-52769 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2023-52769 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | 6.5.0-1015.15~22.04.1 | UBUNTU-CVE-2023-52769 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2023-52769 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2023-52769 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | 6.5.0-1016.16~22.04.1 | UBUNTU-CVE-2023-52769 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2023-52769 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2023-52769 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2023-52769 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2023-52769 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | 6.5.0-1015.15~22.04.1 | UBUNTU-CVE-2023-52769 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-52769 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-52769 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | 6.5.0-25.25~22.04.1 | UBUNTU-CVE-2023-52769 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-52769 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-52769 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | 6.5.0-25.25.1~22.04.1 | UBUNTU-CVE-2023-52769 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2023-52769 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | 6.5.0-1014.14 | UBUNTU-CVE-2023-52769 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2023-52769 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2023-52769 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2023-52769 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | 6.5.0-1016.17 | UBUNTU-CVE-2023-52769 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | 6.5.0-1018.18~22.04.1 | UBUNTU-CVE-2023-52769 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2023-52769 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2023-52769 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | 6.5.0-25.25.1~22.04.1 | UBUNTU-CVE-2023-52769 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2023-52769 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2023-52769 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | 6.5.0-1009.10~22.04.1 | UBUNTU-CVE-2023-52769 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | d889913205cf7ebda905b1e62c5867ed4e39f6c2 – before d908ca431e20b0e4bfc5d911d1744910ed779bdbd889913205cf7ebda905b1e62c5867ed4e39f6c2 – before afd3425bd69610f318403084fe491e24a1357fb9d889913205cf7ebda905b1e62c5867ed4e39f6c2 – before 6afc57ea315e0f660b1f870a681737bb7b71faef |
| Linux | Linux | 6.3 |