Go to homepageCyberStrike

Menu

Star on GitHub · 3.3k
Sign inDownload

CVE-2021-46971

3.3 · LOW

In the Linux kernel, the following vulnerability has been resolved: perf/core: Fix unconditional security_locked_down() call Currently, the lockdown state is queried unconditionally, even though…

Published Feb 27, 2024EPSS 0.23%

Overview

CVE-2021-46971 is a low-severity vulnerability. It was published on February 27, 2024 and has a CVSS 3.1 base score of 3.3 (LOW).

This vulnerability has a CVSS 3.1 base score of 3.3, rated LOW. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

perf/core: Fix unconditional security_locked_down() call

Currently, the lockdown state is queried unconditionally, even though

its result is used only if the PERF_SAMPLE_REGS_INTR bit is set in

attr.sample_type. While that doesn't matter in case of the Lockdown LSM,

it causes trouble with the SELinux's lockdown hook implementation.

SELinux implements the locked_down hook with a check whether the current

task's type has the corresponding "lockdown" class permission

("integrity" or "confidentiality") allowed in the policy. This means

that calling the hook when the access control decision would be ignored

generates a bogus permission check and audit record.

Fix this by checking sample_type first and only calling the hook when

its result would be honored.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/08ef1af4de5fe7de9c6d69f1e22e51b66e385d9bRefgit.kernel.org/stable/c/4348d3b5027bc3ff6336368b6c60605d4ef8e1ceRefgit.kernel.org/stable/c/b246759284d6a2bc5b6f1009caeeb3abce2ec9ffRefgit.kernel.org/stable/c/c7b0208ee370b89d20486fae71cd9abb759819c1Refgit.kernel.org/stable/c/f5809ca4c311b71bfaba6d13f4e39eab0557895eRefgit.kernel.org/stable/c/08ef1af4de5fe7de9c6d69f1e22e51b66e385d9bRefgit.kernel.org/stable/c/4348d3b5027bc3ff6336368b6c60605d4ef8e1ceRefgit.kernel.org/stable/c/b246759284d6a2bc5b6f1009caeeb3abce2ec9ffRefgit.kernel.org/stable/c/c7b0208ee370b89d20486fae71cd9abb759819c1Refgit.kernel.org/stable/c/f5809ca4c311b71bfaba6d13f4e39eab0557895e

How CyberStrike helps

Frequently asked questions

What is CVE-2021-46971?

CVE-2021-46971 is a low-severity vulnerability. It was published on February 27, 2024 and has a CVSS 3.1 base score of 3.3 (LOW).

How severe is CVE-2021-46971?

This vulnerability has a CVSS 3.1 base score of 3.3, rated LOW. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2021-46971?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2021-46971?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2021-46971 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related LOW CVEs from 2021

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999
LiveWatch live →