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: <2024111905-CVE-2024-53083-6ed0@gregkh> Date: Tue, 19 Nov 2024 18:45:03 +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-53083: usb: typec: qcom-pmic: init value of hdr_len/txbuf_len earlier Description =========== In the Linux kernel, the following vulnerability has been resolved: usb: typec: qcom-pmic: init value of hdr_len/txbuf_len earlier If the read of USB_PDPHY_RX_ACKNOWLEDGE_REG failed, then hdr_len and txbuf_len are uninitialized. This commit stops to print uninitialized value and misleading/false data. The Linux kernel CVE team has assigned CVE-2024-53083 to this issue. Affected and fixed versions =========================== Issue introduced in 6.5 with commit a4422ff22142 and fixed in 6.6.61 with commit 35925e2b7b40 Issue introduced in 6.5 with commit a4422ff22142 and fixed in 6.11.8 with commit 74d8cee747b3 Issue introduced in 6.5 with commit a4422ff22142 and fixed in 6.12 with commit 029778a4fd2c 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-53083 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/usb/typec/tcpm/qcom/qcom_pmic_typec_pdphy.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/35925e2b7b404cad3db857434d3312b892b55432 https://git.kernel.org/stable/c/74d8cee747b37cd9f5ca631f678e66e7f40f2b5f https://git.kernel.org/stable/c/029778a4fd2c90c2e76a902b797c2348a722f1b8
Powered by blists - more mailing lists