Double Free of cond_list in selinux

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1000649: selinux: fix double free of cond_list on error paths. Affects Kernel versions < 7ed9cbf7ac0d4ed86b356e1b944304ae9ee450d4. 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 selinux package is a security module for the Linux kernel that provides access control security policies. It enforces mandatory access control policies that restrict user and process access to various system resources. The vulnerability in selinux involves a double free of the cond_list data structure on error paths.

Vulnerability Detail

The vulnerability occurs when certain error conditions are encountered during the execution of selinux. These error paths can lead to a double free of the cond_list data structure, which can result in memory corruption and potential exploitation by an attacker. The impact and attack plausibility of this vulnerability have not been proven yet. It is important to note that this vulnerability has been fixed in the Linux Kernel version v5.16.8 by commit 7ed9cbf7ac0d4ed86b356e1b944304ae9ee450d4.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.16.8 or later. This can be done by pulling the latest changes from the official Linux Kernel repository and rebuilding the kernel. Alternatively, users can wait for their Linux distribution to release an updated kernel package that includes the fix.

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

Workaround

There is no specific workaround mentioned for this vulnerability. The recommended approach is to apply the fix by updating the Linux Kernel.

Conclusion

The double free vulnerability in selinux has been addressed in the Linux Kernel version v5.16.8. It is crucial to update the kernel to ensure the security and stability of the system. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

Selinux is a security module for the Linux kernel that provides access control security policies.

A double free vulnerability occurs when a program attempts to free a memory block that has already been freed, potentially leading to memory corruption and exploitation.

The impact of this vulnerability is not yet proven. However, if successfully exploited, it could lead to memory corruption and potential security breaches.

To fix this vulnerability, update the Linux Kernel to version v5.16.8 or later.

No specific workaround is mentioned for this vulnerability. It is recommended to apply the fix by updating the Linux Kernel.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.16.8 or later. This can be done by pulling the latest changes from the official Linux Kernel repository and rebuilding the kernel. Alternatively, users can wait for their Linux distribution to release an updated kernel package that includes the fix.

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.