Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2021-46971 | First vendor Publication | 2024-02-27 |
Vendor | Cve | Last vendor Modification | 2025-01-08 |
Security-Database Scoring CVSS v3
Cvss vector : CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N | |||
---|---|---|---|
Overall CVSS Score | 3.3 | ||
Base Score | 3.3 | Environmental Score | 3.3 |
impact SubScore | 1.4 | Temporal Score | 3.3 |
Exploitabality Sub Score | 1.8 | ||
Attack Vector | Local | Attack Complexity | Low |
Privileges Required | Low | User Interaction | None |
Scope | Unchanged | Confidentiality Impact | None |
Integrity Impact | Low | Availability Impact | None |
Calculate full CVSS 3.0 Vectors scores |
Security-Database Scoring CVSS v2
Cvss vector : | |||
---|---|---|---|
Cvss Base Score | N/A | Attack Range | N/A |
Cvss Impact Score | N/A | Attack Complexity | N/A |
Cvss Expoit Score | N/A | Authentication | N/A |
Calculate full CVSS 2.0 Vectors scores |
Detail
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. |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-46971 |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
Date | Informations |
---|---|
2025-06-26 01:51:30 |
|
2025-06-25 12:15:45 |
|
2025-06-24 01:55:59 |
|
2025-03-29 02:56:58 |
|
2025-03-28 13:27:19 |
|
2025-03-28 02:41:55 |
|
2025-03-18 02:49:47 |
|
2025-03-14 02:39:51 |
|
2025-01-08 21:21:43 |
|
2024-11-25 09:26:41 |
|
2024-02-28 17:27:37 |
|
2024-02-28 00:27:26 |
|