Executive Summary
| Informations | |||
|---|---|---|---|
| Name | CVE-2022-48660 | First vendor Publication | 2024-04-28 |
| Vendor | Cve | Last vendor Modification | 2024-11-21 |
Security-Database Scoring CVSS v3
| Cvss vector : CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H | |||
|---|---|---|---|
| Overall CVSS Score | 5.5 | ||
| Base Score | 5.5 | Environmental Score | 5.5 |
| impact SubScore | 3.6 | Temporal Score | 5.5 |
| Exploitabality Sub Score | 1.8 | ||
| Attack Vector | Local | Attack Complexity | Low |
| Privileges Required | Low | User Interaction | None |
| Scope | Unchanged | Confidentiality Impact | None |
| Integrity Impact | None | Availability Impact | High |
| Calculate full CVSS 3.0 Vectors scores | |||
Security-Database Scoring CVSS v2
| Cvss vector : | |||
|---|---|---|---|
| Cvss Base Score | N/A | Attack Range | N/A |
| Cvss Impact Score | N/A | Attack Complexity | N/A |
| Cvss Expoit Score | N/A | Authentication | N/A |
| Calculate full CVSS 2.0 Vectors scores | |||
Detail
| 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. |
Original Source
| Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-48660 |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
| Date | Informations |
|---|---|
| 2025-06-26 02:08:20 |
|
| 2025-06-25 12:21:06 |
|
| 2025-06-24 02:13:01 |
|
| 2025-05-27 13:22:27 |
|
| 2025-05-27 02:08:05 |
|
| 2025-03-29 03:13:17 |
|
| 2025-03-28 13:33:39 |
|
| 2025-03-28 02:55:54 |
|
| 2025-03-19 02:52:34 |
|
| 2025-03-18 03:04:15 |
|
| 2025-03-14 02:53:15 |
|
| 2025-02-22 03:01:51 |
|
| 2025-01-08 02:47:06 |
|
| 2025-01-07 02:46:44 |
|
| 2024-12-25 02:45:32 |
|
| 2024-12-12 02:48:22 |
|
| 2024-11-25 09:25:57 |
|
| 2024-11-21 21:24:06 |
|
| 2024-11-20 02:43:15 |
|
| 2024-11-14 02:43:08 |
|
| 2024-11-09 02:43:46 |
|
| 2024-10-27 21:27:57 |
|
| 2024-10-26 02:41:32 |
|
| 2024-10-25 02:43:18 |
|
| 2024-10-23 02:42:42 |
|
| 2024-10-03 02:38:45 |
|
| 2024-10-02 02:37:09 |
|
| 2024-09-04 02:36:33 |
|
| 2024-08-22 02:34:57 |
|
| 2024-08-02 13:43:15 |
|
| 2024-08-02 01:31:15 |
|
| 2024-04-30 21:27:30 |
|
| 2024-04-29 17:27:26 |
|
| 2024-04-28 17:27:28 |
|
