CVE-2021-46971

Low

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.

SeverityLow
CVSS3.3
Exploit probability—
ProductLinux Kernel
PublishedFeb 27, 2024
First seenFeb 27, 2024

How to fix

Update
  • linux linux_kernel5.4.117, 5.10.35, 5.11.19, 5.12.2 or later

Affected products

ProductAffected versionsFixed in
linux linux_kernel5.4 ≤ v < 5.4.117, 5.5 ≤ v < 5.10.35, 5.11 ≤ v < 5.11.19, 5.12 ≤ v < 5.12.25.4.117, 5.10.35, 5.11.19, 5.12.2

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.