Double Free of cond_list in selinux Package

Kernel Updated 02 Oct 2025

Summary

18/02/2022
N/A
No i
Unrated
Not published

GSD-2022-1000279: selinux: fix double free of cond_list on error paths. Affects Kernel versions < 70caa32e6d81f45f0702070c0e4dfe945e92fbd7. 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 selinux package is a security module for the Linux kernel that provides access control security policies. It is designed to enforce mandatory access control policies, restricting the actions that processes can perform on the system. The package uses a set of security rules and labels to determine the permissions granted to processes and files. However, a vulnerability has been discovered in the selinux package that could lead to a double free of the cond_list object, potentially resulting in a system crash or arbitrary code execution.

Vulnerability Detail

The vulnerability in the selinux package arises from a double free of the cond_list object on error paths. This can occur when certain error conditions are encountered during the execution of selinux functions. A double free vulnerability allows an attacker to free the same memory location twice, which can lead to memory corruption and potentially enable them to execute arbitrary code or crash the system. The impact of this vulnerability depends on the context in which the double free occurs and the attacker's ability to control the freed memory. It is important to note that the actual impact and attack plausibility have not yet been proven.

How To Fix

No fixed version is published for this vulnerability.

The vulnerability has been fixed in the Linux Kernel version v5.15.22 by commit 70caa32e6d81f45f0702070c0e4dfe945e92fbd7. To fix the vulnerability, users should update their Linux Kernel to the latest version available. This can be done by downloading the updated kernel source code from the official Linux Kernel repository (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/) and compiling it according to the provided instructions.

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

Workaround

No workaround has been provided for this vulnerability.

Conclusion

The selinux package is vulnerable to a double free of the cond_list object, which can potentially lead to system crashes or arbitrary code execution. It is recommended to update the Linux Kernel to the latest version to fix this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The selinux package is a security module for the Linux kernel that provides access control security policies.

A double free vulnerability occurs when the same memory location is freed twice, leading to memory corruption and potential security issues.

The potential consequences of this vulnerability include system crashes and arbitrary code execution.

No, the actual impact and attack plausibility of this vulnerability have not yet been proven.

To fix this vulnerability, users should update their Linux Kernel to the latest version available.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

How To Fix

No fixed version is published for this vulnerability.

The vulnerability has been fixed in the Linux Kernel version v5.15.22 by commit 70caa32e6d81f45f0702070c0e4dfe945e92fbd7. To fix the vulnerability, users should update their Linux Kernel to the latest version available. This can be done by downloading the updated kernel source code from the official Linux Kernel repository (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/) and compiling it according to the provided instructions.

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.