Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2024-47746 | First vendor Publication | 2024-10-21 |
Vendor | Cve | Last vendor Modification | 2024-10-22 |
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: fuse: use exclusive lock when FUSE_I_CACHE_IO_MODE is set This may be a typo. The comment has said shared locks are not allowed when this bit is set. If using shared lock, the wait in `fuse_file_cached_io_open` may be forever. |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47746 |
CWE : Common Weakness Enumeration
% | Id | Name |
---|---|---|
100 % | CWE-667 | Insufficient Locking |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
Date | Informations |
---|---|
2024-11-23 03:03:56 |
|
2024-11-22 03:02:05 |
|
2024-11-20 03:00:23 |
|
2024-11-14 03:00:40 |
|
2024-11-09 03:00:40 |
|
2024-10-26 00:28:36 |
|
2024-10-25 21:29:30 |
|
2024-10-25 00:28:35 |
|
2024-10-24 21:27:52 |
|
2024-10-24 03:04:19 |
|
2024-10-23 00:27:33 |
|
2024-10-22 21:27:46 |
|
2024-10-21 21:27:31 |
|
2024-10-21 17:27:34 |
|