CVE-2026-23274 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: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels IDLETIMER revision 0 rules reuse existing timers by label and always call mod_timer() on timer->timer. If the label was created first by revision 1 with XT_IDLETIMER_ALARM, the object uses alarm timer semantics and timer->timer is never initialized. Reusing that object from revision 0 causes mod_timer() on an uninitialized timer_list, triggering debugobjects warnings and possible panic when panic_on_warn=1. Fix this by rejecting revision 0 rule insertion when...

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>= 68983a354a655c35d3fb204489d383a2a051fda7 < 32e937dc6e97f5ed3cdfe3fc0b2b19a05e23fa44, >= 68983a354a655c35d3fb204489d383a2a051fda7 < 144f88054ba0180467356f40895bd660b5dceeec, >= 68983a354a655c35d3fb204489d383a2a051fda7 < 28c7cfaf0c0ab17cbd7754092116fd1af45271f9, >= 68983a354a655c35d3fb204489d383a2a051fda7 < 54080355999381fed4a26129579a5765bab87491, >= 68983a354a655c35d3fb204489d383a2a051fda7 < 5e7ece24c5cb75a60402aad4d803c7898ea40aa9, >= 68983a354a655c35d3fb204489d383a2a051fda7 < f5ef97c13165542480a6ffdbe6f09f40bbb7cbf1, >= 68983a354a655c35d3fb204489d383a2a051fda7 < f228b9ae2a7e84d1153616d8e71c4236cb1f1309, >= 68983a354a655c35d3fb204489d383a2a051fda7 < 329f0b9b48ee6ab59d1ab72fef55fe8c6463a6cf, >= 5.7, >= V3.1.6, >= V3.1.5, >= 5.7 < 5.10.253, >= 5.11 < 5.15.203, >= 5.16 < 6.1.167, >= 6.2 < 6.6.130, >= 6.7 < 6.12.78, >= 6.13 < 6.18.19, >= 6.19 < 6.19.9, 7.0

Fixed versions5.10.253, 5.15.203, 6.1.167, 6.6.130, 6.12.78, 6.18.19, 6.19.9

Priority basisReview · CVSS 7.8 · EPSS 0.17%

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: >= 68983a354a655c35d3fb204489d383a2a051fda7 < 32e937dc6e97f5ed3cdfe3fc0b2b19a05e23fa44, >= 68983a354a655c35d3fb204489d383a2a051fda7 < 144f88054ba0180467356f40895bd660b5dceeec, >= 68983a354a655c35d3fb204489d383a2a051fda7 < 28c7cfaf0c0ab17cbd7754092116fd1af45271f9, >= 68983a354a655c35d3fb204489d383a2a051fda7 < 54080355999381fed4a26129579a5765bab87491, >= 68983a354a655c35d3fb204489d383a2a051fda7 < 5e7ece24c5cb75a60402aad4d803c7898ea40aa9, >= 68983a354a655c35d3fb204489d383a2a051fda7 < f5ef97c13165542480a6ffdbe6f09f40bbb7cbf1, >= 68983a354a655c35d3fb204489d383a2a051fda7 < f228b9ae2a7e84d1153616d8e71c4236cb1f1309, >= 68983a354a655c35d3fb204489d383a2a051fda7 < 329f0b9b48ee6ab59d1ab72fef55fe8c6463a6cf, >= 5.7, >= V3.1.6, >= V3.1.5, >= 5.7 < 5.10.253, >= 5.11 < 5.15.203, >= 5.16 < 6.1.167, >= 6.2 < 6.6.130, >= 6.7 < 6.12.78, >= 6.13 < 6.18.19, >= 6.19 < 6.19.9, 7.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: 5.10.253, 5.15.203, 6.1.167, 6.6.130, 6.12.78, 6.18.19, 6.19.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.