CVE-2024-26644

一、漏洞信息
 漏洞编号：[CVE-2024-26644](https://nvd.nist.gov/vuln/detail/CVE-2024-26644)
 漏洞归属组件：[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
 CVSS V2.0分值：
 BaseScore：0.0 Low
 Vector：CVSS：2.0/
 漏洞简述：
 In the Linux kernel, the following vulnerability has been resolved:btrfs: don t abort filesystem when attempting to snapshot deleted subvolumeIf the source file descriptor to the snapshot ioctl refers to a deletedsubvolume, we get the following abort: BTRFS: Transaction aborted (error -2) WARNING: CPU: 0 PID: 833 at fs/btrfs/transaction.c:1875 create_pending_snapshot+0x1040/0x1190 [btrfs] Modules linked in: pata_acpi btrfs ata_piix libata scsi_mod virtio_net blake2b_generic xor net_failover virtio_rng failover scsi_common rng_core raid6_pq libcrc32c CPU: 0 PID: 833 Comm: t_snapshot_dele Not tainted 6.7.0-rc6 #2 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-1.fc39 04/01/2014 RIP: 0010:create_pending_snapshot+0x1040/0x1190 [btrfs] RSP: 0018:ffffa09c01337af8 EFLAGS: 00010282 RAX: 0000000000000000 RBX: ffff9982053e7c78 RCX: 0000000000000027 RDX: ffff99827dc20848 RSI: 0000000000000001 RDI: ffff99827dc20840 RBP: ffffa09c01337c00 R08: 0000000000000000 R09: ffffa09c01337998 R10: 0000000000000003 R11: ffffffffb96da248 R12: fffffffffffffffe R13: ffff99820535bb28 R14: ffff99820b7bd000 R15: ffff99820381ea80 FS: 00007fe20aadabc0(0000) GS:ffff99827dc00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000559a120b502f CR3: 00000000055b6000 CR4: 00000000000006f0 Call Trace: <TASK> ? create_pending_snapshot+0x1040/0x1190 [btrfs] ? __warn+0x81/0x130 ? create_pending_snapshot+0x1040/0x1190 [btrfs] ? report_bug+0x171/0x1a0 ? handle_bug+0x3a/0x70 ? exc_invalid_op+0x17/0x70 ? asm_exc_invalid_op+0x1a/0x20 ? create_pending_snapshot+0x1040/0x1190 [btrfs] ? create_pending_snapshot+0x1040/0x1190 [btrfs] create_pending_snapshots+0x92/0xc0 [btrfs] btrfs_commit_transaction+0x66b/0xf40 [btrfs] btrfs_mksubvol+0x301/0x4d0 [btrfs] btrfs_mksnapshot+0x80/0xb0 [btrfs] __btrfs_ioctl_snap_create+0x1c2/0x1d0 [btrfs] btrfs_ioctl_snap_create_v2+0xc4/0x150 [btrfs] btrfs_ioctl+0x8a6/0x2650 [btrfs] ? kmem_cache_free+0x22/0x340 ? do_sys_openat2+0x97/0xe0 __x64_sys_ioctl+0x97/0xd0 do_syscall_64+0x46/0xf0 entry_SYSCALL_64_after_hwframe+0x6e/0x76 RIP: 0033:0x7fe20abe83af RSP: 002b:00007ffe6eff1360 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 00007fe20abe83af RDX: 00007ffe6eff23c0 RSI: 0000000050009417 RDI: 0000000000000003 RBP: 0000000000000003 R08: 0000000000000000 R09: 00007fe20ad16cd0 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffe6eff13c0 R14: 00007fe20ad45000 R15: 0000559a120b6d58 </TASK> ---[ end trace 0000000000000000 ]--- BTRFS: error (device vdc: state A) in create_pending_snapshot:1875: errno=-2 No such entry BTRFS info (device vdc: state EA): forced readonly BTRFS warning (device vdc: state EA): Skipping commit of aborted transaction. BTRFS: error (device vdc: state EA) in cleanup_transaction:2055: errno=-2 No such entryThis happens because create_pending_snapshot() initializes the new rootitem as a copy of the source root item. This includes the refs field,which is 0 for a deleted subvolume. The call to btrfs_insert_root()therefore inserts a root with refs == 0. btrfs_get_new_fs_root() thenfinds the root and returns -ENOENT if refs == 0, which causescreate_pending_snapshot() to abort.Fix it by checking the source root s refs before attempting thesnapshot, but after locking subvol_sem to avoid racing with deletion.
 漏洞公开时间：2024-03-27 00:15:12
 漏洞创建时间：2024-03-27 00:47:45
 漏洞详情参考链接：
 https://nvd.nist.gov/vuln/detail/CVE-2024-26644
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/0877497dc97834728e1b528ddf1e1c484292c29c |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/2bdf872bcfe629a6202ffd6641615a8ed00e8464 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/6e6bca99e8d88d989a7cde4c064abea552d5219b |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/7081929ab2572920e94d70be3d332e5c9f97095a |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/d8680b722f0ff6d7a01ddacc1844e0d52354d6ff |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/ec794a7528199e1be6d47bec03f4755aa75df256 |  |
| suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-26644 | https://bugzilla.suse.com/show_bug.cgi?id=1222072 |
| suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-26644.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1222072 |
| suse_bugzilla | https://git.kernel.org/stable/c/2bdf872bcfe629a6202ffd6641615a8ed00e8464 | https://bugzilla.suse.com/show_bug.cgi?id=1222072 |
| suse_bugzilla | https://git.kernel.org/stable/c/0877497dc97834728e1b528ddf1e1c484292c29c | https://bugzilla.suse.com/show_bug.cgi?id=1222072 |
| suse_bugzilla | https://git.kernel.org/stable/c/6e6bca99e8d88d989a7cde4c064abea552d5219b | https://bugzilla.suse.com/show_bug.cgi?id=1222072 |
| suse_bugzilla | https://git.kernel.org/stable/c/ec794a7528199e1be6d47bec03f4755aa75df256 | https://bugzilla.suse.com/show_bug.cgi?id=1222072 |
| suse_bugzilla | https://git.kernel.org/stable/c/d8680b722f0ff6d7a01ddacc1844e0d52354d6ff | https://bugzilla.suse.com/show_bug.cgi?id=1222072 |
| suse_bugzilla | https://git.kernel.org/stable/c/7081929ab2572920e94d70be3d332e5c9f97095a | https://bugzilla.suse.com/show_bug.cgi?id=1222072 |
| suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2024-26644 | https://bugzilla.suse.com/show_bug.cgi?id=1222072 |
| suse_bugzilla | https://bugzilla.redhat.com/show_bug.cgi?id=2271644 | https://bugzilla.suse.com/show_bug.cgi?id=1222072 |
| redhat_bugzilla | https://lore.kernel.org/linux-cve-announce/20240326151722.1258576-3-lee@kernel.org/T | https://bugzilla.redhat.com/show_bug.cgi?id=2271644 |
| ubuntu | https://git.kernel.org/linus/7081929ab2572920e94d70be3d332e5c9f97095a (6.8-rc2) | https://ubuntu.com/security/CVE-2024-26644 |
| ubuntu | https://git.kernel.org/stable/c/2bdf872bcfe629a6202ffd6641615a8ed00e8464 | https://ubuntu.com/security/CVE-2024-26644 |
| ubuntu | https://git.kernel.org/stable/c/0877497dc97834728e1b528ddf1e1c484292c29c | https://ubuntu.com/security/CVE-2024-26644 |
| ubuntu | https://git.kernel.org/stable/c/6e6bca99e8d88d989a7cde4c064abea552d5219b | https://ubuntu.com/security/CVE-2024-26644 |
| ubuntu | https://git.kernel.org/stable/c/ec794a7528199e1be6d47bec03f4755aa75df256 | https://ubuntu.com/security/CVE-2024-26644 |
| ubuntu | https://git.kernel.org/stable/c/d8680b722f0ff6d7a01ddacc1844e0d52354d6ff | https://ubuntu.com/security/CVE-2024-26644 |
| ubuntu | https://git.kernel.org/stable/c/7081929ab2572920e94d70be3d332e5c9f97095a | https://ubuntu.com/security/CVE-2024-26644 |
| ubuntu | https://www.cve.org/CVERecord?id=CVE-2024-26644 | https://ubuntu.com/security/CVE-2024-26644 |
| ubuntu | https://ubuntu.com/security/notices/USN-6765-1 | https://ubuntu.com/security/CVE-2024-26644 |
| ubuntu | https://ubuntu.com/security/notices/USN-6766-1 | https://ubuntu.com/security/CVE-2024-26644 |
| ubuntu | https://nvd.nist.gov/vuln/detail/CVE-2024-26644 | https://ubuntu.com/security/CVE-2024-26644 |
| ubuntu | https://launchpad.net/bugs/cve/CVE-2024-26644 | https://ubuntu.com/security/CVE-2024-26644 |
| ubuntu | https://security-tracker.debian.org/tracker/CVE-2024-26644 | https://ubuntu.com/security/CVE-2024-26644 |
| debian |  | https://security-tracker.debian.org/tracker/CVE-2024-26644 |
| cve_search |  | https://git.kernel.org/stable/c/2bdf872bcfe629a6202ffd6641615a8ed00e8464 |
| cve_search |  | https://git.kernel.org/stable/c/0877497dc97834728e1b528ddf1e1c484292c29c |
| cve_search |  | https://git.kernel.org/stable/c/6e6bca99e8d88d989a7cde4c064abea552d5219b |
| cve_search |  | https://git.kernel.org/stable/c/ec794a7528199e1be6d47bec03f4755aa75df256 |
| cve_search |  | https://git.kernel.org/stable/c/d8680b722f0ff6d7a01ddacc1844e0d52354d6ff |
| cve_search |  | https://git.kernel.org/stable/c/7081929ab2572920e94d70be3d332e5c9f97095a |
| ubuntu | https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-26644 | https://ubuntu.com/security/CVE-2024-26644 |

</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/7081929ab2572920e94d70be3d332e5c9f97095a | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |

</details>

二、漏洞分析结构反馈
 影响性分析说明：
 In the Linux kernel, the following vulnerability has been resolved:btrfs: don t abort filesystem when attempting to snapshot deleted subvolumeIf the source file descriptor to the snapshot ioctl refers to a deletedsubvolume, we get the following abort: BTRFS: Transaction aborted (error -2) WARNING: CPU: 0 PID: 833 at fs/btrfs/transaction.c:1875 create_pending_snapshot+0x1040/0x1190 [btrfs] Modules linked in: pata_acpi btrfs ata_piix libata scsi_mod virtio_net blake2b_generic xor net_failover virtio_rng failover scsi_common rng_core raid6_pq libcrc32c CPU: 0 PID: 833 Comm: t_snapshot_dele Not tainted 6.7.0-rc6 #2 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-1.fc39 04/01/2014 RIP: 0010:create_pending_snapshot+0x1040/0x1190 [btrfs] RSP: 0018:ffffa09c01337af8 EFLAGS: 00010282 RAX: 0000000000000000 RBX: ffff9982053e7c78 RCX: 0000000000000027 RDX: ffff99827dc20848 RSI: 0000000000000001 RDI: ffff99827dc20840 RBP: ffffa09c01337c00 R08: 0000000000000000 R09: ffffa09c01337998 R10: 0000000000000003 R11: ffffffffb96da248 R12: fffffffffffffffe R13: ffff99820535bb28 R14: ffff99820b7bd000 R15: ffff99820381ea80 FS: 00007fe20aadabc0(0000) GS:ffff99827dc00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000559a120b502f CR3: 00000000055b6000 CR4: 00000000000006f0 Call Trace: <TASK> ? create_pending_snapshot+0x1040/0x1190 [btrfs] ? __warn+0x81/0x130 ? create_pending_snapshot+0x1040/0x1190 [btrfs] ? report_bug+0x171/0x1a0 ? handle_bug+0x3a/0x70 ? exc_invalid_op+0x17/0x70 ? asm_exc_invalid_op+0x1a/0x20 ? create_pending_snapshot+0x1040/0x1190 [btrfs] ? create_pending_snapshot+0x1040/0x1190 [btrfs] create_pending_snapshots+0x92/0xc0 [btrfs] btrfs_commit_transaction+0x66b/0xf40 [btrfs] btrfs_mksubvol+0x301/0x4d0 [btrfs] btrfs_mksnapshot+0x80/0xb0 [btrfs] __btrfs_ioctl_snap_create+0x1c2/0x1d0 [btrfs] btrfs_ioctl_snap_create_v2+0xc4/0x150 [btrfs] btrfs_ioctl+0x8a6/0x2650 [btrfs] ? kmem_cache_free+0x22/0x340 ? do_sys_openat2+0x97/0xe0 __x64_sys_ioctl+0x97/0xd0 do_syscall_64+0x46/0xf0 entry_SYSCALL_64_after_hwframe+0x6e/0x76 RIP: 0033:0x7fe20abe83af RSP: 002b:00007ffe6eff1360 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 00007fe20abe83af RDX: 00007ffe6eff23c0 RSI: 0000000050009417 RDI: 0000000000000003 RBP: 0000000000000003 R08: 0000000000000000 R09: 00007fe20ad16cd0 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffe6eff13c0 R14: 00007fe20ad45000 R15: 0000559a120b6d58 </TASK> ---[ end trace 0000000000000000 ]--- BTRFS: error (device vdc: state A) in create_pending_snapshot:1875: errno=-2 No such entry BTRFS info (device vdc: state EA): forced readonly BTRFS warning (device vdc: state EA): Skipping commit of aborted transaction. BTRFS: error (device vdc: state EA) in cleanup_transaction:2055: errno=-2 No such entryThis happens because create_pending_snapshot() initializes the new rootitem as a copy of the source root item. This includes the refs field,which is 0 for a deleted subvolume. The call to btrfs_insert_root()therefore inserts a root with refs == 0. btrfs_get_new_fs_root() thenfinds the root and returns -ENOENT if refs == 0, which causescreate_pending_snapshot() to abort.Fix it by checking the source root s refs before attempting thesnapshot, but after locking subvol_sem to avoid racing with deletion. 
 openEuler评分：
 5.5
 Vector：CVSS：2.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
 受影响版本排查(受影响/不受影响)：
 1.openEuler-20.03-LTS-SP1(4.19.90):受影响
2.openEuler-20.03-LTS-SP4(4.19.90):受影响
3.openEuler-22.03-LTS(5.10.0):受影响
4.openEuler-22.03-LTS-SP1(5.10.0):受影响
5.openEuler-22.03-LTS-SP2(5.10.0):受影响
6.openEuler-22.03-LTS-SP3(5.10.0):受影响
7.master(6.1.0):不受影响
8.openEuler-22.03-LTS-Next(5.10.0):不受影响
9.openEuler-24.03-LTS:不受影响
10.openEuler-24.03-LTS-Next:不受影响

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

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

@yangyingliang ,@gatieme ,@jiaoff ,@guohaocs2c ,@hanjun-guo ,@woqidaideshi ,@newbeats ,@zhangyi089 ,@colyli ,@thundertown ,@htforge ,@chiqijun ,@lengchao ,@zhujianwei001 ,@kylin-mayukun ,@wangxiongfeng ,@wkfxxx ,@SuperSix173 ,@jentlestea ,@oskernel0719 
**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-SP1(4.19.90):
3.openEuler-20.03-LTS-SP4:
4.openEuler-22.03-LTS(5.10.0):
5.openEuler-22.03-LTS-Next(5.10.0):
6.openEuler-22.03-LTS-SP1(5.10.0):
7.openEuler-22.03-LTS-SP2(5.10.0):
8.openEuler-22.03-LTS-SP3:
9.openEuler-24.03-LTS:

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

-----------------------------------------------------------------------
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-26644</td><td>None</td><td>None</td><td><a href=https://git.kernel.org/stable/c/6e6bca99e8d88d989a7cde4c064abea552d5219b>https://git.kernel.org/stable/c/6e6bca99e8d88d989a7cde4c064abea552d5219b</a> <a href=https://git.kernel.org/stable/c/2bdf872bcfe629a6202ffd6641615a8ed00e8464>https://git.kernel.org/stable/c/2bdf872bcfe629a6202ffd6641615a8ed00e8464</a> <a href=https://git.kernel.org/stable/c/0877497dc97834728e1b528ddf1e1c484292c29c>https://git.kernel.org/stable/c/0877497dc97834728e1b528ddf1e1c484292c29c</a> <a href=https://git.kernel.org/stable/c/7081929ab2572920e94d70be3d332e5c9f97095a>https://git.kernel.org/stable/c/7081929ab2572920e94d70be3d332e5c9f97095a</a> <a href=https://git.kernel.org/stable/c/ec794a7528199e1be6d47bec03f4755aa75df256>https://git.kernel.org/stable/c/ec794a7528199e1be6d47bec03f4755aa75df256</a> <a href=https://git.kernel.org/stable/c/d8680b722f0ff6d7a01ddacc1844e0d52354d6ff>https://git.kernel.org/stable/c/d8680b722f0ff6d7a01ddacc1844e0d52354d6ff</a></td></tr><tr><td rowspan="1">https://ubuntu.com/security/CVE-2024-26644</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-26644</td><td>None</td><td>None</td><td><a href=https://git.kernel.org/stable/c/6e6bca99e8d88d989a7cde4c064abea552d5219b>https://git.kernel.org/stable/c/6e6bca99e8d88d989a7cde4c064abea552d5219b</a> <a href=https://git.kernel.org/stable/c/2bdf872bcfe629a6202ffd6641615a8ed00e8464>https://git.kernel.org/stable/c/2bdf872bcfe629a6202ffd6641615a8ed00e8464</a> <a href=https://git.kernel.org/stable/c/0877497dc97834728e1b528ddf1e1c484292c29c>https://git.kernel.org/stable/c/0877497dc97834728e1b528ddf1e1c484292c29c</a> <a href=https://git.kernel.org/stable/c/7081929ab2572920e94d70be3d332e5c9f97095a>https://git.kernel.org/stable/c/7081929ab2572920e94d70be3d332e5c9f97095a</a> <a href=https://git.kernel.org/stable/c/ec794a7528199e1be6d47bec03f4755aa75df256>https://git.kernel.org/stable/c/ec794a7528199e1be6d47bec03f4755aa75df256</a> <a href=https://git.kernel.org/stable/c/d8680b722f0ff6d7a01ddacc1844e0d52354d6ff>https://git.kernel.org/stable/c/d8680b722f0ff6d7a01ddacc1844e0d52354d6ff</a></td></tr><tr><td>https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2024-26644</td><td></td><td></td><td></td></tr><tr><td>https://security-tracker.debian.org/tracker/CVE-2024-26644</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-26644

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

btrfs: don't abort filesystem when attempting to snapshot deleted subvolume

If the source file descriptor to the snapshot ioctl refers to a deleted
subvolume, we get the following abort:

BTRFS: Transaction aborted (error -2)
 WARNING: CPU: 0 PID: 833 at fs/btrfs/transaction.c:1875 create_pending_snapshot+0x1040/0x1190 [btrfs]
 Modules linked in: pata_acpi btrfs ata_piix libata scsi_mod virtio_net blake2b_generic xor net_failover virtio_rng failover scsi_common rng_core raid6_pq libcrc32c
 CPU: 0 PID: 833 Comm: t_snapshot_dele Not tainted 6.7.0-rc6 #2
 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-1.fc39 04/01/2014
 RIP: 0010:create_pending_snapshot+0x1040/0x1190 [btrfs]
 RSP: 0018:ffffa09c01337af8 EFLAGS: 00010282
 RAX: 0000000000000000 RBX: ffff9982053e7c78 RCX: 0000000000000027
 RDX: ffff99827dc20848 RSI: 0000000000000001 RDI: ffff99827dc20840
 RBP: ffffa09c01337c00 R08: 0000000000000000 R09: ffffa09c01337998
 R10: 0000000000000003 R11: ffffffffb96da248 R12: fffffffffffffffe
 R13: ffff99820535bb28 R14: ffff99820b7bd000 R15: ffff99820381ea80
 FS: 00007fe20aadabc0(0000) GS:ffff99827dc00000(0000) knlGS:0000000000000000
 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
 CR2: 0000559a120b502f CR3: 00000000055b6000 CR4: 00000000000006f0
 Call Trace:
 <TASK>
 ? create_pending_snapshot+0x1040/0x1190 [btrfs]
 ? __warn+0x81/0x130
 ? create_pending_snapshot+0x1040/0x1190 [btrfs]
 ? report_bug+0x171/0x1a0
 ? handle_bug+0x3a/0x70
 ? exc_invalid_op+0x17/0x70
 ? asm_exc_invalid_op+0x1a/0x20
 ? create_pending_snapshot+0x1040/0x1190 [btrfs]
 ? create_pending_snapshot+0x1040/0x1190 [btrfs]
 create_pending_snapshots+0x92/0xc0 [btrfs]
 btrfs_commit_transaction+0x66b/0xf40 [btrfs]
 btrfs_mksubvol+0x301/0x4d0 [btrfs]
 btrfs_mksnapshot+0x80/0xb0 [btrfs]
 __btrfs_ioctl_snap_create+0x1c2/0x1d0 [btrfs]
 btrfs_ioctl_snap_create_v2+0xc4/0x150 [btrfs]
 btrfs_ioctl+0x8a6/0x2650 [btrfs]
 ? kmem_cache_free+0x22/0x340
 ? do_sys_openat2+0x97/0xe0
 __x64_sys_ioctl+0x97/0xd0
 do_syscall_64+0x46/0xf0
 entry_SYSCALL_64_after_hwframe+0x6e/0x76
 RIP: 0033:0x7fe20abe83af
 RSP: 002b:00007ffe6eff1360 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
 RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 00007fe20abe83af
 RDX: 00007ffe6eff23c0 RSI: 0000000050009417 RDI: 0000000000000003
 RBP: 0000000000000003 R08: 0000000000000000 R09: 00007fe20ad16cd0
 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
 R13: 00007ffe6eff13c0 R14: 00007fe20ad45000 R15: 0000559a120b6d58
 </TASK>
 ---[ end trace 0000000000000000 ]---
 BTRFS: error (device vdc: state A) in create_pending_snapshot:1875: errno=-2 No such entry
 BTRFS info (device vdc: state EA): forced readonly
 BTRFS warning (device vdc: state EA): Skipping commit of aborted transaction.
 BTRFS: error (device vdc: state EA) in cleanup_transaction:2055: errno=-2 No such entry

This happens because create_pending_snapshot() initializes the new root
item as a copy of the source root item. This includes the refs field,
which is 0 for a deleted subvolume. The call to btrfs_insert_root()
therefore inserts a root with refs == 0. btrfs_get_new_fs_root() then
finds the root and returns -ENOENT if refs == 0, which causes
create_pending_snapshot() to abort.

Fix it by checking the source root's refs before attempting the
snapshot, but after locking subvol_sem to avoid racing with deletion.

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-SP1:受影响
2.openEuler-20.03-LTS-SP4:受影响
3.openEuler-22.03-LTS:受影响
4.openEuler-22.03-LTS-SP1:受影响
5.openEuler-22.03-LTS-SP2:受影响
6.openEuler-22.03-LTS-SP3:受影响
7.master(6.1.0):不受影响
8.openEuler-22.03-LTS-Next:不受影响
9.openEuler-24.03-LTS:不受影响
10.openEuler-24.03-LTS-Next:不受影响

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

===========================================================

@sanglipeng 经过 cve-manager 解析, 已分析的内容如下表所示:
| 状态 | 需分析 | 内容 |
|:--:|:--:|---------|
|已分析|1.影响性分析说明|In the Linux kernel, the following vulnerability has been resolved:btrfs: don't abort filesystem when attempting to snapshot deleted subvolumeIf the source file descriptor to the snapshot ioctl refers to a deletedsubvolume, we get the following abort: BTRFS: Transaction aborted (error -2) WARNING: CPU: 0 PID: 833 at fs/btrfs/transaction.c:1875 create_pending_snapshot+0x1040/0x1190 [btrfs] Modules linked in: pata_acpi btrfs ata_piix libata scsi_mod virtio_net blake2b_generic xor net_failover virtio_rng failover scsi_common rng_core raid6_pq libcrc32c CPU: 0 PID: 833 Comm: t_snapshot_dele Not tainted 6.7.0-rc6 #2 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-1.fc39 04/01/2014 RIP: 0010:create_pending_snapshot+0x1040/0x1190 [btrfs] RSP: 0018:ffffa09c01337af8 EFLAGS: 00010282 RAX: 0000000000000000 RBX: ffff9982053e7c78 RCX: 0000000000000027 RDX: ffff99827dc20848 RSI: 0000000000000001 RDI: ffff99827dc20840 RBP: ffffa09c01337c00 R08: 0000000000000000 R09: ffffa09c01337998 R10: 0000000000000003 R11: ffffffffb96da248 R12: fffffffffffffffe R13: ffff99820535bb28 R14: ffff99820b7bd000 R15: ffff99820381ea80 FS: 00007fe20aadabc0(0000) GS:ffff99827dc00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000559a120b502f CR3: 00000000055b6000 CR4: 00000000000006f0 Call Trace: <TASK> ? create_pending_snapshot+0x1040/0x1190 [btrfs] ? __warn+0x81/0x130 ? create_pending_snapshot+0x1040/0x1190 [btrfs] ? report_bug+0x171/0x1a0 ? handle_bug+0x3a/0x70 ? exc_invalid_op+0x17/0x70 ? asm_exc_invalid_op+0x1a/0x20 ? create_pending_snapshot+0x1040/0x1190 [btrfs] ? create_pending_snapshot+0x1040/0x1190 [btrfs] create_pending_snapshots+0x92/0xc0 [btrfs] btrfs_commit_transaction+0x66b/0xf40 [btrfs] btrfs_mksubvol+0x301/0x4d0 [btrfs] btrfs_mksnapshot+0x80/0xb0 [btrfs] __btrfs_ioctl_snap_create+0x1c2/0x1d0 [btrfs] btrfs_ioctl_snap_create_v2+0xc4/0x150 [btrfs] btrfs_ioctl+0x8a6/0x2650 [btrfs] ? kmem_cache_free+0x22/0x340 ? do_sys_openat2+0x97/0xe0 __x64_sys_ioctl+0x97/0xd0 do_syscall_64+0x46/0xf0 entry_SYSCALL_64_after_hwframe+0x6e/0x76 RIP: 0033:0x7fe20abe83af RSP: 002b:00007ffe6eff1360 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 00007fe20abe83af RDX: 00007ffe6eff23c0 RSI: 0000000050009417 RDI: 0000000000000003 RBP: 0000000000000003 R08: 0000000000000000 R09: 00007fe20ad16cd0 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffe6eff13c0 R14: 00007fe20ad45000 R15: 0000559a120b6d58 </TASK> ---[ end trace 0000000000000000 ]--- BTRFS: error (device vdc: state A) in create_pending_snapshot:1875: errno=-2 No such entry BTRFS info (device vdc: state EA): forced readonly BTRFS warning (device vdc: state EA): Skipping commit of aborted transaction. BTRFS: error (device vdc: state EA) in cleanup_transaction:2055: errno=-2 No such entryThis happens because create_pending_snapshot() initializes the new rootitem as a copy of the source root item. This includes the refs field,which is 0 for a deleted subvolume. The call to btrfs_insert_root()therefore inserts a root with refs == 0. btrfs_get_new_fs_root() thenfinds the root and returns -ENOENT if refs == 0, which causescreate_pending_snapshot() to abort.Fix it by checking the source root's refs before attempting thesnapshot, but after locking subvol_sem to avoid racing with deletion.|
|已分析|2.openEulerScore|5.5|
|已分析|3.openEulerVector|AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H|
|已分析|4.受影响版本排查|openEuler-20.03-LTS-SP1:受影响,openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS:受影响,openEuler-22.03-LTS-SP1:受影响,openEuler-22.03-LTS-SP2:受影响,openEuler-22.03-LTS-SP3:受影响,master:不受影响,openEuler-22.03-LTS-Next:不受影响,openEuler-24.03-LTS:不受影响,openEuler-24.03-LTS-Next:不受影响|
|已分析|5.修复是否涉及abi变化|openEuler-20.03-LTS-SP1:否,openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS:否,openEuler-22.03-LTS-SP1:否,openEuler-22.03-LTS-SP2:否,openEuler-22.03-LTS-SP3:否,master:否,openEuler-22.03-LTS-Next:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否|

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