CVE-2024-56788

一、漏洞信息
 漏洞编号：[CVE-2024-56788](https://nvd.nist.gov/vuln/detail/CVE-2024-56788)
 漏洞归属组件：[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：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:net: ethernet: oa_tc6: fix tx skb race condition between reference pointersThere are two skb pointers to manage tx skb s enqueued from n/w stack.waiting_tx_skb pointer points to the tx skb which needs to be processedand ongoing_tx_skb pointer points to the tx skb which is being processed.SPI thread prepares the tx data chunks from the tx skb pointed by theongoing_tx_skb pointer. When the tx skb pointed by the ongoing_tx_skb isprocessed, the tx skb pointed by the waiting_tx_skb is assigned toongoing_tx_skb and the waiting_tx_skb pointer is assigned with NULL.Whenever there is a new tx skb from n/w stack, it will be assigned towaiting_tx_skb pointer if it is NULL. Enqueuing and processing of a tx skbhandled in two different threads.Consider a scenario where the SPI thread processed an ongoing_tx_skb andit moves next tx skb from waiting_tx_skb pointer to ongoing_tx_skb pointerwithout doing any NULL check. At this time, if the waiting_tx_skb pointeris NULL then ongoing_tx_skb pointer is also assigned with NULL. Afterthat, if a new tx skb is assigned to waiting_tx_skb pointer by the n/wstack and there is a chance to overwrite the tx skb pointer with NULL inthe SPI thread. Finally one of the tx skb will be left as unhandled,resulting packet missing and memory leak.- Consider the below scenario where the TXC reported from the previoustransfer is 10 and ongoing_tx_skb holds an tx ethernet frame which can betransported in 20 TXCs and waiting_tx_skb is still NULL.	tx_credits = 10; /* 21 are filled in the previous transfer */	ongoing_tx_skb = 20;	waiting_tx_skb = NULL; /* Still NULL */- So, (tc6->ongoing_tx_skb || tc6->waiting_tx_skb) becomes true.- After oa_tc6_prepare_spi_tx_buf_for_tx_skbs()	ongoing_tx_skb = 10;	waiting_tx_skb = NULL; /* Still NULL */- Perform SPI transfer.- Process SPI rx buffer to get the TXC from footers.- Now let s assume previously filled 21 TXCs are freed so we are good totransport the next remaining 10 tx chunks from ongoing_tx_skb.	tx_credits = 21;	ongoing_tx_skb = 10;	waiting_tx_skb = NULL;- So, (tc6->ongoing_tx_skb || tc6->waiting_tx_skb) becomes true again.- In the oa_tc6_prepare_spi_tx_buf_for_tx_skbs()	ongoing_tx_skb = NULL;	waiting_tx_skb = NULL;- Now the below bad case might happen,Thread1 (oa_tc6_start_xmit)	Thread2 (oa_tc6_spi_thread_handler)---------------------------	------------------------------------ if waiting_tx_skb is NULL				- if ongoing_tx_skb is NULL				- ongoing_tx_skb = waiting_tx_skb- waiting_tx_skb = skb				- waiting_tx_skb = NULL				...				- ongoing_tx_skb = NULL- if waiting_tx_skb is NULL- waiting_tx_skb = skbTo overcome the above issue, protect the moving of tx skb reference fromwaiting_tx_skb pointer to ongoing_tx_skb pointer and assigning new tx skbto waiting_tx_skb pointer, so that the other thread can t access thewaiting_tx_skb pointer until the current thread completes moving the txskb reference safely.
 漏洞公开时间：2025-01-11 21:15:29
 漏洞创建时间：2025-01-22 16:37:04
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2024-56788
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/1f2eb6c32bae04b375bb7a0aedbeefb6dbbcb775 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/e592b5110b3e9393881b0a019d86832bbf71a47f |  |
| suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-56788 | https://bugzilla.suse.com/show_bug.cgi?id=1235754 |
| suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2024-56788 | https://bugzilla.suse.com/show_bug.cgi?id=1235754 |
| suse_bugzilla | https://git.kernel.org/stable/c/1f2eb6c32bae04b375bb7a0aedbeefb6dbbcb775 | https://bugzilla.suse.com/show_bug.cgi?id=1235754 |
| suse_bugzilla | https://git.kernel.org/stable/c/e592b5110b3e9393881b0a019d86832bbf71a47f | https://bugzilla.suse.com/show_bug.cgi?id=1235754 |
| suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-56788.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1235754 |
| suse_bugzilla | https://bugzilla.redhat.com/show_bug.cgi?id=2337107 | https://bugzilla.suse.com/show_bug.cgi?id=1235754 |
| redhat_bugzilla | https://lore.kernel.org/linux-cve-announce/2025011147-CVE-2024-56788-7a74@gregkh/T | https://bugzilla.redhat.com/show_bug.cgi?id=2337107 |
| debian |  | https://security-tracker.debian.org/tracker/CVE-2024-56788 |
| anolis |  | https://anas.openanolis.cn/cves/detail/CVE-2024-56788 |

</details>

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

| 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源  |
| ------- | -------- | ------- | -------- | --------- |
| linux_kernel | 6.12.7 | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=1f2eb6c32bae04b375bb7a0aedbeefb6dbbcb775 | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=53fbde8ab21e8c2c6187159cc17fc10cbf20900a | linuxkernelcves |
| linux_kernel | 6.13-rc4 | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e592b5110b3e9393881b0a019d86832bbf71a47f | https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=53fbde8ab21e8c2c6187159cc17fc10cbf20900a | linuxkernelcves |

</details>

二、漏洞分析结构反馈
 影响性分析说明：
  Reserved.
 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.openEuler-22.03-LTS-SP3(5.10.0):不受影响
3.openEuler-22.03-LTS-SP4(5.10.0):不受影响
4.master(6.6.0):不受影响
5.openEuler-24.03-LTS(6.6.0):不受影响
6.openEuler-24.03-LTS-Next(6.6.0):不受影响
7.openEuler-24.03-LTS-SP1(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.master(6.6.0):不受影响-漏洞代码不能被攻击者触发
2.openEuler-24.03-LTS-Next(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.openEuler-24.03-LTS(6.6.0):不受影响-漏洞代码不存在
7.openEuler-24.03-LTS-SP1(6.6.0):不受影响-漏洞代码不存在

src-openEuler/kernel
关闭

内容风险标识

评论 (10)

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

内容风险标识

CVE-2024-56788

评论 (10)

搜索帮助

src-openEuler/kernel
关闭