CVE-2024-40979

一、漏洞信息
 漏洞编号：[CVE-2024-40979](https://nvd.nist.gov/vuln/detail/CVE-2024-40979)
 漏洞归属组件：[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 V2.0分值：
  BaseScore：0.0 Medium
  Vector：CVSS：2.0/
 漏洞简述：
  In the Linux kernel, the following vulnerability has been resolved:wifi: ath12k: fix kernel crash during resumeCurrently during resume, QMI target memory is not properly handled, resultingin kernel crash in case DMA remap is not supported:BUG: Bad page state in process kworker/u16:54  pfn:36e80page: refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x36e80page dumped because: nonzero _refcountCall Trace: bad_page free_page_is_bad_report __free_pages_ok __free_pages dma_direct_free dma_free_attrs ath12k_qmi_free_target_mem_chunk ath12k_qmi_msg_mem_request_cbThe reason is:Once ath12k module is loaded, firmware sends memory request to host. In caseDMA remap not supported, ath12k refuses the first request due to failure inallocating with large segment size:ath12k_pci 0000:04:00.0: qmi firmware request memory requestath12k_pci 0000:04:00.0: qmi mem seg type 1 size 7077888ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 8454144ath12k_pci 0000:04:00.0: qmi dma allocation failed (7077888 B type 1), will try later with small sizeath12k_pci 0000:04:00.0: qmi delays mem_request 2ath12k_pci 0000:04:00.0: qmi firmware request memory requestLater firmware comes back with more but small segments and allocationsucceeds:ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 262144ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 65536ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 524288Now ath12k is working. If suspend is triggered, firmware will be reloadedduring resume. As same as before, firmware requests two large segments atfirst. In ath12k_qmi_msg_mem_request_cb() segment count and size areassigned:	ab->qmi.mem_seg_count == 2	ab->qmi.target_mem[0].size == 7077888	ab->qmi.target_mem[1].size == 8454144Then allocation failed like before and ath12k_qmi_free_target_mem_chunk()is called to free all allocated segments. Note the first segment is skippedbecause its v.addr is cleared due to allocation failure:	chunk->v.addr = dma_alloc_coherent()Also note that this leaks that segment because it has not been freed.While freeing the second segment, a size of 8454144 is passed todma_free_coherent(). However remember that this segment is allocated atthe first time firmware is loaded, before suspend. So its real size is524288, much smaller than 8454144. As a result kernel found we are freeingsome memory which is in use and thus cras---truncated---
 漏洞公开时间：2024-07-12 21:15:19
 漏洞创建时间：2024-07-13 17:56:41
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2024-40979
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/303c017821d88ebad887814114d4e5966d320b28 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/bb50a4e711ff95348ad53641acb1306d89eb4c3a |  |
| suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-40979 | https://bugzilla.suse.com/show_bug.cgi?id=1227855 |
| suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2024-40979 | https://bugzilla.suse.com/show_bug.cgi?id=1227855 |
| suse_bugzilla | https://git.kernel.org/stable/c/303c017821d88ebad887814114d4e5966d320b28 | https://bugzilla.suse.com/show_bug.cgi?id=1227855 |
| suse_bugzilla | https://git.kernel.org/stable/c/bb50a4e711ff95348ad53641acb1306d89eb4c3a | https://bugzilla.suse.com/show_bug.cgi?id=1227855 |
| suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-40979.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1227855 |
| ubuntu | https://www.cve.org/CVERecord?id=CVE-2024-40979 | https://ubuntu.com/security/CVE-2024-40979 |
| ubuntu | https://git.kernel.org/linus/303c017821d88ebad887814114d4e5966d320b28 (6.10-rc1) | https://ubuntu.com/security/CVE-2024-40979 |
| ubuntu | https://git.kernel.org/stable/c/bb50a4e711ff95348ad53641acb1306d89eb4c3a | https://ubuntu.com/security/CVE-2024-40979 |
| ubuntu | https://git.kernel.org/stable/c/303c017821d88ebad887814114d4e5966d320b28 | https://ubuntu.com/security/CVE-2024-40979 |
| ubuntu | https://nvd.nist.gov/vuln/detail/CVE-2024-40979 | https://ubuntu.com/security/CVE-2024-40979 |
| ubuntu | https://launchpad.net/bugs/cve/CVE-2024-40979 | https://ubuntu.com/security/CVE-2024-40979 |
| ubuntu | https://security-tracker.debian.org/tracker/CVE-2024-40979 | https://ubuntu.com/security/CVE-2024-40979 |
| debian |  | https://security-tracker.debian.org/tracker/CVE-2024-40979 |

</details>

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

| 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源  |
| ------- | -------- | ------- | -------- | --------- |
| linux |  | https://git.kernel.org/linus/303c017821d88ebad887814114d4e5966d320b28 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |

</details>

二、漏洞分析结构反馈
 影响性分析说明：
    In the Linux kernel, the following vulnerability has been resolved:wifi: ath12k: fix kernel crash during resumeCurrently during resume, QMI target memory is not properly handled, resultingin kernel crash in case DMA remap is not supported:BUG: Bad page state in process kworker/u16:54  pfn:36e80page: refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x36e80page dumped because: nonzero _refcountCall Trace: bad_page free_page_is_bad_report __free_pages_ok __free_pages dma_direct_free dma_free_attrs ath12k_qmi_free_target_mem_chunk ath12k_qmi_msg_mem_request_cbThe reason is:Once ath12k module is loaded, firmware sends memory request to host. In caseDMA remap not supported, ath12k refuses the first request due to failure inallocating with large segment size:ath12k_pci 0000:04:00.0: qmi firmware request memory requestath12k_pci 0000:04:00.0: qmi mem seg type 1 size 7077888ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 8454144ath12k_pci 0000:04:00.0: qmi dma allocation failed (7077888 B type 1), will try later with small sizeath12k_pci 0000:04:00.0: qmi delays mem_request 2ath12k_pci 0000:04:00.0: qmi firmware request memory requestLater firmware comes back with more but small segments and allocationsucceeds:ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 262144ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 65536ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 524288Now ath12k is working. If suspend is triggered, firmware will be reloadedduring resume. As same as before, firmware requests two large segments atfirst. In ath12k_qmi_msg_mem_request_cb() segment count and size areassigned:ab->qmi.mem_seg_count == 2ab->qmi.target_mem[0].size == 7077888ab->qmi.target_mem[1].size == 8454144Then allocation failed like before and ath12k_qmi_free_target_mem_chunk()is called to free all allocated segments. Note the first segment is skippedbecause its v.addr is cleared due to allocation failure:chunk->v.addr = dma_alloc_coherent()Also note that this leaks that segment because it has not been freed.While freeing the second segment, a size of 8454144 is passed todma_free_coherent(). However remember that this segment is allocated atthe first time firmware is loaded, before suspend. So its real size is524288, much smaller than 8454144. As a result kernel found we are freeingsome memory which is in use and thus cras---truncated--- 
 openEuler评分：
  4.4
 Vector：CVSS：2.0/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
 受影响版本排查(受影响/不受影响)：
  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.openEuler-22.03-LTS-SP4(5.10.0):不受影响
5.master(6.1.0):不受影响
6.openEuler-24.03-LTS(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-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):否

src-openEuler/kernel

内容风险标识

评论 (7)

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

内容风险标识

CVE-2024-40979

评论 (7)

搜索帮助

src-openEuler/kernel