CVE REMEDIATION GUIDE
Review reviewHighFixed-version data available

CVE-2025-37921 remediation guide

Linux Linux, linux kernel, debian linux

In the Linux kernel, the following vulnerability has been resolved: vxlan: vnifilter: Fix unlocked deletion of default FDB entry When a VNI is deleted from a VXLAN device in 'vnifilter' mode, the FDB entry associated with the default remote (assuming one was configured) is deleted without holding the hash lock. This is wrong and will result in a warning [1] being generated by the lockdep annotation that was added by commit ebe642067455 ("vxlan: Create wrappers for FDB lookup"). Reproducer: # ip link add vx0 up type vxlan dstport 4789 external vnifilter local 192.0.2.1 # bridge vni add vni 1...

Open CVE record
ProductLinux Linux, linux kernel, debian linux
Affected versions>= f9c4bb0b245cee35ef66f75bf409c9573d934cf9 < 2d4a121296aa3940d2df9906f955c2b6b4e38bc3, >= f9c4bb0b245cee35ef66f75bf409c9573d934cf9 < 3576e9a80b6c4381b01ce0cbaa07f5e92d4492ed, >= f9c4bb0b245cee35ef66f75bf409c9573d934cf9 < 5cb9e07f84e527974b12e82e2549fa6c0cc6eef0, >= f9c4bb0b245cee35ef66f75bf409c9573d934cf9 < 470206205588559e60035fceb5f256640cb45f99, >= f9c4bb0b245cee35ef66f75bf409c9573d934cf9 < 087a9eb9e5978e3ba362e1163691e41097e8ca20, >= 5.18, >= 5.18 < 6.1.138, >= 6.2 < 6.6.90, >= 6.7 < 6.12.28, >= 6.13 < 6.14.6, 6.15, 11.0
Fixed versions6.1.138, 6.6.90, 6.12.28, 6.14.6
Priority basisReview · CVSS 7.8 · EPSS 0.18%
01

Identify the affected asset

Confirm whether Linux Linux, linux kernel, debian linux 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: >= f9c4bb0b245cee35ef66f75bf409c9573d934cf9 < 2d4a121296aa3940d2df9906f955c2b6b4e38bc3, >= f9c4bb0b245cee35ef66f75bf409c9573d934cf9 < 3576e9a80b6c4381b01ce0cbaa07f5e92d4492ed, >= f9c4bb0b245cee35ef66f75bf409c9573d934cf9 < 5cb9e07f84e527974b12e82e2549fa6c0cc6eef0, >= f9c4bb0b245cee35ef66f75bf409c9573d934cf9 < 470206205588559e60035fceb5f256640cb45f99, >= f9c4bb0b245cee35ef66f75bf409c9573d934cf9 < 087a9eb9e5978e3ba362e1163691e41097e8ca20, >= 5.18, >= 5.18 < 6.1.138, >= 6.2 < 6.6.90, >= 6.7 < 6.12.28, >= 6.13 < 6.14.6, 6.15, 11.0. 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: 6.1.138, 6.6.90, 6.12.28, 6.14.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.