| 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: <2026021429-CVE-2026-23180-19a8@gregkh> Date: Sat, 14 Feb 2026 17:28:37 +0100 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2026-23180: dpaa2-switch: add bounds check for if_id in IRQ handler From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: dpaa2-switch: add bounds check for if_id in IRQ handler The IRQ handler extracts if_id from the upper 16 bits of the hardware status register and uses it to index into ethsw->ports[] without validation. Since if_id can be any 16-bit value (0-65535) but the ports array is only allocated with sw_attr.num_ifs elements, this can lead to an out-of-bounds read potentially. Add a bounds check before accessing the array, consistent with the existing validation in dpaa2_switch_rx(). The Linux kernel CVE team has assigned CVE-2026-23180 to this issue. Affected and fixed versions =========================== Issue introduced in 5.15 with commit 24ab724f8a4661b2dc8e696b41df93bdc108f7a1 and fixed in 5.15.200 with commit 77611cab5bdfff7a070ae574bbfba20a1de99d1b Issue introduced in 5.15 with commit 24ab724f8a4661b2dc8e696b41df93bdc108f7a1 and fixed in 6.1.163 with commit 34b56c16efd61325d80bf1d780d0e176be662f59 Issue introduced in 5.15 with commit 24ab724f8a4661b2dc8e696b41df93bdc108f7a1 and fixed in 6.6.124 with commit f89e33c9c37f0001b730e23b3b05ab7b1ecface2 Issue introduced in 5.15 with commit 24ab724f8a4661b2dc8e696b41df93bdc108f7a1 and fixed in 6.12.70 with commit 2447edc367800ba914acf7ddd5d250416b45fb31 Issue introduced in 5.15 with commit 24ab724f8a4661b2dc8e696b41df93bdc108f7a1 and fixed in 6.18.10 with commit 1b381a638e1851d8cfdfe08ed9cdbec5295b18c9 Issue introduced in 5.15 with commit 24ab724f8a4661b2dc8e696b41df93bdc108f7a1 and fixed in 6.19 with commit 31a7a0bbeb006bac2d9c81a2874825025214b6d8 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-2026-23180 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/ethernet/freescale/dpaa2/dpaa2-switch.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/77611cab5bdfff7a070ae574bbfba20a1de99d1b https://git.kernel.org/stable/c/34b56c16efd61325d80bf1d780d0e176be662f59 https://git.kernel.org/stable/c/f89e33c9c37f0001b730e23b3b05ab7b1ecface2 https://git.kernel.org/stable/c/2447edc367800ba914acf7ddd5d250416b45fb31 https://git.kernel.org/stable/c/1b381a638e1851d8cfdfe08ed9cdbec5295b18c9 https://git.kernel.org/stable/c/31a7a0bbeb006bac2d9c81a2874825025214b6d8
Powered by blists - more mailing lists