tipc: Use-after-free Read in tipc_named_reinit

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1004473: tipc: fix use-after-free Read in tipc_named_reinit. Affects Kernel versions >= d966ddcc38217a6110a6a0ff37ad2dee7d42e23e, < cd7789e659e84f137631dc1f5ec8d794f2700e6c. 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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The Kernel is a critical component of the Linux operating system that provides essential services and functions for the system's operation. It manages hardware resources, facilitates communication between software and hardware, and enforces security policies. The vulnerability in question affects the tipc module within the Kernel. The Transparent Inter-Process Communication (TIPC) protocol is a communication mechanism used for inter-process communication in distributed systems. The tipc_named_reinit function is responsible for reinitializing the TIPC named socket table. However, a use-after-free vulnerability exists in this function, which can lead to a read access to an already freed memory area. This vulnerability can potentially be exploited by an attacker to execute arbitrary code or cause a denial-of-service condition.

Vulnerability Detail

The use-after-free vulnerability in tipc_named_reinit arises due to improper handling of memory during the reinitialization process. When the function is called, it attempts to free the existing named socket table and allocate a new one. However, if an error occurs during the allocation, the function fails to properly handle the cleanup of the previously allocated memory. This can result in a situation where the memory is freed, but a reference to it still exists. Subsequent read operations on this freed memory can lead to unexpected behavior, including the potential for code execution or system crashes. The vulnerability was introduced in Linux Kernel version 5.10 and has been fixed in version 5.15.51.

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 use-after-free vulnerability in the tipc_named_reinit function of the tipc module within the Linux Kernel can lead to arbitrary code execution or denial-of-service attacks. It is crucial to update the Kernel to version 5.15.51 or later to mitigate the risk of exploitation. Regularly monitoring for vulnerabilities using tools like Vulert can help ensure the timely application of security updates. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The use-after-free vulnerability in tipc_named_reinit can potentially be exploited by an attacker to execute arbitrary code or cause a denial-of-service condition. This could lead to unauthorized access, data breaches, system crashes, or other malicious activities.

You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Vulert analyzes your application's manifest file, such as package-lock.json, to identify and alert in real-time for open-source vulnerabilities, including this one.

At the moment, there is no known workaround for this vulnerability. It is recommended to update the Linux Kernel to the fixed version to mitigate the risk.

There are no known instances of this vulnerability being exploited in the wild. However, it is crucial to apply the necessary updates to protect against potential exploitation.

The discovery and reporting of this vulnerability are attributed to the Linux Kernel development community. The vulnerability was identified through code analysis and subsequently fixed in the Linux Kernel source code.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

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