Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 13/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 08ef1af4de5fe7de9c6d69f1e22e51b66e385d9b, 4348d3b5027bc3ff6336368b6c60605d4ef8e1ce, b246759284d6a2bc5b6f1009caeeb3abce2ec9ff.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 08ef1af4de5fe7de9c6d69f1e22e51b66e385d9b, 4348d3b5027bc3ff6336368b6c60605d4ef8e1ce, b246759284d6a2bc5b6f1009caeeb3abce2ec9ff or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

LowCVSS 3.3 · v3.1—No exploit Fix available
Published
Feb 27, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 13th percentile
CWE
—

Report tools

JSON

Action score

13

Monitor

Low priority for now.

CVSS
13 / 40 · 3.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2021-46971

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.4 and later · before 5.4.117
  • linux linux kernel5.5 and later · before 5.10.35
  • linux linux kernel5.11 and later · before 5.11.19
  • linux linux kernel5.12 and later · before 5.12.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.4affected
    • b0c8fdc7fdb77586c3d1937050925b960743306e and later · before b246759284d6a2bc5b6f1009caeeb3abce2ec9ffaffected · git
    • b0c8fdc7fdb77586c3d1937050925b960743306e and later · before 4348d3b5027bc3ff6336368b6c60605d4ef8e1ceaffected · git
    • b0c8fdc7fdb77586c3d1937050925b960743306e and later · before f5809ca4c311b71bfaba6d13f4e39eab0557895eaffected · git
    • b0c8fdc7fdb77586c3d1937050925b960743306e and later · before c7b0208ee370b89d20486fae71cd9abb759819c1affected · git
    • b0c8fdc7fdb77586c3d1937050925b960743306e and later · before 08ef1af4de5fe7de9c6d69f1e22e51b66e385d9baffected · git
    • before 5.4not affected · semver
    • 5.4.117 and later · up to and including 5.4.*not affected · semver
    • 5.10.35 and later · up to and including 5.10.*not affected · semver
    • 5.11.19 and later · up to and including 5.11.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 5.10.38-15.10.38-1
SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSkernel-default-basebefore 5.3.18-150200.24.188.1.150200.9.95.35.3.18-150200.24.188.1.150200.9.95.3
SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSkernel-docsbefore 5.3.18-150200.24.188.15.3.18-150200.24.188.1
SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSkernel-obs-buildbefore 5.3.18-150200.24.188.15.3.18-150200.24.188.1
SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSkernel-preemptbefore 5.3.18-150200.24.188.15.3.18-150200.24.188.1
SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSkernel-sourcebefore 5.3.18-150200.24.188.15.3.18-150200.24.188.1
SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSkernel-symsbefore 5.3.18-150200.24.188.15.3.18-150200.24.188.1
SUSE:Linux Enterprise Live Patching 15 SP2kernel-defaultbefore 5.3.18-150200.24.188.15.3.18-150200.24.188.1
SUSE:Linux Enterprise Live Patching 15 SP2kernel-livepatch-SLE15-SP2_Update_47before 1-150200.5.3.31-150200.5.3.3

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2021-46969Feb 27, 2024 · bus: mhi: core: Fix invalid error returning in mhi_queue
    31Monitor
  • ← EarlierCVE-2021-46970Feb 27, 2024 · bus: mhi: pci_generic: Remove WQ_MEM_RECLAIM flag from state workqueue
    22Monitor
  • Later →CVE-2021-46972Feb 27, 2024 · ovl: fix leaked dentry
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux08ef1af4de5fe7de9c6d69f1e22e51b66e385d9bVendor (CNA)
Linux Linux4348d3b5027bc3ff6336368b6c60605d4ef8e1ceVendor (CNA)
Linux Linuxb246759284d6a2bc5b6f1009caeeb3abce2ec9ffVendor (CNA)
Linux Linuxc7b0208ee370b89d20486fae71cd9abb759819c1Vendor (CNA)
Linux Linuxf5809ca4c311b71bfaba6d13f4e39eab0557895eVendor (CNA)
debian:linux5.10.38-1 · Debian:12Package registry (OSV)
suse:kernel-default5.3.18-150200.24.188.1 · SUSE:Linux Enterprise Live Patching 15 SP2Package registry (OSV)
suse:kernel-default-base5.3.18-150200.24.188.1.150200.9.95.3 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSPackage registry (OSV)
suse:kernel-docs5.3.18-150200.24.188.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSPackage registry (OSV)
suse:kernel-livepatch-SLE15-SP2_Update_471-150200.5.3.3 · SUSE:Linux Enterprise Live Patching 15 SP2Package registry (OSV)
suse:kernel-obs-build5.3.18-150200.24.188.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSPackage registry (OSV)
suse:kernel-preempt5.3.18-150200.24.188.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSPackage registry (OSV)
suse:kernel-source5.3.18-150200.24.188.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSPackage registry (OSV)
suse:kernel-syms5.3.18-150200.24.188.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
low · data or configuration can be modified
Availability
none
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
Low
Availability impact
None

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records