Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2025-21753 | First vendor Publication | 2025-02-27 |
Vendor | Cve | Last vendor Modification | 2025-03-24 |
Security-Database Scoring CVSS v3
Cvss vector : N/A | |||
---|---|---|---|
Overall CVSS Score | NA | ||
Base Score | NA | Environmental Score | NA |
impact SubScore | NA | Temporal Score | NA |
Exploitabality Sub Score | NA | ||
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: fix use-after-free when attempting to join an aborted transaction When we are trying to join the current transaction and if it's aborted, we read its 'aborted' field after unlocking fs_info->trans_lock and without holding any extra reference count on it. This means that a concurrent task that is aborting the transaction may free the transaction before we read its 'aborted' field, leading to a use-after-free. Fix this by reading the 'aborted' field while holding fs_info->trans_lock since any freeing task must first acquire that lock and set fs_info->running_transaction to NULL before freeing the transaction. This was reported by syzbot and Dmitry with the following stack traces from KASAN: ================================================================== CPU: 0 UID: 0 PID: 1128 Comm: kworker/u4:9 Not tainted 6.13.0-rc7-syzkaller-00019-gc45323b7560e #0 Allocated by task 5315: Freed by task 5336: |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21753 |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
Date | Informations |
---|---|
2025-06-26 02:40:56 |
|
2025-06-25 12:37:59 |
|
2025-06-24 02:45:23 |
|
2025-05-27 02:52:25 |
|
2025-03-28 17:20:54 |
|
2025-03-28 13:48:59 |
|
2025-03-28 03:24:18 |
|
2025-03-25 03:30:34 |
|
2025-03-25 00:20:42 |
|
2025-03-13 17:20:55 |
|
2025-02-28 03:46:08 |
|
2025-02-28 03:46:04 |
|
2025-02-28 00:20:33 |
|
2025-02-27 09:20:31 |
|