CVE-2021-46971

perf/core: Fix unconditional security_locked_down() call

published February 27, 2024

CVSS
—
EPSS
0%
Percentile
13.1
In the wild
Unconfirmed
What it is

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.

The record
Technical detail
CVSS
Not scored
CVSS v4.0
Not supplied
EPSS
0.00230 · 13.1th percentile
Published
2024-02-27T18:47Z
EPSS history
Timeline
  • 27 FEB 18:47Z
    perf/core: Fix unconditional security_locked_down() call
    cvelistv5