Double Free of io_acct_set Bioset in Linux Kernel

Kernel Updated 02 Oct 2025

Summary

28/06/2022
N/A
No i
Unrated
Not published

GSD-2022-1003294: md: fix double free of io_acct_set bioset. Affects Kernel versions >= 00e3d58f50a875343124bcf5a9637520a492b0d1, < 36a2fc44c574a59ee3b5e2cb327182f227b2b07e. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Linux Kernel is a widely used open-source operating system kernel that serves as the foundation for various Linux distributions. It provides essential functionality for managing system resources, including memory, processes, and device drivers. The io_acct_set bioset is a data structure used by the kernel's md (multiple devices) subsystem to track I/O accounting information for software RAID devices. This subsystem allows multiple physical devices to be combined into a single logical device, providing redundancy and improved performance. The vulnerability in question involves a double free of the io_acct_set bioset, which can lead to memory corruption and potentially be exploited by attackers to gain unauthorized access or cause a denial-of-service (DoS) condition.

Vulnerability Detail

The vulnerability arises from a double free issue in the md subsystem of the Linux Kernel. A double free occurs when a program attempts to free a memory block that has already been freed. In this case, the io_acct_set bioset is freed twice, which can result in memory corruption and subsequent undefined behavior. An attacker may be able to exploit this vulnerability to execute arbitrary code, escalate privileges, or crash the system. The vulnerability was introduced in Linux Kernel version v5.15.17 and is fixed in version v5.15.46.

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

As a workaround, users can avoid the vulnerability by disabling the md subsystem or removing any software RAID configurations from their system. However, this may not be feasible for systems that rely on software RAID for data redundancy and performance. It is strongly recommended to apply the official fix by updating the Linux Kernel.

Conclusion

The double free vulnerability in the io_acct_set bioset of the Linux Kernel's md subsystem can lead to memory corruption and potential security risks. It is crucial to update the Linux Kernel to version v5.15.46 or later to address this vulnerability. Failure to do so may expose systems to exploitation by attackers. For further assistance or support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability can potentially be exploited by attackers to execute arbitrary code, escalate privileges, or cause a denial-of-service (DoS) condition.

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 Playground will analyze it for any known vulnerabilities.

At the time of this report, there is no known public exploit for this vulnerability. However, it is important to apply the fix as soon as possible to mitigate any potential risks.

The vulnerability itself does not provide remote code execution capabilities. However, if an attacker already has access to the system, they may be able to exploit the vulnerability to escalate privileges or cause a DoS condition.

If updating the kernel is not immediately possible, you can mitigate the risk by implementing strict access controls, such as limiting privileged access to the affected system and monitoring for any suspicious activity.

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