Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2024-39477 | First vendor Publication | 2024-07-05 |
Vendor | Cve | Last vendor Modification | 2024-07-08 |
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: mm/hugetlb: do not call vma_add_reservation upon ENOMEM sysbot reported a splat [1] on __unmap_hugepage_range(). This is because vma_needs_reservation() can return -ENOMEM if allocate_file_region_entries() fails to allocate the file_region struct for the reservation. Check for that and do not call vma_add_reservation() if that is the case, otherwise region_abort() and region_del() will see that we do not have any file_regions. If we detect that vma_needs_reservation() returned -ENOMEM, we clear the hugetlb_restore_reserve flag as if this reservation was still consumed, so free_huge_folio() will not increment the resv count. [1] https://lore.kernel.org/linux-mm/0000000000004096100617c58d54@google.com/T/#ma5983bc1ab18a54910da83416b3f89f3c7ee43aa |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-39477 |
CWE : Common Weakness Enumeration
% | Id | Name |
---|---|---|
100 % | CWE-770 | Allocation of Resources Without Limits or Throttling |
CPE : Common Platform Enumeration
Sources (Detail)
Source | Url |
---|
Alert History
Date | Informations |
---|---|
2024-11-21 21:22:56 |
|
2024-11-20 02:58:12 |
|
2024-11-14 02:58:31 |
|
2024-11-09 02:58:31 |
|
2024-10-26 02:55:56 |
|
2024-10-25 02:57:50 |
|
2024-10-23 02:57:03 |
|
2024-10-03 02:52:23 |
|
2024-10-02 02:50:47 |
|
2024-09-15 02:48:37 |
|
2024-09-12 02:48:10 |
|
2024-09-07 02:47:10 |
|
2024-09-06 02:46:22 |
|
2024-09-04 02:49:35 |
|
2024-08-22 02:47:35 |
|
2024-08-02 13:56:34 |
|
2024-08-02 01:35:48 |
|
2024-07-08 21:27:29 |
|
2024-07-05 17:27:24 |
|
2024-07-05 13:27:27 |
|