CVE-2024-43882 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: exec: Fix ToCToU between perm check and set-uid/gid usage When opening a file for exec via do_filp_open(), permission checking is done against the file's metadata at that moment, and on success, a file pointer is passed back. Much later in the execve() code path, the file metadata (specifically mode, uid, and gid) is used to determine if/how to set the uid and gid. However, those values may have changed since the permissions check, meaning the execution may gain unintended privileges. For example, if a file could change per...

Open CVE record

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

Affected versions>= 9167b0b9a0ab7907191523f5a0528e3b9c288e21 < d5c3c7e26275a2d83b894d30f7582a42853a958f, >= 9167b0b9a0ab7907191523f5a0528e3b9c288e21 < 368f6985d46657b8b466a421dddcacd4051f7ada, >= 9167b0b9a0ab7907191523f5a0528e3b9c288e21 < 15469d46ba34559bfe7e3de6659115778c624759, >= 9167b0b9a0ab7907191523f5a0528e3b9c288e21 < 9b424c5d4130d56312e2a3be17efb0928fec4d64, >= 9167b0b9a0ab7907191523f5a0528e3b9c288e21 < f6cfc6bcfd5e1cf76115b6450516ea4c99897ae1, >= 9167b0b9a0ab7907191523f5a0528e3b9c288e21 < d2a2a4714d80d09b0f8eb6438ab4224690b7121e, >= 9167b0b9a0ab7907191523f5a0528e3b9c288e21 < 90dfbba89ad4f0d9c9744ecbb1adac4aa2ff4f3e, >= 9167b0b9a0ab7907191523f5a0528e3b9c288e21 < f50733b45d865f91db90919f8311e2127ce5a0cb, >= 2.6.18, < V3.1, < 4.19.320, >= 4.20 < 5.4.282, >= 5.5 < 5.10.224, >= 5.11 < 5.15.165, >= 5.16 < 6.1.106, >= 6.2 < 6.6.47, >= 6.7 < 6.10.6, 6.11

Fixed versions4.19.320, 5.4.282, 5.10.224, 5.15.165, 6.1.106, 6.6.47, 6.10.6

Priority basisReview · CVSS 7 · EPSS 0.24%

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.

Validate the affected-version match

Compare the deployed version with the affected range: >= 9167b0b9a0ab7907191523f5a0528e3b9c288e21 < d5c3c7e26275a2d83b894d30f7582a42853a958f, >= 9167b0b9a0ab7907191523f5a0528e3b9c288e21 < 368f6985d46657b8b466a421dddcacd4051f7ada, >= 9167b0b9a0ab7907191523f5a0528e3b9c288e21 < 15469d46ba34559bfe7e3de6659115778c624759, >= 9167b0b9a0ab7907191523f5a0528e3b9c288e21 < 9b424c5d4130d56312e2a3be17efb0928fec4d64, >= 9167b0b9a0ab7907191523f5a0528e3b9c288e21 < f6cfc6bcfd5e1cf76115b6450516ea4c99897ae1, >= 9167b0b9a0ab7907191523f5a0528e3b9c288e21 < d2a2a4714d80d09b0f8eb6438ab4224690b7121e, >= 9167b0b9a0ab7907191523f5a0528e3b9c288e21 < 90dfbba89ad4f0d9c9744ecbb1adac4aa2ff4f3e, >= 9167b0b9a0ab7907191523f5a0528e3b9c288e21 < f50733b45d865f91db90919f8311e2127ce5a0cb, >= 2.6.18, < V3.1, < 4.19.320, >= 4.20 < 5.4.282, >= 5.5 < 5.10.224, >= 5.11 < 5.15.165, >= 5.16 < 6.1.106, >= 6.2 < 6.6.47, >= 6.7 < 6.10.6, 6.11. 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: 4.19.320, 5.4.282, 5.10.224, 5.15.165, 6.1.106, 6.6.47, 6.10.6. 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.