CVE-2024-43914

一、漏洞信息
 漏洞编号：[CVE-2024-43914](https://nvd.nist.gov/vuln/detail/CVE-2024-43914)
 漏洞归属组件：[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：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:md/raid5: avoid BUG_ON() while continue reshape after reassemblingCurrently, mdadm support --revert-reshape to abort the reshape whilereassembling, as the test 07revert-grow. However, following BUG_ON()can be triggerred by the test:kernel BUG at drivers/md/raid5.c:6278!invalid opcode: 0000 [#1] PREEMPT SMP PTIirq event stamp: 158985CPU: 6 PID: 891 Comm: md0_reshape Not tainted 6.9.0-03335-g7592a0b0049a #94RIP: 0010:reshape_request+0x3f1/0xe60Call Trace: <TASK> raid5_sync_request+0x43d/0x550 md_do_sync+0xb7a/0x2110 md_thread+0x294/0x2b0 kthread+0x147/0x1c0 ret_from_fork+0x59/0x70 ret_from_fork_asm+0x1a/0x30 </TASK>Root cause is that --revert-reshape update the raid_disks from 5 to 4,while reshape position is still set, and after reassembling the array,reshape position will be read from super block, then during reshape thechecking of  writepos  that is caculated by old reshape position willfail.Fix this panic the easy way first, by converting the BUG_ON() toWARN_ON(), and stop the reshape if checkings fail.Noted that mdadm must fix --revert-shape as well, and probably md/raidshould enhance metadata validation as well, however this meansreassemble will fail and there must be user tools to fix the wrongmetadata.
 漏洞公开时间：2024-08-26 19:15:05
 漏洞创建时间：2024-08-27 09:11:30
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2024-43914
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/2c92f8c1c456d556f15cbf51667b385026b2e6a0 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/305a5170dc5cf3d395bb4c4e9239bca6d0b54b49 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/3b33740c1750a39e046339ff9240e954f0156707 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/4811d6e5d9f4090c3e0ff9890eb24077108046ab |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/6b33c468d543f6a83de2d61f09fec74b27e19fd2 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/775a9ba16c9ffe98fe54ebf14e55d5660f2bf600 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/bf0ff69a42a3d2d46876d0514ecf13dffc516666 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/c384dd4f1fb3b14a2fd199360701cc163ea88705 |  |
| suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-43914 | https://bugzilla.suse.com/show_bug.cgi?id=1229790 |
| suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2024-43914 | https://bugzilla.suse.com/show_bug.cgi?id=1229790 |
| suse_bugzilla | https://git.kernel.org/stable/c/2c92f8c1c456d556f15cbf51667b385026b2e6a0 | https://bugzilla.suse.com/show_bug.cgi?id=1229790 |
| suse_bugzilla | https://git.kernel.org/stable/c/305a5170dc5cf3d395bb4c4e9239bca6d0b54b49 | https://bugzilla.suse.com/show_bug.cgi?id=1229790 |
| suse_bugzilla | https://git.kernel.org/stable/c/3b33740c1750a39e046339ff9240e954f0156707 | https://bugzilla.suse.com/show_bug.cgi?id=1229790 |
| suse_bugzilla | https://git.kernel.org/stable/c/4811d6e5d9f4090c3e0ff9890eb24077108046ab | https://bugzilla.suse.com/show_bug.cgi?id=1229790 |
| suse_bugzilla | https://git.kernel.org/stable/c/6b33c468d543f6a83de2d61f09fec74b27e19fd2 | https://bugzilla.suse.com/show_bug.cgi?id=1229790 |
| suse_bugzilla | https://git.kernel.org/stable/c/775a9ba16c9ffe98fe54ebf14e55d5660f2bf600 | https://bugzilla.suse.com/show_bug.cgi?id=1229790 |
| suse_bugzilla | https://git.kernel.org/stable/c/bf0ff69a42a3d2d46876d0514ecf13dffc516666 | https://bugzilla.suse.com/show_bug.cgi?id=1229790 |
| suse_bugzilla | https://git.kernel.org/stable/c/c384dd4f1fb3b14a2fd199360701cc163ea88705 | https://bugzilla.suse.com/show_bug.cgi?id=1229790 |
| suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-43914.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1229790 |
| redhat_bugzilla | https://lore.kernel.org/linux-cve-announce/2024082635-CVE-2024-43914-a664@gregkh/T | https://bugzilla.redhat.com/show_bug.cgi?id=2307887 |
| ubuntu | https://www.cve.org/CVERecord?id=CVE-2024-43914 | https://ubuntu.com/security/CVE-2024-43914 |
| ubuntu | https://git.kernel.org/linus/305a5170dc5cf3d395bb4c4e9239bca6d0b54b49 (6.11-rc1) | https://ubuntu.com/security/CVE-2024-43914 |
| ubuntu | https://git.kernel.org/stable/c/2c92f8c1c456d556f15cbf51667b385026b2e6a0 | https://ubuntu.com/security/CVE-2024-43914 |
| ubuntu | https://git.kernel.org/stable/c/6b33c468d543f6a83de2d61f09fec74b27e19fd2 | https://ubuntu.com/security/CVE-2024-43914 |
| ubuntu | https://git.kernel.org/stable/c/c384dd4f1fb3b14a2fd199360701cc163ea88705 | https://ubuntu.com/security/CVE-2024-43914 |
| ubuntu | https://git.kernel.org/stable/c/bf0ff69a42a3d2d46876d0514ecf13dffc516666 | https://ubuntu.com/security/CVE-2024-43914 |
| ubuntu | https://git.kernel.org/stable/c/3b33740c1750a39e046339ff9240e954f0156707 | https://ubuntu.com/security/CVE-2024-43914 |
| ubuntu | https://git.kernel.org/stable/c/775a9ba16c9ffe98fe54ebf14e55d5660f2bf600 | https://ubuntu.com/security/CVE-2024-43914 |
| ubuntu | https://git.kernel.org/stable/c/4811d6e5d9f4090c3e0ff9890eb24077108046ab | https://ubuntu.com/security/CVE-2024-43914 |
| ubuntu | https://git.kernel.org/stable/c/305a5170dc5cf3d395bb4c4e9239bca6d0b54b49 | https://ubuntu.com/security/CVE-2024-43914 |
| ubuntu | https://nvd.nist.gov/vuln/detail/CVE-2024-43914 | https://ubuntu.com/security/CVE-2024-43914 |
| ubuntu | https://launchpad.net/bugs/cve/CVE-2024-43914 | https://ubuntu.com/security/CVE-2024-43914 |
| ubuntu | https://security-tracker.debian.org/tracker/CVE-2024-43914 | https://ubuntu.com/security/CVE-2024-43914 |
| debian |  | https://security-tracker.debian.org/tracker/CVE-2024-43914 |

</details>

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

| 影响的包 | 修复版本 | 修复补丁 | 问题引入补丁 | 来源  |
| ------- | -------- | ------- | -------- | --------- |
|  |  | https://git.kernel.org/stable/c/2c92f8c1c456d556f15cbf51667b385026b2e6a0 |  | nvd |
|  |  | https://git.kernel.org/stable/c/305a5170dc5cf3d395bb4c4e9239bca6d0b54b49 |  | nvd |
|  |  | https://git.kernel.org/stable/c/3b33740c1750a39e046339ff9240e954f0156707 |  | nvd |
|  |  | https://git.kernel.org/stable/c/4811d6e5d9f4090c3e0ff9890eb24077108046ab |  | nvd |
|  |  | https://git.kernel.org/stable/c/6b33c468d543f6a83de2d61f09fec74b27e19fd2 |  | nvd |
|  |  | https://git.kernel.org/stable/c/775a9ba16c9ffe98fe54ebf14e55d5660f2bf600 |  | nvd |
|  |  | https://git.kernel.org/stable/c/bf0ff69a42a3d2d46876d0514ecf13dffc516666 |  | nvd |
|  |  | https://git.kernel.org/stable/c/c384dd4f1fb3b14a2fd199360701cc163ea88705 |  | nvd |
| linux |  | https://git.kernel.org/linus/305a5170dc5cf3d395bb4c4e9239bca6d0b54b49 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |

</details>

二、漏洞分析结构反馈
 影响性分析说明：
          In the Linux kernel, the following vulnerability has been resolved:md/raid5: avoid BUG_ON() while continue reshape after reassemblingCurrently, mdadm support --revert-reshape to abort the reshape whilereassembling, as the test 07revert-grow. However, following BUG_ON()can be triggerred by the test:kernel BUG at drivers/md/raid5.c:6278!invalid opcode: 0000 [#1] PREEMPT SMP PTIirq event stamp: 158985CPU: 6 PID: 891 Comm: md0_reshape Not tainted 6.9.0-03335-g7592a0b0049a #94RIP: 0010:reshape_request+0x3f1/0xe60Call Trace: &lt;TASK&gt; raid5_sync_request+0x43d/0x550 md_do_sync+0xb7a/0x2110 md_thread+0x294/0x2b0 kthread+0x147/0x1c0 ret_from_fork+0x59/0x70 ret_from_fork_asm+0x1a/0x30 &lt;/TASK&gt;Root cause is that --revert-reshape update the raid_disks from 5 to 4,while reshape position is still set, and after reassembling the array,reshape position will be read from super block, then during reshape thechecking of &#39;writepos&#39; that is caculated by old reshape position willfail.Fix this panic the easy way first, by converting the BUG_ON() toWARN_ON(), and stop the reshape if checkings fail.Noted that mdadm must fix --revert-shape as well, and probably md/raidshould enhance metadata validation as well, however this meansreassemble will fail and there must be user tools to fix the wrongmetadata.The Linux kernel CVE team has assigned CVE-2024-43914 to this issue.    
 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-SP1(5.10.0):受影响
3.openEuler-22.03-LTS-SP3(5.10.0):受影响
4.openEuler-22.03-LTS-SP4(5.10.0):受影响
5.openEuler-24.03-LTS(6.6.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-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-2126

Hi openeuler-ci-bot, welcome to the openEuler Community.
I'm the Bot here serving you. You can find the instructions on how to interact with me at Here.
If you have any questions, please contact the SIG: Kernel, and any of the maintainers.

@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

参考网址	关联pr	状态	补丁链接
https://nvd.nist.gov/vuln/detail/CVE-2024-43914	None	None	https://git.kernel.org/stable/c/305a5170dc5cf3d395bb4c4e9239bca6d0b54b49 https://git.kernel.org/stable/c/3b33740c1750a39e046339ff9240e954f0156707 https://git.kernel.org/stable/c/6b33c468d543f6a83de2d61f09fec74b27e19fd2 https://git.kernel.org/stable/c/4811d6e5d9f4090c3e0ff9890eb24077108046ab https://git.kernel.org/stable/c/775a9ba16c9ffe98fe54ebf14e55d5660f2bf600 https://git.kernel.org/stable/c/c384dd4f1fb3b14a2fd199360701cc163ea88705 https://git.kernel.org/stable/c/bf0ff69a42a3d2d46876d0514ecf13dffc516666 https://git.kernel.org/stable/c/2c92f8c1c456d556f15cbf51667b385026b2e6a0
https://ubuntu.com/security/CVE-2024-43914	None	None	https://discourse.ubuntu.com/c/ubuntu-pro
https://www.opencve.io/cve/CVE-2024-43914	None	None	https://git.kernel.org/stable/c/305a5170dc5cf3d395bb4c4e9239bca6d0b54b49 https://git.kernel.org/stable/c/3b33740c1750a39e046339ff9240e954f0156707 https://git.kernel.org/stable/c/6b33c468d543f6a83de2d61f09fec74b27e19fd2 https://git.kernel.org/stable/c/4811d6e5d9f4090c3e0ff9890eb24077108046ab https://git.kernel.org/stable/c/775a9ba16c9ffe98fe54ebf14e55d5660f2bf600 https://git.kernel.org/stable/c/c384dd4f1fb3b14a2fd199360701cc163ea88705 https://git.kernel.org/stable/c/bf0ff69a42a3d2d46876d0514ecf13dffc516666 https://git.kernel.org/stable/c/2c92f8c1c456d556f15cbf51667b385026b2e6a0
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2024-43914
https://security-tracker.debian.org/tracker/CVE-2024-43914	None	None	https://git.kernel.org/linus/305a5170dc5cf3d395bb4c4e9239bca6d0b54b49

说明：补丁链接仅供初步排查参考，实际可用性请人工再次确认，补丁下载验证可使用CVE补丁工具。
若补丁不准确，烦请在此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-43914

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

md/raid5: avoid BUG_ON() while continue reshape after reassembling

Currently, mdadm support --revert-reshape to abort the reshape while
reassembling, as the test 07revert-grow. However, following BUG_ON()
can be triggerred by the test:

kernel BUG at drivers/md/raid5.c:6278!
invalid opcode: 0000 [#1] PREEMPT SMP PTI
irq event stamp: 158985
CPU: 6 PID: 891 Comm: md0_reshape Not tainted 6.9.0-03335-g7592a0b0049a #94
RIP: 0010:reshape_request+0x3f1/0xe60
Call Trace:
 &lt;TASK&gt;
 raid5_sync_request+0x43d/0x550
 md_do_sync+0xb7a/0x2110
 md_thread+0x294/0x2b0
 kthread+0x147/0x1c0
 ret_from_fork+0x59/0x70
 ret_from_fork_asm+0x1a/0x30
 &lt;/TASK&gt;

Root cause is that --revert-reshape update the raid_disks from 5 to 4,
while reshape position is still set, and after reassembling the array,
reshape position will be read from super block, then during reshape the
checking of &#39;writepos&#39; that is caculated by old reshape position will
fail.

Fix this panic the easy way first, by converting the BUG_ON() to
WARN_ON(), and stop the reshape if checkings fail.

Noted that mdadm must fix --revert-shape as well, and probably md/raid
should enhance metadata validation as well, however this means
reassemble will fail and there must be user tools to fix the wrong
metadata.

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

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

受影响版本排查(受影响/不受影响):
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:md/raid5: avoid BUG_ON() while continue reshape after reassemblingCurrently, mdadm support --revert-reshape to abort the reshape whilereassembling, as the test 07revert-grow. However, following BUG_ON()can be triggerred by the test:kernel BUG at drivers/md/raid5.c:6278!invalid opcode: 0000 [#1] PREEMPT SMP PTIirq event stamp: 158985CPU: 6 PID: 891 Comm: md0_reshape Not tainted 6.9.0-03335-g7592a0b0049a #94RIP: 0010:reshape_request+0x3f1/0xe60Call Trace: &lt;TASK&gt; raid5_sync_request+0x43d/0x550 md_do_sync+0xb7a/0x2110 md_thread+0x294/0x2b0 kthread+0x147/0x1c0 ret_from_fork+0x59/0x70 ret_from_fork_asm+0x1a/0x30 &lt;/TASK&gt;Root cause is that --revert-reshape update the raid_disks from 5 to 4,while reshape position is still set, and after reassembling the array,reshape position will be read from super block, then during reshape thechecking of &#39;writepos&#39; that is caculated by old reshape position willfail.Fix this panic the easy way first, by converting the BUG_ON() toWARN_ON(), and stop the reshape if checkings fail.Noted that mdadm must fix --revert-shape as well, and probably md/raidshould enhance metadata validation as well, however this meansreassemble will fail and there must be user tools to fix the wrongmetadata.The Linux kernel CVE team has assigned CVE-2024-43914 to this issue.|
|已分析|2.openEulerScore|3.9|
|已分析|3.openEulerVector|AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L|
|已分析|4.受影响版本排查|openEuler-20.03-LTS-SP4:不受影响,openEuler-22.03-LTS-SP1:不受影响,openEuler-22.03-LTS-SP3:不受影响,openEuler-22.03-LTS-SP4:不受影响,master:不受影响,openEuler-24.03-LTS:不受影响,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:否|

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