mirror of
https://github.com/fkie-cad/nvd-json-data-feeds.git
synced 2025-06-01 03:01:36 +00:00
32 lines
1.8 KiB
JSON
32 lines
1.8 KiB
JSON
![]() |
{
|
||
|
"id": "CVE-2022-48660",
|
||
|
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||
|
"published": "2024-04-28T13:15:07.853",
|
||
|
"lastModified": "2024-04-28T13:15:07.853",
|
||
|
"vulnStatus": "Received",
|
||
|
"descriptions": [
|
||
|
{
|
||
|
"lang": "en",
|
||
|
"value": "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."
|
||
|
}
|
||
|
],
|
||
|
"metrics": {},
|
||
|
"references": [
|
||
|
{
|
||
|
"url": "https://git.kernel.org/stable/c/657803b918e097e47d99d1489da83a603c36bcdd",
|
||
|
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||
|
},
|
||
|
{
|
||
|
"url": "https://git.kernel.org/stable/c/69bef19d6b9700e96285f4b4e28691cda3dcd0d1",
|
||
|
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||
|
},
|
||
|
{
|
||
|
"url": "https://git.kernel.org/stable/c/97da736cd11ae73bdf2f5e21e24446b8349e0168",
|
||
|
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||
|
},
|
||
|
{
|
||
|
"url": "https://git.kernel.org/stable/c/b1489043d3b9004dd8d5a0357b08b5f0e6691c43",
|
||
|
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||
|
}
|
||
|
]
|
||
|
}
|