CVE-2025-21631: block, bfq: fix waker_bfqq UAF after bfq_split_bfqq()
block, bfq: fix wakerbfqq UAF after bfqsplitbfqq()
Other sources
This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.
— Launchpad
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.27-1 - Upgrade
Upgrade
debian/linux-6.1to a version that resolves this vulnerability.Fixed in 6.1.129-1~deb11u1
Event History
Frequently Asked Questions
What is the severity of CVE-2025-21631?
CVE-2025-21631 has been classified as a critical vulnerability due to potential exploitability impacts on the kernel.
How do I fix CVE-2025-21631?
To mitigate CVE-2025-21631, it is recommended to upgrade the Linux kernel to a patched version above 6.6.72.
What systems are affected by CVE-2025-21631?
CVE-2025-21631 affects multiple versions of the Linux kernel including versions between 5.15.168 and 6.6.54.
What type of vulnerability is CVE-2025-21631?
CVE-2025-21631 is a use-after-free vulnerability found in the Linux kernel's block BFQ I/O scheduler.
What impact does CVE-2025-21631 have on system security?
CVE-2025-21631 may allow an attacker to execute arbitrary code, leading to unauthorized activities within the affected system.