| 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: <2025022635-CVE-2022-49308-23f0@gregkh> Date: Wed, 26 Feb 2025 03:09:42 +0100 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org> Subject: CVE-2022-49308: extcon: Modify extcon device to be created after driver data is set Description =========== In the Linux kernel, the following vulnerability has been resolved: extcon: Modify extcon device to be created after driver data is set Currently, someone can invoke the sysfs such as state_show() intermittently before dev_set_drvdata() is done. And it can be a cause of kernel Oops because of edev is Null at that time. So modified the driver registration to after setting drviver data. - Oops's backtrace. Backtrace: [<c067865c>] (state_show) from [<c05222e8>] (dev_attr_show) [<c05222c0>] (dev_attr_show) from [<c02c66e0>] (sysfs_kf_seq_show) [<c02c6648>] (sysfs_kf_seq_show) from [<c02c496c>] (kernfs_seq_show) [<c02c4938>] (kernfs_seq_show) from [<c025e2a0>] (seq_read) [<c025e11c>] (seq_read) from [<c02c50a0>] (kernfs_fop_read) [<c02c5064>] (kernfs_fop_read) from [<c0231cac>] (__vfs_read) [<c0231c5c>] (__vfs_read) from [<c0231ee0>] (vfs_read) [<c0231e34>] (vfs_read) from [<c0232464>] (ksys_read) [<c02323f0>] (ksys_read) from [<c02324fc>] (sys_read) [<c02324e4>] (sys_read) from [<c00091d0>] (__sys_trace_return) The Linux kernel CVE team has assigned CVE-2022-49308 to this issue. Affected and fixed versions =========================== Fixed in 4.14.283 with commit 6e721f3ad0535b24f19a62420f4da95212cf069c Fixed in 4.19.247 with commit cb81ea998c461868d1168411a867d8ffee12f23f Fixed in 5.4.198 with commit d472c78cc82999d07bd09193a6718016ce9cd386 Fixed in 5.10.122 with commit abf3b222614f49f98e606fccdd269161c0d70204 Fixed in 5.15.47 with commit 368e68ad6da4317fc4170e8d92b51c13d1bfe7a7 Fixed in 5.17.15 with commit 35ff1ac55d301efb3f467cf5426faaeb3452994b Fixed in 5.18.4 with commit 033ec4e7e59ae5e1ef1e8c10bc6552926044ed1c Fixed in 5.19 with commit 5dcc2afe716d69f5112ce035cb14f007461ff189 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-2022-49308 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/extcon/extcon.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/6e721f3ad0535b24f19a62420f4da95212cf069c https://git.kernel.org/stable/c/cb81ea998c461868d1168411a867d8ffee12f23f https://git.kernel.org/stable/c/d472c78cc82999d07bd09193a6718016ce9cd386 https://git.kernel.org/stable/c/abf3b222614f49f98e606fccdd269161c0d70204 https://git.kernel.org/stable/c/368e68ad6da4317fc4170e8d92b51c13d1bfe7a7 https://git.kernel.org/stable/c/35ff1ac55d301efb3f467cf5426faaeb3452994b https://git.kernel.org/stable/c/033ec4e7e59ae5e1ef1e8c10bc6552926044ed1c https://git.kernel.org/stable/c/5dcc2afe716d69f5112ce035cb14f007461ff189
Powered by blists - more mailing lists