SECUFOCUSNOW
Home›Remediation guides›CVE-2025-71123
CVE REMEDIATION GUIDE
Review reviewHighFixed-version data available

CVE-2025-71123 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: ext4: fix string copying in parse_apply_sb_mount_options() strscpy_pad() can't be used to copy a non-NUL-term string into a NUL-term string of possibly bigger size. Commit 0efc5990bca5 ("string.h: Introduce memtostr() and memtostr_pad()") provides additional information in that regard. So if this happens, the following warning is observed: strnlen: detected buffer overflow: 65 byte read of buffer size 64 WARNING: CPU: 0 PID: 28655 at lib/string_helpers.c:1032 __fortify_report+0x96/0xc0 lib/string_helpers.c:1032 Modules link...

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>= b2bac84fde28fb6a88817b8b761abda17a1d300b < 52ac96c4a2dd7bc47666000440b0602d9742e820, >= e651294218d2684302ee5ed95ccf381646f3e5b4 < 6e37143560e37869d51b7d9e0ac61fc48895f8a0, >= 01829af7656b56d83682b3491265d583d502e502 < 902ca2356f1e3ec5355c5808ad5d3f9d0095b0cc, >= 2a0cf438320cdb783e0378570744c0ef0d83e934 < db9ee13fab0267eccf6544ee35b16c9522db9aac, >= 8ecb790ea8c3fc69e77bace57f14cf0d7c177bd8 < 5bbacbbf1ca4419861dca3c6b82707c10e9c021c, >= 8ecb790ea8c3fc69e77bace57f14cf0d7c177bd8 < ee5a977b4e771cc181f39d504426dbd31ed701cc, >= 7bf46ff83a0ef11836e38ebd72cdc5107209342d, >= a6e94557cd05adc82fae0400f6e17745563e5412, >= 5.10.246 < 5.10.248, >= 6.1.158 < 6.1.160, >= 6.6.114 < 6.6.120, >= 6.12.54 < 6.12.64, >= 5.4.301 < 5.5, >= 6.17.4 < 6.18, >= 6.18, >= V3.1.6, >= 6.18.1 < 6.18.3, 6.18, 6.19
Fixed versions5.5, 5.10.248, 6.1.160, 6.6.120, 6.12.64, 6.18, 6.18.3
Priority basisReview · CVSS 7.8 · EPSS 0.14%
01

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.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= b2bac84fde28fb6a88817b8b761abda17a1d300b < 52ac96c4a2dd7bc47666000440b0602d9742e820, >= e651294218d2684302ee5ed95ccf381646f3e5b4 < 6e37143560e37869d51b7d9e0ac61fc48895f8a0, >= 01829af7656b56d83682b3491265d583d502e502 < 902ca2356f1e3ec5355c5808ad5d3f9d0095b0cc, >= 2a0cf438320cdb783e0378570744c0ef0d83e934 < db9ee13fab0267eccf6544ee35b16c9522db9aac, >= 8ecb790ea8c3fc69e77bace57f14cf0d7c177bd8 < 5bbacbbf1ca4419861dca3c6b82707c10e9c021c, >= 8ecb790ea8c3fc69e77bace57f14cf0d7c177bd8 < ee5a977b4e771cc181f39d504426dbd31ed701cc, >= 7bf46ff83a0ef11836e38ebd72cdc5107209342d, >= a6e94557cd05adc82fae0400f6e17745563e5412, >= 5.10.246 < 5.10.248, >= 6.1.158 < 6.1.160, >= 6.6.114 < 6.6.120, >= 6.12.54 < 6.12.64, >= 5.4.301 < 5.5, >= 6.17.4 < 6.18, >= 6.18, >= V3.1.6, >= 6.18.1 < 6.18.3, 6.18, 6.19. Treat incomplete inventory results as unresolved.

03

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.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 5.5, 5.10.248, 6.1.160, 6.6.120, 6.12.64, 6.18, 6.18.3. Preserve configuration and rollback material before change.

05

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.