Vulnerability · Published Mar 2, 2024 · Assigned by Linux

CVE-2023-52531wifi: iwlwifi: mvm: Fix a memory corruption issue

High 7.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.2% (higher than 15% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)7.8High
Exploit odds (30 days)0.2%top 85.2% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: mvm: Fix a memory corruption issue A few lines above, space is kzalloc()'ed for: sizeof(struct iwl_nvm_data) + sizeof(struct ieee80211_channel) + sizeof(struct ieee80211_rate) 'mvm->nvm_data' is a 'struct iwl_nvm_data', so it is fine. At the end of this structure, there is the 'channels' flex array. Each element is of type 'struct ieee80211_channel'. So only 1 element is allocated in this array. When doing: mvm->nvm_data->bands[0].channels = mvm->nvm_data->channels; We point at the first element of the 'channels' flex array. So this is fine. However, when doing: mvm->nvm_data->bands[0].bitrates = (void *)((u8 *)mvm->nvm_data->channels + 1); because of the "(u8 *)" cast, we add only 1 to the address of the beginning of the flex array. It is likely that we want point at the 'struct ieee80211_rate' allocated just after. Remove the spurious casting so that the pointer arithmetic works as expected.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux6.1.64-1DEBIAN-CVE-2023-52531
Debian:13linux6.5.8-1DEBIAN-CVE-2023-52531
Debian:14linux6.5.8-1DEBIAN-CVE-2023-52531
Ubuntu:22.04:LTSlinux5.15.0-94.104UBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-aws5.15.0-1053.58UBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-azure5.15.0-1056.64UBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-azure-fde5.15.0-1056.64.1UBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-gcp5.15.0-1051.59UBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-gke5.15.0-1050.55UBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-gkeop5.15.0-1036.42UBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-ibm5.15.0-1046.49UBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1047.53UBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-kvm5.15.0-1050.55UBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-94.104UBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-nvidia5.15.0-1044.44UBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-nvidia-6.56.5.0-1014.14UBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-nvidia-tegra5.15.0-1022.22UBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-nvidia-tegra-igx5.15.0-1009.9UBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-oracle5.15.0-1051.57UBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-raspi5.15.0-1046.49UBUNTU-CVE-2023-52531
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2023-52531
Ubuntu:22.04:LTSlinux-xilinx-zynqmp5.15.0-1027.31UBUNTU-CVE-2023-52531

Affected products (as reported)

VendorProductVersions
Linux Linux 8ca151b568b67a7b72dcfc6ee6ea7c107ddd795c – before 7c8faa31080342aec4903c9acb20caf82fcca1ef8ca151b568b67a7b72dcfc6ee6ea7c107ddd795c – before 6b3223449c959a8be94a1f042288059e40fcccb08ca151b568b67a7b72dcfc6ee6ea7c107ddd795c – before f06cdd8d4ba5252986f51f80cc302636363971288ca151b568b67a7b72dcfc6ee6ea7c107ddd795c – before 8ba438ef3cacc4808a63ed0ce24d4f0942cfe55d
Linux Linux 3.9

References