Vulnerability in coresight: cpu-debug Package

Kernel Updated 02 Oct 2025

Summary

28/06/2022

Disclosed on

N/A

Severity

No i

Fix available

Unrated

Severity

Not published

CVSS Score

GSD-2022-1003730: coresight: cpu-debug: Replace mutex with mutex_trylock on panic notifier. Affects Kernel versions >= 2227b7c7463402ce92706a6f35c82cad6e8ee19a, < 0f91755514b8466b5efa201b7ff7acbe26234d09. 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 Browse

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.

Background

The coresight: cpu-debug package is a component of the Linux Kernel ecosystem. It provides functionality for debugging CPUs in the coresight subsystem. The package includes various features and tools for monitoring and analyzing CPU behavior. However, a vulnerability has been identified in the package that could potentially lead to security issues.

Vulnerability Detail

The vulnerability in the coresight: cpu-debug package involves the use of a mutex instead of mutex_trylock on the panic notifier. This vulnerability was introduced in version v4.13 of the Linux Kernel and has been fixed in version v5.4.198. The impact and attack plausibility of this vulnerability have not been proven yet. However, if exploited, it could potentially lead to unauthorized access or denial of service attacks. The vulnerability is specific to the coresight: cpu-debug package and does not affect other components of the Linux 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.4.198 or later. This update includes the necessary fix commit (0f91755514b8466b5efa201b7ff7acbe26234d09) that addresses the vulnerability. Updating the Linux Kernel will ensure that the coresight: cpu-debug package is patched and protected against potential security risks.

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. The recommended approach is to update the Linux Kernel to the fixed version.

Conclusion

In conclusion, the coresight: cpu-debug package in the Linux Kernel has a vulnerability that could potentially lead to security issues. It is recommended to update the Linux Kernel to version v5.4.198 or later to fix this vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for Kernel →