lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <2025011120-CVE-2024-48873-75a9@gregkh> Date: Sat, 11 Jan 2025 13:25:24 +0100 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org> Subject: CVE-2024-48873: wifi: rtw89: check return value of ieee80211_probereq_get() for RNR Description =========== In the Linux kernel, the following vulnerability has been resolved: wifi: rtw89: check return value of ieee80211_probereq_get() for RNR The return value of ieee80211_probereq_get() might be NULL, so check it before using to avoid NULL pointer access. Addresses-Coverity-ID: 1529805 ("Dereference null return value") The Linux kernel CVE team has assigned CVE-2024-48873 to this issue. Affected and fixed versions =========================== Fixed in 6.6.66 with commit 1a0f54cb3fea5d087440b2bae03202c445156a8d Fixed in 6.12.5 with commit 7296e5611adb2c619bd7bd3817ddde7ba865ef17 Fixed in 6.13-rc1 with commit 630d5d8f2bf6b340202b6bc2c05d794bbd8e4c1c Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2024-48873 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: drivers/net/wireless/realtek/rtw89/fw.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/1a0f54cb3fea5d087440b2bae03202c445156a8d https://git.kernel.org/stable/c/7296e5611adb2c619bd7bd3817ddde7ba865ef17 https://git.kernel.org/stable/c/630d5d8f2bf6b340202b6bc2c05d794bbd8e4c1c
Powered by blists - more mailing lists