CVE-2022-48660 Affecting kernel-zfcpdump-modules-internal package, versions *
Threat Intelligence
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk ID SNYK-RHEL9-KERNELZFCPDUMPMODULESINTERNAL-6734553
- published 30 Apr 2024
- disclosed 28 Apr 2024
Introduced: 28 Apr 2024
CVE-2022-48660 Open this link in a new tabHow to fix?
There is no fixed version for RHEL:9 kernel-zfcpdump-modules-internal.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kernel-zfcpdump-modules-internal package and not the kernel-zfcpdump-modules-internal package as distributed by RHEL.
See How to fix? for RHEL:9 relevant fixed versions and status.
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.
References
- https://access.redhat.com/security/cve/CVE-2022-48660
- https://git.kernel.org/stable/c/657803b918e097e47d99d1489da83a603c36bcdd
- https://git.kernel.org/stable/c/69bef19d6b9700e96285f4b4e28691cda3dcd0d1
- https://git.kernel.org/stable/c/97da736cd11ae73bdf2f5e21e24446b8349e0168
- https://git.kernel.org/stable/c/b1489043d3b9004dd8d5a0357b08b5f0e6691c43