CVE-2025-21758: ipv6: mcast: add RCU protection to mld_newpack()
In the Linux kernel, the following vulnerability has been resolved:
ipv6: mcast: add RCU protection to mld_newpack()
mld_newpack() can be called without RTNL or RCU being held.
Note that we no longer can use sock_alloc_send_skb() because
ipv6.igmp_sk uses GFP_KERNEL allocations which can sleep.
Instead use alloc_skb() and charge the net->ipv6.igmp_sk
socket under RCU protection.
Security readout for executives and security teams
Plain-English summary
CVE-2025-21758 is a Linux kernel IPv6 multicast bug. The public description says a kernel function can run without required locking protection, creating a concurrency-safety issue. Severity is not scored in the provided record, so business urgency depends on where affected Linux kernels are used, especially internet, network, or appliance workloads with IPv6 enabled.
Executive priority
Prioritize normal security patching unless vendor advisories identify critical affected assets. Escalate for internet-facing, network infrastructure, industrial, or appliance systems because kernel issues can have high operational impact even when severity metadata is incomplete.
Technical view
The issue is in IPv6 multicast handling: mld_newpack() may be called without RTNL or RCU held. The kernel fix adds RCU protection and changes allocation behavior around net->ipv6.igmp_sk charging. The source bundle does not provide CVSS, CWE, privilege requirements, or a confirmed impact class.
Likely exposure
Exposure is likely limited to Linux systems running affected kernel builds with IPv6 multicast code reachable. The bundle also references Debian LTS and Siemens advisories, suggesting downstream products or distributions may include affected kernels. Exact affected product versions beyond the provided Linux kernel entries require vendor confirmation.
Exploitation context
The bundle does not report active exploitation, public exploit code, or CISA KEV listing. Treat exploitation status as unconfirmed. The available evidence supports a kernel concurrency flaw fixed upstream, not a demonstrated attack path.
Researcher notes
The public record is sparse: no CVSS, CWE, impact statement, or exploitability details are provided. Analysis should focus on code-path reachability, kernel branch mapping, and downstream vendor advisories. Avoid assuming privilege level, remote exploitability, or denial-of-service impact without additional source evidence.
Mitigation direction
Update Linux kernels through distribution or vendor-supported security channels.
Prioritize systems using IPv6, network appliances, and externally exposed Linux hosts.
Review Debian LTS guidance if running Debian LTS kernels.
Review Siemens advisories for affected industrial or appliance products.
Track kernel stable fixes referenced in the CVE record.
Validation and detection
Inventory Linux kernel versions across servers, appliances, and embedded systems.
Confirm whether IPv6 is enabled on potentially affected systems.
Map installed kernels against vendor advisories and fixed package releases.
Check Debian LTS or product vendor bulletins for applicable updates.
Document exceptions where vendor-fixed kernels are not yet available.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-21758 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
2ADP providers
10Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Feb 27, 2025, 02:18 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.