CVE-2024-56687

一、漏洞信息
 漏洞编号：[CVE-2024-56687](https://nvd.nist.gov/vuln/detail/CVE-2024-56687)
 漏洞归属组件：[kernel](https://gitee.com/src-openeuler/kernel)
 漏洞归属的版本：4.19.140,4.19.194,4.19.90,5.10.0,6.1.19,6.1.8,6.4.0,6.6.0
 CVSS V3.0分值：
  BaseScore：5.5 Medium
  Vector：CVSS：3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
 漏洞简述：
  In the Linux kernel, the following vulnerability has been resolved:usb: musb: Fix hardware lockup on first Rx endpoint requestThere is a possibility that a request s callback could be invoked fromusb_ep_queue() (call trace below, supplemented with missing calls):req->complete from usb_gadget_giveback_request	(drivers/usb/gadget/udc/core.c:999)usb_gadget_giveback_request from musb_g_giveback	(drivers/usb/musb/musb_gadget.c:147)musb_g_giveback from rxstate	(drivers/usb/musb/musb_gadget.c:784)rxstate from musb_ep_restart	(drivers/usb/musb/musb_gadget.c:1169)musb_ep_restart from musb_ep_restart_resume_work	(drivers/usb/musb/musb_gadget.c:1176)musb_ep_restart_resume_work from musb_queue_resume_work	(drivers/usb/musb/musb_core.c:2279)musb_queue_resume_work from musb_gadget_queue	(drivers/usb/musb/musb_gadget.c:1241)musb_gadget_queue from usb_ep_queue	(drivers/usb/gadget/udc/core.c:300)According to the docstring of usb_ep_queue(), this should not happen: Note that @req s ->complete() callback must never be called from withinusb_ep_queue() as that can create deadlock situations. In fact, a hardware lockup might occur in the following sequence:1. The gadget is initialized using musb_gadget_enable().2. Meanwhile, a packet arrives, and the RXPKTRDY flag is set, raising an   interrupt.3. If IRQs are enabled, the interrupt is handled, but musb_g_rx() finds an   empty queue (next_request() returns NULL). The interrupt flag has   already been cleared by the glue layer handler, but the RXPKTRDY flag   remains set.4. The first request is enqueued using usb_ep_queue(), leading to the call   of req->complete(), as shown in the call trace above.5. If the callback enables IRQs and another packet is waiting, step (3)   repeats. The request queue is empty because usb_g_giveback() removes the   request before invoking the callback.6. The endpoint remains locked up, as the interrupt triggered by hardware   setting the RXPKTRDY flag has been handled, but the flag itself remains   set.For this scenario to occur, it is only necessary for IRQs to be enabled atsome point during the complete callback. This happens with the USB Ethernetgadget, whose rx_complete() callback calls netif_rx(). If called in thetask context, netif_rx() disables the bottom halves (BHs). When the BHs arere-enabled, IRQs are also enabled to allow soft IRQs to be processed. Thegadget itself is initialized at module load (or at boot if built-in), butthe first request is enqueued when the network interface is brought up,triggering rx_complete() in the task context via ioctl(). If a packetarrives while the interface is down, it can prevent the interface fromreceiving any further packets from the USB host.The situation is quite complicated with many parties involved. Thisparticular issue can be resolved in several possible ways:1. Ensure that callbacks never enable IRQs. This would be difficult to   enforce, as discovering how netif_rx() interacts with interrupts was   already quite challenging and u_ether is not the only function driver.   Similar  bugs  could be hidden in other drivers as well.2. Disable MUSB interrupts in musb_g_giveback() before calling the callback   and re-enable them afterwars (by calling musb_{dis,en}able_interrupts(),   for example). This would ensure that MUSB interrupts are not handled   during the callback, even if IRQs are enabled. In fact, it would allow   IRQs to be enabled when releasing the lock. However, this feels like an   inelegant hack.3. Modify the interrupt handler to clear the RXPKTRDY flag if the request   queue is empty. While this approach also feels like a hack, it wastes   CPU time by attempting to handle incoming packets when the software is   not ready to process them.4. Flush the Rx FIFO instead of calling rxstate() in musb_ep_restart().   This ensures that the hardware can receive packets when there is at   least one request in the queue. Once I---truncated---
 漏洞公开时间：2024-12-28 18:15:12
 漏洞创建时间：2024-12-28 18:32:28
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2024-56687
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/0c89445e6d475b78d37b64ae520831cd43af7db4 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/3fc137386c4620305bbc2a216868c53f9245670a |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/5906ee3693674d734177df13a519a21bb03f730d |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/c749500b28cae67410792096133ee7f282439c51 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/f05ad9755bb294328c3d0f429164ac6d4d08c548 |  |
| suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-56687 | https://bugzilla.suse.com/show_bug.cgi?id=1235537 |
| suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2024-56687 | https://bugzilla.suse.com/show_bug.cgi?id=1235537 |
| suse_bugzilla | https://git.kernel.org/stable/c/0c89445e6d475b78d37b64ae520831cd43af7db4 | https://bugzilla.suse.com/show_bug.cgi?id=1235537 |
| suse_bugzilla | https://git.kernel.org/stable/c/3fc137386c4620305bbc2a216868c53f9245670a | https://bugzilla.suse.com/show_bug.cgi?id=1235537 |
| suse_bugzilla | https://git.kernel.org/stable/c/5906ee3693674d734177df13a519a21bb03f730d | https://bugzilla.suse.com/show_bug.cgi?id=1235537 |
| suse_bugzilla | https://git.kernel.org/stable/c/c749500b28cae67410792096133ee7f282439c51 | https://bugzilla.suse.com/show_bug.cgi?id=1235537 |
| suse_bugzilla | https://git.kernel.org/stable/c/f05ad9755bb294328c3d0f429164ac6d4d08c548 | https://bugzilla.suse.com/show_bug.cgi?id=1235537 |
| suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-56687.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1235537 |
| suse_bugzilla | https://bugzilla.redhat.com/show_bug.cgi?id=2334669 | https://bugzilla.suse.com/show_bug.cgi?id=1235537 |
| redhat_bugzilla | https://lore.kernel.org/linux-cve-announce/2024122834-CVE-2024-56687-99e2@gregkh/T | https://bugzilla.redhat.com/show_bug.cgi?id=2334669 |
| debian |  | https://security-tracker.debian.org/tracker/CVE-2024-56687 |

</details>

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

| 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源  |
| ------- | -------- | ------- | -------- | --------- |
| linux_kernel | 6.1.120 | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c749500b28cae67410792096133ee7f282439c51Issue | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=baebdf48c360080710f80699eea3affbb13d6c65 | linuxkernelcves |
| linux_kernel | 6.6.64 | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=5906ee3693674d734177df13a519a21bb03f730dIssue | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=baebdf48c360080710f80699eea3affbb13d6c65 | linuxkernelcves |
| linux_kernel | 6.11.11 | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f05ad9755bb294328c3d0f429164ac6d4d08c548Issue | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=baebdf48c360080710f80699eea3affbb13d6c65 | linuxkernelcves |
| linux_kernel | 6.12.2 | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=0c89445e6d475b78d37b64ae520831cd43af7db4Issue | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=baebdf48c360080710f80699eea3affbb13d6c65 | linuxkernelcves |
| linux_kernel | 6.13-rc1 | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=3fc137386c4620305bbc2a216868c53f9245670aPlease | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=baebdf48c360080710f80699eea3affbb13d6c65 | linuxkernelcves |

</details>

二、漏洞分析结构反馈
 影响性分析说明：
  In the Linux kernel, the following vulnerability has been resolved:usb: musb: Fix hardware lockup on first Rx endpoint requestThere is a possibility that a request s callback could be invoked fromusb_ep_queue() (call trace below, supplemented with missing calls):req->complete from usb_gadget_giveback_request(drivers/usb/gadget/udc/core.c:999)usb_gadget_giveback_request from musb_g_giveback(drivers/usb/musb/musb_gadget.c:147)musb_g_giveback from rxstate(drivers/usb/musb/musb_gadget.c:784)rxstate from musb_ep_restart(drivers/usb/musb/musb_gadget.c:1169)musb_ep_restart from musb_ep_restart_resume_work(drivers/usb/musb/musb_gadget.c:1176)musb_ep_restart_resume_work from musb_queue_resume_work(drivers/usb/musb/musb_core.c:2279)musb_queue_resume_work from musb_gadget_queue(drivers/usb/musb/musb_gadget.c:1241)musb_gadget_queue from usb_ep_queue(drivers/usb/gadget/udc/core.c:300)According to the docstring of usb_ep_queue(), this should not happen: Note that @req s ->complete() callback must never be called from withinusb_ep_queue() as that can create deadlock situations. In fact, a hardware lockup might occur in the following sequence:1. The gadget is initialized using musb_gadget_enable().2. Meanwhile, a packet arrives, and the RXPKTRDY flag is set, raising an   interrupt.3. If IRQs are enabled, the interrupt is handled, but musb_g_rx() finds an   empty queue (next_request() returns NULL). The interrupt flag has   already been cleared by the glue layer handler, but the RXPKTRDY flag   remains set.4. The first request is enqueued using usb_ep_queue(), leading to the call   of req->complete(), as shown in the call trace above.5. If the callback enables IRQs and another packet is waiting, step (3)   repeats. The request queue is empty because usb_g_giveback() removes the   request before invoking the callback.6. The endpoint remains locked up, as the interrupt triggered by hardware   setting the RXPKTRDY flag has been handled, but the flag itself remains   set.For this scenario to occur, it is only necessary for IRQs to be enabled atsome point during the complete callback. This happens with the USB Ethernetgadget, whose rx_complete() callback calls netif_rx(). If called in thetask context, netif_rx() disables the bottom halves (BHs). When the BHs arere-enabled, IRQs are also enabled to allow soft IRQs to be processed. Thegadget itself is initialized at module load (or at boot if built-in), butthe first request is enqueued when the network interface is brought up,triggering rx_complete() in the task context via ioctl(). If a packetarrives while the interface is down, it can prevent the interface fromreceiving any further packets from the USB host.The situation is quite complicated with many parties involved. Thisparticular issue can be resolved in several possible ways:1. Ensure that callbacks never enable IRQs. This would be difficult to   enforce, as discovering how netif_rx() interacts with interrupts was   already quite challenging and u_ether is not the only function driver.   Similar  bugs  could be hidden in other drivers as well.2. Disable MUSB interrupts in musb_g_giveback() before calling the callback   and re-enable them afterwars (by calling musb_{dis,en}able_interrupts(),   for example). This would ensure that MUSB interrupts are not handled   during the callback, even if IRQs are enabled. In fact, it would allow   IRQs to be enabled when releasing the lock. However, this feels like an   inelegant hack.3. Modify the interrupt handler to clear the RXPKTRDY flag if the request   queue is empty. While this approach also feels like a hack, it wastes   CPU time by attempting to handle incoming packets when the software is   not ready to process them.4. Flush the Rx FIFO instead of calling rxstate() in musb_ep_restart().   This ensures that the hardware can receive packets when there is at   least one request in the queue. Once I---truncated---
 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-24.03-LTS(6.6.0):受影响
2.openEuler-24.03-LTS-SP1(6.6.0):受影响
3.openEuler-20.03-LTS-SP4(4.19.90):不受影响
4.openEuler-22.03-LTS-SP3(5.10.0):不受影响
5.openEuler-22.03-LTS-SP4(5.10.0):不受影响
6.master(6.6.0):不受影响
7.openEuler-24.03-LTS-Next(6.6.0):不受影响

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

原因说明：
  1.openEuler-24.03-LTS(6.6.0):正常修复
2.openEuler-24.03-LTS-SP1(6.6.0):正常修复
3.master(6.6.0):不受影响-漏洞代码不能被攻击者触发
4.openEuler-24.03-LTS-Next(6.6.0):不受影响-漏洞代码不能被攻击者触发
5.openEuler-20.03-LTS-SP4(4.19.90):不受影响-漏洞代码不存在
6.openEuler-22.03-LTS-SP3(5.10.0):不受影响-漏洞代码不存在
7.openEuler-22.03-LTS-SP4(5.10.0):不受影响-漏洞代码不存在

三、漏洞修复
安全公告链接：https://www.openeuler.org/zh/security/safety-bulletin/detail/?id=openEuler-SA-2025-1097

src-openEuler/kernel

Content Risk Flag

Comments (9)

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

Content Risk Flag

CVE-2024-56687

Comments (9)

Search

src-openEuler/kernel