{"schema_version":"1.9.0","id":"CVE-2022-48660","published":"2024-04-28T13:01:22.239Z","modified":"2026-08-12T03:51:09.090079121Z","related":["SUSE-SU-2024:1641-1","SUSE-SU-2024:1644-1","SUSE-SU-2024:1647-1","SUSE-SU-2024:1659-1","SUSE-SU-2024:1663-1"],"summary":"gpiolib: cdev: Set lineevent_state::irq after IRQ register successfully","details":"In the Linux kernel, the following vulnerability has been resolved:\n\ngpiolib: cdev: Set lineevent_state::irq after IRQ register successfully\n\nWhen running gpio test on nxp-ls1028 platform with below command\ngpiomon --num-events=3 --rising-edge gpiochip1 25\nThere will be a warning trace as below:\nCall trace:\nfree_irq+0x204/0x360\nlineevent_free+0x64/0x70\ngpio_ioctl+0x598/0x6a0\n__arm64_sys_ioctl+0xb4/0x100\ninvoke_syscall+0x5c/0x130\n......\nel0t_64_sync+0x1a0/0x1a4\nThe reason of this issue is that calling request_threaded_irq()\nfunction failed, and then lineevent_free() is invoked to release\nthe resource. Since the lineevent_state::irq was already set, so\nthe subsequent invocation of free_irq() would trigger the above\nwarning call trace. To fix this issue, set the lineevent_state::irq\nafter the IRQ register successfully.","affected":[{"ranges":[{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"468242724143a8e732f82f664b1e77432d149618"},{"fixed":"657803b918e097e47d99d1489da83a603c36bcdd"},{"fixed":"97da736cd11ae73bdf2f5e21e24446b8349e0168"},{"fixed":"b1489043d3b9004dd8d5a0357b08b5f0e6691c43"},{"fixed":"69bef19d6b9700e96285f4b4e28691cda3dcd0d1"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-48660.json"}},{"package":{"name":"Kernel","ecosystem":"Linux"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"5.9.0"},{"fixed":"5.10.146"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.11.0"},{"fixed":"5.15.71"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.16.0"},{"fixed":"5.19.12"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-48660.json"}}],"references":[{"type":"WEB","url":"https://git.kernel.org/stable/c/657803b918e097e47d99d1489da83a603c36bcdd"},{"type":"WEB","url":"https://git.kernel.org/stable/c/69bef19d6b9700e96285f4b4e28691cda3dcd0d1"},{"type":"WEB","url":"https://git.kernel.org/stable/c/97da736cd11ae73bdf2f5e21e24446b8349e0168"},{"type":"WEB","url":"https://git.kernel.org/stable/c/b1489043d3b9004dd8d5a0357b08b5f0e6691c43"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/48xxx/CVE-2022-48660.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48660"},{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"}],"database_specific":{"cna_assigner":"Linux","osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/48xxx/CVE-2022-48660.json"},"severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"}]}