CVE-2025-38724 remediation guide

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

In the Linux kernel, the following vulnerability has been resolved: nfsd: handle get_client_locked() failure in nfsd4_setclientid_confirm() Lei Lu recently reported that nfsd4_setclientid_confirm() did not check the return value from get_client_locked(). a SETCLIENTID_CONFIRM could race with a confirmed client expiring and fail to get a reference. That could later lead to a UAF. Fix this by getting a reference early in the case where there is an extant confirmed client. If that fails then treat it as if there were no confirmed client found at all. In the case where the unconfirmed client is...

Open CVE record

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

Affected versions>= d20c11d86d8f821a64eac7d6c8f296f06d935f4f < 3f252a73e81aa01660cb426735eab932e6182e8d, >= d20c11d86d8f821a64eac7d6c8f296f06d935f4f < d35ac850410966010e92f401f4e21868a9ea4d8b, >= d20c11d86d8f821a64eac7d6c8f296f06d935f4f < f3aac6cf390d8b80e1d82975faf4ac61175519c0, >= d20c11d86d8f821a64eac7d6c8f296f06d935f4f < 22f45cedf281e6171817c8a3432c44d788c550e1, >= d20c11d86d8f821a64eac7d6c8f296f06d935f4f < d71abd1ae4e0413707cd42b10c24a11d1aa71772, >= d20c11d86d8f821a64eac7d6c8f296f06d935f4f < 74ad36ed60df561a303a19ecef400c7096b20306, >= d20c11d86d8f821a64eac7d6c8f296f06d935f4f < 36e83eda90e0e4ac52f259f775b40b2841f8a0a3, >= d20c11d86d8f821a64eac7d6c8f296f06d935f4f < 571a5e46c71490285d2d8c06f6b5a7cbf6c7edd1, >= d20c11d86d8f821a64eac7d6c8f296f06d935f4f < 908e4ead7f757504d8b345452730636e298cbf68, >= 3.17, < V5.0, >= V3.1.5, >= 3.17 < 5.4.297, >= 5.5 < 5.10.241, >= 5.11 < 5.15.190, >= 5.16 < 6.1.149, >= 6.2 < 6.6.103, >= 6.7 < 6.12.43, >= 6.13 < 6.15.11, >= 6.16 < 6.16.2

Fixed versions5.4.297, 5.10.241, 5.15.190, 6.1.149, 6.6.103, 6.12.43, 6.15.11, 6.16.2

Priority basisReview · CVSS 7.8 · EPSS 0.38%

Identify the affected asset

Confirm whether Linux Linux, SIMATIC CN 4100, SIMATIC S7-1500 CPU 1518-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: >= d20c11d86d8f821a64eac7d6c8f296f06d935f4f < 3f252a73e81aa01660cb426735eab932e6182e8d, >= d20c11d86d8f821a64eac7d6c8f296f06d935f4f < d35ac850410966010e92f401f4e21868a9ea4d8b, >= d20c11d86d8f821a64eac7d6c8f296f06d935f4f < f3aac6cf390d8b80e1d82975faf4ac61175519c0, >= d20c11d86d8f821a64eac7d6c8f296f06d935f4f < 22f45cedf281e6171817c8a3432c44d788c550e1, >= d20c11d86d8f821a64eac7d6c8f296f06d935f4f < d71abd1ae4e0413707cd42b10c24a11d1aa71772, >= d20c11d86d8f821a64eac7d6c8f296f06d935f4f < 74ad36ed60df561a303a19ecef400c7096b20306, >= d20c11d86d8f821a64eac7d6c8f296f06d935f4f < 36e83eda90e0e4ac52f259f775b40b2841f8a0a3, >= d20c11d86d8f821a64eac7d6c8f296f06d935f4f < 571a5e46c71490285d2d8c06f6b5a7cbf6c7edd1, >= d20c11d86d8f821a64eac7d6c8f296f06d935f4f < 908e4ead7f757504d8b345452730636e298cbf68, >= 3.17, < V5.0, >= V3.1.5, >= 3.17 < 5.4.297, >= 5.5 < 5.10.241, >= 5.11 < 5.15.190, >= 5.16 < 6.1.149, >= 6.2 < 6.6.103, >= 6.7 < 6.12.43, >= 6.13 < 6.15.11, >= 6.16 < 6.16.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: 5.4.297, 5.10.241, 5.15.190, 6.1.149, 6.6.103, 6.12.43, 6.15.11, 6.16.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.