CVE-2024-39276

一、漏洞信息
 漏洞编号：[CVE-2024-39276](https://nvd.nist.gov/vuln/detail/CVE-2024-39276)
 漏洞归属组件：[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 Medium
 Vector：CVSS：2.0/
 漏洞简述：
 In the Linux kernel, the following vulnerability has been resolved:ext4: fix mb_cache_entry s e_refcnt leak in ext4_xattr_block_cache_find()Syzbot reports a warning as follows:============================================WARNING: CPU: 0 PID: 5075 at fs/mbcache.c:419 mb_cache_destroy+0x224/0x290Modules linked in:CPU: 0 PID: 5075 Comm: syz-executor199 Not tainted 6.9.0-rc6-gb947cc5bf6d7RIP: 0010:mb_cache_destroy+0x224/0x290 fs/mbcache.c:419Call Trace: <TASK> ext4_put_super+0x6d4/0xcd0 fs/ext4/super.c:1375 generic_shutdown_super+0x136/0x2d0 fs/super.c:641 kill_block_super+0x44/0x90 fs/super.c:1675 ext4_kill_sb+0x68/0xa0 fs/ext4/super.c:7327[...]============================================This is because when finding an entry in ext4_xattr_block_cache_find(), ifext4_sb_bread() returns -ENOMEM, the ce s e_refcnt, which has already grownin the __entry_find(), won t be put away, and eventually trigger the aboveissue in mb_cache_destroy() due to reference count leakage.So call mb_cache_entry_put() on the -ENOMEM error branch as a quick fix.
 漏洞公开时间：2024-06-25 23:15:13
 漏洞创建时间：2024-07-09 14:11:20
 漏洞详情参考链接：
 https://nvd.nist.gov/vuln/detail/CVE-2024-39276
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/0c0b4a49d3e7f49690a6827a41faeffad5df7e21 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/681ff9a09accd8a4379f8bd30b7a1641ee19bb3e |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/76dc776153a47372719d664e0fc50d6355791abb |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/896a7e7d0d555ad8b2b46af0c2fa7de7467f9483 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/9ad75e78747b5a50dc5a52f0f8e92e920a653f16 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/a95df6f04f2c37291adf26a74205cde0314d4577 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/b37c0edef4e66fb21a2fbc211471195a383e5ab8 |  |
| 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | https://git.kernel.org/stable/c/e941b712e758f615d311946bf98216e79145ccd9 |  |
| suse_bugzilla | http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-39276 | https://bugzilla.suse.com/show_bug.cgi?id=1226993 |
| suse_bugzilla | https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-39276.mbox | https://bugzilla.suse.com/show_bug.cgi?id=1226993 |
| suse_bugzilla | https://git.kernel.org/stable/c/9ad75e78747b5a50dc5a52f0f8e92e920a653f16 | https://bugzilla.suse.com/show_bug.cgi?id=1226993 |
| suse_bugzilla | https://git.kernel.org/stable/c/896a7e7d0d555ad8b2b46af0c2fa7de7467f9483 | https://bugzilla.suse.com/show_bug.cgi?id=1226993 |
| suse_bugzilla | https://git.kernel.org/stable/c/76dc776153a47372719d664e0fc50d6355791abb | https://bugzilla.suse.com/show_bug.cgi?id=1226993 |
| suse_bugzilla | https://git.kernel.org/stable/c/681ff9a09accd8a4379f8bd30b7a1641ee19bb3e | https://bugzilla.suse.com/show_bug.cgi?id=1226993 |
| suse_bugzilla | https://git.kernel.org/stable/c/e941b712e758f615d311946bf98216e79145ccd9 | https://bugzilla.suse.com/show_bug.cgi?id=1226993 |
| suse_bugzilla | https://git.kernel.org/stable/c/a95df6f04f2c37291adf26a74205cde0314d4577 | https://bugzilla.suse.com/show_bug.cgi?id=1226993 |
| suse_bugzilla | https://git.kernel.org/stable/c/b37c0edef4e66fb21a2fbc211471195a383e5ab8 | https://bugzilla.suse.com/show_bug.cgi?id=1226993 |
| suse_bugzilla | https://git.kernel.org/stable/c/0c0b4a49d3e7f49690a6827a41faeffad5df7e21 | https://bugzilla.suse.com/show_bug.cgi?id=1226993 |
| suse_bugzilla | https://www.cve.org/CVERecord?id=CVE-2024-39276 | https://bugzilla.suse.com/show_bug.cgi?id=1226993 |
| suse_bugzilla | https://bugzilla.redhat.com/show_bug.cgi?id=2294274 | https://bugzilla.suse.com/show_bug.cgi?id=1226993 |
| redhat_bugzilla | https://lore.kernel.org/linux-cve-announce/2024062548-CVE-2024-39276-5205@gregkh/T | https://bugzilla.redhat.com/show_bug.cgi?id=2294274 |
| redhat_bugzilla | https://access.redhat.com/errata/RHSA-2024:5102 | https://bugzilla.redhat.com/show_bug.cgi?id=2294274 |
| redhat_bugzilla | https://access.redhat.com/errata/RHSA-2024:5101 | https://bugzilla.redhat.com/show_bug.cgi?id=2294274 |
| ubuntu | https://www.cve.org/CVERecord?id=CVE-2024-39276 | https://ubuntu.com/security/CVE-2024-39276 |
| ubuntu | https://git.kernel.org/linus/0c0b4a49d3e7f49690a6827a41faeffad5df7e21 (6.10-rc1) | https://ubuntu.com/security/CVE-2024-39276 |
| ubuntu | https://git.kernel.org/stable/c/9ad75e78747b5a50dc5a52f0f8e92e920a653f16 | https://ubuntu.com/security/CVE-2024-39276 |
| ubuntu | https://git.kernel.org/stable/c/896a7e7d0d555ad8b2b46af0c2fa7de7467f9483 | https://ubuntu.com/security/CVE-2024-39276 |
| ubuntu | https://git.kernel.org/stable/c/76dc776153a47372719d664e0fc50d6355791abb | https://ubuntu.com/security/CVE-2024-39276 |
| ubuntu | https://git.kernel.org/stable/c/681ff9a09accd8a4379f8bd30b7a1641ee19bb3e | https://ubuntu.com/security/CVE-2024-39276 |
| ubuntu | https://git.kernel.org/stable/c/e941b712e758f615d311946bf98216e79145ccd9 | https://ubuntu.com/security/CVE-2024-39276 |
| ubuntu | https://git.kernel.org/stable/c/a95df6f04f2c37291adf26a74205cde0314d4577 | https://ubuntu.com/security/CVE-2024-39276 |
| ubuntu | https://git.kernel.org/stable/c/b37c0edef4e66fb21a2fbc211471195a383e5ab8 | https://ubuntu.com/security/CVE-2024-39276 |
| ubuntu | https://git.kernel.org/stable/c/0c0b4a49d3e7f49690a6827a41faeffad5df7e21 | https://ubuntu.com/security/CVE-2024-39276 |
| ubuntu | https://ubuntu.com/security/notices/USN-6951-1 | https://ubuntu.com/security/CVE-2024-39276 |
| ubuntu | https://ubuntu.com/security/notices/USN-6953-1 | https://ubuntu.com/security/CVE-2024-39276 |
| ubuntu | https://ubuntu.com/security/notices/USN-6951-2 | https://ubuntu.com/security/CVE-2024-39276 |
| ubuntu | https://ubuntu.com/security/notices/USN-6951-3 | https://ubuntu.com/security/CVE-2024-39276 |
| ubuntu | https://ubuntu.com/security/notices/USN-6951-4 | https://ubuntu.com/security/CVE-2024-39276 |
| ubuntu | https://ubuntu.com/security/notices/USN-6979-1 | https://ubuntu.com/security/CVE-2024-39276 |
| ubuntu | https://nvd.nist.gov/vuln/detail/CVE-2024-39276 | https://ubuntu.com/security/CVE-2024-39276 |
| ubuntu | https://launchpad.net/bugs/cve/CVE-2024-39276 | https://ubuntu.com/security/CVE-2024-39276 |
| ubuntu | https://security-tracker.debian.org/tracker/CVE-2024-39276 | https://ubuntu.com/security/CVE-2024-39276 |
| debian |  | https://security-tracker.debian.org/tracker/CVE-2024-39276 |
| anolis |  | https://anas.openanolis.cn/cves/detail/CVE-2024-39276 |
| cve_search |  | https://git.kernel.org/stable/c/9ad75e78747b5a50dc5a52f0f8e92e920a653f16 |
| cve_search |  | https://git.kernel.org/stable/c/896a7e7d0d555ad8b2b46af0c2fa7de7467f9483 |
| cve_search |  | https://git.kernel.org/stable/c/76dc776153a47372719d664e0fc50d6355791abb |
| cve_search |  | https://git.kernel.org/stable/c/681ff9a09accd8a4379f8bd30b7a1641ee19bb3e |
| cve_search |  | https://git.kernel.org/stable/c/e941b712e758f615d311946bf98216e79145ccd9 |
| cve_search |  | https://git.kernel.org/stable/c/a95df6f04f2c37291adf26a74205cde0314d4577 |
| cve_search |  | https://git.kernel.org/stable/c/b37c0edef4e66fb21a2fbc211471195a383e5ab8 |
| cve_search |  | https://git.kernel.org/stable/c/0c0b4a49d3e7f49690a6827a41faeffad5df7e21 |
| mageia |  | http://advisories.mageia.org/MGASA-2024-0263.html |

</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/0c0b4a49d3e7f49690a6827a41faeffad5df7e21 | https://git.kernel.org/linus/fb265c9cb49e2074ddcdd4de99728aefdd3b3592 | ubuntu |

</details>

二、漏洞分析结构反馈
 影响性分析说明：
 In the Linux kernel, the following vulnerability has been resolved:ext4: fix mb_cache_entry s e_refcnt leak in ext4_xattr_block_cache_find()Syzbot reports a warning as follows:============================================WARNING: CPU: 0 PID: 5075 at fs/mbcache.c:419 mb_cache_destroy+0x224/0x290Modules linked in:CPU: 0 PID: 5075 Comm: syz-executor199 Not tainted 6.9.0-rc6-gb947cc5bf6d7RIP: 0010:mb_cache_destroy+0x224/0x290 fs/mbcache.c:419Call Trace: <TASK> ext4_put_super+0x6d4/0xcd0 fs/ext4/super.c:1375 generic_shutdown_super+0x136/0x2d0 fs/super.c:641 kill_block_super+0x44/0x90 fs/super.c:1675 ext4_kill_sb+0x68/0xa0 fs/ext4/super.c:7327[...]============================================This is because when finding an entry in ext4_xattr_block_cache_find(), ifext4_sb_bread() returns -ENOMEM, the ce s e_refcnt, which has already grownin the __entry_find(), won t be put away, and eventually trigger the aboveissue in mb_cache_destroy() due to reference count leakage.So call mb_cache_entry_put() on the -ENOMEM error branch as a quick fix. 
 openEuler评分：
 4.7
 Vector：CVSS：2.0/AV:L/AC:H/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.1.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):否

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

@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-39276</td><td>None</td><td>None</td><td><a href=https://git.kernel.org/stable/c/681ff9a09accd8a4379f8bd30b7a1641ee19bb3e>https://git.kernel.org/stable/c/681ff9a09accd8a4379f8bd30b7a1641ee19bb3e</a> <a href=https://git.kernel.org/stable/c/9ad75e78747b5a50dc5a52f0f8e92e920a653f16>https://git.kernel.org/stable/c/9ad75e78747b5a50dc5a52f0f8e92e920a653f16</a> <a href=https://git.kernel.org/stable/c/b37c0edef4e66fb21a2fbc211471195a383e5ab8>https://git.kernel.org/stable/c/b37c0edef4e66fb21a2fbc211471195a383e5ab8</a> <a href=https://git.kernel.org/stable/c/a95df6f04f2c37291adf26a74205cde0314d4577>https://git.kernel.org/stable/c/a95df6f04f2c37291adf26a74205cde0314d4577</a> <a href=https://git.kernel.org/stable/c/e941b712e758f615d311946bf98216e79145ccd9>https://git.kernel.org/stable/c/e941b712e758f615d311946bf98216e79145ccd9</a> <a href=https://git.kernel.org/stable/c/76dc776153a47372719d664e0fc50d6355791abb>https://git.kernel.org/stable/c/76dc776153a47372719d664e0fc50d6355791abb</a> <a href=https://git.kernel.org/stable/c/896a7e7d0d555ad8b2b46af0c2fa7de7467f9483>https://git.kernel.org/stable/c/896a7e7d0d555ad8b2b46af0c2fa7de7467f9483</a> <a href=https://git.kernel.org/stable/c/0c0b4a49d3e7f49690a6827a41faeffad5df7e21>https://git.kernel.org/stable/c/0c0b4a49d3e7f49690a6827a41faeffad5df7e21</a></td></tr><tr><td rowspan="1">https://ubuntu.com/security/CVE-2024-39276</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-39276</td><td>None</td><td>None</td><td><a href=https://git.kernel.org/stable/c/681ff9a09accd8a4379f8bd30b7a1641ee19bb3e>https://git.kernel.org/stable/c/681ff9a09accd8a4379f8bd30b7a1641ee19bb3e</a> <a href=https://git.kernel.org/stable/c/9ad75e78747b5a50dc5a52f0f8e92e920a653f16>https://git.kernel.org/stable/c/9ad75e78747b5a50dc5a52f0f8e92e920a653f16</a> <a href=https://git.kernel.org/stable/c/b37c0edef4e66fb21a2fbc211471195a383e5ab8>https://git.kernel.org/stable/c/b37c0edef4e66fb21a2fbc211471195a383e5ab8</a> <a href=https://git.kernel.org/stable/c/a95df6f04f2c37291adf26a74205cde0314d4577>https://git.kernel.org/stable/c/a95df6f04f2c37291adf26a74205cde0314d4577</a> <a href=https://git.kernel.org/stable/c/e941b712e758f615d311946bf98216e79145ccd9>https://git.kernel.org/stable/c/e941b712e758f615d311946bf98216e79145ccd9</a> <a href=https://git.kernel.org/stable/c/76dc776153a47372719d664e0fc50d6355791abb>https://git.kernel.org/stable/c/76dc776153a47372719d664e0fc50d6355791abb</a> <a href=https://git.kernel.org/stable/c/896a7e7d0d555ad8b2b46af0c2fa7de7467f9483>https://git.kernel.org/stable/c/896a7e7d0d555ad8b2b46af0c2fa7de7467f9483</a> <a href=https://git.kernel.org/stable/c/0c0b4a49d3e7f49690a6827a41faeffad5df7e21>https://git.kernel.org/stable/c/0c0b4a49d3e7f49690a6827a41faeffad5df7e21</a></td></tr><tr><td>https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2024-39276</td><td></td><td></td><td></td></tr><tr><td rowspan="1">https://security-tracker.debian.org/tracker/CVE-2024-39276</td><td>None</td><td>None</td><td><a href=https://git.kernel.org/linus/0c0b4a49d3e7f49690a6827a41faeffad5df7e21>https://git.kernel.org/linus/0c0b4a49d3e7f49690a6827a41faeffad5df7e21</a></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-39276

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

ext4: fix mb_cache_entry&#39;s e_refcnt leak in ext4_xattr_block_cache_find()

Syzbot reports a warning as follows:

============================================
WARNING: CPU: 0 PID: 5075 at fs/mbcache.c:419 mb_cache_destroy+0x224/0x290
Modules linked in:
CPU: 0 PID: 5075 Comm: syz-executor199 Not tainted 6.9.0-rc6-gb947cc5bf6d7
RIP: 0010:mb_cache_destroy+0x224/0x290 fs/mbcache.c:419
Call Trace:
 &lt;TASK&gt;
 ext4_put_super+0x6d4/0xcd0 fs/ext4/super.c:1375
 generic_shutdown_super+0x136/0x2d0 fs/super.c:641
 kill_block_super+0x44/0x90 fs/super.c:1675
 ext4_kill_sb+0x68/0xa0 fs/ext4/super.c:7327
[...]
============================================

This is because when finding an entry in ext4_xattr_block_cache_find(), if
ext4_sb_bread() returns -ENOMEM, the ce&#39;s e_refcnt, which has already grown
in the __entry_find(), won&#39;t be put away, and eventually trigger the above
issue in mb_cache_destroy() due to reference count leakage.

So call mb_cache_entry_put() on the -ENOMEM error branch as a quick fix.

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

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

受影响版本排查(受影响/不受影响):
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.openEuler-22.03-LTS-SP4:不受影响
8.master(6.1.0):不受影响
9.openEuler-22.03-LTS-Next:不受影响
10.openEuler-24.03-LTS:受影响
11.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:否
11.openEuler-22.03-LTS-SP4:否

@ 经过 cve-manager 解析, 已分析的内容如下表所示:
| 状态  | 需分析 | 内容 |
|:--:|:--:|---------|
|已分析|1.影响性分析说明|In the Linux kernel, the following vulnerability has been resolved:ext4: fix mb_cache_entry&#39;s e_refcnt leak in ext4_xattr_block_cache_find()Syzbot reports a warning as follows:============================================WARNING: CPU: 0 PID: 5075 at fs/mbcache.c:419 mb_cache_destroy+0x224/0x290Modules linked in:CPU: 0 PID: 5075 Comm: syz-executor199 Not tainted 6.9.0-rc6-gb947cc5bf6d7RIP: 0010:mb_cache_destroy+0x224/0x290 fs/mbcache.c:419Call Trace: &lt;TASK&gt; ext4_put_super+0x6d4/0xcd0 fs/ext4/super.c:1375 generic_shutdown_super+0x136/0x2d0 fs/super.c:641 kill_block_super+0x44/0x90 fs/super.c:1675 ext4_kill_sb+0x68/0xa0 fs/ext4/super.c:7327[...]============================================This is because when finding an entry in ext4_xattr_block_cache_find(), ifext4_sb_bread() returns -ENOMEM, the ce&#39;s e_refcnt, which has already grownin the __entry_find(), won&#39;t be put away, and eventually trigger the aboveissue in mb_cache_destroy() due to reference count leakage.So call mb_cache_entry_put() on the -ENOMEM error branch as a quick fix.The Linux kernel CVE team has assigned CVE-2024-39276 to this issue.|
|已分析|2.openEulerScore|4.7|
|已分析|3.openEulerVector|AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:N|
|已分析|4.受影响版本排查|openEuler-20.03-LTS-SP1:受影响,openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP1:受影响,openEuler-22.03-LTS-SP3:受影响,openEuler-24.03-LTS:受影响,openEuler-24.03-LTS-Next:受影响,openEuler-22.03-LTS:不受影响,openEuler-22.03-LTS-SP2:不受影响,openEuler-22.03-LTS-SP4:不受影响,master:不受影响,openEuler-22.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:否,openEuler-22.03-LTS-SP4:否|

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