CVEvulnerability
CVE-2021-47646
7.8 HIGH
Official page ↗
- Status
- Modified
- Published
- 2025-02-26
- Last modified
- 2026-08-11
- Assigner
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- CVSS 3.1 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)
- 7.8 HIGH — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CVSS 3.1 (134c704f-9b21-4f2e-91b3-4a467353bcc0)
- 7.8 HIGH — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weaknesses
- CWE-416
Description
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
Affected configurations
• linux linux kernel (< 4.19.238)
• linux linux kernel (>= 4.20 < 5.4.189)
• linux linux kernel (>= 5.5 < 5.10.110)
• linux linux kernel (>= 5.11 < 5.15.33)
• linux linux kernel (>= 5.16 < 5.16.19)
• linux linux kernel (>= 5.17 < 5.17.2)
Related
Weakness · CWE (1)
- CWE-416 Use After Free weakness
References
- https://git.kernel.org/stable/c/15729ff8143f8135b03988a100a19e66d7cb7ecd Patch
- https://git.kernel.org/stable/c/4083925bd6dc89216d156474a8076feec904e607 Patch
- https://git.kernel.org/stable/c/65d8a737452e88f251fe5d925371de6d606df613 Patch
- https://git.kernel.org/stable/c/abc2129e646af7b43025d90a071f83043f1ae76c Patch