CVE-2022-48660
published 2024-04-28CVE-2022-48660: In the Linux kernel, the following vulnerability has been resolved: gpiolib: cdev: Set lineevent_state::irq after IRQ register successfully When running gpio…
PriorityP419medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.24%
14.6th percentile
In the Linux kernel, the following vulnerability has been resolved:
gpiolib: cdev: Set lineevent_state::irq after IRQ register successfully
When running gpio test on nxp-ls1028 platform with below command
gpiomon --num-events=3 --rising-edge gpiochip1 25
There will be a warning trace as below:
Call trace:
free_irq+0x204/0x360
lineevent_free+0x64/0x70
gpio_ioctl+0x598/0x6a0
__arm64_sys_ioctl+0xb4/0x100
invoke_syscall+0x5c/0x130
......
el0t_64_sync+0x1a0/0x1a4
The reason of this issue is that calling request_threaded_irq()
function failed, and then lineevent_free() is invoked to release
the resource. Since the lineevent_state::irq was already set, so
the subsequent invocation of free_irq() would trigger the above
warning call trace. To fix this issue, set the lineevent_state::irq
after the IRQ register successfully.
Affected
13 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.0.2-1 (bookworm) | linux 6.0.2-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 468242724143a8e732f82f664b1e77432d149618 < 657803b918e097e47d99d1489da83a603c36bcdd | 657803b918e097e47d99d1489da83a603c36bcdd |
| linux | linux | >= 468242724143a8e732f82f664b1e77432d149618 < 97da736cd11ae73bdf2f5e21e24446b8349e0168 | 97da736cd11ae73bdf2f5e21e24446b8349e0168 |
| linux | linux | >= 468242724143a8e732f82f664b1e77432d149618 < b1489043d3b9004dd8d5a0357b08b5f0e6691c43 | b1489043d3b9004dd8d5a0357b08b5f0e6691c43 |
| linux | linux | >= 468242724143a8e732f82f664b1e77432d149618 < 69bef19d6b9700e96285f4b4e28691cda3dcd0d1 | 69bef19d6b9700e96285f4b4e28691cda3dcd0d1 |
| linux | linux_kernel | >= 0 < 5.10.148-1 | 5.10.148-1 |
| linux | linux_kernel | >= 0 < 6.0.2-1 | 6.0.2-1 |
| linux | linux_kernel | >= 0 < 6.0.2-1 | 6.0.2-1 |
| linux | linux_kernel | >= 0 < 6.0.2-1 | 6.0.2-1 |
| linux | linux_kernel | >= 5.11 < 5.15.71 | 5.15.71 |
| linux | linux_kernel | >= 5.16 < 5.19.12 | 5.19.12 |
| linux | linux_kernel | >= 5.9 < 5.10.146 | 5.10.146 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: gpiolib: cdev: Set lineevent_state::irq after IRQ register successfully
vendor_redhat·2024-04-28·CVSS 5.5
CVE-2022-48660 [MEDIUM] CWE-415 kernel: gpiolib: cdev: Set lineevent_state::irq after IRQ register successfully
kernel: gpiolib: cdev: Set lineevent_state::irq after IRQ register successfully
In the Linux kernel, the following vulnerability has been resolved:
gpiolib: cdev: Set lineevent_state::irq after IRQ register successfully
When running gpio test on nxp-ls1028 platform with below command
gpiomon --num-events=3 --rising-edge gpiochip1 25
There will be a warning trace as below:
Call trace:
free_irq+0x204/0x360
lineevent_free+0x64/0x70
gpio_ioctl+0x598/0x6a0
__arm64_sys_ioctl+0xb4/0x100
invoke_syscall+0x5c/0x130
......
el0t_64_sync+0x1a0/0x1a4
The reason of this issue is that calling request_threaded_irq()
function failed, and then lineevent_free() is invoked to release
the resource. Since the lineevent_state::irq was already set, so
the subsequent invocation of free_irq() would trigger the abov
Debian
CVE-2022-48660: linux - In the Linux kernel, the following vulnerability has been resolved: gpiolib: cd...
vendor_debian·2022·CVSS 5.5
CVE-2022-48660 [MEDIUM] CVE-2022-48660: linux - In the Linux kernel, the following vulnerability has been resolved: gpiolib: cd...
In the Linux kernel, the following vulnerability has been resolved: gpiolib: cdev: Set lineevent_state::irq after IRQ register successfully When running gpio test on nxp-ls1028 platform with below command gpiomon --num-events=3 --rising-edge gpiochip1 25 There will be a warning trace as below: Call trace: free_irq+0x204/0x360 lineevent_free+0x64/0x70 gpio_ioctl+0x598/0x6a0 __arm64_sys_ioctl+0xb4/0x100 invoke_syscall+0x5c/0x130 ...... el0t_64_sync+0x1a0/0x1a4 The reason of this issue is that calling request_threaded_irq() function failed, and then lineevent_free() is invoked to release the resource. Since the lineevent_state::irq was already set, so the subsequent invocation of free_irq() would trigger the above warning call trace. To fix this issue, set the lineevent_state::irq after the I
OSV
CVE-2022-48660: In the Linux kernel, the following vulnerability has been resolved: gpiolib: cdev: Set lineevent_state::irq after IRQ register successfully When runni
osv·2024-04-28·CVSS 5.5
CVE-2022-48660 [MEDIUM] CVE-2022-48660: In the Linux kernel, the following vulnerability has been resolved: gpiolib: cdev: Set lineevent_state::irq after IRQ register successfully When runni
In the Linux kernel, the following vulnerability has been resolved: gpiolib: cdev: Set lineevent_state::irq after IRQ register successfully When running gpio test on nxp-ls1028 platform with below command gpiomon --num-events=3 --rising-edge gpiochip1 25 There will be a warning trace as below: Call trace: free_irq+0x204/0x360 lineevent_free+0x64/0x70 gpio_ioctl+0x598/0x6a0 __arm64_sys_ioctl+0xb4/0x100 invoke_syscall+0x5c/0x130 ...... el0t_64_sync+0x1a0/0x1a4 The reason of this issue is that calling request_threaded_irq() function failed, and then lineevent_free() is invoked to release the resource. Since the lineevent_state::irq was already set, so the subsequent invocation of free_irq() would trigger the above warning call trace. To fix this issue, set the lineevent_state::irq after the I
GHSA
GHSA-59cp-mx5q-cw86: In the Linux kernel, the following vulnerability has been resolved:
gpiolib: cdev: Set lineevent_state::irq after IRQ register successfully
When run
ghsa_unreviewed·2024-04-28
CVE-2022-48660 [MEDIUM] GHSA-59cp-mx5q-cw86: In the Linux kernel, the following vulnerability has been resolved:
gpiolib: cdev: Set lineevent_state::irq after IRQ register successfully
When run
In the Linux kernel, the following vulnerability has been resolved:
gpiolib: cdev: Set lineevent_state::irq after IRQ register successfully
When running gpio test on nxp-ls1028 platform with below command
gpiomon --num-events=3 --rising-edge gpiochip1 25
There will be a warning trace as below:
Call trace:
free_irq+0x204/0x360
lineevent_free+0x64/0x70
gpio_ioctl+0x598/0x6a0
__arm64_sys_ioctl+0xb4/0x100
invoke_syscall+0x5c/0x130
......
el0t_64_sync+0x1a0/0x1a4
The reason of this issue is that calling request_threaded_irq()
function failed, and then lineevent_free() is invoked to release
the resource. Since the lineevent_state::irq was already set, so
the subsequent invocation of free_irq() would trigger the above
warning call trace. To fix this issue, set the lineevent_state::irq
after the
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/657803b918e097e47d99d1489da83a603c36bcddhttps://git.kernel.org/stable/c/69bef19d6b9700e96285f4b4e28691cda3dcd0d1https://git.kernel.org/stable/c/97da736cd11ae73bdf2f5e21e24446b8349e0168https://git.kernel.org/stable/c/b1489043d3b9004dd8d5a0357b08b5f0e6691c43https://git.kernel.org/stable/c/657803b918e097e47d99d1489da83a603c36bcddhttps://git.kernel.org/stable/c/69bef19d6b9700e96285f4b4e28691cda3dcd0d1https://git.kernel.org/stable/c/97da736cd11ae73bdf2f5e21e24446b8349e0168https://git.kernel.org/stable/c/b1489043d3b9004dd8d5a0357b08b5f0e6691c43
2024-04-28
Published