Executive Summary
| Informations | |||
|---|---|---|---|
| Name | CVE-2024-39472 | First vendor Publication | 2024-07-05 |
| 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: xfs: fix log recovery buffer allocation for the legacy h_size fixup Commit a70f9fe52daa ("xfs: detect and handle invalid iclog size set by mkfs") added a fixup for incorrect h_size values used for the initial umount record in old xfsprogs versions. Later commit 0c771b99d6c9 ("xfs: clean up calculation of LR header blocks") cleaned up the log reover buffer calculation, but stoped using the fixed up h_size value to size the log recovery buffer, which can lead to an out of bounds access when the incorrect h_size does not come from the old mkfs tool, but a fuzzer. Fix this by open coding xlog_logrec_hblks and taking the fixed h_size into account for this calculation. |
Original Source
| Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-39472 |
CWE : Common Weakness Enumeration
| % | Id | Name |
|---|---|---|
| 100 % | CWE-770 | Allocation of Resources Without Limits or Throttling |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
| Date | Informations |
|---|---|
| 2025-06-26 02:32:30 |
|
| 2025-06-25 12:31:49 |
|
| 2025-06-24 02:37:09 |
|
| 2025-05-27 02:41:36 |
|
| 2025-03-29 03:37:52 |
|
| 2025-03-28 13:43:13 |
|
| 2025-03-28 03:16:30 |
|
| 2025-03-19 03:11:54 |
|
| 2025-03-18 03:24:47 |
|
| 2025-03-14 03:12:09 |
|
| 2025-03-06 14:08:33 |
|
| 2025-02-22 03:22:03 |
|
| 2025-01-08 03:03:24 |
|
| 2025-01-07 03:02:57 |
|
| 2024-12-25 03:01:35 |
|
| 2024-12-12 03:04:33 |
|
| 2024-11-25 09:24:17 |
|
| 2024-11-22 21:23:20 |
|
| 2024-11-21 21:22:56 |
|
| 2024-11-20 02:58:12 |
|
| 2024-11-14 02:58:30 |
|
| 2024-11-09 02:58:31 |
|
| 2024-10-26 02:55:55 |
|
| 2024-10-25 02:57:50 |
|
| 2024-10-23 02:57:02 |
|
| 2024-10-03 02:52:23 |
|
| 2024-10-02 02:50:47 |
|
| 2024-09-15 02:48:36 |
|
| 2024-09-12 02:48:09 |
|
| 2024-09-07 02:47:10 |
|
| 2024-09-06 02:46:21 |
|
| 2024-09-04 02:49:35 |
|
| 2024-08-22 00:28:01 |
|
| 2024-08-19 13:27:38 |
|
| 2024-08-14 21:27:39 |
|
| 2024-08-02 13:56:34 |
|
| 2024-08-02 01:35:47 |
|
| 2024-07-08 21:27:35 |
|
| 2024-07-05 17:27:24 |
|
| 2024-07-05 13:27:27 |
|
