net/sched: sch_taprio: properly cancel timer from taprio_destroy() - Kernel

Kernel Updated 02 Oct 2025

Summary

19/10/2021
N/A
No i
Unrated
Not published

GSD-2021-1001582: net/sched: sch_taprio: properly cancel timer from taprio_destroy(). Affects Kernel versions >= c71c512f4a65267e6a18163f4df729c489a51035, < c951c08a5996365aecbc5f1a9bddec3905e1ddfc. 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 Your last release was probably never penetration tested 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 fundamental component of the Linux operating system, responsible for managing system resources and providing an interface between hardware and software. It includes various subsystems, such as networking, file systems, and process management. The sch_taprio module within the networking subsystem is used for implementing Time-Aware Priority (TAP) scheduling. TAP scheduling allows for precise control over packet transmission times, which is crucial for real-time applications. However, a vulnerability has been identified in the sch_taprio module that can lead to a timer not being properly canceled during the destruction of a taprio instance.

Vulnerability Detail

The vulnerability in the sch_taprio module arises from a failure to cancel a timer when a taprio instance is destroyed. This can result in the timer continuing to run even after the instance has been freed, leading to a use-after-free scenario. An attacker may be able to exploit this vulnerability to execute arbitrary code or cause a denial-of-service condition. The impact and attack plausibility of this vulnerability have not been proven yet. The vulnerability was introduced in Linux Kernel version v5.4.87 and has been fixed in version v5.4.153.

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 known workaround for this vulnerability.

Conclusion

The sch_taprio module in the Linux Kernel is vulnerable to a use-after-free scenario due to a failure to cancel a timer during the destruction of a taprio instance. This vulnerability can potentially be exploited to execute arbitrary code or cause a denial-of-service condition. It is recommended to update the Linux Kernel to version v5.4.153 or later to fix this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The impact of this vulnerability can vary depending on the specific use case. It could potentially allow an attacker to execute arbitrary code or cause a denial-of-service condition.

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

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

Yes, the vulnerability was introduced in Linux Kernel version v5.4.87. Any versions between v5.4.87 and v5.4.152 are also affected.

There is currently no evidence of this vulnerability being exploited in the wild. However, it is still important to apply the patch to ensure the security of your system.

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