Missing TID Updates on Slab Deactivation in Linux Kernel
Summary
GSD-2022-1004278: mm/slub: add missing TID updates on slab deactivation. Affects Kernel versions >= c17dda40a6a4ed95f035db38b7ba4fab0d99da44, < 197e257da473c725dfe47759c3ee02f2398d8ea5. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The Linux Kernel is the core component of the Linux operating system, responsible for managing system resources and providing an interface for applications to interact with the hardware. The mm/slub subsystem within the kernel handles memory allocation and deallocation using a slab allocator. Slabs are pre-allocated chunks of memory used to satisfy allocation requests efficiently. However, a vulnerability has been discovered in the mm/slub subsystem that results in missing TID (Thread ID) updates on slab deactivation.
Vulnerability Detail
The vulnerability arises from the mm/slub subsystem's failure to update the TID when deactivating a slab. This missing update can lead to incorrect TID information being associated with the slab, potentially causing various issues. Attackers may exploit this vulnerability to manipulate or corrupt memory, leading to privilege escalation, information disclosure, or denial of service. The vulnerability was introduced in version v3.6 of the Linux Kernel and has been fixed in version v5.18.8.
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 →
Conclusion
The missing TID updates on slab deactivation vulnerability in the Linux Kernel's mm/slub subsystem can have serious security implications. It is crucial to update the kernel to version v5.18.8 or later to mitigate the risk. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can potentially be exploited by attackers to manipulate or corrupt memory, leading to privilege escalation, information disclosure, or denial of service.
You can use Vulert's playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities without requiring access to the code or installation.
No specific workarounds have been identified for this vulnerability. It is recommended to update the Linux Kernel to the fixed version.
The vulnerability was introduced in version v3.6 of the Linux Kernel. All versions between v3.6 and v5.18.8 (inclusive) are affected.
Yes, the vulnerability has been patched in version v5.18.8 of the Linux Kernel.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
