CVE-2024-49854
Severity CVSS v4.0:
Pending analysis
Type:
CWE-416
Use After Free
Publication date:
21/10/2024
Last modified:
03/11/2025
Description
In the Linux kernel, the following vulnerability has been resolved:<br />
<br />
block, bfq: fix uaf for accessing waker_bfqq after splitting<br />
<br />
After commit 42c306ed7233 ("block, bfq: don&#39;t break merge chain in<br />
bfq_split_bfqq()"), if the current procress is the last holder of bfqq,<br />
the bfqq can be freed after bfq_split_bfqq(). Hence recored the bfqq and<br />
then access bfqq->waker_bfqq may trigger UAF. What&#39;s more, the waker_bfqq<br />
may in the merge chain of bfqq, hence just recored waker_bfqq is still<br />
not safe.<br />
<br />
Fix the problem by adding a helper bfq_waker_bfqq() to check if<br />
bfqq->waker_bfqq is in the merge chain, and current procress is the only<br />
holder.
Impact
Base Score 3.x
7.80
Severity 3.x
HIGH
Vulnerable products and versions
| CPE | From | Up to |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | 5.10.227 (including) | 5.15.168 (excluding) |
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | 5.16 (including) | 6.1.113 (excluding) |
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | 6.2 (including) | 6.6.54 (excluding) |
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | 6.7 (including) | 6.10.13 (excluding) |
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | 6.11 (including) | 6.11.2 (excluding) |
To consult the complete list of CPE names with products and versions, see this page
References to Advisories, Solutions, and Tools
- https://git.kernel.org/stable/c/0780451f03bf518bc032a7c584de8f92e2d39d7f
- https://git.kernel.org/stable/c/0b8bda0ff17156cd3f60944527c9d8c9f99f1583
- https://git.kernel.org/stable/c/1ba0403ac6447f2d63914fb760c44a3b19c44eaf
- https://git.kernel.org/stable/c/63a07379fdb6c72450cb05294461c6016b8b7726
- https://git.kernel.org/stable/c/cae58d19121a70329cf971359e2518c93fec04fe
- https://git.kernel.org/stable/c/de0456460f2abf921e356ed2bd8da87a376680bd
- https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html



