CVE-2025-21763: neighbour: use RCU protection in __neigh_notify()
In the Linux kernel, the following vulnerability has been resolved:
neighbour: use RCU protection in __neigh_notify()
__neigh_notify() can be called without RTNL or RCU protection.
Use RCU protection to avoid potential UAF.
Security readout for executives and security teams
Plain-English summary
CVE-2025-21763 is a Linux kernel use-after-free flaw in neighbour notification handling. A local, low-privileged attacker may be able to impact confidentiality, integrity, and availability. It is serious for multi-user Linux systems, container hosts, and appliances that run affected kernels.
Executive priority
Prioritize remediation in the next normal emergency patch cycle for internet-facing service hosts, shared infrastructure, and systems running untrusted local workloads. No active exploitation is cited, but kernel memory-safety flaws can materially affect host control.
Technical view
The flaw is CWE-416 in Linux kernel __neigh_notify(). The CVE states the function can run without RTNL or RCU protection, creating potential use-after-free risk. Stable kernel commits resolve it by adding RCU protection. CVSS 3.1 is 7.8 with local attack vector and low privileges required.
Likely exposure
Exposure is likely on systems running affected Linux kernel versions or vendor products built on those kernels. The bundle lists Linux 2.6.25 through multiple stable branches as affected, with fixed stable commits referenced. Confirm against your distribution kernel package, not only upstream version numbers.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation. The CVSS vector indicates local access with low privileges and no user interaction. Treat this mainly as a local privilege and host-compromise risk until vendor advisories provide more specific exploitation evidence.
Researcher notes
Focus validation on neighbour subsystem patch presence and vendor backport status. The available sources identify the vulnerable function and fix direction, but do not provide exploit details, affected distribution package matrices, or proof of active exploitation.
Mitigation direction
Update to a vendor kernel containing the referenced stable fixes.
Prioritize shared Linux servers, container hosts, and systems with local user access.
Review Debian LTS advisories if running Debian-derived systems.
Check appliance and OEM advisories for embedded Linux exposure.
Use vendor guidance where package backports obscure upstream version numbers.
Validation and detection
Inventory Linux kernel versions across servers, containers hosts, and appliances.
Map installed kernel packages to vendor advisories and fixed builds.
Confirm whether your kernel includes the RCU protection commits.
Review EDR or audit logs for suspicious local privilege activity.
Track CVE and vendor advisories for exploitation-status changes.
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.
1CVSS vectors
3Timeline events
3ADP providers
12Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
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.