CVE-2024-58240 remediation guide
Linux Linux, SIMATIC CN 4100, linux kernel
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.
Identify the affected asset
Confirm whether Linux Linux, SIMATIC CN 4100, linux kernel is installed, record the deployed version and installation path, and identify exposed interfaces.
- Record the product name, package or appliance identifier, and installed version.
- Identify internet-facing, administrative, API, and internal access paths.
- Preserve the pre-change configuration and relevant service logs.
Validate the affected-version match
Compare the deployed version with the affected range: >= 3c4d7559159bfe1e3b94df3a657b2cda3a34e218 < 48905146d11dbf1ddbb2967319016a83976953f5, >= 3c4d7559159bfe1e3b94df3a657b2cda3a34e218 < dec5b6e7b211e405d3bcb504562ab21aa7e5a64d, >= 3c4d7559159bfe1e3b94df3a657b2cda3a34e218 < 999115298017a675d8ddf61414fc7a85c89f1186, >= 3c4d7559159bfe1e3b94df3a657b2cda3a34e218 < 41532b785e9d79636b3815a64ddf6a096647d011, >= 4.13, < V5.0, >= 4.13 < 6.1.149, >= 6.2 < 6.6.21, >= 6.7 < 6.7.9, 6.8, 11.0. Treat incomplete inventory results as unresolved.
Prioritize with independent signals
The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.
Apply supported remediation
Follow the vendor advisory or supported update path. Current fixed-version status: 6.1.149, 6.6.21, 6.7.9. Preserve configuration and rollback material before change.
Verify the result
Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.
- Confirm the expected version and package state.
- Run a functional health check for critical service paths.
- Review authentication, error, application, and security monitoring logs.
- Reassess exposure if the supported fix cannot be applied.
Operational boundary
This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.