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

Kernel Updated 02 Oct 2025

Summary

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

GSD-2021-1001480: watchdog: Fix possible use-after-free in wdt_startup(). Affects Kernel versions < 63a3dc24bd053792f84cb4eef0168b1266202a02. 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 watchdog package is a part of the Linux Kernel ecosystem and is responsible for monitoring the system's health and ensuring its stability. It includes a wdt_startup() function that initializes the watchdog timer. However, a use-after-free vulnerability has been discovered in this function, which could potentially lead to security breaches and system instability.

Vulnerability Detail

The use-after-free vulnerability in the wdt_startup() function arises when the function continues to reference memory after it has been freed. This can result in unpredictable behavior, including the execution of arbitrary code or a system crash. Attackers may exploit this vulnerability to gain unauthorized access to the system or disrupt its normal functioning. The vulnerability has been fixed in Linux Kernel version v4.4.276 by commit 63a3dc24bd053792f84cb4eef0168b1266202a02.

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 mentioned for this vulnerability. Updating the Linux Kernel to the fixed version is the recommended solution.

Conclusion

The use-after-free vulnerability in the wdt_startup() function of the watchdog package can have serious security implications, including the execution of arbitrary code and system crashes. It is crucial to update the Linux Kernel to version v4.4.276 or later to fix this vulnerability. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The use-after-free vulnerability in the wdt_startup() function can potentially allow attackers to execute arbitrary code or cause a system crash, leading to unauthorized access or disruption of normal system functioning.

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.

Yes, a patch has been released in Linux Kernel version v4.4.276. It is recommended to update the kernel to this version or later to fix the vulnerability.

Yes, this vulnerability can be exploited remotely if the affected system is accessible over the network. Attackers can send specially crafted requests to trigger the use-after-free vulnerability and potentially gain unauthorized access or disrupt the system.

There are no known instances of this vulnerability being exploited in the wild at the moment. However, it is important to apply the patch and update the Linux Kernel to mitigate the risk.

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