Unconditional security_locked_down() call in perf/core

Kernel Updated 02 Oct 2025

Summary

31/05/2021
N/A
No i
Unrated
Not published

GSD-2021-1000162: perf/core: Fix unconditional security_locked_down() call. Affects Kernel versions >= b0c8fdc7fdb77586c3d1937050925b960743306e, < 4348d3b5027bc3ff6336368b6c60605d4ef8e1ce. 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 perf/core component is a part of the Linux Kernel, which is responsible for performance monitoring and profiling. It provides tools and interfaces for collecting and analyzing system performance data. The security_locked_down() function is used to check if the system is in a locked-down state, where certain security restrictions are enforced. This vulnerability arises from an unconditional call to security_locked_down() in the perf/core code, which can lead to security bypass or privilege escalation.

Vulnerability Detail

The vulnerability in perf/core arises from an unconditional call to the security_locked_down() function. This means that regardless of the system's locked-down state, the function is always invoked. This can potentially bypass security restrictions and allow unauthorized access or privilege escalation. The impact and attack plausibility of this vulnerability have not been proven yet. The vulnerability was introduced in Linux Kernel version v5.4 and fixed in version v5.10.35.

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

As a workaround, users can manually modify the perf/core code to remove the unconditional call to security_locked_down(). However, this is not recommended as it involves modifying the Kernel code, which can be complex and may introduce other issues. It is strongly advised to update to the fixed version of the Linux Kernel instead.

Conclusion

The vulnerability in perf/core, arising from an unconditional security_locked_down() call, can potentially bypass security restrictions and lead to unauthorized access or privilege escalation. It is crucial to update the Linux Kernel to version v5.10.35 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

perf/core is a component of the Linux Kernel that provides tools and interfaces for performance monitoring and profiling. It allows users to collect and analyze system performance data.

security_locked_down() is a function in the Linux Kernel that checks if the system is in a locked-down state, where certain security restrictions are enforced. It is used to prevent unauthorized access and privilege escalation.

The unconditional security_locked_down() call can potentially bypass security restrictions and allow unauthorized access or privilege escalation. However, the actual impact and attack plausibility of this vulnerability have not been proven yet.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.10.35 or later, which includes the fix for this issue.

A workaround involves manually modifying the perf/core code to remove the unconditional call to security_locked_down(). However, this is not recommended as it can be complex and may introduce other issues. It is best to update to the fixed version of the Linux Kernel.

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