Missing TID Updates on Slab Deactivation in Kernel

Kernel Updated 02 Oct 2025

Summary

31/07/2022
N/A
No i
Unrated
Not published

GSD-2022-1004478: mm/slub: add missing TID updates on slab deactivation. Affects Kernel versions >= c17dda40a6a4ed95f035db38b7ba4fab0d99da44, < 0515cc9b6b24877f59b222ade704bfaa42caa2a6. 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 Kernel is a critical component of the Linux operating system that manages system resources and facilitates communication between hardware and software. It provides essential functionalities such as memory management, process scheduling, and device drivers. The mm/slub module in the Kernel is responsible for managing the slab allocator, which efficiently allocates and deallocates small memory objects. However, a vulnerability has been identified in the mm/slub module that results in missing TID (Thread ID) updates on slab deactivation.

Vulnerability Detail

The vulnerability in the mm/slub module occurs when a slab is deactivated without updating the associated TID information. This can lead to various security issues, including potential use-after-free vulnerabilities and memory corruption. Attackers may exploit this vulnerability to execute arbitrary code, escalate privileges, or cause denial-of-service conditions. The vulnerability was introduced in version v3.6 of the Linux Kernel and has been fixed in version v5.15.54.

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 consider implementing strict access controls and limiting the exposure of vulnerable systems to untrusted networks. Additionally, monitoring system logs for any suspicious activities and promptly applying security updates can help mitigate the risk associated with this vulnerability.

Conclusion

The missing TID updates on slab deactivation vulnerability in the mm/slub module of the Linux Kernel can have severe security implications. It is crucial to update the Kernel to the latest version and apply the recommended fixes to mitigate the risk. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

This vulnerability can potentially allow attackers to execute arbitrary code, escalate privileges, or cause denial-of-service conditions.

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 to the playground, and it will provide real-time alerts for open-source vulnerabilities.

At the time of this report, there is no known public exploit for this vulnerability. However, it is essential to apply the recommended fixes to mitigate the risk.

Yes, this vulnerability can be exploited remotely if the affected system is exposed to untrusted networks. Implementing strict access controls and network segmentation can help reduce the risk.

The primary solution is to update the Linux Kernel to the latest version. However, if updating is not feasible, implementing additional security measures such as intrusion detection systems and network firewalls can provide some level of protection.

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