Answer in brief
CVE-2024-26583 records a Unknown severity vulnerability in tls: fix race between async notify and socket close. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2024-26583 records a Unknown severity vulnerability in tls: fix race between async notify and socket close. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=0cada33241d9de205522e3858b18e506ca5cce2c <f17d21ea73918ace8afb9c2d8e734dbf71c2c9d7 || >=0cada33241d9de205522e3858b18e506ca5cce2c <7a3ca06d04d589deec81f56229a9a9d62352ce01 || >=0cada33241d9de205522e3858b18e506ca5cce2c <86dc27ee36f558fe223dbdfbfcb6856247356f4a || >=0cada33241d9de205522e3858b18e506ca5cce2c <6209319b2efdd8524691187ee99c40637558fa33 || >=0cada33241d9de205522e3858b18e506ca5cce2c <aec7961916f3f9e88766e2688992da6980f11b8d || cf4cc95a15f599560c7abd89095a7973a4b9cec3 || 9b81d43da15e56ed89f083f326561acdcaf549ce || >=5.4.44 <5.5 || >=5.6.16 <5.7 | f17d21ea73918ace8afb9c2d8e734dbf71c2c9d7, 7a3ca06d04d589deec81f56229a9a9d62352ce01, 86dc27ee36f558fe223dbdfbfcb6856247356f4a, 6209319b2efdd8524691187ee99c40637558fa33, aec7961916f3f9e88766e2688992da6980f11b8d, 5.5, 5.7 |
| Linux/Linuxgeneric | 5.7 | Not reported |
Published upstream
Feb 21, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=0cada33241d9de205522e3858b18e506ca5cce2c <f17d21ea73918ace8afb9c2d8e734dbf71c2c9d7 || >=0cada33241d9de205522e3858b18e506ca5cce2c <7a3ca06d04d589deec81f56229a9a9d62352ce01 || >=0cada33241d9de205522e3858b18e506ca5cce2c <86dc27ee36f558fe223dbdfbfcb6856247356f4a || >=0cada33241d9de205522e3858b18e506ca5cce2c <6209319b2efdd8524691187ee99c40637558fa33 || >=0cada33241d9de205522e3858b18e506ca5cce2c <aec7961916f3f9e88766e2688992da6980f11b8d || cf4cc95a15f599560c7abd89095a7973a4b9cec3 || 9b81d43da15e56ed89f083f326561acdcaf549ce || >=5.4.44 <5.5 || >=5.6.16 <5.7 | f17d21ea73918ace8afb9c2d8e734dbf71c2c9d7, 7a3ca06d04d589deec81f56229a9a9d62352ce01, 86dc27ee36f558fe223dbdfbfcb6856247356f4a, 6209319b2efdd8524691187ee99c40637558fa33, aec7961916f3f9e88766e2688992da6980f11b8d, 5.5, 5.7 |
| Linux/Linuxgeneric | 5.7 | Not reported |
Published upstream
Feb 21, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.