Vulnerability in Kernel: x86/entry: Clear X86_FEATURE_SMAP when CONFIG_X86_SMAP=n

Kernel Updated 02 Oct 2025

Summary

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

GSD-2021-1001618: x86/entry: Clear X86_FEATURE_SMAP when CONFIG_X86_SMAP=n. Affects Kernel versions >= 3c73b81a9164d0c1b6379d6672d2772a9e95168e, < f2447f6587b8ffe42ba04d14ce67d429a1163e5e. 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 Kernel is a critical component of the Linux operating system that acts as a bridge between the hardware and software layers. It provides essential functionalities and services to enable the proper functioning of the system. This vulnerability specifically affects the x86/entry module of the Kernel. The x86/entry module is responsible for handling system calls and interrupts on x86 architecture. It contains code that manages the transition from user mode to kernel mode and vice versa. The vulnerability arises when the CONFIG_X86_SMAP configuration option is disabled, but the X86_FEATURE_SMAP flag is not cleared properly. This can lead to potential security risks.

Vulnerability Detail

The vulnerability occurs due to a misconfiguration in the Kernel when the CONFIG_X86_SMAP option is disabled. The X86_FEATURE_SMAP flag, which is responsible for enabling Supervisor Mode Access Prevention (SMAP) on x86 processors, is not cleared properly. SMAP is a security feature that prevents the kernel from accessing user-space memory directly. By not clearing the X86_FEATURE_SMAP flag, an attacker may be able to bypass SMAP protection and gain unauthorized access to user-space memory from the kernel. This could potentially lead to information disclosure or privilege escalation attacks. The vulnerability was introduced in version v5.8 of the Linux Kernel and has been fixed in version v5.10.73.

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

Conclusion

The vulnerability in the Kernel's x86/entry module, which fails to clear the X86_FEATURE_SMAP flag when the CONFIG_X86_SMAP option is disabled, can lead to security risks. It is crucial to update the Linux Kernel to version v5.10.73 or later to fix this vulnerability. For further assistance and support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability can potentially allow an attacker to bypass Supervisor Mode Access Prevention (SMAP) protection and gain unauthorized access to user-space memory from the kernel. This could lead to information disclosure or privilege escalation attacks.

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 Vulert will analyze it for any open-source vulnerabilities, including this one.

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

The recommended solution is to update the Linux Kernel to the fixed version. However, if updating is not feasible, it is advised to follow best security practices such as restricting access to vulnerable systems, implementing network segmentation, and monitoring for any suspicious activities.

At the time of this report, there are no known exploits for this vulnerability. However, it is important to apply the necessary updates as soon as possible to mitigate any potential risks.

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