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-1004090: x86/delay: Fix the wrong asm constraint in delay_loop(). Affects Kernel versions >= e01b70ef3eb3080fecc35e15f68cd274c0a48163, < 55bd0545d2792cb512559ba493c29b45f49e20f4. 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 crucial component of the Linux operating system that manages system resources and provides an interface for user applications. It is responsible for handling hardware devices, memory management, and process scheduling. The delay_loop() function in the x86 architecture is used to introduce a delay in the execution of code. However, a vulnerability has been identified in the implementation of delay_loop() that can lead to incorrect behavior and potential security issues.

Vulnerability Detail

The vulnerability arises from a wrong asm constraint in the delay_loop() function in the x86 architecture. This incorrect constraint can result in unexpected behavior and potentially allow attackers to exploit the system. The impact and attack plausibility of this vulnerability have not been proven yet. The vulnerability was introduced in version v2.6.27 of the Linux Kernel and is fixed in version v4.9.318.

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 v4.9.318 or later. This can be done by downloading the latest stable version of the Kernel from the official Git repository (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/) and following the installation instructions provided by the Kernel developers.

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.

Conclusion

The vulnerability in the Kernel's delay_loop() function can lead to incorrect behavior and potential security issues. It is recommended to update the Linux Kernel to version v4.9.318 or later to fix this vulnerability. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The impact of this vulnerability is not yet proven. However, it has the potential to lead to incorrect behavior and may be exploitable by attackers.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your manifest file (e.g., package-lock.json) and the playground will provide real-time alerts for open-source vulnerabilities.

Yes, a patch is available in version v4.9.318 of the Linux Kernel. It is recommended to update to this version or a later one to fix the vulnerability.

Yes, the vulnerability was introduced in version v2.6.27 of the Linux Kernel. It is advisable to update to version v4.9.318 or later to mitigate the vulnerability.

No known exploit for this vulnerability has been reported at this time.

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 v4.9.318 or later. This can be done by downloading the latest stable version of the Kernel from the official Git repository (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/) and following the installation instructions provided by the Kernel developers.

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.