# CVE-2024-43842: wifi: rtw89: Fix array index mistake in rtw89_sta_info_get_iter() > An array index mistake in the rtw89 WiFi driver allows out-of-bounds access, potentially causing crashes or code execution. - **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 17 Aug 2024 - **Updated:** 11 May 2026 - **Also known as:** ALSA-2025:8246, ALSA-2025:8247, BELL-CVE-2024-43842, DEBIAN-CVE-2024-43842, GHSA-frrf-pwhq-w5pw, RLSA-2025:8246, RLSA-2025:8247, ROOT-OS-UBUNTU-2204-CVE-2024-43842, UBUNTU-CVE-2024-43842 ## What is CVE-2024-43842? CVE-2024-43842 is a high-severity memory corruption vulnerability in Linux kernel, published on 17 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description In the Linux kernel, the following vulnerability has been resolved: wifi: rtw89: Fix array index mistake in rtw89_sta_info_get_iter() In rtw89_sta_info_get_iter() 'status->he_gi' is compared to array size. But then 'rate->he_gi' is used as array index instead of 'status->he_gi'. This can lead to go beyond array boundaries in case of 'rate->he_gi' is not equal to 'status->he_gi' and is bigger than array size. Looks like "copy-paste" mistake. Fix this mistake by replacing 'rate->he_gi' with 'status->he_gi'. Found by Linux Verification Center (linuxtesting.org) with SVACE. Weakness: CWE-129 (Improper Validation of Array Index) ## Which versions are affected by CVE-2024-43842? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `bpftool` | AlmaLinux:8 | All versions | 4.18.0-553.54.1.el8_10 | | `kernel` | AlmaLinux:8 | All versions | 4.18.0-553.54.1.el8_10 | | `kernel-abi-stablelists` | AlmaLinux:8 | All versions | 4.18.0-553.54.1.el8_10 | | `kernel-core` | AlmaLinux:8 | All versions | 4.18.0-553.54.1.el8_10 | | `kernel-cross-headers` | AlmaLinux:8 | All versions | 4.18.0-553.54.1.el8_10 | | `kernel-debug` | AlmaLinux:8 | All versions | 4.18.0-553.54.1.el8_10 | | `kernel-debug-core` | AlmaLinux:8 | All versions | 4.18.0-553.54.1.el8_10 | | `kernel-debug-devel` | AlmaLinux:8 | All versions | 4.18.0-553.54.1.el8_10 | | `kernel-debug-modules` | AlmaLinux:8 | All versions | 4.18.0-553.54.1.el8_10 | | `kernel-debug-modules-extra` | AlmaLinux:8 | All versions | 4.18.0-553.54.1.el8_10 | | `kernel-devel` | AlmaLinux:8 | All versions | 4.18.0-553.54.1.el8_10 | | `kernel-doc` | AlmaLinux:8 | All versions | 4.18.0-553.54.1.el8_10 | | `kernel-headers` | AlmaLinux:8 | All versions | 4.18.0-553.54.1.el8_10 | | `kernel-modules` | AlmaLinux:8 | All versions | 4.18.0-553.54.1.el8_10 | | `kernel-modules-extra` | AlmaLinux:8 | All versions | 4.18.0-553.54.1.el8_10 | | `kernel-rt` | AlmaLinux:8 | All versions | 4.18.0-553.54.1.rt7.395.el8_10 | | `kernel-rt-core` | AlmaLinux:8 | All versions | 4.18.0-553.54.1.rt7.395.el8_10 | | `kernel-rt-debug` | AlmaLinux:8 | All versions | 4.18.0-553.54.1.rt7.395.el8_10 | | `kernel-rt-debug-core` | AlmaLinux:8 | All versions | 4.18.0-553.54.1.rt7.395.el8_10 | | `kernel-rt-debug-devel` | AlmaLinux:8 | All versions | 4.18.0-553.54.1.rt7.395.el8_10 | | `kernel-rt-debug-modules` | AlmaLinux:8 | All versions | 4.18.0-553.54.1.rt7.395.el8_10 | | `kernel-rt-debug-modules-extra` | AlmaLinux:8 | All versions | 4.18.0-553.54.1.rt7.395.el8_10 | | `kernel-rt-devel` | AlmaLinux:8 | All versions | 4.18.0-553.54.1.rt7.395.el8_10 | | `kernel-rt-modules` | AlmaLinux:8 | All versions | 4.18.0-553.54.1.rt7.395.el8_10 | | `kernel-rt-modules-extra` | AlmaLinux:8 | All versions | 4.18.0-553.54.1.rt7.395.el8_10 | | `kernel-tools` | AlmaLinux:8 | All versions | 4.18.0-553.54.1.el8_10 | | `kernel-tools-libs` | AlmaLinux:8 | All versions | 4.18.0-553.54.1.el8_10 | | `kernel-tools-libs-devel` | AlmaLinux:8 | All versions | 4.18.0-553.54.1.el8_10 | | `kernel-zfcpdump` | AlmaLinux:8 | All versions | 4.18.0-553.54.1.el8_10 | | `kernel-zfcpdump-core` | AlmaLinux:8 | All versions | 4.18.0-553.54.1.el8_10 | | `kernel-zfcpdump-devel` | AlmaLinux:8 | All versions | 4.18.0-553.54.1.el8_10 | | `kernel-zfcpdump-modules` | AlmaLinux:8 | All versions | 4.18.0-553.54.1.el8_10 | | `kernel-zfcpdump-modules-extra` | AlmaLinux:8 | All versions | 4.18.0-553.54.1.el8_10 | | `perf` | AlmaLinux:8 | All versions | 4.18.0-553.54.1.el8_10 | | `python3-perf` | AlmaLinux:8 | All versions | 4.18.0-553.54.1.el8_10 | | `kernel` | Rocky Linux:8 | All versions | 0:4.18.0-553.54.1.el8_10 | | `kernel-rt` | Rocky Linux:8 | All versions | 0:4.18.0-553.54.1.rt7.395.el8_10 | Products: Linux kernel. ## How do I fix CVE-2024-43842? Apply the vendor's patch. ## Is CVE-2024-43842 being exploited? There is no known exploitation of CVE-2024-43842 in the wild and no public exploit code. ## Other vulnerabilities in Linux kernel - [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild) - [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild) - [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild) - [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild) - [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-43842 and fix it if it is affected. What it is: CVE-2024-43842 is a high-severity memory corruption vulnerability in Linux kernel, published on 17 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-43842 in the wild and no public exploit code. Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-43842/ (Markdown: https://insights.sbomify.com/CVE-2024-43842/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-43842 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-43842 - OSV: https://osv.dev/vulnerability/CVE-2024-43842 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-43842/ Summaries are generated and may contain mistakes; the official description above is the record.