CVE-2026-73453
CVSS
10.0 Critical
2026-09-16
Unauthenticated remote code execution in Arista EOS P4Runtime leading to full administrative control
On affected platforms running Arista EOS with P4Runtime configured, an unauthenticated P4Runtime (Programming Protocol-Independent Packet Processors Runtime) client can, under certain conditions, achieve arbitrary code execution. Arista EOS disables P4Runtime by default. By constructing a malicious packet during P4Runtime session initialization, an attacker can obtain full administrative control of the compromised switch. Arista discovered this issue internally and is not aware of any malicious exploitation of this vulnerability in customer networks.
Component
Arista EOS is an enterprise-grade network operating system developed by Arista Networks. It is widely used in data-center and enterprise networks and supports advanced programmable features such as P4Runtime for flexible packet processing.
Risks
- Full administrative control: An attacker can obtain full administrative control of a compromised switch by constructing a malicious packet and then execute arbitrary code
- Network-infrastructure compromise: Because the vulnerability exists in a core network device, a successful exploit lets the attacker fully control network traffic, steal sensitive data, or launch further intranet attacks
- Unauthenticated attack: The vulnerability allows an unauthenticated client to attack; the attacker needs no credentials to trigger it remotely, so the exploitation barrier is very low
Source
Remediation
- Keep P4Runtime disabled unless the business explicitly requires it (the default configuration)
- If P4Runtime must be enabled, strictly restrict source IPs and enforce network-layer access-control lists (ACLs)
- Monitor abnormal traffic and malicious-packet characteristics during P4Runtime session initialization
CVE-2026-90038
CVSS
9.8 Critical
2026-09-16
Use-after-free in the Linux kernel NFSD module leading to remote code execution
Before Linux kernel 7.2.5 and 7.3-rc1, the NFSD (NFS server daemon) module has a use-after-free (Use-After-Free, CWE-416) security flaw caused by a concurrency-handling defect. During export-state revocation, `nfsd4_revoke_export_states()` releases `nn->client_lock` without pinning the client reference, so under a race the client may already have been freed when `revoke_one_stid()` dereferences it. An attacker can construct a specific NFS export-removal operation (such as `exportfs -u`) racing with client expiration, trigger memory corruption, and threaten system stability and security. The vulnerability affects all Linux kernel users who have not updated to a fixed version, including servers and embedded deployments. An attacker needs only network access to trigger it, with no user interaction, and can operate remotely.
Component
The Linux kernel is the core component of the Linux operating system. It manages hardware resources, process scheduling and the network protocol stack; the NFSD module provides NFS network-filesystem service.
Risks
- From ordinary user to administrator: If an attacker can trigger a kernel-space vulnerability, they may break user-space isolation and obtain root privileges
- Complete system control: An attacker can use this vulnerability to execute arbitrary code in kernel space, causing a crash, data disclosure, or full takeover of the server
- No-user-interaction attack: The vulnerability is triggered directly through the network protocol stack (T1190); the attacker needs no click or interaction from the target user
Source
Remediation
- Immediately upgrade the Linux kernel to 7.2.5 or 7.3-rc1 or later
- Monitor NFS service logs for abnormal export-revocation or client-expiration race behavior
- Restrict the network-access scope of the NFS service and allow only trusted clients