Fix the wrong asm constraint in delay_loop() in Kernel

Kernel Updated 02 Oct 2025

Summary

28/06/2022
N/A
No i
Unrated
Not published

GSD-2022-1003133: x86/delay: Fix the wrong asm constraint in delay_loop(). Affects Kernel versions >= e01b70ef3eb3080fecc35e15f68cd274c0a48163, < ca392c194afd38fde1cb4cea9a3deb3cc279b4da. 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 crucial component of the Linux operating system, responsible for managing system resources and facilitating communication between hardware and software. It provides essential functionalities, such as process management, memory management, and device drivers. The vulnerability in question affects the x86/delay module within the Kernel.

The delay_loop() function in x86/delay contains a wrong asm constraint, which can lead to unexpected behavior and potential security vulnerabilities.

Vulnerability Detail

The vulnerability arises from a wrong asm constraint in the delay_loop() function of the x86/delay module. This issue was introduced in version v2.6.27 of the Linux Kernel and has been present until version v5.17.14. The incorrect constraint can result in incorrect loop iterations, leading to unexpected delays or timing issues. While the impact and attack plausibility have not been proven, this vulnerability has the potential to be exploited by attackers to disrupt system operations or launch timing-based attacks.

To mitigate this vulnerability, it is recommended to update the Linux Kernel to version v5.17.14 or later, where the issue has been fixed.

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. It is recommended to apply the fix by updating the Linux Kernel to the latest stable version.

Conclusion

The vulnerability in the x86/delay module of the Kernel, caused by a wrong asm constraint in the delay_loop() function, has the potential to result in unexpected delays or timing issues. To mitigate this vulnerability, it is crucial to update the Linux Kernel to version v5.17.14 or later. This fix addresses the incorrect constraint and ensures proper functioning of the delay_loop() function. For further assistance or support in 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 has the potential to cause unexpected delays or timing issues, which may disrupt system operations or enable timing-based attacks.

You can check if your system is affected by this vulnerability by verifying the version of the Linux Kernel in use. If the version is earlier than v5.17.14, it is recommended to update to the latest stable version.

At the time of this report, no known exploits for this vulnerability have been disclosed. However, it is crucial to apply the fix promptly to mitigate any potential risks.

The exact attack vectors and exploitability of this vulnerability have not been proven. However, it is always advisable to keep systems up to date with the latest security patches to minimize the risk of remote exploitation.

For more detailed information about this vulnerability, including technical specifics and the fix implementation, refer to the provided references link in the vulnerability details section.

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