CVE-2024-27405

一、漏洞信息
 漏洞编号：[CVE-2024-27405](https://nvd.nist.gov/vuln/detail/CVE-2024-27405)
 漏洞归属组件：[kernel](https://gitee.com/src-openeuler/kernel)
 漏洞归属的版本：4.19.140,4.19.194,4.19.90,5.10.0,6.1.0,6.1.14,6.1.19,6.1.5,6.1.6,6.1.8,6.4.0,6.6.0
 CVSS V3.0分值：
  BaseScore：7.5 High
  Vector：CVSS：3.0/
 漏洞简述：
  In the Linux kernel, the following vulnerability has been resolved:usb: gadget: ncm: Avoid dropping datagrams of properly parsed NTBsIt is observed sometimes when tethering is used over NCM with Windows 11as host, at some instances, the gadget_giveback has one byte appended atthe end of a proper NTB. When the NTB is parsed, unwrap call looks forany leftover bytes in SKB provided by u_ether and if there are any pendingbytes, it treats them as a separate NTB and parses it. But in case thesecond NTB (as per unwrap call) is faulty/corrupt, all the datagrams thatwere parsed properly in the first NTB and saved in rx_list are dropped.Adding a few custom traces showed the following:[002] d..1  7828.532866: dwc3_gadget_giveback: ep1out:req 000000003868811a length 1025/16384 zsI ==> 0[002] d..1  7828.532867: ncm_unwrap_ntb: K: ncm_unwrap_ntb toprocess: 1025[002] d..1  7828.532867: ncm_unwrap_ntb: K: ncm_unwrap_ntb nth: 1751999342[002] d..1  7828.532868: ncm_unwrap_ntb: K: ncm_unwrap_ntb seq: 0xce67[002] d..1  7828.532868: ncm_unwrap_ntb: K: ncm_unwrap_ntb blk_len: 0x400[002] d..1  7828.532868: ncm_unwrap_ntb: K: ncm_unwrap_ntb ndp_len: 0x10[002] d..1  7828.532869: ncm_unwrap_ntb: K: Parsed NTB with 1 framesIn this case, the giveback is of 1025 bytes and block length is 1024.The rest 1 byte (which is 0x00) won t be parsed resulting in drop ofall datagrams in rx_list.Same is case with packets of size 2048:[002] d..1  7828.557948: dwc3_gadget_giveback: ep1out:req 0000000011dfd96e length 2049/16384 zsI ==> 0[002] d..1  7828.557949: ncm_unwrap_ntb: K: ncm_unwrap_ntb nth: 1751999342[002] d..1  7828.557950: ncm_unwrap_ntb: K: ncm_unwrap_ntb blk_len: 0x800Lecroy shows one byte coming in extra confirming that the byte is comingin from PC: Transfer 2959 - Bytes Transferred(1025)  Timestamp((18.524 843 590) - Transaction 8391 - Data(1025 bytes) Timestamp(18.524 843 590) --- Packet 4063861       Data(1024 bytes)       Duration(2.117us) Idle(14.700ns) Timestamp(18.524 843 590) --- Packet 4063863       Data(1 byte)       Duration(66.160ns) Time(282.000ns) Timestamp(18.524 845 722)According to Windows driver, no ZLP is needed if wBlockLength is non-zero,because the non-zero wBlockLength has already told the function side thesize of transfer to be expected. However, there are in-market NCM devicesthat rely on ZLP as long as the wBlockLength is multiple of wMaxPacketSize.To deal with such devices, it pads an extra 0 at end so the transfer is nolonger multiple of wMaxPacketSize.
 漏洞公开时间：2024-05-17 20:15:10
 漏洞创建时间：2024-05-17 20:27:48
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2024-27405
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/059285e04ebb273d32323fbad5431c5b94f77e48 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/2b7ec68869d50ea998908af43b643bca7e54577e |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/2cb66b62a5d64ccf09b0591ab86fb085fa491fc5 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/35b604a37ec70d68b19dafd10bbacf1db505c9ca |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/57ca0e16f393bb21d69734e536e383a3a4c665fd |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/76c51146820c5dac629f21deafab0a7039bc3ccd |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/a31cf46d108dabce3df80b3e5c07661e24912151 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/c7f43900bc723203d7554d299a2ce844054fab8e |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://lists.debian.org/debian-lts-announce/2024/06/msg00017.html |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://lists.debian.org/debian-lts-announce/2024/06/msg00020.html |  |
| suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-27405 | https://bugzilla.suse.com/show_bug.cgi?id=1224423 |
| suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-27405.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1224423 |
| suse_bugzilla | https://git.kernel.org/stable/c/059285e04ebb273d32323fbad5431c5b94f77e48 | https://bugzilla.suse.com/show_bug.cgi?id=1224423 |
| suse_bugzilla | https://git.kernel.org/stable/c/a31cf46d108dabce3df80b3e5c07661e24912151 | https://bugzilla.suse.com/show_bug.cgi?id=1224423 |
| suse_bugzilla | https://git.kernel.org/stable/c/57ca0e16f393bb21d69734e536e383a3a4c665fd | https://bugzilla.suse.com/show_bug.cgi?id=1224423 |
| suse_bugzilla | https://git.kernel.org/stable/c/2cb66b62a5d64ccf09b0591ab86fb085fa491fc5 | https://bugzilla.suse.com/show_bug.cgi?id=1224423 |
| suse_bugzilla | https://git.kernel.org/stable/c/35b604a37ec70d68b19dafd10bbacf1db505c9ca | https://bugzilla.suse.com/show_bug.cgi?id=1224423 |
| suse_bugzilla | https://git.kernel.org/stable/c/2b7ec68869d50ea998908af43b643bca7e54577e | https://bugzilla.suse.com/show_bug.cgi?id=1224423 |
| suse_bugzilla | https://git.kernel.org/stable/c/c7f43900bc723203d7554d299a2ce844054fab8e | https://bugzilla.suse.com/show_bug.cgi?id=1224423 |
| suse_bugzilla | https://git.kernel.org/stable/c/76c51146820c5dac629f21deafab0a7039bc3ccd | https://bugzilla.suse.com/show_bug.cgi?id=1224423 |
| suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2024-27405 | https://bugzilla.suse.com/show_bug.cgi?id=1224423 |
| ubuntu | https://www.cve.org/CVERecord?id=CVE-2024-27405 | https://ubuntu.com/security/CVE-2024-27405 |
| ubuntu | https://git.kernel.org/linus/76c51146820c5dac629f21deafab0a7039bc3ccd (6.8-rc6) | https://ubuntu.com/security/CVE-2024-27405 |
| ubuntu | https://git.kernel.org/stable/c/059285e04ebb273d32323fbad5431c5b94f77e48 | https://ubuntu.com/security/CVE-2024-27405 |
| ubuntu | https://git.kernel.org/stable/c/a31cf46d108dabce3df80b3e5c07661e24912151 | https://ubuntu.com/security/CVE-2024-27405 |
| ubuntu | https://git.kernel.org/stable/c/57ca0e16f393bb21d69734e536e383a3a4c665fd | https://ubuntu.com/security/CVE-2024-27405 |
| ubuntu | https://git.kernel.org/stable/c/2cb66b62a5d64ccf09b0591ab86fb085fa491fc5 | https://ubuntu.com/security/CVE-2024-27405 |
| ubuntu | https://git.kernel.org/stable/c/35b604a37ec70d68b19dafd10bbacf1db505c9ca | https://ubuntu.com/security/CVE-2024-27405 |
| ubuntu | https://git.kernel.org/stable/c/2b7ec68869d50ea998908af43b643bca7e54577e | https://ubuntu.com/security/CVE-2024-27405 |
| ubuntu | https://git.kernel.org/stable/c/c7f43900bc723203d7554d299a2ce844054fab8e | https://ubuntu.com/security/CVE-2024-27405 |
| ubuntu | https://git.kernel.org/stable/c/76c51146820c5dac629f21deafab0a7039bc3ccd | https://ubuntu.com/security/CVE-2024-27405 |
| ubuntu | https://ubuntu.com/security/notices/USN-6820-1 | https://ubuntu.com/security/CVE-2024-27405 |
| ubuntu | https://ubuntu.com/security/notices/USN-6821-1 | https://ubuntu.com/security/CVE-2024-27405 |
| ubuntu | https://ubuntu.com/security/notices/USN-6821-2 | https://ubuntu.com/security/CVE-2024-27405 |
| ubuntu | https://ubuntu.com/security/notices/USN-6828-1 | https://ubuntu.com/security/CVE-2024-27405 |
| ubuntu | https://ubuntu.com/security/notices/USN-6820-2 | https://ubuntu.com/security/CVE-2024-27405 |
| ubuntu | https://ubuntu.com/security/notices/USN-6821-3 | https://ubuntu.com/security/CVE-2024-27405 |
| ubuntu | https://ubuntu.com/security/notices/USN-6831-1 | https://ubuntu.com/security/CVE-2024-27405 |
| ubuntu | https://ubuntu.com/security/notices/USN-6821-4 | https://ubuntu.com/security/CVE-2024-27405 |
| ubuntu | https://nvd.nist.gov/vuln/detail/CVE-2024-27405 | https://ubuntu.com/security/CVE-2024-27405 |
| ubuntu | https://launchpad.net/bugs/cve/CVE-2024-27405 | https://ubuntu.com/security/CVE-2024-27405 |
| ubuntu | https://security-tracker.debian.org/tracker/CVE-2024-27405 | https://ubuntu.com/security/CVE-2024-27405 |
| debian |  | https://security-tracker.debian.org/tracker/CVE-2024-27405 |

</details>

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

| 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源  |
| ------- | -------- | ------- | -------- | --------- |
| linux |  | https://git.kernel.org/linus/76c51146820c5dac629f21deafab0a7039bc3ccd | https://git.kernel.org/linus/9f6ce4240a2bf456402c15c06768059e5973f28c | ubuntu |

</details>

二、漏洞分析结构反馈
 影响性分析说明：
          In the Linux kernel, the following vulnerability has been resolved:usb: gadget: ncm: Avoid dropping datagrams of properly parsed NTBsIt is observed sometimes when tethering is used over NCM with Windows 11as host, at some instances, the gadget_giveback has one byte appended atthe end of a proper NTB. When the NTB is parsed, unwrap call looks forany leftover bytes in SKB provided by u_ether and if there are any pendingbytes, it treats them as a separate NTB and parses it. But in case thesecond NTB (as per unwrap call) is faulty/corrupt, all the datagrams thatwere parsed properly in the first NTB and saved in rx_list are dropped.Adding a few custom traces showed the following:[002] d..1  7828.532866: dwc3_gadget_giveback: ep1out:req 000000003868811a length 1025/16384 zsI ==> 0[002] d..1  7828.532867: ncm_unwrap_ntb: K: ncm_unwrap_ntb toprocess: 1025[002] d..1  7828.532867: ncm_unwrap_ntb: K: ncm_unwrap_ntb nth: 1751999342[002] d..1  7828.532868: ncm_unwrap_ntb: K: ncm_unwrap_ntb seq: 0xce67[002] d..1  7828.532868: ncm_unwrap_ntb: K: ncm_unwrap_ntb blk_len: 0x400[002] d..1  7828.532868: ncm_unwrap_ntb: K: ncm_unwrap_ntb ndp_len: 0x10[002] d..1  7828.532869: ncm_unwrap_ntb: K: Parsed NTB with 1 framesIn this case, the giveback is of 1025 bytes and block length is 1024.The rest 1 byte (which is 0x00) won t be parsed resulting in drop ofall datagrams in rx_list.Same is case with packets of size 2048:[002] d..1  7828.557948: dwc3_gadget_giveback: ep1out:req 0000000011dfd96e length 2049/16384 zsI ==> 0[002] d..1  7828.557949: ncm_unwrap_ntb: K: ncm_unwrap_ntb nth: 1751999342[002] d..1  7828.557950: ncm_unwrap_ntb: K: ncm_unwrap_ntb blk_len: 0x800Lecroy shows one byte coming in extra confirming that the byte is comingin from PC: Transfer 2959 - Bytes Transferred(1025)  Timestamp((18.524 843 590) - Transaction 8391 - Data(1025 bytes) Timestamp(18.524 843 590) --- Packet 4063861       Data(1024 bytes)       Duration(2.117us) Idle(14.700ns) Timestamp(18.524 843 590) --- Packet 4063863       Data(1 byte)       Duration(66.160ns) Time(282.000ns) Timestamp(18.524 845 722)According to Windows driver, no ZLP is needed if wBlockLength is non-zero,because the non-zero wBlockLength has already told the function side thesize of transfer to be expected. However, there are in-market NCM devicesthat rely on ZLP as long as the wBlockLength is multiple of wMaxPacketSize.To deal with such devices, it pads an extra 0 at end so the transfer is nolonger multiple of wMaxPacketSize.    
 openEuler评分：
  3.3
 Vector：CVSS：3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
 受影响版本排查(受影响/不受影响)：
  1.openEuler-22.03-LTS-SP3(5.10.0):受影响
2.openEuler-24.03-LTS(6.6.0):受影响
3.openEuler-20.03-LTS-SP4(4.19.90):不受影响
4.openEuler-22.03-LTS-SP1(5.10.0):不受影响
5.openEuler-22.03-LTS-SP4(5.10.0):不受影响
6.master(6.1.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-SP1(5.10.0):否
3.openEuler-22.03-LTS-SP3(5.10.0):否
4.master(6.1.0):否
5.openEuler-24.03-LTS(6.6.0):否
6.openEuler-24.03-LTS-Next(6.6.0):否
7.openEuler-22.03-LTS-SP4(5.10.0):否

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

src-openEuler/kernel
Closed

Content Risk Flag

Comments (51)

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

Content Risk Flag

CVE-2024-27405

Comments (51)

Search

src-openEuler/kernel
Closed