CVE-2024-42111

一、漏洞信息
 漏洞编号：[CVE-2024-42111](https://nvd.nist.gov/vuln/detail/CVE-2024-42111)
 漏洞归属组件：[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 Low
  Vector：CVSS：2.0/
 漏洞简述：
  In the Linux kernel, the following vulnerability has been resolved:btrfs: always do the basic checks for btrfs_qgroup_inherit structure[BUG]Syzbot reports the following regression detected by KASAN:  BUG: KASAN: slab-out-of-bounds in btrfs_qgroup_inherit+0x42e/0x2e20 fs/btrfs/qgroup.c:3277  Read of size 8 at addr ffff88814628ca50 by task syz-executor318/5171  CPU: 0 PID: 5171 Comm: syz-executor318 Not tainted 6.10.0-rc2-syzkaller-00010-g2ab795141095 #0  Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024  Call Trace:   <TASK>   __dump_stack lib/dump_stack.c:88 [inline]   dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114   print_address_description mm/kasan/report.c:377 [inline]   print_report+0x169/0x550 mm/kasan/report.c:488   kasan_report+0x143/0x180 mm/kasan/report.c:601   btrfs_qgroup_inherit+0x42e/0x2e20 fs/btrfs/qgroup.c:3277   create_pending_snapshot+0x1359/0x29b0 fs/btrfs/transaction.c:1854   create_pending_snapshots+0x195/0x1d0 fs/btrfs/transaction.c:1922   btrfs_commit_transaction+0xf20/0x3740 fs/btrfs/transaction.c:2382   create_snapshot+0x6a1/0x9e0 fs/btrfs/ioctl.c:875   btrfs_mksubvol+0x58f/0x710 fs/btrfs/ioctl.c:1029   btrfs_mksnapshot+0xb5/0xf0 fs/btrfs/ioctl.c:1075   __btrfs_ioctl_snap_create+0x387/0x4b0 fs/btrfs/ioctl.c:1340   btrfs_ioctl_snap_create_v2+0x1f2/0x3a0 fs/btrfs/ioctl.c:1422   btrfs_ioctl+0x99e/0xc60   vfs_ioctl fs/ioctl.c:51 [inline]   __do_sys_ioctl fs/ioctl.c:907 [inline]   __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893   do_syscall_x64 arch/x86/entry/common.c:52 [inline]   do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83   entry_SYSCALL_64_after_hwframe+0x77/0x7f  RIP: 0033:0x7fcbf1992509  RSP: 002b:00007fcbf1928218 EFLAGS: 00000246 ORIG_RAX: 0000000000000010  RAX: ffffffffffffffda RBX: 00007fcbf1a1f618 RCX: 00007fcbf1992509  RDX: 0000000020000280 RSI: 0000000050009417 RDI: 0000000000000003  RBP: 00007fcbf1a1f610 R08: 00007ffea1298e97 R09: 0000000000000000  R10: 0000000000000000 R11: 0000000000000246 R12: 00007fcbf19eb660  R13: 00000000200002b8 R14: 00007fcbf19e60c0 R15: 0030656c69662f2e   </TASK>And it also pinned it down to commit b5357cb268c4 ( btrfs: qgroup: do notcheck qgroup inherit if qgroup is disabled ).[CAUSE]That offending commit skips the whole qgroup inherit check if qgroup isnot enabled.But that also skips the very basic checks likenum_ref_copies/num_excl_copies and the structure size checks.Meaning if a qgroup enable/disable race is happening at the background,and we pass a btrfs_qgroup_inherit structure when the qgroup isdisabled, the check would be completely skipped.Then at the time of transaction commitment, qgroup is re-enabled andbtrfs_qgroup_inherit() is going to use the incorrect structure andcausing the above KASAN error.[FIX]Make btrfs_qgroup_check_inherit() only skip the source qgroup checks.So that even if invalid btrfs_qgroup_inherit structure is passed in, wecan still reject invalid ones no matter if qgroup is enabled or not.Furthermore we do already have an extra safety insidebtrfs_qgroup_inherit(), which would just ignore invalid qgroup sources,so even if we only skip the qgroup source check we re still safe.
 漏洞公开时间：2024-07-30 16:15:03
 漏洞创建时间：2024-07-31 11:32:12
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2024-42111
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/724d8042cef84496ddb4492dc120291f997ae26b |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/ebe5ea02577b2c527958af1b76ac472c7ab53a56 |  |
| suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-42111 | https://bugzilla.suse.com/show_bug.cgi?id=1228506 |
| suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-42111.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1228506 |
| suse_bugzilla | https://git.kernel.org/stable/c/ebe5ea02577b2c527958af1b76ac472c7ab53a56 | https://bugzilla.suse.com/show_bug.cgi?id=1228506 |
| suse_bugzilla | https://git.kernel.org/stable/c/724d8042cef84496ddb4492dc120291f997ae26b | https://bugzilla.suse.com/show_bug.cgi?id=1228506 |
| redhat_bugzilla | https://lore.kernel.org/linux-cve-announce/2024073021-CVE-2024-42111-034c@gregkh/T | https://bugzilla.redhat.com/show_bug.cgi?id=2301474 |
| ubuntu | https://www.cve.org/CVERecord?id=CVE-2024-42111 | https://ubuntu.com/security/CVE-2024-42111 |
| ubuntu | https://git.kernel.org/linus/724d8042cef84496ddb4492dc120291f997ae26b (6.10-rc7) | https://ubuntu.com/security/CVE-2024-42111 |
| ubuntu | https://git.kernel.org/stable/c/ebe5ea02577b2c527958af1b76ac472c7ab53a56 | https://ubuntu.com/security/CVE-2024-42111 |
| ubuntu | https://git.kernel.org/stable/c/724d8042cef84496ddb4492dc120291f997ae26b | https://ubuntu.com/security/CVE-2024-42111 |
| ubuntu | https://nvd.nist.gov/vuln/detail/CVE-2024-42111 | https://ubuntu.com/security/CVE-2024-42111 |
| ubuntu | https://launchpad.net/bugs/cve/CVE-2024-42111 | https://ubuntu.com/security/CVE-2024-42111 |
| ubuntu | https://security-tracker.debian.org/tracker/CVE-2024-42111 | https://ubuntu.com/security/CVE-2024-42111 |
| debian |  | https://security-tracker.debian.org/tracker/CVE-2024-42111 |

</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/724d8042cef84496ddb4492dc120291f997ae26b | https://git.kernel.org/linus/b5357cb268c41b4e2b7383d2759fc562f5b58c33 | ubuntu |

</details>

二、漏洞分析结构反馈
 影响性分析说明：
    Reserved. 
 openEuler评分：
  3.9
 Vector：CVSS：2.0/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L
 受影响版本排查(受影响/不受影响)：
  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):否

@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

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.

参考网址	关联pr	状态	补丁链接
https://nvd.nist.gov/vuln/detail/CVE-2024-42111	None	None	https://git.kernel.org/stable/c/ebe5ea02577b2c527958af1b76ac472c7ab53a56 https://git.kernel.org/stable/c/724d8042cef84496ddb4492dc120291f997ae26b
https://ubuntu.com/security/CVE-2024-42111	None	None	https://discourse.ubuntu.com/c/ubuntu-pro
https://www.opencve.io/cve/CVE-2024-42111	None	None	https://git.kernel.org/stable/c/ebe5ea02577b2c527958af1b76ac472c7ab53a56 https://git.kernel.org/stable/c/724d8042cef84496ddb4492dc120291f997ae26b
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2024-42111
https://security-tracker.debian.org/tracker/CVE-2024-42111	None	None	https://git.kernel.org/linus/724d8042cef84496ddb4492dc120291f997ae26b

说明：补丁链接仅供初步排查参考，实际可用性请人工再次确认，补丁下载验证可使用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-42111

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

btrfs: always do the basic checks for btrfs_qgroup_inherit structure

[BUG]
Syzbot reports the following regression detected by KASAN:

BUG: KASAN: slab-out-of-bounds in btrfs_qgroup_inherit+0x42e/0x2e20 fs/btrfs/qgroup.c:3277
  Read of size 8 at addr ffff88814628ca50 by task syz-executor318/5171

CPU: 0 PID: 5171 Comm: syz-executor318 Not tainted 6.10.0-rc2-syzkaller-00010-g2ab795141095 #0
  Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024
  Call Trace:
   &lt;TASK&gt;
   __dump_stack lib/dump_stack.c:88 [inline]
   dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114
   print_address_description mm/kasan/report.c:377 [inline]
   print_report+0x169/0x550 mm/kasan/report.c:488
   kasan_report+0x143/0x180 mm/kasan/report.c:601
   btrfs_qgroup_inherit+0x42e/0x2e20 fs/btrfs/qgroup.c:3277
   create_pending_snapshot+0x1359/0x29b0 fs/btrfs/transaction.c:1854
   create_pending_snapshots+0x195/0x1d0 fs/btrfs/transaction.c:1922
   btrfs_commit_transaction+0xf20/0x3740 fs/btrfs/transaction.c:2382
   create_snapshot+0x6a1/0x9e0 fs/btrfs/ioctl.c:875
   btrfs_mksubvol+0x58f/0x710 fs/btrfs/ioctl.c:1029
   btrfs_mksnapshot+0xb5/0xf0 fs/btrfs/ioctl.c:1075
   __btrfs_ioctl_snap_create+0x387/0x4b0 fs/btrfs/ioctl.c:1340
   btrfs_ioctl_snap_create_v2+0x1f2/0x3a0 fs/btrfs/ioctl.c:1422
   btrfs_ioctl+0x99e/0xc60
   vfs_ioctl fs/ioctl.c:51 [inline]
   __do_sys_ioctl fs/ioctl.c:907 [inline]
   __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893
   do_syscall_x64 arch/x86/entry/common.c:52 [inline]
   do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
   entry_SYSCALL_64_after_hwframe+0x77/0x7f
  RIP: 0033:0x7fcbf1992509
  RSP: 002b:00007fcbf1928218 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
  RAX: ffffffffffffffda RBX: 00007fcbf1a1f618 RCX: 00007fcbf1992509
  RDX: 0000000020000280 RSI: 0000000050009417 RDI: 0000000000000003
  RBP: 00007fcbf1a1f610 R08: 00007ffea1298e97 R09: 0000000000000000
  R10: 0000000000000000 R11: 0000000000000246 R12: 00007fcbf19eb660
  R13: 00000000200002b8 R14: 00007fcbf19e60c0 R15: 0030656c69662f2e
   &lt;/TASK&gt;

And it also pinned it down to commit b5357cb268c4 (&#34;btrfs: qgroup: do not
check qgroup inherit if qgroup is disabled&#34;).

[CAUSE]
That offending commit skips the whole qgroup inherit check if qgroup is
not enabled.

But that also skips the very basic checks like
num_ref_copies/num_excl_copies and the structure size checks.

Meaning if a qgroup enable/disable race is happening at the background,
and we pass a btrfs_qgroup_inherit structure when the qgroup is
disabled, the check would be completely skipped.

Then at the time of transaction commitment, qgroup is re-enabled and
btrfs_qgroup_inherit() is going to use the incorrect structure and
causing the above KASAN error.

[FIX]
Make btrfs_qgroup_check_inherit() only skip the source qgroup checks.
So that even if invalid btrfs_qgroup_inherit structure is passed in, we
can still reject invalid ones no matter if qgroup is enabled or not.

Furthermore we do already have an extra safety inside
btrfs_qgroup_inherit(), which would just ignore invalid qgroup sources,
so even if we only skip the qgroup source check we&#39;re still safe.

The Linux kernel CVE team has assigned CVE-2024-42111 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:btrfs: always do the basic checks for btrfs_qgroup_inherit structure[BUG]Syzbot reports the following regression detected by KASAN:  BUG: KASAN: slab-out-of-bounds in btrfs_qgroup_inherit+0x42e/0x2e20 fs/btrfs/qgroup.c:3277  Read of size 8 at addr ffff88814628ca50 by task syz-executor318/5171  CPU: 0 PID: 5171 Comm: syz-executor318 Not tainted 6.10.0-rc2-syzkaller-00010-g2ab795141095 #0  Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024  Call Trace:   &lt;TASK&gt;   __dump_stack lib/dump_stack.c:88 [inline]   dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114   print_address_description mm/kasan/report.c:377 [inline]   print_report+0x169/0x550 mm/kasan/report.c:488   kasan_report+0x143/0x180 mm/kasan/report.c:601   btrfs_qgroup_inherit+0x42e/0x2e20 fs/btrfs/qgroup.c:3277   create_pending_snapshot+0x1359/0x29b0 fs/btrfs/transaction.c:1854   create_pending_snapshots+0x195/0x1d0 fs/btrfs/transaction.c:1922   btrfs_commit_transaction+0xf20/0x3740 fs/btrfs/transaction.c:2382   create_snapshot+0x6a1/0x9e0 fs/btrfs/ioctl.c:875   btrfs_mksubvol+0x58f/0x710 fs/btrfs/ioctl.c:1029   btrfs_mksnapshot+0xb5/0xf0 fs/btrfs/ioctl.c:1075   __btrfs_ioctl_snap_create+0x387/0x4b0 fs/btrfs/ioctl.c:1340   btrfs_ioctl_snap_create_v2+0x1f2/0x3a0 fs/btrfs/ioctl.c:1422   btrfs_ioctl+0x99e/0xc60   vfs_ioctl fs/ioctl.c:51 [inline]   __do_sys_ioctl fs/ioctl.c:907 [inline]   __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893   do_syscall_x64 arch/x86/entry/common.c:52 [inline]   do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83   entry_SYSCALL_64_after_hwframe+0x77/0x7f  RIP: 0033:0x7fcbf1992509  RSP: 002b:00007fcbf1928218 EFLAGS: 00000246 ORIG_RAX: 0000000000000010  RAX: ffffffffffffffda RBX: 00007fcbf1a1f618 RCX: 00007fcbf1992509  RDX: 0000000020000280 RSI: 0000000050009417 RDI: 0000000000000003  RBP: 00007fcbf1a1f610 R08: 00007ffea1298e97 R09: 0000000000000000  R10: 0000000000000000 R11: 0000000000000246 R12: 00007fcbf19eb660  R13: 00000000200002b8 R14: 00007fcbf19e60c0 R15: 0030656c69662f2e   &lt;/TASK&gt;And it also pinned it down to commit b5357cb268c4 (&#34;btrfs: qgroup: do notcheck qgroup inherit if qgroup is disabled&#34;).[CAUSE]That offending commit skips the whole qgroup inherit check if qgroup isnot enabled.But that also skips the very basic checks likenum_ref_copies/num_excl_copies and the structure size checks.Meaning if a qgroup enable/disable race is happening at the background,and we pass a btrfs_qgroup_inherit structure when the qgroup isdisabled, the check would be completely skipped.Then at the time of transaction commitment, qgroup is re-enabled andbtrfs_qgroup_inherit() is going to use the incorrect structure andcausing the above KASAN error.[FIX]Make btrfs_qgroup_check_inherit() only skip the source qgroup checks.So that even if invalid btrfs_qgroup_inherit structure is passed in, wecan still reject invalid ones no matter if qgroup is enabled or not.Furthermore we do already have an extra safety insidebtrfs_qgroup_inherit(), which would just ignore invalid qgroup sources,so even if we only skip the qgroup source check we&#39;re still safe.The Linux kernel CVE team has assigned CVE-2024-42111 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:否|

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