CVE-2026-99025

openvswitch: fix soft lockup in the netlink flow dump

Description

In the Linux kernel, the following vulnerability has been resolved: openvswitch: fix soft lockup in the netlink flow dump A production compute node carrying a few thousand datapath flows hit a soft lockup inside a single netlink flow dump and panicked. ovs_flow_cmd_dump() calls ovs_flow_stats_get() for every flow it emits, and that releases stats->lock with spin_unlock_bh() once per CPU that has touched the flow. Every release is a local_bh_enable(), and each one runs the pending softirq backlog in the dumping thread's own context. The skb bounds the flows one callback emits, but not the softirq work it absorbs. On a CPU that carries the box's packet load the backlog refills as fast as it drains, so the dumping thread becomes that CPU's softirq engine. It never sleeps and it has no reschedule point, so under voluntary preemption nothing can take the CPU away from it: neither the ksoftirqd the kernel woke to take the work over, nor the stopper thread the softlockup detector dispatches to refresh its timestamp. Hold BH off across the whole callback instead, the way ctnetlink_dump_table() does, so the nested spin_unlock_bh() stop draining softirqs. The loop already runs under rcu_read_lock() and cannot sleep. What it gives up is preemption under CONFIG_PREEMPT, since a BH-off region is not preemptible outside PREEMPT_RT. The region stays short: the skb caps the flows one callback emits, and empty buckets cost no skb space but are each visited once per dump, as the cursor only moves forward. The table grows on insert and shrinks only on flush, so the walk is bounded by the largest flow count the datapath has held. The softirq backlog the callback used to absorb has no bound at all.

Key facts

Published
23 Oct 2026
Last changed
30 Oct 2026
Assigned by
Linux
EPSS
0.177% likely to be exploited in the next 30 days, higher than 7.374% of CVEs (scores for 17 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 63e7959c4b9bd6f791061c460a22d9ee32ae2240 up to but excluding ef77dd59cb7b7b0ac0bedd3fe9ee7a8acd8a58f2 (affected)
  • 63e7959c4b9bd6f791061c460a22d9ee32ae2240 up to but excluding 9ffb9897b39037a688ae01d0b3aea4ccce27dd75 (affected)
  • 63e7959c4b9bd6f791061c460a22d9ee32ae2240 up to but excluding 5b6a8bbdcdd7d0fddee466c1c7fe5b7f30aa392c (affected)
  • 63e7959c4b9bd6f791061c460a22d9ee32ae2240 up to but excluding c995c52eba1926a5e82823fa5573a6f1b1010e5d (affected)
  • 63e7959c4b9bd6f791061c460a22d9ee32ae2240 up to but excluding b872de585edff534056c65ba30970b68499fca14 (affected)
  • 63e7959c4b9bd6f791061c460a22d9ee32ae2240 up to but excluding 55f12552b00a34ca7ab5cf2d2b5ed02f8f06a965 (affected)
  • 63e7959c4b9bd6f791061c460a22d9ee32ae2240 up to but excluding 80db24f3c16fdeef85460d9d66a4aae7a9cb92b4 (affected)
  • 63e7959c4b9bd6f791061c460a22d9ee32ae2240 up to but excluding aaaaf87ea99b8766c9a8aa0e71aa42e6bc8a5320 (affected)
LinuxLinux
  • Default status: affected
  • 3.16 (affected)
  • 0 up to but excluding 3.16 (unaffected)
  • 5.10.273 up to and including 5.10.* (unaffected)
  • 5.15.224 up to and including 5.15.* (unaffected)
  • 6.1.191 up to and including 6.1.* (unaffected)
  • 6.6.160 up to and including 6.6.* (unaffected)
  • 6.12.113 up to and including 6.12.* (unaffected)
  • 6.18.57 up to and including 6.18.* (unaffected)
  • 7.2.11 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 23 Oct 2026 Published

References