Executive Summary
| Informations | |||
|---|---|---|---|
| Name | CVE-2021-47646 | First vendor Publication | 2025-02-26 |
| 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: Revert "Revert "block, bfq: honor already-setup queue merges"" A crash [1] happened to be triggered in conjunction with commit 2d52c58b9c9b ("block, bfq: honor already-setup queue merges"). The latter was then reverted by commit ebc69e897e17 ("Revert "block, bfq: honor already-setup queue merges""). Yet, the reverted commit was not the one introducing the bug. In fact, it actually triggered a UAF introduced by a different commit, and now fixed by commit d29bd41428cf ("block, bfq: reset last_bfqq_created on group change"). So, there is no point in keeping commit 2d52c58b9c9b ("block, bfq: honor already-setup queue merges") out. This commit restores it. [1] https://bugzilla.kernel.org/show_bug.cgi?id=214503 |
Original Source
| Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-47646 |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
| Date | Informations |
|---|---|
| 2025-06-26 01:52:59 |
|
| 2025-06-25 12:17:13 |
|
| 2025-06-24 01:57:27 |
|
| 2025-05-27 01:52:34 |
|
| 2025-03-28 17:21:06 |
|
| 2025-03-28 13:28:35 |
|
| 2025-03-28 02:42:58 |
|
| 2025-03-25 00:21:49 |
|
| 2025-02-27 21:20:35 |
|
| 2025-02-26 17:20:34 |
|
