Answer in brief
CVE-2024-58240 records a Unknown severity vulnerability in tls: separate no-async decryption request handling from async. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC CN 4100 (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-58240 records a Unknown severity vulnerability in tls: separate no-async decryption request handling from async. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC CN 4100 (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), Siemens/SIMATIC CN 4100 (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3c4d7559159bfe1e3b94df3a657b2cda3a34e218 <48905146d11dbf1ddbb2967319016a83976953f5 || >=3c4d7559159bfe1e3b94df3a657b2cda3a34e218 <dec5b6e7b211e405d3bcb504562ab21aa7e5a64d || >=3c4d7559159bfe1e3b94df3a657b2cda3a34e218 <999115298017a675d8ddf61414fc7a85c89f1186 || >=3c4d7559159bfe1e3b94df3a657b2cda3a34e218 <41532b785e9d79636b3815a64ddf6a096647d011 | 48905146d11dbf1ddbb2967319016a83976953f5, dec5b6e7b211e405d3bcb504562ab21aa7e5a64d, 999115298017a675d8ddf61414fc7a85c89f1186, 41532b785e9d79636b3815a64ddf6a096647d011 |
| Linux/Linuxgeneric | 4.13 | Not reported |
| Siemens/SIMATIC CN 4100generic | >=0 <V5.0 | V5.0 |
Published upstream
Aug 28, 2025
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: separate no-async decryption request handling from async If we're not doing async, the handling is much simpler. There's no reference counting, we just need to wait for the completion to wake us up and return its result. We should preferably also use a separate crypto_wait. I'm not seeing a UAF as I did in the past, I think aec7961916f3 ("tls: fix race between async notify and socket close") took care of it. This will make the next fix easier.
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), Siemens/SIMATIC CN 4100 (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3c4d7559159bfe1e3b94df3a657b2cda3a34e218 <48905146d11dbf1ddbb2967319016a83976953f5 || >=3c4d7559159bfe1e3b94df3a657b2cda3a34e218 <dec5b6e7b211e405d3bcb504562ab21aa7e5a64d || >=3c4d7559159bfe1e3b94df3a657b2cda3a34e218 <999115298017a675d8ddf61414fc7a85c89f1186 || >=3c4d7559159bfe1e3b94df3a657b2cda3a34e218 <41532b785e9d79636b3815a64ddf6a096647d011 | 48905146d11dbf1ddbb2967319016a83976953f5, dec5b6e7b211e405d3bcb504562ab21aa7e5a64d, 999115298017a675d8ddf61414fc7a85c89f1186, 41532b785e9d79636b3815a64ddf6a096647d011 |
| Linux/Linuxgeneric | 4.13 | Not reported |
| Siemens/SIMATIC CN 4100generic | >=0 <V5.0 | V5.0 |
Published upstream
Aug 28, 2025
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: separate no-async decryption request handling from async If we're not doing async, the handling is much simpler. There's no reference counting, we just need to wait for the completion to wake us up and return its result. We should preferably also use a separate crypto_wait. I'm not seeing a UAF as I did in the past, I think aec7961916f3 ("tls: fix race between async notify and socket close") took care of it. This will make the next fix easier.
Quoted source text, attributed separately from HOL analysis.