Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2025-21794 | First vendor Publication | 2025-02-27 |
Vendor | Cve | Last vendor Modification | 2025-03-05 |
Security-Database Scoring CVSS v3
Cvss vector : CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H | |||
---|---|---|---|
Overall CVSS Score | 7.1 | ||
Base Score | 7.1 | Environmental Score | 7.1 |
impact SubScore | 5.2 | Temporal Score | 7.1 |
Exploitabality Sub Score | 1.8 | ||
Attack Vector | Local | Attack Complexity | Low |
Privileges Required | Low | User Interaction | None |
Scope | Unchanged | Confidentiality Impact | High |
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: HID: hid-thrustmaster: fix stack-out-of-bounds read in usb_check_int_endpoints() Syzbot[1] has detected a stack-out-of-bounds read of the ep_addr array from hid-thrustmaster driver. This array is passed to usb_check_int_endpoints function from usb.c core driver, which executes a for loop that iterates over the elements of the passed array. Not finding a null element at the end of the array, it tries to read the next, non-existent element, crashing the kernel. To fix this, a 0 element was added at the end of the array to break the for loop. [1] https://syzkaller.appspot.com/bug?extid=9c9179ac46169c56c1ad |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21794 |
CWE : Common Weakness Enumeration
% | Id | Name |
---|---|---|
100 % | CWE-125 | Out-of-bounds Read |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
Date | Informations |
---|---|
2025-06-26 02:41:01 |
|
2025-06-25 12:38:04 |
|
2025-06-24 02:45:27 |
|
2025-05-27 02:52:29 |
|
2025-03-29 03:46:33 |
|
2025-03-28 13:49:03 |
|
2025-03-28 03:24:24 |
|
2025-03-25 16:30:11 |
|
2025-03-25 03:30:12 |
|
2025-03-19 03:18:43 |
|
2025-03-18 03:31:42 |
|
2025-03-14 00:20:59 |
|
2025-03-13 21:20:56 |
|
2025-03-06 14:15:14 |
|
2025-03-06 03:09:45 |
|
2025-03-05 17:20:45 |
|
2025-02-27 09:20:31 |
|