Use-after-free vulnerability in wdt_startup() function in Kernel

Kernel Updated 02 Oct 2025

Summary

03/08/2021
N/A
No i
Unrated
Not published

GSD-2021-1001194: watchdog: Fix possible use-after-free in wdt_startup(). Affects Kernel versions < 8adbbe6c86bb13e14f8a19e036ae5f4f5661fd90. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The Kernel is a fundamental component of the Linux operating system that manages core system functions, including hardware communication and process management. It provides an interface between the hardware and software layers, allowing applications to run on the system. The wdt_startup() function is part of the watchdog subsystem in the Kernel, which is responsible for monitoring system health and ensuring proper operation. This vulnerability affects the wdt_startup() function and can lead to a use-after-free condition.

Vulnerability Detail

The use-after-free vulnerability in the wdt_startup() function occurs when the function attempts to access memory that has already been freed. This can result in various issues, including crashes, data corruption, and potential privilege escalation. An attacker may be able to exploit this vulnerability to execute arbitrary code or gain elevated privileges on the affected system. The vulnerability has been fixed in Linux Kernel version v5.13.4 by commit 8adbbe6c86bb13e14f8a19e036ae5f4f5661fd90.

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.13.4 or later. This can be done by obtaining the updated Kernel source code from the official repository and compiling it for the target system. Alternatively, users can wait for their Linux distribution to provide an updated package containing the fixed Kernel version.

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. However, users can mitigate the risk by ensuring they have proper security measures in place, such as using a firewall, keeping software up to date, and following best practices for system administration.

Conclusion

The use-after-free vulnerability in the wdt_startup() function of the Kernel can have serious consequences, including crashes, data corruption, and potential privilege escalation. It is crucial to update the Linux Kernel to version v5.13.4 or later to mitigate the risk. Additionally, users should follow best practices for system security and keep their software up to date. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The use-after-free vulnerability in the wdt_startup() function can lead to crashes, data corruption, and potential privilege escalation. It may allow an attacker to execute arbitrary code or gain elevated privileges on the affected system.

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 potential vulnerabilities.

Yes, the vulnerability has been fixed in Linux Kernel version v5.13.4 by commit 8adbbe6c86bb13e14f8a19e036ae5f4f5661fd90. It is recommended to update to this version or later to mitigate the risk.

At the time of this report, there are no known exploits for this vulnerability. However, it is important to apply the necessary updates and security measures to protect against potential attacks.

You can find more information about this vulnerability in the official Linux Kernel repository. The vulnerability ID is GSD-2021-1001194.

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.13.4 or later. This can be done by obtaining the updated Kernel source code from the official repository and compiling it for the target system. Alternatively, users can wait for their Linux distribution to provide an updated package containing the fixed Kernel version.

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.