CVE-2025-21760: ndisc: extend RCU protection in ndisc_send_skb()
In the Linux kernel, the following vulnerability has been resolved:
ndisc: extend RCU protection in ndisc_send_skb()
ndisc_send_skb() can be called without RTNL or RCU held.
Acquire rcu_read_lock() earlier, so that we can use dev_net_rcu()
and avoid a potential UAF.
Security readout for executives and security teams
Plain-English summary
A Linux kernel networking function may access memory after it has been released because protection is acquired too late. Successful exploitation could seriously affect confidentiality, integrity, or availability, although the supplied evidence does not establish practical exploitation conditions or attacks in the wild.
Executive priority
Treat this as high-priority kernel maintenance, particularly for critical or network-facing Linux systems. Schedule prompt vendor-approved updates, but the supplied evidence does not justify claiming an active-exploitation emergency. Require asset owners to confirm the running kernel after remediation.
Technical view
CVE-2025-21760 is a CWE-416 use-after-free in ndisc_send_skb(). The function can run without RTNL or RCU protection. The kernel fix acquires rcu_read_lock() earlier, allowing dev_net_rcu() to be used safely. CVSS 3.1 is 8.1: network-accessible, unauthenticated, high-complexity, with potentially high confidentiality, integrity, and availability impact.
Likely exposure
Potential exposure exists on Linux systems running affected kernel builds where the vulnerable network-neighbour-discovery path is reachable. The supplied version data does not clearly distinguish introduced versions from fixed branch releases. Validate exposure through the applicable distribution or appliance advisory and corresponding stable-kernel fix, not version strings alone.
Exploitation context
The supplied record is not in KEV, and no cited source establishes active exploitation or a public proof of concept. The CVSS vector describes an unauthenticated network attack with high complexity and no user interaction. KEV absence does not prove exploitation is impossible.
Researcher notes
The record identifies a race-related RCU lifetime failure and CWE-416. Precise triggering conditions, affected-version boundaries, exploit reliability, and observable indicators are incomplete in the supplied bundle. The stable commits document the code-level correction, while Debian advisories provide downstream remediation context.
Mitigation direction
Install a vendor-supported kernel package containing the applicable stable-kernel fix.
Check distribution or appliance advisories for exact fixed package versions.
Prioritize systems processing untrusted network traffic or supporting critical services.
Reboot into the updated kernel when required by the vendor package process.
Validation and detection
Inventory running kernel releases and vendor package versions across Linux assets.
Map each build to its vendor advisory and applicable stable-kernel fix.
Confirm the updated kernel is running, rather than merely installed.
Regression-test network connectivity after updating, including IPv6 where enabled.
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.
cwe · low confidence lookup
CWE-416: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
2CVSS vectors
3Timeline events
3ADP providers
13Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-416 · source CWE mapping
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.