CVE-2023-53188 — linux / linux_kernel
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')In the Linux kernel, the following vulnerability has been resolved:
net: openvswitch: fix race on port output
assume the following setup on a single machine:
- An openvswitch instance with one bridge and default flows
- two network namespaces "server" and "client"
- two ovs interfaces "server" and "client" on the bridge
- for each ovs interface a veth pair with a matching name and 32 rx and tx queues
- move the ends of the veth pairs to the respective network namespaces
- assign ip addresses to each of the veth ends in the namespaces (needs to be the same subnet)
- start some http server on the server network namespace
- test if a client in the client namespace can reach the http server
when following the actions below the host has a chance of getting a cpu stuck in a infinite loop:
- send a large amount of parallel requests to the http server (around 3000 curls should work)
- in parallel delete the network namespace (do not delete interfaces or stop the server, just kill the namespace)
there is a low chance that this will cause the below kernel cpu stuck message. If this does not happen just retry. Below there is also the output of bpftrace for the functions mentioned in the output.
The series of events happening here is:
- the network namespace is deleted calling
unregister_netdevice_many_notifysomewhere in the process - this sets first
NETREG_UNREGISTERINGon both ends of the veth and then runssynchronize_net - it then calls
call_netdevice_notifierswithNETDEV_UNREGISTER - this is then handled by
dp_device_eventwhich callsovs_netdev_detach_dev(if a vport is found, which is the case for the veth interface attached to ovs) - this removes the rx_handlers of the device but does not prevent packages to be sent to the device
dp_device_eventthen queues the vport deletion to work in background as a ovs_lock is needed that we do not hold in the unregistration pathunregister_netdevice_many_notifycontinues to callnetdev_unregister_kobjectwhich setsreal_num_tx_queuesto 0- port deletion continues (but details are not relevant for this issue)
- at some future point the background task deletes the vport
If after 7. but before 9. a packet is send to the ovs vport (which is
not deleted at this point in time) which forwards it to the
dev_queue_xmit flow even though the device is unregistering.
In skb_tx_hash (which is called in the dev_queue_xmit) path there is
a while loop (if the packet has a rx_queue recorded) that is infinite if
dev->real_num_tx_queues is zero.
To prevent this from happening we update do_output to handle devices
without carrier the same as if the device is not found (which would
be the code path after 9. is done).
Additionally we now produce a warning in skb_tx_hash if we will hit
the infinite loop.
bpftrace (first word is function name):
_dev_queue_xmit server: real_num_tx_queues: 1, cpu: 2, pid: 28024, tid: 28024, skb_addr: 0xffff9edb6f207000, reg_state: 1 netdev_core_pick_tx server: addr: 0xffff9f0a46d4a000 real_num_tx_queues: 1, cpu: 2, pid: 28024, tid: 28024, skb_addr: 0xffff9edb6f207000, reg_state: 1 dp_device_event server: real_num_tx_queues: 1 cpu 9, pid: 21024, tid: 21024, event 2, reg_state: 1 synchronize_rcu_expedited: cpu 9, pid: 21024, tid: 21024 synchronize_rcu_expedited: cpu 9, pid: 21024, tid: 21024 synchronize_rcu_expedited: cpu 9, pid: 21024, tid: 21024 synchronize_rcu_expedited: cpu 9, pid: 21024, tid: 21024 dp_device_event server: real_num_tx_queues: 1 cpu 9, pid: 21024, tid: 21024, event 6, reg_state: 2 ovs_netdev_detach_dev server: real_num_tx_queues: 1 cpu 9, pid: 21024, tid: 21024, reg_state: 2 netdev_rx_handler_unregister server: real_num_tx_queues: 1, cpu: 9, pid: 21024, tid: 21024, reg_state: 2 synchronize_rcu_expedited: cpu 9, pid: 21024, tid: 21024 netdev_rx_handler_unregister ret server: real_num_tx_queues: 1, cpu: 9, pid: 21024, tid: 21024, reg_state: 2 dp ---truncated---
| Software | From | Fixed in |
|---|---|---|
| linux / linux_kernel | 4.3 | 5.4.293 |
| linux / linux_kernel | 5.5 | 5.10.237 |
| linux / linux_kernel | 5.11 | 5.15.181 |
| linux / linux_kernel | 5.16 | 6.1.25 |
| linux / linux_kernel | 6.2 | 6.2.12 |
| linux / linux_kernel | 6.3-rc1 | 6.3-rc1.x |
| linux / linux_kernel | 6.3-rc2 | 6.3-rc2.x |
| linux / linux_kernel | 6.3-rc3 | 6.3-rc3.x |
| linux / linux_kernel | 6.3-rc4 | 6.3-rc4.x |
| linux / linux_kernel | 6.3-rc5 | 6.3-rc5.x |
| linux / linux_kernel | 6.3-rc6 | 6.3-rc6.x |
- https://git.kernel.org/stable/c/066b86787fa3d97b7aefb5ac0a99a22dad2d15f8
- https://git.kernel.org/stable/c/284be5db6c8d06d247ed056cfc448c4f79bbb16c
- https://git.kernel.org/stable/c/56252da41426f3d01957456f13caf46ce670ea29
- https://git.kernel.org/stable/c/5efcb301523baacd98a47553d4996e924923114d
- https://git.kernel.org/stable/c/644b3051b06ba465bc7401bfae9b14963cbc8c1c
- https://git.kernel.org/stable/c/9b0dd09c1ceb35950d2884848099fccc9ec9a123
Deep Security Visibility Without the Complexity
SynScan provides clear, real-time security insights so you can monitor your attack surface, spot risks early, and act fast—without extra complexity.
- No setup fees
- 5-min deployment
- Cancel anytime
Frequently Asked Questions
A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.
CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.
A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.
Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.
Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.
SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.