CVE-2021-46971

perf/core: Fix unconditional security_locked_down() call

LOW
3.3
CVSS Score
Published: February 27, 2024 at 06:47 PM UTC
Updated: June 17, 2026 at 04:16 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
LOW3.3
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.11 ≤ v < 5.11.195.12 ≤ v < 5.12.25.4 ≤ v < 5.10.355.4 ≤ v < 5.11.195.4 ≤ v < 5.12.25.4 ≤ v < 5.135.4 ≤ v < 5.4.1175.5 ≤ v < 5.10.355.4b0c8fdc7fdb77586c3d1937050925b960743306e
Vendor states this is fixed in 08ef1af4de5fe7de9c6d69f1e22e51b66e385d9b (fixed)
Vendor states this is fixed in 4348d3b5027bc3ff6336368b6c60605d4ef8e1ce (fixed)
Vendor states this is fixed in b246759284d6a2bc5b6f1009caeeb3abce2ec9ff (fixed)
Vendor states this is fixed in c7b0208ee370b89d20486fae71cd9abb759819c1 (fixed)
Vendor states this is fixed in f5809ca4c311b71bfaba6d13f4e39eab0557895e (fixed)
Vendor states this is fixed in 5.10.35 (unaffected)
Vendor states this is fixed in 5.11.19 (unaffected)
Vendor states this is fixed in 5.12.2 (unaffected)
Vendor states this is fixed in 5.13 (unaffected)
Vendor states this is fixed in 5.4 (unaffected)
Vendor states this is fixed in 5.4.117 (unaffected)

References (5)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/08ef1af4de5fe7de9c6d69f1e22e51b66e385d9b
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/4348d3b5027bc3ff6336368b6c60605d4ef8e1ce
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/b246759284d6a2bc5b6f1009caeeb3abce2ec9ff
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/c7b0208ee370b89d20486fae71cd9abb759819c1
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/f5809ca4c311b71bfaba6d13f4e39eab0557895e

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
LOW
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card