Critical Use-After-Free Vulnerability in Linux Kernel BFQ I/O Scheduler

linux Updated 02 Oct 2025

Summary

19/01/2025
N/A
Yes i
High
7.8

CVE-2025-21631: In the Linux kernel, the following vulnerability has been resolved: block, bfq: fix waker_bfqq UAF after bfq_split_bfqq() Our syzkaller report a following UAF for v6.6: BUG: KASAN: slab-use-after-free in bfq_init_rq+0x17... Affects linux versions < 6.1.128-1. Fixed in 6.1.128-1. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The Linux kernel is the core component of many operating systems, providing essential services for hardware and software interactions. It supports various file systems, device drivers, and system calls, making it a critical part of system performance and stability. The BFQ (Budget Fair Queueing) I/O scheduler is designed to optimize disk I/O operations, ensuring fair allocation of resources among processes. However, a recent vulnerability has been identified in the BFQ scheduler that could lead to severe system instability.

Vulnerability Detail

The vulnerability, identified as CVE-2025-21631, is a use-after-free (UAF) issue in the BFQ I/O scheduler of the Linux kernel. It arises when the system attempts to access memory that has already been freed, potentially leading to arbitrary code execution or system crashes. The vulnerability was reported through syzkaller, a tool for finding bugs in the kernel, and it affects versions of the Linux kernel up to 6.6. The specific error occurs in the bfq_init_rq function, where a freed memory address is accessed, resulting in a KASAN (Kernel Address Sanitizer) report of slab-use-after-free.

How To Fix

Minimum fixed version

6.1.128-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade linux

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

Currently, there are no specific workarounds available for this vulnerability. The best course of action is to apply the patch as soon as it is available.

Conclusion

CVE-2025-21631 is a critical vulnerability in the Linux kernel's BFQ I/O scheduler that poses significant risks to system stability and security. Users are strongly encouraged to update their systems to the latest patched version to mitigate these risks. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for linux →

Share this vulnerability

FAQ

CVE-2025-21631 is a use-after-free vulnerability in the BFQ I/O scheduler of the Linux kernel that can lead to system instability or arbitrary code execution.

You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected by this vulnerability.

Exploitation of this vulnerability could lead to system crashes, data corruption, or unauthorized access to system resources.

Yes, a patch is available in the latest versions of the Linux kernel. Users are advised to update their systems to the patched version.

While there are no specific workarounds, it is crucial to monitor your system for any unusual behavior and plan for an update as soon as possible.

Related vulnerabilities

Recent vulnerabilities recorded for linux.

How To Fix

Minimum fixed version

6.1.128-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade linux

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback