CVE-2024-53170 remediation guide

Linux Linux, SIMATIC S7-1500 CPU 1518-4 PN/DP MFP, SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP

In the Linux kernel, the following vulnerability has been resolved: block: fix uaf for flush rq while iterating tags blk_mq_clear_flush_rq_mapping() is not called during scsi probe, by checking blk_queue_init_done(). However, QUEUE_FLAG_INIT_DONE is cleared in del_gendisk by commit aec89dc5d421 ("block: keep q_usage_counter in atomic mode after del_gendisk"), hence for disk like scsi, following blk_mq_destroy_queue() will not clear flush rq from tags->rqs[] as well, cause following uaf that is found by our syzkaller for v6.6: =================================================================...

Open CVE record

ProductLinux Linux, SIMATIC S7-1500 CPU 1518-4 PN/DP MFP, SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP

Affected versions>= 6cfeadbff3f8905f2854735ebb88e581402c16c4 < 1921fe7d2836f8be1d321cf430d17e0d4e05301b, >= 6cfeadbff3f8905f2854735ebb88e581402c16c4 < 1364a29b71c7837770f1902c49e7a6e234d72c92, >= 6cfeadbff3f8905f2854735ebb88e581402c16c4 < a0e93b9fefafe97d596f9c98701ae6c3b04b3ff6, >= 6cfeadbff3f8905f2854735ebb88e581402c16c4 < 61092568f2a9acb0e6e186f03f2e0649a4e86d09, >= 6cfeadbff3f8905f2854735ebb88e581402c16c4 < 3802f73bd80766d70f319658f334754164075bc3, >= 5.19, >= V3.1.6, >= 5.19 < 6.11.11, >= 6.12 < 6.12.2

Fixed versions6.11.11, 6.12.2

Priority basisReview · CVSS 7.8 · EPSS 0.24%

Identify the affected asset

Confirm whether Linux Linux, SIMATIC S7-1500 CPU 1518-4 PN/DP MFP, SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP 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: >= 6cfeadbff3f8905f2854735ebb88e581402c16c4 < 1921fe7d2836f8be1d321cf430d17e0d4e05301b, >= 6cfeadbff3f8905f2854735ebb88e581402c16c4 < 1364a29b71c7837770f1902c49e7a6e234d72c92, >= 6cfeadbff3f8905f2854735ebb88e581402c16c4 < a0e93b9fefafe97d596f9c98701ae6c3b04b3ff6, >= 6cfeadbff3f8905f2854735ebb88e581402c16c4 < 61092568f2a9acb0e6e186f03f2e0649a4e86d09, >= 6cfeadbff3f8905f2854735ebb88e581402c16c4 < 3802f73bd80766d70f319658f334754164075bc3, >= 5.19, >= V3.1.6, >= 5.19 < 6.11.11, >= 6.12 < 6.12.2. 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.11.11, 6.12.2. 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.