First published: Mon Oct 21 2024(Updated: )
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.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Kernel | >=5.10.227<5.15.168 | |
Linux Kernel | >=5.16<6.1.113 | |
Linux Kernel | >=6.2<6.6.54 | |
Linux Kernel | >=6.7<6.10.13 | |
Linux Kernel | >=6.11<6.11.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-49854 is classified as a security vulnerability in the Linux kernel due to a use-after-free error.
To resolve CVE-2024-49854, update the Linux kernel to a patched version that addresses this vulnerability.
CVE-2024-49854 affects Linux kernel versions between 5.10.227 and 5.15.168, 5.16 and 6.1.113, 6.2 and 6.6.54, 6.7 and 6.10.13, and 6.11 and 6.11.2.
The impact of CVE-2024-49854 includes potential system instability and security risks associated with the use-after-free condition.
CVE-2024-49854 can potentially be exploited by local attackers to escalate privileges on affected Linux systems.