Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2024-44963 | First vendor Publication | 2024-09-04 |
Vendor | Cve | Last vendor Modification | 2024-12-09 |
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: btrfs: do not BUG_ON() when freeing tree block after error When freeing a tree block, at btrfs_free_tree_block(), if we fail to create a delayed reference we don't deal with the error and just do a BUG_ON(). The error most likely to happen is -ENOMEM, and we have a comment mentioning that only -ENOMEM can happen, but that is not true, because in case qgroups are enabled any error returned from btrfs_qgroup_trace_extent_post() (can be -EUCLEAN or anything returned from btrfs_search_slot() for example) can be propagated back to btrfs_free_tree_block(). So stop doing a BUG_ON() and return the error to the callers and make them abort the transaction to prevent leaking space. Syzbot was triggering this, likely due to memory allocation failure injection. |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-44963 |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
Date | Informations |
---|---|
2025-03-29 03:39:58 |
|
2025-03-28 13:44:30 |
|
2025-03-28 03:18:09 |
|
2025-03-19 03:13:31 |
|
2025-03-18 03:26:27 |
|
2025-03-14 03:13:44 |
|
2025-03-06 14:10:16 |
|
2025-02-22 03:23:49 |
|
2025-01-08 03:04:52 |
|
2025-01-07 03:04:25 |
|
2024-12-25 03:03:03 |
|
2024-12-12 00:21:01 |
|
2024-12-09 17:20:35 |
|
2024-11-23 03:03:00 |
|
2024-11-22 03:01:11 |
|
2024-11-20 02:59:31 |
|
2024-11-14 02:59:49 |
|
2024-11-09 02:59:49 |
|
2024-10-26 02:57:12 |
|
2024-10-25 02:59:05 |
|
2024-10-23 02:58:17 |
|
2024-10-04 21:28:03 |
|
2024-09-05 17:27:25 |
|
2024-09-05 00:27:26 |
|