CVE REMEDIATION GUIDE
Review reviewHighFixed-version data available

CVE-2025-21719 remediation guide

Linux Linux, SIMATIC S7-1500 TM MFP - GNU/Linux subsystem, linux kernel

In the Linux kernel, the following vulnerability has been resolved: ipmr: do not call mr_mfc_uses_dev() for unres entries syzbot found that calling mr_mfc_uses_dev() for unres entries would crash [1], because c->mfc_un.res.minvif / c->mfc_un.res.maxvif alias to "struct sk_buff_head unresolved", which contain two pointers. This code never worked, lets remove it. [1] Unable to handle kernel paging request at virtual address ffff5fff2d536613 KASAN: maybe wild-memory-access in range [0xfffefff96a9b3098-0xfffefff96a9b309f] Modules linked in: CPU: 1 UID: 0 PID: 7321 Comm: syz.0.16 Not tainted 6.1...

Open CVE record
ProductLinux Linux, SIMATIC S7-1500 TM MFP - GNU/Linux subsystem, linux kernel
Affected versions>= cb167893f41e21e6bd283d78e53489289dc0592d < 71a0fcb68c0a5f3ec912b540cd5d72148e6ee5f1, >= cb167893f41e21e6bd283d78e53489289dc0592d < 53df27fd38f84bd3cd6b004eb4ff3c4903114f1d, >= cb167893f41e21e6bd283d78e53489289dc0592d < 547ef7e8cbb98f966c8719a3e15d4e078aaa9b47, >= cb167893f41e21e6bd283d78e53489289dc0592d < 57177c5f47a8da852f8d76cf6945cf803f8bb9e5, >= cb167893f41e21e6bd283d78e53489289dc0592d < b379b3162ff55a70464c6a934ae9bf0497478a62, >= cb167893f41e21e6bd283d78e53489289dc0592d < a099834a51ccf9bbba3de86a251b3433539abfde, >= cb167893f41e21e6bd283d78e53489289dc0592d < 26bb7d991f04eeef47dfad23e533834995c26f7a, >= cb167893f41e21e6bd283d78e53489289dc0592d < 15a901361ec3fb1c393f91880e1cbf24ec0a88bd, >= 4.20, >= 4.20 < 5.4.291, >= 5.5 < 5.10.235, >= 5.11 < 5.15.179, >= 5.16 < 6.1.129, >= 6.2 < 6.6.76, >= 6.7 < 6.12.13, >= 6.13 < 6.13.2
Fixed versions5.4.291, 5.10.235, 5.15.179, 6.1.129, 6.6.76, 6.12.13, 6.13.2
Priority basisReview · CVSS 7.1 · EPSS 0.19%
01

Identify the affected asset

Confirm whether Linux Linux, SIMATIC S7-1500 TM MFP - GNU/Linux subsystem, linux kernel 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: >= cb167893f41e21e6bd283d78e53489289dc0592d < 71a0fcb68c0a5f3ec912b540cd5d72148e6ee5f1, >= cb167893f41e21e6bd283d78e53489289dc0592d < 53df27fd38f84bd3cd6b004eb4ff3c4903114f1d, >= cb167893f41e21e6bd283d78e53489289dc0592d < 547ef7e8cbb98f966c8719a3e15d4e078aaa9b47, >= cb167893f41e21e6bd283d78e53489289dc0592d < 57177c5f47a8da852f8d76cf6945cf803f8bb9e5, >= cb167893f41e21e6bd283d78e53489289dc0592d < b379b3162ff55a70464c6a934ae9bf0497478a62, >= cb167893f41e21e6bd283d78e53489289dc0592d < a099834a51ccf9bbba3de86a251b3433539abfde, >= cb167893f41e21e6bd283d78e53489289dc0592d < 26bb7d991f04eeef47dfad23e533834995c26f7a, >= cb167893f41e21e6bd283d78e53489289dc0592d < 15a901361ec3fb1c393f91880e1cbf24ec0a88bd, >= 4.20, >= 4.20 < 5.4.291, >= 5.5 < 5.10.235, >= 5.11 < 5.15.179, >= 5.16 < 6.1.129, >= 6.2 < 6.6.76, >= 6.7 < 6.12.13, >= 6.13 < 6.13.2. 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.291, 5.10.235, 5.15.179, 6.1.129, 6.6.76, 6.12.13, 6.13.2. 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.