Executive Summary
| Informations | |||
|---|---|---|---|
| Name | CVE-2025-21661 | First vendor Publication | 2025-01-21 |
| Vendor | Cve | Last vendor Modification | 2025-02-28 |
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: gpio: virtuser: fix missing lookup table cleanups When a virtuser device is created via configfs and the probe fails due to an incorrect lookup table, the table is not removed. This prevents subsequent probe attempts from succeeding, even if the issue is corrected, unless the device is released. Additionally, cleanup is also needed in the less likely case of platform_device_register_full() failure. Besides, a consistent memory leak in lookup_table->dev_id was spotted using kmemleak by toggling the live state between 0 and 1 with a correct lookup table. Introduce gpio_virtuser_remove_lookup_table() as the counterpart to the existing gpio_virtuser_make_lookup_table() and call it from all necessary points to ensure proper cleanup. |
Original Source
| Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21661 |
CPE : Common Platform Enumeration
Sources (Detail)
| Source | Url |
|---|
Alert History
| Date | Informations |
|---|---|
| 2025-06-26 02:40:47 |
|
| 2025-06-25 12:37:50 |
|
| 2025-06-24 02:45:15 |
|
| 2025-05-27 02:52:14 |
|
| 2025-03-29 03:46:21 |
|
| 2025-03-28 13:48:49 |
|
| 2025-03-28 03:24:06 |
|
| 2025-03-25 03:30:00 |
|
| 2025-03-19 03:18:36 |
|
| 2025-03-18 03:31:34 |
|
| 2025-03-14 03:18:36 |
|
| 2025-03-06 14:15:08 |
|
| 2025-03-06 03:09:29 |
|
| 2025-03-01 00:45:43 |
|
| 2025-01-21 17:20:28 |
|
