In the Linux kernel, the following vulnerability has been resolved: tls: fix race between async notify and socket close The submitting thread (one which called recvmsg/sendmsg) may exit as soon as the async crypto handler calls complete() so any code past that point risks touching already freed data. Try to avoid the locking and extra flags altogether. Have the main thread hold an extra reference, this way we can depend solely on the atomic ref counter for synchronization. Don't futz with reiniting the completion, either, we are now tightly controlling when completion fires.
Published 2024-02-21 15:15:09
Updated 2024-03-15 13:05:03
Source Linux
View at NVD,   CVE.org

Exploit prediction scoring system (EPSS) score for CVE-2024-26583

Probability of exploitation activity in the next 30 days: 0.04%

Percentile, the proportion of vulnerabilities that are scored at or less: ~ 5 % EPSS Score History EPSS FAQ

CVSS scores for CVE-2024-26583

Base Score Base Severity CVSS Vector Exploitability Score Impact Score Score Source
4.7
MEDIUM CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
1.0
3.6
NIST

CWE ids for CVE-2024-26583

References for CVE-2024-26583

Products affected by CVE-2024-26583

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!