Vulnerability in Kernel: mm: memcg: synchronize objcg lists with a dedicated spinlock

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1000530: mm: memcg: synchronize objcg lists with a dedicated spinlock. Affects Kernel versions >= bf4f059954dcb221384b2f784677e19a13cd4bdb, < babfa07e9594373e10b9c01ada6278d0248665e1. 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 critical component of the Linux operating system that manages system resources and facilitates communication between hardware and software. It provides essential functionality for the proper functioning of the system. The mm (memory management) subsystem within the Kernel is responsible for managing memory allocation and deallocation. Within the mm subsystem, the memcg (memory control group) feature allows for resource isolation and control of memory usage by different processes or groups of processes. However, a vulnerability has been discovered in the mm subsystem that affects the synchronization of objcg (object control group) lists. This vulnerability can potentially be exploited to gain unauthorized access or cause denial of service.

Vulnerability Detail

The vulnerability in the Kernel's mm subsystem arises from a lack of proper synchronization of objcg lists. This can lead to race conditions and data inconsistencies when multiple processes or threads attempt to access or modify the lists concurrently. An attacker could potentially exploit this vulnerability to manipulate the objcg lists, leading to unauthorized access to sensitive data or causing system instability. The vulnerability was introduced in version v5.9 of the Linux Kernel and has been fixed in version v5.16.10.

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

There is no specific workaround available for this vulnerability. It is recommended to apply the fix by updating the Linux Kernel as mentioned in the 'how_to_fix' section.

Conclusion

The vulnerability in the Kernel's mm subsystem, specifically in the synchronization of objcg lists, can pose significant security risks if left unaddressed. It is crucial to update the Linux Kernel to version v5.16.10 or later to mitigate these risks. Additionally, using tools like Vulert Playground can help identify if your system is affected by this vulnerability. Prompt action should be taken to ensure the security and stability of the system.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability can potentially allow unauthorized access to sensitive data or cause system instability.

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 open-source vulnerabilities, including this one.

The exact exploitability of this vulnerability depends on various factors, including the system configuration and network setup. However, in general, remote exploitation is possible if an attacker can gain access to the targeted system.

There are no known instances of this vulnerability being actively exploited in the wild. However, it is important to apply the fix as soon as possible to mitigate any potential risks.

For further support and assistance with vulnerability remediation, you can reach out to 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