CVE-2021-46971
Last modified
CVE-2021-46971 is a low-severity vulnerability rated 3.3/10 on the CVSS scale. 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. EPSS estimates a 0.23% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 5.4, < 5.4.117 |
| Linux | Linux Kernel | >= 5.5, < 5.10.35 |
| Linux | Linux Kernel | >= 5.11, < 5.11.19 |
| Linux | Linux Kernel | >= 5.12, < 5.12.2 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2021-46971?
How severe is CVE-2021-46971?
How do I fix CVE-2021-46971?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2021
- CVE-2021-46965In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2021-46966In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2021-46967In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2021-46968In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2021-46969In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2021-46970In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2021-46972In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2021-46973In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2021-46974In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2021-46975Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2021-46976In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2021-46977In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2021-46971?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
