SECUFOCUSNOW
Home›Remediation guides›CVE-2024-39503
CVE REMEDIATION GUIDE
Review reviewHighFixed-version data available

CVE-2024-39503 remediation guide

Linux Linux, RUGGEDCOM RST2428P, SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family

In the Linux kernel, the following vulnerability has been resolved: netfilter: ipset: Fix race between namespace cleanup and gc in the list:set type Lion Ackermann reported that there is a race condition between namespace cleanup in ipset and the garbage collection of the list:set type. The namespace cleanup can destroy the list:set type of sets while the gc of the set type is waiting to run in rcu cleanup. The latter uses data from the destroyed set which thus leads use after free. The patch contains the following parts: - When destroying all sets, first remove the garbage collectors, then...

Open CVE record
ProductLinux Linux, RUGGEDCOM RST2428P, SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family
Affected versions>= c7f2733e5011bfd136f1ca93497394d43aa76225 < c0761d1f1ce1d5b85b5e82bbb714df12de1aa8c3, >= a24d5f2ac8ef702a58e55ec276aad29b4bd97e05 < 93b53c202b51a69e42ca57f5a183f7e008e19f83, >= c2dc077d8f722a1c73a24e674f925602ee5ece49 < 0f1bb77c6d837c9513943bc7c08f04c5cc5c6568, >= 653bc5e6d9995d7d5f497c665b321875a626161c < 390b353d1a1da3e9c6c0fd14fe650d69063c95d6, >= b93a6756a01f4fd2f329a39216f9824c56a66397 < 2ba35b37f780c6410bb4bba9c3072596d8576702, >= 97f7cf1cd80eeed3b7c808b7c12463295c751001 < 90ae20d47de602198eb69e6cd7a3db3420abfc08, >= 97f7cf1cd80eeed3b7c808b7c12463295c751001 < 4e7aaa6b82d63e8ddcbfb56b4fd3d014ca586f10, >= 970709a67696b100a57b33af1a3d75fc34b747eb, >= 5.4.269 < 5.4.279, >= 5.10.210 < 5.10.221, >= 5.15.149 < 5.15.162, >= 6.1.79 < 6.1.95, >= 6.6.18 < 6.6.35, >= 6.7.6 < 6.8, >= 6.8, < V3.1, >= 6.8.1 < 6.9.6, 6.8, 6.10
Fixed versions5.4.279, 5.10.221, 5.15.162, 6.1.95, 6.6.35, 6.8, 6.9.6
Priority basisReview · CVSS 7 · EPSS 0.22%
01

Identify the affected asset

Confirm whether Linux Linux, RUGGEDCOM RST2428P, SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family 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: >= c7f2733e5011bfd136f1ca93497394d43aa76225 < c0761d1f1ce1d5b85b5e82bbb714df12de1aa8c3, >= a24d5f2ac8ef702a58e55ec276aad29b4bd97e05 < 93b53c202b51a69e42ca57f5a183f7e008e19f83, >= c2dc077d8f722a1c73a24e674f925602ee5ece49 < 0f1bb77c6d837c9513943bc7c08f04c5cc5c6568, >= 653bc5e6d9995d7d5f497c665b321875a626161c < 390b353d1a1da3e9c6c0fd14fe650d69063c95d6, >= b93a6756a01f4fd2f329a39216f9824c56a66397 < 2ba35b37f780c6410bb4bba9c3072596d8576702, >= 97f7cf1cd80eeed3b7c808b7c12463295c751001 < 90ae20d47de602198eb69e6cd7a3db3420abfc08, >= 97f7cf1cd80eeed3b7c808b7c12463295c751001 < 4e7aaa6b82d63e8ddcbfb56b4fd3d014ca586f10, >= 970709a67696b100a57b33af1a3d75fc34b747eb, >= 5.4.269 < 5.4.279, >= 5.10.210 < 5.10.221, >= 5.15.149 < 5.15.162, >= 6.1.79 < 6.1.95, >= 6.6.18 < 6.6.35, >= 6.7.6 < 6.8, >= 6.8, < V3.1, >= 6.8.1 < 6.9.6, 6.8, 6.10. 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.4.279, 5.10.221, 5.15.162, 6.1.95, 6.6.35, 6.8, 6.9.6. 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.