SECUFOCUSNOW
Home›CVE index›CVE-2026-64423
Review reviewHigh

CVE-2026-64423

Linux

In the Linux kernel, the following vulnerability has been resolved: ipv4: igmp: remove multicast group from hash table on device destruction When a device is destroyed under RTNL, ip_mc_destroy_dev() iterates through the multicast list and calls ip_ma_put() on each membership, scheduling them for RCU reclamation. However, they are not unlinked from the device's multicast hash table (mc_hash). Since the device remains published in dev->ip_ptr until after ip_mc_destroy_dev() completes, concurrent RCU readers traversing mc_hash can still locate and access the multicast group after its refcount...

CVSS
7.8
EPSS
-
- percentile
CISA KEV
Not listed
Published
2026.07.25
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability-
Technical severityCVSS 7.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: ipv4: igmp: remove multicast group from hash table on device destruction When a device is destroyed under RTNL, ip_mc_destroy_dev() iterates through the multicast list and calls ip_ma_put() on each membership, scheduling them for RCU reclamation. However, they are not unlinked from the device's multicast hash table (mc_hash). Since the device remains published in dev->ip_ptr until after ip_mc_destroy_dev() completes, concurrent RCU readers traversing mc_hash can still locate and access the multicast group after its refcount...

Affected product and versions

Product
Linux
Affected versions
>= e9897071350bd9d94a56b5b6f79c85b1a98fc7e7 < 412ba7def06ffe974ba9a1d862b022362c54ffa5, >= e9897071350bd9d94a56b5b6f79c85b1a98fc7e7 < c6cb5f8ebe1c1a78710c19f102db9fe48b9e6ba9, >= e9897071350bd9d94a56b5b6f79c85b1a98fc7e7 < 5f42729d74bd6c61306d864423290d92962de4e1, >= e9897071350bd9d94a56b5b6f79c85b1a98fc7e7 < 76d030ac95e17f91d69a595f17ebc5979700cf9a, >= e9897071350bd9d94a56b5b6f79c85b1a98fc7e7 < 8820b530cb2388503d7418228d03ba074bf7a03e, >= e9897071350bd9d94a56b5b6f79c85b1a98fc7e7 < 2ca18df1c2611f70eb3eb487e02ae85eb703b284, >= e9897071350bd9d94a56b5b6f79c85b1a98fc7e7 < f91883031e5a62877a29ce139442973cbea769f1, >= e9897071350bd9d94a56b5b6f79c85b1a98fc7e7 < 7993211bde166471dffac074dc965489f86531f8, >= 3.11
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
Not available