CVE-2023-53188

一、漏洞信息
 漏洞编号：[CVE-2023-53188](https://nvd.nist.gov/vuln/detail/CVE-2023-53188)
 漏洞归属组件：[kernel](https://gitee.com/src-openeuler/kernel)
 漏洞归属的版本：4.19.140,4.19.194,4.19.90,5.10.0,6.1.19,6.4.0,6.6.0
 CVSS V3.0分值：
  BaseScore：N/A None
  Vector：CVSS：3.0/
 漏洞简述：
  In the Linux kernel, the following vulnerability has been resolved:net: openvswitch: fix race on port outputassume the following setup on a single machine:1. An openvswitch instance with one bridge and default flows2. two network namespaces  server  and  client 3. two ovs interfaces  server  and  client  on the bridge4. for each ovs interface a veth pair with a matching name and 32 rx and   tx queues5. move the ends of the veth pairs to the respective network namespaces6. assign ip addresses to each of the veth ends in the namespaces (needs   to be the same subnet)7. start some http server on the server network namespace8. test if a client in the client namespace can reach the http serverwhen following the actions below the host has a chance of getting a cpustuck in a infinite loop:1. send a large amount of parallel requests to the http server (around   3000 curls should work)2. 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 stuckmessage. If this does not happen just retry.Below there is also the output of bpftrace for the functions mentionedin the output.The series of events happening here is:1. the network namespace is deleted calling   `unregister_netdevice_many_notify` somewhere in the process2. this sets first `NETREG_UNREGISTERING` on both ends of the veth and   then runs `synchronize_net`3. it then calls `call_netdevice_notifiers` with `NETDEV_UNREGISTER`4. this is then handled by `dp_device_event` which calls   `ovs_netdev_detach_dev` (if a vport is found, which is the case for   the veth interface attached to ovs)5. this removes the rx_handlers of the device but does not prevent   packages to be sent to the device6. `dp_device_event` then queues the vport deletion to work in   background as a ovs_lock is needed that we do not hold in the   unregistration path7. `unregister_netdevice_many_notify` continues to call   `netdev_unregister_kobject` which sets `real_num_tx_queues` to 08. port deletion continues (but details are not relevant for this issue)9. at some future point the background task deletes the vportIf after 7. but before 9. a packet is send to the ovs vport (which isnot 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 isa 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 deviceswithout carrier the same as if the device is not found (which wouldbe the code path after 9. is done).Additionally we now produce a warning in `skb_tx_hash` if we will hitthe 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: 1netdev_core_pick_tx server: addr: 0xffff9f0a46d4a000 real_num_tx_queues: 1, cpu: 2, pid: 28024, tid: 28024, skb_addr: 0xffff9edb6f207000, reg_state: 1dp_device_event server: real_num_tx_queues: 1 cpu 9, pid: 21024, tid: 21024, event 2, reg_state: 1synchronize_rcu_expedited: cpu 9, pid: 21024, tid: 21024synchronize_rcu_expedited: cpu 9, pid: 21024, tid: 21024synchronize_rcu_expedited: cpu 9, pid: 21024, tid: 21024synchronize_rcu_expedited: cpu 9, pid: 21024, tid: 21024dp_device_event server: real_num_tx_queues: 1 cpu 9, pid: 21024, tid: 21024, event 6, reg_state: 2ovs_netdev_detach_dev server: real_num_tx_queues: 1 cpu 9, pid: 21024, tid: 21024, reg_state: 2netdev_rx_handler_unregister server: real_num_tx_queues: 1, cpu: 9, pid: 21024, tid: 21024, reg_state: 2synchronize_rcu_expedited: cpu 9, pid: 21024, tid: 21024netdev_rx_handler_unregister ret server: real_num_tx_queues: 1, cpu: 9, pid: 21024, tid: 21024, reg_state: 2dp_---truncated---
 漏洞公开时间：2025-09-15 22:15:41
 漏洞创建时间：2025-09-15 22:37:36
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2023-53188
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
|  | 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 |  |
|  | https://lore.kernel.org/linux-cve-announce/2025091557-CVE-2023-53188-373f@gregkh/T/#u |  |
|  | https://security-tracker.debian.org/tracker/CVE-2023-53188 |  |
|  | https://www.cve.org/CVERecord?id=CVE-2023-53188 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2023-53188 |  |
|  | https://lore.kernel.org/linux-cve-announce/2025091557-CVE-2023-53188-373f@gregkh/T |  |
|  | https://bugzilla.redhat.com/show_bug.cgi?id=2395416 |  |
|  | https://docs.bell-sw.com/security/cves/CVE-2023-53188 |  |

</details>

漏洞分析指导链接：
  https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
 漏洞数据来源:
  七彩瞬析开源风险感知平台
 漏洞补丁信息：
  <details>
<summary>详情(点击展开)</summary>

| 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源  |
| ------- | -------- | ------- | -------- | --------- |
| gregkh/linux |  | https://git.kernel.org/stable/c/284be5db6c8d06d247ed056cfc448c4f79bbb16c.patch |  | ljqc |
| gregkh/linux |  | https://git.kernel.org/stable/c/56252da41426f3d01957456f13caf46ce670ea29 |  | ljqc |
| gregkh/linux |  | https://git.kernel.org/stable/c/5efcb301523baacd98a47553d4996e924923114d |  | ljqc |
| gregkh/linux |  | https://git.kernel.org/stable/c/644b3051b06ba465bc7401bfae9b14963cbc8c1c |  | ljqc |
| gregkh/linux |  | https://git.kernel.org/stable/c/9b0dd09c1ceb35950d2884848099fccc9ec9a123 |  | ljqc |
|  |  | https://git.kernel.org/stable/c/066b86787fa3d97b7aefb5ac0a99a22dad2d15f8 |  | nvd |
|  |  | https://git.kernel.org/stable/c/284be5db6c8d06d247ed056cfc448c4f79bbb16c |  | nvd |
|  |  | https://git.kernel.org/stable/c/56252da41426f3d01957456f13caf46ce670ea29 |  | nvd |
|  |  | https://git.kernel.org/stable/c/5efcb301523baacd98a47553d4996e924923114d |  | nvd |
|  |  | https://git.kernel.org/stable/c/644b3051b06ba465bc7401bfae9b14963cbc8c1c |  | nvd |
|  |  | https://git.kernel.org/stable/c/9b0dd09c1ceb35950d2884848099fccc9ec9a123 |  | nvd |

</details>
 
二、漏洞分析结构反馈
 影响性分析说明：
                          
 openEuler评分：
   
 受影响版本排查(受影响/不受影响)：
  1.master(6.12.33):
2.openEuler-20.03-LTS-SP4(4.19.90):
3.openEuler-22.03-LTS-SP3(5.10.0):
4.openEuler-22.03-LTS-SP4(5.10.0):
5.openEuler-24.03-LTS:
6.openEuler-24.03-LTS-Next:
7.openEuler-24.03-LTS-SP1:
8.openEuler-24.03-LTS-SP2:

修复是否涉及abi变化(是/否)：
  1.master(6.12.33):
2.openEuler-20.03-LTS-SP4(4.19.90):
3.openEuler-22.03-LTS-SP3(5.10.0):
4.openEuler-22.03-LTS-SP4(5.10.0):
5.openEuler-24.03-LTS:
6.openEuler-24.03-LTS-Next:
7.openEuler-24.03-LTS-SP1:
8.openEuler-24.03-LTS-SP2:

原因说明：
  1.master(6.12.33):
2.openEuler-20.03-LTS-SP4(4.19.90):
3.openEuler-22.03-LTS-SP3(5.10.0):
4.openEuler-22.03-LTS-SP4(5.10.0):
5.openEuler-24.03-LTS:
6.openEuler-24.03-LTS-Next:
7.openEuler-24.03-LTS-SP1:
8.openEuler-24.03-LTS-SP2:

src-openEuler/kernel

内容风险标识

评论 (3)

src-openEuler/kernel .gitee-modal { width: 500px !important; }

内容风险标识

CVE-2023-53188

评论 (3)

搜索帮助

src-openEuler/kernel