| 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: <2025091627-CVE-2023-53298-2ca9@gregkh> Date: Tue, 16 Sep 2025 10:11:48 +0200 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2023-53298: nfc: fix memory leak of se_io context in nfc_genl_se_io From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: nfc: fix memory leak of se_io context in nfc_genl_se_io The callback context for sending/receiving APDUs to/from the selected secure element is allocated inside nfc_genl_se_io and supposed to be eventually freed in se_io_cb callback function. However, there are several error paths where the bwi_timer is not charged to call se_io_cb later, and the cb_context is leaked. The patch proposes to free the cb_context explicitly on those error paths. At the moment we can't simply check 'dev->ops->se_io()' return value as it may be negative in both cases: when the timer was charged and was not. The Linux kernel CVE team has assigned CVE-2023-53298 to this issue. Affected and fixed versions =========================== Issue introduced in 3.13 with commit 5ce3f32b5264b337bfd13a780452a17705307725 and fixed in 4.14.308 with commit 5321da6d84b87a34eea441677d649c34bd854169 Issue introduced in 3.13 with commit 5ce3f32b5264b337bfd13a780452a17705307725 and fixed in 4.19.276 with commit af452e35b9e6a87cd49e54a7a3d60d934b194651 Issue introduced in 3.13 with commit 5ce3f32b5264b337bfd13a780452a17705307725 and fixed in 5.4.235 with commit 271eed1736426103335c5aac50f15b0f4d236bc0 Issue introduced in 3.13 with commit 5ce3f32b5264b337bfd13a780452a17705307725 and fixed in 5.10.173 with commit 8978315cb4bf8878c9c8ec05dafd8f7ff539860d Issue introduced in 3.13 with commit 5ce3f32b5264b337bfd13a780452a17705307725 and fixed in 5.15.100 with commit c494365432dcdc549986f4d9af9eb6190cbdb153 Issue introduced in 3.13 with commit 5ce3f32b5264b337bfd13a780452a17705307725 and fixed in 6.1.18 with commit b2036a252381949d3b743a3de069324ae3028a57 Issue introduced in 3.13 with commit 5ce3f32b5264b337bfd13a780452a17705307725 and fixed in 6.2.5 with commit ba98db08895748c12e5ded52cd1598dce2c79e55 Issue introduced in 3.13 with commit 5ce3f32b5264b337bfd13a780452a17705307725 and fixed in 6.3 with commit 25ff6f8a5a3b8dc48e8abda6f013e8cc4b14ffea 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-2023-53298 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/nfc/st-nci/se.c drivers/nfc/st21nfca/se.c net/nfc/netlink.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/5321da6d84b87a34eea441677d649c34bd854169 https://git.kernel.org/stable/c/af452e35b9e6a87cd49e54a7a3d60d934b194651 https://git.kernel.org/stable/c/271eed1736426103335c5aac50f15b0f4d236bc0 https://git.kernel.org/stable/c/8978315cb4bf8878c9c8ec05dafd8f7ff539860d https://git.kernel.org/stable/c/c494365432dcdc549986f4d9af9eb6190cbdb153 https://git.kernel.org/stable/c/b2036a252381949d3b743a3de069324ae3028a57 https://git.kernel.org/stable/c/ba98db08895748c12e5ded52cd1598dce2c79e55 https://git.kernel.org/stable/c/25ff6f8a5a3b8dc48e8abda6f013e8cc4b14ffea
Powered by blists - more mailing lists