CVEvulnerability
CVE-2022-48660
5.5 MEDIUM
Official page ↗
- Status
- Modified
- Published
- 2024-04-28
- Last modified
- 2026-06-17
- Assigner
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- CVSS 3.1 ([email protected])
- 5.5 MEDIUM — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- CVSS 3.1 (134c704f-9b21-4f2e-91b3-4a467353bcc0)
- 5.5 MEDIUM — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Description
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 configurations
• linux linux kernel (>= 5.9 < 5.10.146)
• linux linux kernel (>= 5.11 < 5.15.71)
• linux linux kernel (>= 5.16 < 5.19.12)
References
- https://git.kernel.org/stable/c/657803b918e097e47d99d1489da83a603c36bcdd Patch
- https://git.kernel.org/stable/c/69bef19d6b9700e96285f4b4e28691cda3dcd0d1 Patch
- https://git.kernel.org/stable/c/97da736cd11ae73bdf2f5e21e24446b8349e0168 Patch
- https://git.kernel.org/stable/c/b1489043d3b9004dd8d5a0357b08b5f0e6691c43 Patch
- https://git.kernel.org/stable/c/657803b918e097e47d99d1489da83a603c36bcdd Patch
- https://git.kernel.org/stable/c/69bef19d6b9700e96285f4b4e28691cda3dcd0d1 Patch
- https://git.kernel.org/stable/c/97da736cd11ae73bdf2f5e21e24446b8349e0168 Patch
- https://git.kernel.org/stable/c/b1489043d3b9004dd8d5a0357b08b5f0e6691c43 Patch