CVE-2025-39826 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: net: rose: convert 'use' field to refcount_t The 'use' field in struct rose_neigh is used as a reference counter but lacks atomicity. This can lead to race conditions where a rose_neigh structure is freed while still being referenced by other code paths. For example, when rose_neigh->use becomes zero during an ioctl operation via rose_rt_ioctl(), the structure may be removed while its timer is still active, potentially causing use-after-free issues. This patch changes the type of 'use' from unsigned short to refcount_t and...

Open CVE record

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

Affected versions>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < fb07156cc0742ba4e93dfcc84280c011d05b301f, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < f8c29fc437d03a98fb075c31c5be761cc8326284, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 0085b250fcc79f900c82a69980ec2f3e1871823b, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 203e4f42596ede31498744018716a3db6dbb7f51, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < d860d1faa6b2ce3becfdb8b0c2b048ad31800061, >= 2.6.12, < V5.0, >= V3.1.6, >= 2.6.12.1 < 6.1.150, >= 6.2 < 6.6.104, >= 6.7 < 6.12.45, >= 6.13 < 6.16.5, 2.6.12, 6.17, 11.0

Fixed versions6.1.150, 6.6.104, 6.12.45, 6.16.5

Priority basisReview · CVSS 7 · EPSS 0.19%

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: >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < fb07156cc0742ba4e93dfcc84280c011d05b301f, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < f8c29fc437d03a98fb075c31c5be761cc8326284, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 0085b250fcc79f900c82a69980ec2f3e1871823b, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 203e4f42596ede31498744018716a3db6dbb7f51, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < d860d1faa6b2ce3becfdb8b0c2b048ad31800061, >= 2.6.12, < V5.0, >= V3.1.6, >= 2.6.12.1 < 6.1.150, >= 6.2 < 6.6.104, >= 6.7 < 6.12.45, >= 6.13 < 6.16.5, 2.6.12, 6.17, 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.150, 6.6.104, 6.12.45, 6.16.5. 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.