CVE-2026-31678: openvswitch: defer tunnel netdev_put to RCU release
In the Linux kernel, the following vulnerability has been resolved:
openvswitch: defer tunnel netdev_put to RCU release
ovs_netdev_tunnel_destroy() may run after NETDEV_UNREGISTER already
detached the device. Dropping the netdev reference in destroy can race
with concurrent readers that still observe vport->dev.
Do not release vport->dev in ovs_netdev_tunnel_destroy(). Instead, let
vport_netdev_free() drop the reference from the RCU callback, matching
the non-tunnel destroy path and avoiding additional synchronization
under RTNL.
Security readout for executives and security teams
Plain-English summary
A Linux Open vSwitch flaw can mishandle a network-device reference while tunnel interfaces are being removed. A concurrent local process may encounter invalid kernel state, potentially compromising confidentiality, integrity, or availability. The supplied CVSS score is 7.8, making this a high-severity issue, but exposure depends on affected kernels and Open vSwitch tunnel use.
Executive priority
Prioritize affected virtualization, container, and networking hosts where Open vSwitch tunnels and untrusted local workloads coexist. Treat remediation as high priority, while validating actual exposure before emergency disruption. There is no supplied evidence of active exploitation, so urgency should be driven by host criticality and local-access risk.
Technical view
A race exists between ovs_netdev_tunnel_destroy() and concurrent readers of vport->dev after NETDEV_UNREGISTER detaches the device. Releasing the reference during tunnel destruction can violate its required lifetime. The stable fix defers netdev_put to the vport_netdev_free() RCU callback, aligning tunnel cleanup with the non-tunnel path.
Likely exposure
Likely exposure is limited to Linux systems running affected kernel builds with Open vSwitch tunnel vports. The CVSS vector indicates exploitation requires local access and low privileges, without user interaction. The supplied version list is ambiguous and does not reliably identify every vulnerable or fixed distribution package.
Exploitation context
The bundle marks this CVE as absent from KEV and provides no evidence of active exploitation or a public exploit. The reported impact is high across confidentiality, integrity, and availability, but practical exploitability and trigger conditions are not fully documented in the supplied sources.
Researcher notes
This is a reference-lifetime race involving tunnel vport teardown and RCU readers. The correction moves reference release into the RCU callback rather than adding synchronization under RTNL. The bundle supplies six stable-tree commits, but no CWE, reproducer, exploit details, or dependable mapping between listed versions and individual fixes.
Mitigation direction
Update to a vendor-supported kernel containing the applicable upstream stable fix, then reboot into it.
Confirm the distribution package includes a backport of one of the cited stable commits.
Consult the Linux distribution's guidance because the supplied sources name no standalone workaround.
Restrict low-privilege local access to exposed hosts while remediation is pending.
Validation and detection
Inventory kernel versions on hosts using Open vSwitch tunnel interfaces.
Map distribution kernel builds to the cited stable commits or vendor backport documentation.
Verify the patched kernel is active after reboot, not merely installed.
Reassess local account and workload access on any host awaiting remediation.
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-2026-31678 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.
1CVSS vectors
3Timeline events
0ADP providers
7Source links
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.