Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2021-46971perf/core: Fix unconditional security_locked_down() call

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2021-46971, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Low3.3CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
EPSS (exploitation in 30 days)
0.23% · top 86% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Low 3.3.

Affected products

  • Linux · Linux

    • affected b0c8fdc7fdb77586c3d1937050925b960743306e – < b246759284d6a2bc5b6f1009caeeb3abce2ec9ff
    • affected b0c8fdc7fdb77586c3d1937050925b960743306e – < 4348d3b5027bc3ff6336368b6c60605d4ef8e1ce
    • affected b0c8fdc7fdb77586c3d1937050925b960743306e – < f5809ca4c311b71bfaba6d13f4e39eab0557895e
    • affected b0c8fdc7fdb77586c3d1937050925b960743306e – < c7b0208ee370b89d20486fae71cd9abb759819c1
    • affected b0c8fdc7fdb77586c3d1937050925b960743306e – < 08ef1af4de5fe7de9c6d69f1e22e51b66e385d9b
  • Linux · Linux

    • affected 5.4
    • unaffected < 5.4
    • unaffected 5.4.117 – ≤ 5.4.*
    • unaffected 5.10.35 – ≤ 5.10.*
    • unaffected 5.11.19 – ≤ 5.11.*
    • unaffected 5.12.2 – ≤ 5.12.*
    • unaffected 5.13 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2021-46971 badge
[![CVE-2021-46971](https://cveledger.app/badge/CVE-2021-46971.svg)](https://cveledger.app/cve/CVE-2021-46971)

Record last updated .