Vulnerability in Kernel: blk-cgroup_bio_start() should use irq-safe operations on blkg->iostat_cpu

Kernel Updated 02 Oct 2025

Summary

14/11/2021
N/A
No i
Unrated
Not published

GSD-2021-1002106: blk-cgroup: blk_cgroup_bio_start() should use irq-safe operations on blkg->iostat_cpu. Affects Kernel versions >= 2d146aa3aa842d7f5065802556b4f9a2c6e8ef12, < b1a34f86b41fd89441fa0e245b6b23627b0d73d3. No fix is published. 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 Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The Kernel is a fundamental component of the Linux operating system that manages system resources and provides an interface for applications to interact with the hardware. It is responsible for tasks such as process management, memory management, and device drivers. The blk-cgroup module within the Kernel is used to implement block I/O resource management and accounting. It allows for control and monitoring of I/O operations on block devices. However, a vulnerability has been discovered in the blk-cgroup module that can lead to potential security risks.

Vulnerability Detail

The vulnerability in blk-cgroup_bio_start() arises from the use of non-irq-safe operations on the blkg->iostat_cpu variable. This can result in race conditions and data corruption when multiple processes or threads attempt to access and modify the variable simultaneously. An attacker could potentially exploit this vulnerability to gain unauthorized access, escalate privileges, or cause denial of service. The vulnerability was introduced in version v5.13 of the Linux Kernel and has been fixed in version v5.14.15.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

If updating the Kernel is not immediately feasible, a possible workaround is to apply the patch provided in the commit b1a34f86b41fd89441fa0e245b6b23627b0d73d3. The patch modifies the blk-cgroup_bio_start() function to use irq-safe operations on blkg->iostat_cpu. Here is an example of the modified code:

// Original code
void blk_cgroup_bio_start(struct request_queue *q, struct bio *bio)
{
    // Non-irq-safe operations on blkg->iostat_cpu
    ...
}

// Patched code
void blk_cgroup_bio_start(struct request_queue *q, struct bio *bio)
{
    // Modified code using irq-safe operations
    ...
}

Conclusion

The vulnerability in the Kernel's blk-cgroup module can pose significant security risks if left unaddressed. It is crucial to update the Kernel to version v5.14.15 or later, or apply the provided patch, to mitigate these risks. Regularly monitoring for open-source vulnerabilities using tools like Vulert can also help ensure the security of your system.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability can potentially be exploited by attackers to gain unauthorized access, escalate privileges, or cause denial of service. It is important to update the Kernel or apply the patch to mitigate these risks.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and the Vulert tool will analyze it for any open-source vulnerabilities, including this one.

There are no known instances of this vulnerability being exploited in the wild. However, it is important to promptly update the Kernel or apply the patch to prevent any potential exploitation.

Yes, you can apply the patch provided in the commit b1a34f86b41fd89441fa0e245b6b23627b0d73d3 without updating the entire Kernel. However, it is recommended to update the Kernel to the latest stable version to ensure comprehensive security fixes.

For further support on vulnerability remediation and assistance with updating the Kernel or applying the patch, you can contact info@devnack.com. Our team of experts will be happy to assist you.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. 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