CVE-2024-49854
Linux Kernel BlockBFQ Uninitialized Function Pointer
Description
In the Linux kernel, the following vulnerability has been resolved: block, bfq: fix uaf for accessing waker_bfqq after splitting After commit 42c306ed7233 ("block, bfq: don't break merge chain in bfq_split_bfqq()"), if the current procress is the last holder of bfqq, the bfqq can be freed after bfq_split_bfqq(). Hence recored the bfqq and then access bfqq->waker_bfqq may trigger UAF. What's more, the waker_bfqq may in the merge chain of bfqq, hence just recored waker_bfqq is still not safe. Fix the problem by adding a helper bfq_waker_bfqq() to check if bfqq->waker_bfqq is in the merge chain, and current procress is the only holder.
INFO
Published Date :
Oct. 21, 2024, 1:15 p.m.
Last Modified :
Oct. 23, 2024, 4:29 p.m.
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Remotely Exploitable :
No
Impact Score :
5.9
Exploitability Score :
1.8
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2024-49854.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2024-49854 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2024-49854 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Oct. 23, 2024
Action Type Old Value New Value Added CVSS V3.1 NIST AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Changed Reference Type https://git.kernel.org/stable/c/0780451f03bf518bc032a7c584de8f92e2d39d7f No Types Assigned https://git.kernel.org/stable/c/0780451f03bf518bc032a7c584de8f92e2d39d7f Patch Changed Reference Type https://git.kernel.org/stable/c/0b8bda0ff17156cd3f60944527c9d8c9f99f1583 No Types Assigned https://git.kernel.org/stable/c/0b8bda0ff17156cd3f60944527c9d8c9f99f1583 Patch Changed Reference Type https://git.kernel.org/stable/c/1ba0403ac6447f2d63914fb760c44a3b19c44eaf No Types Assigned https://git.kernel.org/stable/c/1ba0403ac6447f2d63914fb760c44a3b19c44eaf Patch Changed Reference Type https://git.kernel.org/stable/c/63a07379fdb6c72450cb05294461c6016b8b7726 No Types Assigned https://git.kernel.org/stable/c/63a07379fdb6c72450cb05294461c6016b8b7726 Patch Changed Reference Type https://git.kernel.org/stable/c/cae58d19121a70329cf971359e2518c93fec04fe No Types Assigned https://git.kernel.org/stable/c/cae58d19121a70329cf971359e2518c93fec04fe Patch Changed Reference Type https://git.kernel.org/stable/c/de0456460f2abf921e356ed2bd8da87a376680bd No Types Assigned https://git.kernel.org/stable/c/de0456460f2abf921e356ed2bd8da87a376680bd Patch Added CWE NIST CWE-416 Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.10.227 up to (excluding) 5.15.168 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.16 up to (excluding) 6.1.113 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.6.54 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.10.13 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.11 up to (excluding) 6.11.2 -
CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Oct. 21, 2024
Action Type Old Value New Value Added Description In the Linux kernel, the following vulnerability has been resolved: block, bfq: fix uaf for accessing waker_bfqq after splitting After commit 42c306ed7233 ("block, bfq: don't break merge chain in bfq_split_bfqq()"), if the current procress is the last holder of bfqq, the bfqq can be freed after bfq_split_bfqq(). Hence recored the bfqq and then access bfqq->waker_bfqq may trigger UAF. What's more, the waker_bfqq may in the merge chain of bfqq, hence just recored waker_bfqq is still not safe. Fix the problem by adding a helper bfq_waker_bfqq() to check if bfqq->waker_bfqq is in the merge chain, and current procress is the only holder. Added Reference kernel.org https://git.kernel.org/stable/c/63a07379fdb6c72450cb05294461c6016b8b7726 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/de0456460f2abf921e356ed2bd8da87a376680bd [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/0780451f03bf518bc032a7c584de8f92e2d39d7f [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/0b8bda0ff17156cd3f60944527c9d8c9f99f1583 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/cae58d19121a70329cf971359e2518c93fec04fe [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/1ba0403ac6447f2d63914fb760c44a3b19c44eaf [No types assigned]
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2024-49854 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2024-49854
weaknesses.