CVE-2024-41048

一、漏洞信息
 漏洞编号：[CVE-2024-41048](https://nvd.nist.gov/vuln/detail/CVE-2024-41048)
 漏洞归属组件：[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 None
  Vector：CVSS：2.0/
 漏洞简述：
  In the Linux kernel, the following vulnerability has been resolved:skmsg: Skip zero length skb in sk_msg_recvmsgWhen running BPF selftests (./test_progs -t sockmap_basic) on a Loongarchplatform, the following kernel panic occurs:  [...]  Oops[#1]:  CPU: 22 PID: 2824 Comm: test_progs Tainted: G           OE  6.10.0-rc2+ #18  Hardware name: LOONGSON Dabieshan/Loongson-TC542F0, BIOS Loongson-UDK2018     ... ...     ra: 90000000048bf6c0 sk_msg_recvmsg+0x120/0x560    ERA: 9000000004162774 copy_page_to_iter+0x74/0x1c0   CRMD: 000000b0 (PLV0 -IE -DA +PG DACF=CC DACM=CC -WE)   PRMD: 0000000c (PPLV0 +PIE +PWE)   EUEN: 00000007 (+FPE +SXE +ASXE -BTE)   ECFG: 00071c1d (LIE=0,2-4,10-12 VS=7)  ESTAT: 00010000 [PIL] (IS= ECode=1 EsubCode=0)   BADV: 0000000000000040   PRID: 0014c011 (Loongson-64bit, Loongson-3C5000)  Modules linked in: bpf_testmod(OE) xt_CHECKSUM xt_MASQUERADE xt_conntrack  Process test_progs (pid: 2824, threadinfo=0000000000863a31, task=...)  Stack : ...  Call Trace:  [<9000000004162774>] copy_page_to_iter+0x74/0x1c0  [<90000000048bf6c0>] sk_msg_recvmsg+0x120/0x560  [<90000000049f2b90>] tcp_bpf_recvmsg_parser+0x170/0x4e0  [<90000000049aae34>] inet_recvmsg+0x54/0x100  [<900000000481ad5c>] sock_recvmsg+0x7c/0xe0  [<900000000481e1a8>] __sys_recvfrom+0x108/0x1c0  [<900000000481e27c>] sys_recvfrom+0x1c/0x40  [<9000000004c076ec>] do_syscall+0x8c/0xc0  [<9000000003731da4>] handle_syscall+0xc4/0x160  Code: ...  ---[ end trace 0000000000000000 ]---  Kernel panic - not syncing: Fatal exception  Kernel relocated by 0x3510000   .text @ 0x9000000003710000   .data @ 0x9000000004d70000   .bss  @ 0x9000000006469400  ---[ end Kernel panic - not syncing: Fatal exception ]---  [...]This crash happens every time when running sockmap_skb_verdict_shutdownsubtest in sockmap_basic.This crash is because a NULL pointer is passed to page_address() in thesk_msg_recvmsg(). Due to the different implementations depending on thearchitecture, page_address(NULL) will trigger a panic on Loongarchplatform but not on x86 platform. So this bug was hidden on x86 platformfor a while, but now it is exposed on Loongarch platform. The root causeis that a zero length skb (skb->len == 0) was put on the queue.This zero length skb is a TCP FIN packet, which was sent by shutdown(),invoked in test_sockmap_skb_verdict_shutdown():	shutdown(p1, SHUT_WR);In this case, in sk_psock_skb_ingress_enqueue(), num_sge is zero, and nopage is put to this sge (see sg_set_page in sg_set_page), but this emptysge is queued into ingress_msg list.And in sk_msg_recvmsg(), this empty sge is used, and a NULL page is got bysg_page(sge). Pass this NULL page to copy_page_to_iter(), which passes itto kmap_local_page() and to page_address(), then kernel panics.To solve this, we should skip this zero length skb. So in sk_msg_recvmsg(),if copy is zero, that means it s a zero length skb, skip invokingcopy_page_to_iter(). We are using the EFAULT return triggered bycopy_page_to_iter to check for is_fin in tcp_bpf.c.
 漏洞公开时间：2024-07-29 23:15:13
 漏洞创建时间：2024-07-29 16:28:10
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2024-41048
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/195b7bcdfc5adc5b2468f279dd9eb7eebd2e7632 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/b180739b45a38b4caa88fe16bb5273072e6613dc |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/f0c18025693707ec344a70b6887f7450bf4c826b |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/f8bd689f37f4198a4c61c4684f591ba639595b97 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/fb61d7b9fb6ef0032de469499a54dab4c7260d0d |  |
| suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-41048 | https://bugzilla.suse.com/show_bug.cgi?id=1228565 |
| suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-41048.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1228565 |
| suse_bugzilla | https://git.kernel.org/stable/c/195b7bcdfc5adc5b2468f279dd9eb7eebd2e7632 | https://bugzilla.suse.com/show_bug.cgi?id=1228565 |
| suse_bugzilla | https://git.kernel.org/stable/c/fb61d7b9fb6ef0032de469499a54dab4c7260d0d | https://bugzilla.suse.com/show_bug.cgi?id=1228565 |
| suse_bugzilla | https://git.kernel.org/stable/c/b180739b45a38b4caa88fe16bb5273072e6613dc | https://bugzilla.suse.com/show_bug.cgi?id=1228565 |
| suse_bugzilla | https://git.kernel.org/stable/c/f8bd689f37f4198a4c61c4684f591ba639595b97 | https://bugzilla.suse.com/show_bug.cgi?id=1228565 |
| suse_bugzilla | https://git.kernel.org/stable/c/f0c18025693707ec344a70b6887f7450bf4c826b | https://bugzilla.suse.com/show_bug.cgi?id=1228565 |
| suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2024-41048 | https://bugzilla.suse.com/show_bug.cgi?id=1228565 |
| ubuntu | https://www.cve.org/CVERecord?id=CVE-2024-41048 | https://ubuntu.com/security/CVE-2024-41048 |
| ubuntu | https://git.kernel.org/linus/f0c18025693707ec344a70b6887f7450bf4c826b (6.10) | https://ubuntu.com/security/CVE-2024-41048 |
| ubuntu | https://git.kernel.org/stable/c/195b7bcdfc5adc5b2468f279dd9eb7eebd2e7632 | https://ubuntu.com/security/CVE-2024-41048 |
| ubuntu | https://git.kernel.org/stable/c/fb61d7b9fb6ef0032de469499a54dab4c7260d0d | https://ubuntu.com/security/CVE-2024-41048 |
| ubuntu | https://git.kernel.org/stable/c/b180739b45a38b4caa88fe16bb5273072e6613dc | https://ubuntu.com/security/CVE-2024-41048 |
| ubuntu | https://git.kernel.org/stable/c/f8bd689f37f4198a4c61c4684f591ba639595b97 | https://ubuntu.com/security/CVE-2024-41048 |
| ubuntu | https://git.kernel.org/stable/c/f0c18025693707ec344a70b6887f7450bf4c826b | https://ubuntu.com/security/CVE-2024-41048 |
| ubuntu | https://nvd.nist.gov/vuln/detail/CVE-2024-41048 | https://ubuntu.com/security/CVE-2024-41048 |
| ubuntu | https://launchpad.net/bugs/cve/CVE-2024-41048 | https://ubuntu.com/security/CVE-2024-41048 |
| ubuntu | https://security-tracker.debian.org/tracker/CVE-2024-41048 | https://ubuntu.com/security/CVE-2024-41048 |
| debian |  | https://security-tracker.debian.org/tracker/CVE-2024-41048 |
| anolis |  | https://anas.openanolis.cn/cves/detail/CVE-2024-41048 |
| mageia |  | http://advisories.mageia.org/MGASA-2024-0278.html |

</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/f0c18025693707ec344a70b6887f7450bf4c826b | https://git.kernel.org/linus/604326b41a6fb9b4a78b6179335decee0365cd8c | ubuntu |

</details>

二、漏洞分析结构反馈
 影响性分析说明：
    In the Linux kernel, the following vulnerability has been resolved:skmsg: Skip zero length skb in sk_msg_recvmsgWhen running BPF selftests (./test_progs -t sockmap_basic) on a Loongarchplatform, the following kernel panic occurs:  [...]  Oops[#1]:  CPU: 22 PID: 2824 Comm: test_progs Tainted: G           OE  6.10.0-rc2+ #18  Hardware name: LOONGSON Dabieshan/Loongson-TC542F0, BIOS Loongson-UDK2018     ... ...     ra: 90000000048bf6c0 sk_msg_recvmsg+0x120/0x560    ERA: 9000000004162774 copy_page_to_iter+0x74/0x1c0   CRMD: 000000b0 (PLV0 -IE -DA +PG DACF=CC DACM=CC -WE)   PRMD: 0000000c (PPLV0 +PIE +PWE)   EUEN: 00000007 (+FPE +SXE +ASXE -BTE)   ECFG: 00071c1d (LIE=0,2-4,10-12 VS=7)  ESTAT: 00010000 [PIL] (IS= ECode=1 EsubCode=0)   BADV: 0000000000000040   PRID: 0014c011 (Loongson-64bit, Loongson-3C5000)  Modules linked in: bpf_testmod(OE) xt_CHECKSUM xt_MASQUERADE xt_conntrack  Process test_progs (pid: 2824, threadinfo=0000000000863a31, task=...)  Stack : ...  Call Trace:  [<9000000004162774>] copy_page_to_iter+0x74/0x1c0  [<90000000048bf6c0>] sk_msg_recvmsg+0x120/0x560  [<90000000049f2b90>] tcp_bpf_recvmsg_parser+0x170/0x4e0  [<90000000049aae34>] inet_recvmsg+0x54/0x100  [<900000000481ad5c>] sock_recvmsg+0x7c/0xe0  [<900000000481e1a8>] __sys_recvfrom+0x108/0x1c0  [<900000000481e27c>] sys_recvfrom+0x1c/0x40  [<9000000004c076ec>] do_syscall+0x8c/0xc0  [<9000000003731da4>] handle_syscall+0xc4/0x160  Code: ...  ---[ end trace 0000000000000000 ]---  Kernel panic - not syncing: Fatal exception  Kernel relocated by 0x3510000   .text @ 0x9000000003710000   .data @ 0x9000000004d70000   .bss  @ 0x9000000006469400  ---[ end Kernel panic - not syncing: Fatal exception ]---  [...]This crash happens every time when running sockmap_skb_verdict_shutdownsubtest in sockmap_basic.This crash is because a NULL pointer is passed to page_address() in thesk_msg_recvmsg(). Due to the different implementations depending on thearchitecture, page_address(NULL) will trigger a panic on Loongarchplatform but not on x86 platform. So this bug was hidden on x86 platformfor a while, but now it is exposed on Loongarch platform. The root causeis that a zero length skb (skb->len == 0) was put on the queue.This zero length skb is a TCP FIN packet, which was sent by shutdown(),invoked in test_sockmap_skb_verdict_shutdown():shutdown(p1, SHUT_WR);In this case, in sk_psock_skb_ingress_enqueue(), num_sge is zero, and nopage is put to this sge (see sg_set_page in sg_set_page), but this emptysge is queued into ingress_msg list.And in sk_msg_recvmsg(), this empty sge is used, and a NULL page is got bysg_page(sge). Pass this NULL page to copy_page_to_iter(), which passes itto kmap_local_page() and to page_address(), then kernel panics.To solve this, we should skip this zero length skb. So in sk_msg_recvmsg(),if copy is zero, that means it s a zero length skb, skip invokingcopy_page_to_iter(). We are using the EFAULT return triggered bycopy_page_to_iter to check for is_fin in tcp_bpf.c. 
 openEuler评分：
  6.5
 Vector：CVSS：2.0/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
 受影响版本排查(受影响/不受影响)：
  1.openEuler-22.03-LTS-SP1(5.10.0):受影响
2.openEuler-22.03-LTS-SP3(5.10.0):受影响
3.openEuler-22.03-LTS-SP4(5.10.0):受影响
4.openEuler-24.03-LTS(6.6.0):受影响
5.openEuler-20.03-LTS-SP4(4.19.90):不受影响
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-SP1(5.10.0):否
3.openEuler-22.03-LTS-SP3(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-22.03-LTS-SP4(5.10.0):否

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

@yangyingliang ,@jiaoff ,@guohaocs2c ,@hanjun-guo ,@woqidaideshi ,@newbeats ,@zhangyi089 ,@colyli ,@thundertown ,@htforge ,@chiqijun ,@lengchao ,@zhujianwei001 ,@kylin-mayukun ,@wangxiongfeng ,@wkfxxx ,@SuperSix173 ,@jentlestea ,@oskernel0719 ,@gasonchen 
**issue处理注意事项:** 
**1. 当前issue受影响的分支提交pr时, 须在pr描述中填写当前issue编号进行关联, 否则无法关闭当前issue;**
**2. 模板内容需要填写完整, 无论是受影响或者不受影响都需要填写完整内容,未引入的分支不需要填写, 否则无法关闭当前issue;**
**3. 以下为模板中需要填写完整的内容, 请复制到评论区回复, 注: 内容的标题名称(影响性分析说明, openEuler评分, 受影响版本排查(受影响/不受影响), 修复是否涉及abi变化(是/否))不能省略,省略后cve-manager将无法正常解析填写内容.**
************************************************************************
影响性分析说明:

openEuler评分: (评分和向量)

受影响版本排查(受影响/不受影响): 
1.master(6.1.0):
2.openEuler-20.03-LTS-SP4(4.19.90):
3.openEuler-22.03-LTS-SP1(5.10.0):
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-Next(6.6.0):

修复是否涉及abi变化(是/否)：
1.master(6.1.0):
2.openEuler-20.03-LTS-SP4(4.19.90):
3.openEuler-22.03-LTS-SP1(5.10.0):
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-Next(6.6.0):

-----------------------------------------------------------------------
issue处理具体操作请参考: 
https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
pr关联issue具体操作请参考:
https://gitee.com/help/articles/4142

<table><tr><th white-space: nowrap;>参考网址</th> <th white-space: nowrap;>关联pr</th> <th white-space: nowrap;>状态</th> <th white-space: nowrap;>补丁链接</th></tr><tr><td rowspan="1">https://nvd.nist.gov/vuln/detail/CVE-2024-41048</td><td>None</td><td>None</td><td><a href=https://git.kernel.org/stable/c/195b7bcdfc5adc5b2468f279dd9eb7eebd2e7632>https://git.kernel.org/stable/c/195b7bcdfc5adc5b2468f279dd9eb7eebd2e7632</a><br /><a href=https://git.kernel.org/stable/c/f8bd689f37f4198a4c61c4684f591ba639595b97>https://git.kernel.org/stable/c/f8bd689f37f4198a4c61c4684f591ba639595b97</a><br /><a href=https://git.kernel.org/stable/c/b180739b45a38b4caa88fe16bb5273072e6613dc>https://git.kernel.org/stable/c/b180739b45a38b4caa88fe16bb5273072e6613dc</a><br /><a href=https://git.kernel.org/stable/c/fb61d7b9fb6ef0032de469499a54dab4c7260d0d>https://git.kernel.org/stable/c/fb61d7b9fb6ef0032de469499a54dab4c7260d0d</a><br /><a href=https://git.kernel.org/stable/c/f0c18025693707ec344a70b6887f7450bf4c826b>https://git.kernel.org/stable/c/f0c18025693707ec344a70b6887f7450bf4c826b</a></td></tr><tr><td rowspan="1">https://ubuntu.com/security/CVE-2024-41048</td><td>None</td><td>None</td><td><a href=https://discourse.ubuntu.com/c/ubuntu-pro>https://discourse.ubuntu.com/c/ubuntu-pro</a></td></tr><tr><td rowspan="1">https://www.opencve.io/cve/CVE-2024-41048</td><td>None</td><td>None</td><td><a href=https://git.kernel.org/stable/c/195b7bcdfc5adc5b2468f279dd9eb7eebd2e7632>https://git.kernel.org/stable/c/195b7bcdfc5adc5b2468f279dd9eb7eebd2e7632</a><br /><a href=https://git.kernel.org/stable/c/f8bd689f37f4198a4c61c4684f591ba639595b97>https://git.kernel.org/stable/c/f8bd689f37f4198a4c61c4684f591ba639595b97</a><br /><a href=https://git.kernel.org/stable/c/b180739b45a38b4caa88fe16bb5273072e6613dc>https://git.kernel.org/stable/c/b180739b45a38b4caa88fe16bb5273072e6613dc</a><br /><a href=https://git.kernel.org/stable/c/fb61d7b9fb6ef0032de469499a54dab4c7260d0d>https://git.kernel.org/stable/c/fb61d7b9fb6ef0032de469499a54dab4c7260d0d</a><br /><a href=https://git.kernel.org/stable/c/f0c18025693707ec344a70b6887f7450bf4c826b>https://git.kernel.org/stable/c/f0c18025693707ec344a70b6887f7450bf4c826b</a></td></tr><tr><td>https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2024-41048</td><td></td><td></td><td></td></tr><tr><td>https://security-tracker.debian.org/tracker/CVE-2024-41048</td><td></td><td></td><td></td></tr></table>

> 说明：补丁链接仅供初步排查参考，实际可用性请人工再次确认，补丁下载验证可使用[CVE补丁工具](https://gitee.com/openeuler/cve-manager/blob/master/cve-agency-manager/cve_tracking/README.md)。
若补丁不准确，烦请在此issue下评论 '/report-patch 参考网址 补丁链接1,补丁链接2' 反馈正确信息，便于我们不断优化工具，不胜感激。
如 /report-patch https://security-tracker.debian.org/tracker/CVE-2021-3997 https://github.com/systemd/systemd/commit/5b1cf7a9be37e20133c0208005274ce4a5b5c6a1

CVE-2024-41048

影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:

skmsg: Skip zero length skb in sk_msg_recvmsg

When running BPF selftests (./test_progs -t sockmap_basic) on a Loongarch
platform, the following kernel panic occurs:

[...]
  Oops[#1]:
  CPU: 22 PID: 2824 Comm: test_progs Tainted: G           OE  6.10.0-rc2+ #18
  Hardware name: LOONGSON Dabieshan/Loongson-TC542F0, BIOS Loongson-UDK2018
     ... ...
     ra: 90000000048bf6c0 sk_msg_recvmsg+0x120/0x560
    ERA: 9000000004162774 copy_page_to_iter+0x74/0x1c0
   CRMD: 000000b0 (PLV0 -IE -DA +PG DACF=CC DACM=CC -WE)
   PRMD: 0000000c (PPLV0 +PIE +PWE)
   EUEN: 00000007 (+FPE +SXE +ASXE -BTE)
   ECFG: 00071c1d (LIE=0,2-4,10-12 VS=7)
  ESTAT: 00010000 [PIL] (IS= ECode=1 EsubCode=0)
   BADV: 0000000000000040
   PRID: 0014c011 (Loongson-64bit, Loongson-3C5000)
  Modules linked in: bpf_testmod(OE) xt_CHECKSUM xt_MASQUERADE xt_conntrack
  Process test_progs (pid: 2824, threadinfo=0000000000863a31, task=...)
  Stack : ...
  Call Trace:
  [&lt;9000000004162774&gt;] copy_page_to_iter+0x74/0x1c0
  [&lt;90000000048bf6c0&gt;] sk_msg_recvmsg+0x120/0x560
  [&lt;90000000049f2b90&gt;] tcp_bpf_recvmsg_parser+0x170/0x4e0
  [&lt;90000000049aae34&gt;] inet_recvmsg+0x54/0x100
  [&lt;900000000481ad5c&gt;] sock_recvmsg+0x7c/0xe0
  [&lt;900000000481e1a8&gt;] __sys_recvfrom+0x108/0x1c0
  [&lt;900000000481e27c&gt;] sys_recvfrom+0x1c/0x40
  [&lt;9000000004c076ec&gt;] do_syscall+0x8c/0xc0
  [&lt;9000000003731da4&gt;] handle_syscall+0xc4/0x160
  Code: ...
  ---[ end trace 0000000000000000 ]---
  Kernel panic - not syncing: Fatal exception
  Kernel relocated by 0x3510000
   .text @ 0x9000000003710000
   .data @ 0x9000000004d70000
   .bss  @ 0x9000000006469400
  ---[ end Kernel panic - not syncing: Fatal exception ]---
  [...]

This crash happens every time when running sockmap_skb_verdict_shutdown
subtest in sockmap_basic.

This crash is because a NULL pointer is passed to page_address() in the
sk_msg_recvmsg(). Due to the different implementations depending on the
architecture, page_address(NULL) will trigger a panic on Loongarch
platform but not on x86 platform. So this bug was hidden on x86 platform
for a while, but now it is exposed on Loongarch platform. The root cause
is that a zero length skb (skb-&gt;len == 0) was put on the queue.

This zero length skb is a TCP FIN packet, which was sent by shutdown(),
invoked in test_sockmap_skb_verdict_shutdown():

shutdown(p1, SHUT_WR);

In this case, in sk_psock_skb_ingress_enqueue(), num_sge is zero, and no
page is put to this sge (see sg_set_page in sg_set_page), but this empty
sge is queued into ingress_msg list.

And in sk_msg_recvmsg(), this empty sge is used, and a NULL page is got by
sg_page(sge). Pass this NULL page to copy_page_to_iter(), which passes it
to kmap_local_page() and to page_address(), then kernel panics.

To solve this, we should skip this zero length skb. So in sk_msg_recvmsg(),
if copy is zero, that means it&#39;s a zero length skb, skip invoking
copy_page_to_iter(). We are using the EFAULT return triggered by
copy_page_to_iter to check for is_fin in tcp_bpf.c.

The Linux kernel CVE team has assigned CVE-2024-41048 to this issue.

openEuler评分:(评分和向量)
5.5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

受影响版本排查(受影响/不受影响):
1.openEuler-20.03-LTS-SP4:不受影响
2.openEuler-22.03-LTS-SP1:受影响
3.openEuler-22.03-LTS-SP3:受影响
4.openEuler-22.03-LTS-SP4:不受影响
5.master(6.1.0):不受影响
6.openEuler-24.03-LTS:受影响
7.openEuler-24.03-LTS-Next:不受影响

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

@ 经过 cve-manager 解析, 已分析的内容如下表所示:
| 状态  | 需分析 | 内容 |
|:--:|:--:|---------|
|已分析|1.影响性分析说明|In the Linux kernel, the following vulnerability has been resolved:skmsg: Skip zero length skb in sk_msg_recvmsgWhen running BPF selftests (./test_progs -t sockmap_basic) on a Loongarchplatform, the following kernel panic occurs:  [...]  Oops[#1]:  CPU: 22 PID: 2824 Comm: test_progs Tainted: G           OE  6.10.0-rc2+ #18  Hardware name: LOONGSON Dabieshan/Loongson-TC542F0, BIOS Loongson-UDK2018     ... ...     ra: 90000000048bf6c0 sk_msg_recvmsg+0x120/0x560    ERA: 9000000004162774 copy_page_to_iter+0x74/0x1c0   CRMD: 000000b0 (PLV0 -IE -DA +PG DACF=CC DACM=CC -WE)   PRMD: 0000000c (PPLV0 +PIE +PWE)   EUEN: 00000007 (+FPE +SXE +ASXE -BTE)   ECFG: 00071c1d (LIE=0,2-4,10-12 VS=7)  ESTAT: 00010000 [PIL] (IS= ECode=1 EsubCode=0)   BADV: 0000000000000040   PRID: 0014c011 (Loongson-64bit, Loongson-3C5000)  Modules linked in: bpf_testmod(OE) xt_CHECKSUM xt_MASQUERADE xt_conntrack  Process test_progs (pid: 2824, threadinfo=0000000000863a31, task=...)  Stack : ...  Call Trace:  [&lt;9000000004162774&gt;] copy_page_to_iter+0x74/0x1c0  [&lt;90000000048bf6c0&gt;] sk_msg_recvmsg+0x120/0x560  [&lt;90000000049f2b90&gt;] tcp_bpf_recvmsg_parser+0x170/0x4e0  [&lt;90000000049aae34&gt;] inet_recvmsg+0x54/0x100  [&lt;900000000481ad5c&gt;] sock_recvmsg+0x7c/0xe0  [&lt;900000000481e1a8&gt;] __sys_recvfrom+0x108/0x1c0  [&lt;900000000481e27c&gt;] sys_recvfrom+0x1c/0x40  [&lt;9000000004c076ec&gt;] do_syscall+0x8c/0xc0  [&lt;9000000003731da4&gt;] handle_syscall+0xc4/0x160  Code: ...  ---[ end trace 0000000000000000 ]---  Kernel panic - not syncing: Fatal exception  Kernel relocated by 0x3510000   .text @ 0x9000000003710000   .data @ 0x9000000004d70000   .bss  @ 0x9000000006469400  ---[ end Kernel panic - not syncing: Fatal exception ]---  [...]This crash happens every time when running sockmap_skb_verdict_shutdownsubtest in sockmap_basic.This crash is because a NULL pointer is passed to page_address() in thesk_msg_recvmsg(). Due to the different implementations depending on thearchitecture, page_address(NULL) will trigger a panic on Loongarchplatform but not on x86 platform. So this bug was hidden on x86 platformfor a while, but now it is exposed on Loongarch platform. The root causeis that a zero length skb (skb-&gt;len == 0) was put on the queue.This zero length skb is a TCP FIN packet, which was sent by shutdown(),invoked in test_sockmap_skb_verdict_shutdown():shutdown(p1, SHUT_WR);In this case, in sk_psock_skb_ingress_enqueue(), num_sge is zero, and nopage is put to this sge (see sg_set_page in sg_set_page), but this emptysge is queued into ingress_msg list.And in sk_msg_recvmsg(), this empty sge is used, and a NULL page is got bysg_page(sge). Pass this NULL page to copy_page_to_iter(), which passes itto kmap_local_page() and to page_address(), then kernel panics.To solve this, we should skip this zero length skb. So in sk_msg_recvmsg(),if copy is zero, that means it&#39;s a zero length skb, skip invokingcopy_page_to_iter(). We are using the EFAULT return triggered bycopy_page_to_iter to check for is_fin in tcp_bpf.c.The Linux kernel CVE team has assigned CVE-2024-41048 to this issue.|
|已分析|2.openEulerScore|5.5|
|已分析|3.openEulerVector|AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H|
|已分析|4.受影响版本排查|openEuler-22.03-LTS-SP1:受影响,openEuler-22.03-LTS-SP3:受影响,openEuler-24.03-LTS:受影响,openEuler-20.03-LTS-SP4:不受影响,openEuler-22.03-LTS-SP4:不受影响,master:不受影响,openEuler-24.03-LTS-Next:不受影响|
|已分析|5.修复是否涉及abi变化|openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS-SP1:否,openEuler-22.03-LTS-SP3:否,master:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否,openEuler-22.03-LTS-SP4:否|

**请确认分析内容的准确性, 确认无误后, 您可以进行后续步骤, 否则您可以继续分析.**