CVE-2023-53489

一、漏洞信息
 漏洞编号：[CVE-2023-53489](https://nvd.nist.gov/vuln/detail/CVE-2023-53489)
 漏洞归属组件：[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:tcp/udp: Fix memleaks of sk and zerocopy skbs with TX timestamp.syzkaller reported [0] memory leaks of an UDP socket and ZEROCOPYskbs.  We can reproduce the problem with these sequences:  sk = socket(AF_INET, SOCK_DGRAM, 0)  sk.setsockopt(SOL_SOCKET, SO_TIMESTAMPING, SOF_TIMESTAMPING_TX_SOFTWARE)  sk.setsockopt(SOL_SOCKET, SO_ZEROCOPY, 1)  sk.sendto(b  , MSG_ZEROCOPY, ( 127.0.0.1 , 53))  sk.close()sendmsg() calls msg_zerocopy_alloc(), which allocates a skb, setsskb->cb->ubuf.refcnt to 1, and calls sock_hold().  Here, structubuf_info_msgzc indirectly holds a refcnt of the socket.  When theskb is sent, __skb_tstamp_tx() clones it and puts the clone intothe socket s error queue with the TX timestamp.When the original skb is received locally, skb_copy_ubufs() callsskb_unclone(), and pskb_expand_head() increments skb->cb->ubuf.refcnt.This additional count is decremented while freeing the skb, but structubuf_info_msgzc still has a refcnt, so __msg_zerocopy_callback() isnot called.The last refcnt is not released unless we retrieve the TX timestampedskb by recvmsg().  Since we clear the error queue in inet_sock_destruct()after the socket s refcnt reaches 0, there is a circular dependency.If we close() the socket holding such skbs, we never call sock_put()and leak the count, sk, and skb.TCP has the same problem, and commit e0c8bccd40fc ( net: stream:purge sk_error_queue in sk_stream_kill_queues() ) tried to fix itby calling skb_queue_purge() during close().  However, there is asmall chance that skb queued in a qdisc or device could be putinto the error queue after the skb_queue_purge() call.In __skb_tstamp_tx(), the cloned skb should not have a referenceto the ubuf to remove the circular dependency, but skb_clone() doesnot call skb_copy_ubufs() for zerocopy skb.  So, we need to callskb_orphan_frags_rx() for the cloned skb to call skb_copy_ubufs().[0]:BUG: memory leakunreferenced object 0xffff88800c6d2d00 (size 1152):  comm  syz-executor392 , pid 264, jiffies 4294785440 (age 13.044s)  hex dump (first 32 bytes):    00 00 00 00 00 00 00 00 cd af e8 81 00 00 00 00  ................    02 00 07 40 00 00 00 00 00 00 00 00 00 00 00 00  ...@............  backtrace:    [<0000000055636812>] sk_prot_alloc+0x64/0x2a0 net/core/sock.c:2024    [<0000000054d77b7a>] sk_alloc+0x3b/0x800 net/core/sock.c:2083    [<0000000066f3c7e0>] inet_create net/ipv4/af_inet.c:319 [inline]    [<0000000066f3c7e0>] inet_create+0x31e/0xe40 net/ipv4/af_inet.c:245    [<000000009b83af97>] __sock_create+0x2ab/0x550 net/socket.c:1515    [<00000000b9b11231>] sock_create net/socket.c:1566 [inline]    [<00000000b9b11231>] __sys_socket_create net/socket.c:1603 [inline]    [<00000000b9b11231>] __sys_socket_create net/socket.c:1588 [inline]    [<00000000b9b11231>] __sys_socket+0x138/0x250 net/socket.c:1636    [<000000004fb45142>] __do_sys_socket net/socket.c:1649 [inline]    [<000000004fb45142>] __se_sys_socket net/socket.c:1647 [inline]    [<000000004fb45142>] __x64_sys_socket+0x73/0xb0 net/socket.c:1647    [<0000000066999e0e>] do_syscall_x64 arch/x86/entry/common.c:50 [inline]    [<0000000066999e0e>] do_syscall_64+0x38/0x90 arch/x86/entry/common.c:80    [<0000000017f238c1>] entry_SYSCALL_64_after_hwframe+0x63/0xcdBUG: memory leakunreferenced object 0xffff888017633a00 (size 240):  comm  syz-executor392 , pid 264, jiffies 4294785440 (age 13.044s)  hex dump (first 32 bytes):    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................    00 00 00 00 00 00 00 00 00 2d 6d 0c 80 88 ff ff  .........-m.....  backtrace:    [<000000002b1c4368>] __alloc_skb+0x229/0x320 net/core/skbuff.c:497    [<00000000143579a6>] alloc_skb include/linux/skbuff.h:1265 [inline]    [<00000000143579a6>] sock_omalloc+0xaa/0x190 net/core/sock.c:2596    [<00000000be626478>] msg_zerocopy_alloc net/core/skbuff.c:1294 [inline]    [<00000000be626478>]---truncated---
 漏洞公开时间：2025-10-01 20:15:51
 漏洞创建时间：2025-10-01 20:44:50
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2023-53489
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
|  | https://git.kernel.org/stable/c/30290f210ba7426ff7592fe2eb4114b1b5bad219 |  |
|  | https://www.cve.org/CVERecord?id=CVE-2023-53489 |  |
|  | https://git.kernel.org/stable/c/cb52e7f24c1d01a536a847dff0d1d95889cc3b5c |  |
|  | https://git.kernel.org/stable/c/602fa8af44fd55a58f9e94eb673e8adad2c6cc46 |  |
|  | https://git.kernel.org/stable/c/50749f2dd6854a41830996ad302aef2ffaf011d8 |  |
|  | https://git.kernel.org/stable/c/281072fb2a7294cde7acbf5375b879f40a8001b7 |  |
|  | https://security-tracker.debian.org/tracker/CVE-2023-53489 |  |
|  | https://git.kernel.org/stable/c/43e4197dd5f6b474a8b16f8b6a42cd45cf4f9d1a |  |
|  | https://bugzilla.redhat.com/show_bug.cgi?id=2400741 |  |
|  | https://lore.kernel.org/linux-cve-announce/2025100123-CVE-2023-53489-eec5@gregkh/T |  |
|  | https://git.kernel.org/stable/c/230a5ed7d813fb516de81d23f09d7506753e41e9 |  |
|  | https://git.kernel.org/stable/c/426384dd4980040651536fef5feac4dcc4d7ee4e |  |
|  | https://lore.kernel.org/linux-cve-announce/2025100123-CVE-2023-53489-eec5@gregkh/T/#u |  |
|  | https://git.kernel.org/stable/c/1f69c086b20e27763af28145981435423f088268 |  |
|  | https://nvd.nist.gov/vuln/detail/CVE-2023-53489 |  |

</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/281072fb2a7294cde7acbf5375b879f40a8001b7 |  | ljqc |
| gregkh/linux |  | https://git.kernel.org/stable/c/1f69c086b20e27763af28145981435423f088268 |  | ljqc |
| gregkh/linux |  | https://git.kernel.org/stable/c/602fa8af44fd55a58f9e94eb673e8adad2c6cc46 |  | ljqc |
| gregkh/linux |  | https://git.kernel.org/stable/c/230a5ed7d813fb516de81d23f09d7506753e41e9 |  | ljqc |
| gregkh/linux |  | https://git.kernel.org/stable/c/43e4197dd5f6b474a8b16f8b6a42cd45cf4f9d1a |  | ljqc |
|  |  | https://git.kernel.org/stable/c/30290f210ba7426ff7592fe2eb4114b1b5bad219 |  | cvelistv5 |
|  |  | https://git.kernel.org/stable/c/cb52e7f24c1d01a536a847dff0d1d95889cc3b5c |  | cvelistv5 |
|  |  | https://git.kernel.org/stable/c/602fa8af44fd55a58f9e94eb673e8adad2c6cc46 |  | cvelistv5 |
|  |  | https://git.kernel.org/stable/c/50749f2dd6854a41830996ad302aef2ffaf011d8 |  | cvelistv5 |
|  |  | https://git.kernel.org/stable/c/281072fb2a7294cde7acbf5375b879f40a8001b7 |  | cvelistv5 |
|  |  | https://git.kernel.org/stable/c/43e4197dd5f6b474a8b16f8b6a42cd45cf4f9d1a |  | cvelistv5 |
|  |  | https://git.kernel.org/stable/c/230a5ed7d813fb516de81d23f09d7506753e41e9 |  | cvelistv5 |
|  |  | https://git.kernel.org/stable/c/426384dd4980040651536fef5feac4dcc4d7ee4e |  | cvelistv5 |
|  |  | https://git.kernel.org/stable/c/1f69c086b20e27763af28145981435423f088268 |  | cvelistv5 |

</details>

二、漏洞分析结构反馈
 影响性分析说明：
                            In the Linux kernel, the following vulnerability has been resolved:tcp/udp: Fix memleaks of sk and zerocopy skbs with TX timestamp.syzkaller reported [0] memory leaks of an UDP socket and ZEROCOPYskbs.  We can reproduce the problem with these sequences:  sk = socket(AF_INET, SOCK_DGRAM, 0)  sk.setsockopt(SOL_SOCKET, SO_TIMESTAMPING, SOF_TIMESTAMPING_TX_SOFTWARE)  sk.setsockopt(SOL_SOCKET, SO_ZEROCOPY, 1)  sk.sendto(b&#39;&#39;, MSG_ZEROCOPY, (&#39;127.0.0.1&#39;, 53))  sk.close()sendmsg() calls msg_zerocopy_alloc(), which allocates a skb, setsskb-&gt;cb-&gt;ubuf.refcnt to 1, and calls sock_hold().  Here, structubuf_info_msgzc indirectly holds a refcnt of the socket.  When theskb is sent, __skb_tstamp_tx() clones it and puts the clone intothe socket&#39;s error queue with the TX timestamp.When the original skb is received locally, skb_copy_ubufs() callsskb_unclone(), and pskb_expand_head() increments skb-&gt;cb-&gt;ubuf.refcnt.This additional count is decremented while freeing the skb, but structubuf_info_msgzc still has a refcnt, so __msg_zerocopy_callback() isnot called.The last refcnt is not released unless we retrieve the TX timestampedskb by recvmsg().  Since we clear the error queue in inet_sock_destruct()after the socket&#39;s refcnt reaches 0, there is a circular dependency.If we close() the socket holding such skbs, we never call sock_put()and leak the count, sk, and skb.TCP has the same problem, and commit e0c8bccd40fc (&#34;net: stream:purge sk_error_queue in sk_stream_kill_queues()&#34;) tried to fix itby calling skb_queue_purge() during close().  However, there is asmall chance that skb queued in a qdisc or device could be putinto the error queue after the skb_queue_purge() call.In __skb_tstamp_tx(), the cloned skb should not have a referenceto the ubuf to remove the circular dependency, but skb_clone() doesnot call skb_copy_ubufs() for zerocopy skb.  So, we need to callskb_orphan_frags_rx() for the cloned skb to call skb_copy_ubufs().[0]:BUG: memory leakunreferenced object 0xffff88800c6d2d00 (size 1152):  comm &#34;syz-executor392&#34;, pid 264, jiffies 4294785440 (age 13.044s)  hex dump (first 32 bytes):    00 00 00 00 00 00 00 00 cd af e8 81 00 00 00 00  ................    02 00 07 40 00 00 00 00 00 00 00 00 00 00 00 00  ...@............  backtrace:    [&lt;0000000055636812&gt;] sk_prot_alloc+0x64/0x2a0 net/core/sock.c:2024    [&lt;0000000054d77b7a&gt;] sk_alloc+0x3b/0x800 net/core/sock.c:2083    [&lt;0000000066f3c7e0&gt;] inet_create net/ipv4/af_inet.c:319 [inline]    [&lt;0000000066f3c7e0&gt;] inet_create+0x31e/0xe40 net/ipv4/af_inet.c:245    [&lt;000000009b83af97&gt;] __sock_create+0x2ab/0x550 net/socket.c:1515    [&lt;00000000b9b11231&gt;] sock_create net/socket.c:1566 [inline]    [&lt;00000000b9b11231&gt;] __sys_socket_create net/socket.c:1603 [inline]    [&lt;00000000b9b11231&gt;] __sys_socket_create net/socket.c:1588 [inline]    [&lt;00000000b9b11231&gt;] __sys_socket+0x138/0x250 net/socket.c:1636    [&lt;000000004fb45142&gt;] __do_sys_socket net/socket.c:1649 [inline]    [&lt;000000004fb45142&gt;] __se_sys_socket net/socket.c:1647 [inline]    [&lt;000000004fb45142&gt;] __x64_sys_socket+0x73/0xb0 net/socket.c:1647    [&lt;0000000066999e0e&gt;] do_syscall_x64 arch/x86/entry/common.c:50 [inline]    [&lt;0000000066999e0e&gt;] do_syscall_64+0x38/0x90 arch/x86/entry/common.c:80    [&lt;0000000017f238c1&gt;] entry_SYSCALL_64_after_hwframe+0x63/0xcdBUG: memory leakunreferenced object 0xffff888017633a00 (size 240):  comm &#34;syz-executor392&#34;, pid 264, jiffies 4294785440 (age 13.044s)  hex dump (first 32 bytes):    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................    00 00 00 00 00 00 00 00 00 2d 6d 0c 80 88 ff ff  .........-m.....  backtrace:    [&lt;000000002b1c4368&gt;] __alloc_skb+0x229/0x320 net/core/skbuff.c:497    [&lt;00000000143579a6&gt;] alloc_skb include/linux/skbuff.h:1265 [inline]    [&lt;00000000143579a6&gt;] sock_omalloc+0xaa/0x190 net/core/sock.c:2596    [&lt;00000000be626478&gt;] msg_zerocopy_alloc net/core/skbuff.c:1294 [inline]    [&lt;00000
 openEuler评分：
  5.5
 Vector：CVSS：3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
 受影响版本排查(受影响/不受影响)：
  1.openEuler-20.03-LTS-SP4(4.19.90):受影响
2.master(6.12.33):不受影响
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.openEuler-20.03-LTS-SP4(4.19.90):正常修复
2.master(6.12.33):不受影响-漏洞代码不能被攻击者触发
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
关闭

内容风险标识

评论 (5)

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

内容风险标识

CVE-2023-53489

评论 (5)

搜索帮助

src-openEuler/kernel
关闭