Vulnerability Details : CVE-2021-3640

A flaw use-after-free in function sco_sock_sendmsg() of the Linux kernel HCI subsystem was found in the way user calls ioct UFFDIO_REGISTER or other way triggers race condition of the call sco_conn_del() together with the call sco_sock_sendmsg() with the expected controllable faulting memory page. A privileged local user could use this flaw to crash the system or escalate their privileges on the system.
Published 2022-03-03 23:15:08
Updated 2023-10-05 14:51:16
Source Red Hat, Inc.
View at NVD,   CVE.org
Vulnerability category: Memory Corruption

Products affected by CVE-2021-3640

Threat overview for CVE-2021-3640

Top countries where our scanners detected CVE-2021-3640
Top open port discovered on systems with this issue 49152
IPs affected by CVE-2021-3640 947,227
Threat actors abusing to this issue? Yes
Find out if you* are affected by CVE-2021-3640!
*Directly or indirectly through your vendors, service providers and 3rd parties. Powered by attack surface intelligence from SecurityScorecard.

Exploit prediction scoring system (EPSS) score for CVE-2021-3640

EPSS FAQ
0.04%
Probability of exploitation activity in the next 30 days EPSS Score History
~ 6 %
Percentile, the proportion of vulnerabilities that are scored at or less

CVSS scores for CVE-2021-3640

Base Score Base Severity CVSS Vector Exploitability Score Impact Score Score Source First Seen
6.9
 MEDIUM AV:L/AC:M/Au:N/C:C/I:C/A:C
3.4
10.0
 NIST
7.0
 HIGH CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
1.0
5.9
 NIST

CWE ids for CVE-2021-3640

  • The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
    Assigned by: secalert@redhat.com (Primary)
  • The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
    Assigned by:
    • nvd@nist.gov (Secondary)
    • secalert@redhat.com (Primary)

References for CVE-2021-3640

Jump to
This web site uses cookies for managing your session, storing preferences, website analytics and additional purposes described in our privacy policy.
By using this web site you are agreeing to CVEdetails.com terms of use!
Accept Close