CVE-2024-42149

一、漏洞信息
漏洞编号：CVE-2024-42149
漏洞归属组件：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:fs: don t misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it s elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.
漏洞公开时间：2024-07-30 16:15:06
漏洞创建时间：2024-07-31 07:54:42
漏洞详情参考链接：
https://nvd.nist.gov/vuln/detail/CVE-2024-42149

更多参考(点击展开)

参考来源	参考链接	来源链接
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/25b1e3906e050d452427bc51620bb7f0a591373a
416baaa9-dc9f-4396-8d5f-8c081fb06d67	https://git.kernel.org/stable/c/2ae4db5647d807efb6a87c09efaa6d1db9c905d7
suse_bugzilla	http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-42149	https://bugzilla.suse.com/show_bug.cgi?id=1228562
suse_bugzilla	https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-42149.mbox	https://bugzilla.suse.com/show_bug.cgi?id=1228562
suse_bugzilla	https://git.kernel.org/stable/c/25b1e3906e050d452427bc51620bb7f0a591373a	https://bugzilla.suse.com/show_bug.cgi?id=1228562
suse_bugzilla	https://git.kernel.org/stable/c/2ae4db5647d807efb6a87c09efaa6d1db9c905d7	https://bugzilla.suse.com/show_bug.cgi?id=1228562
suse_bugzilla	https://www.cve.org/CVERecord?id=CVE-2024-42149	https://bugzilla.suse.com/show_bug.cgi?id=1228562
ubuntu	https://www.cve.org/CVERecord?id=CVE-2024-42149	https://ubuntu.com/security/CVE-2024-42149
ubuntu	https://git.kernel.org/linus/2ae4db5647d807efb6a87c09efaa6d1db9c905d7 (6.10-rc7)	https://ubuntu.com/security/CVE-2024-42149
ubuntu	https://git.kernel.org/stable/c/25b1e3906e050d452427bc51620bb7f0a591373a	https://ubuntu.com/security/CVE-2024-42149
ubuntu	https://git.kernel.org/stable/c/2ae4db5647d807efb6a87c09efaa6d1db9c905d7	https://ubuntu.com/security/CVE-2024-42149
ubuntu	https://nvd.nist.gov/vuln/detail/CVE-2024-42149	https://ubuntu.com/security/CVE-2024-42149
ubuntu	https://launchpad.net/bugs/cve/CVE-2024-42149	https://ubuntu.com/security/CVE-2024-42149
ubuntu	https://security-tracker.debian.org/tracker/CVE-2024-42149	https://ubuntu.com/security/CVE-2024-42149
debian		https://security-tracker.debian.org/tracker/CVE-2024-42149

漏洞分析指导链接：
https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
漏洞数据来源:
其它
漏洞补丁信息：

详情(点击展开)

影响的包	修复版本	修复补丁	问题引入补丁	来源
linux		https://git.kernel.org/linus/2ae4db5647d807efb6a87c09efaa6d1db9c905d7	https://git.kernel.org/linus/49ef8832fb1a9e0da0020eb17480fd286433bc13	ubuntu

二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 to this issue.
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):否

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-42149	None	None	https://git.kernel.org/stable/c/25b1e3906e050d452427bc51620bb7f0a591373a https://git.kernel.org/stable/c/2ae4db5647d807efb6a87c09efaa6d1db9c905d7
https://ubuntu.com/security/CVE-2024-42149
https://www.opencve.io/cve/CVE-2024-42149	None	None	https://git.kernel.org/stable/c/25b1e3906e050d452427bc51620bb7f0a591373a https://git.kernel.org/stable/c/2ae4db5647d807efb6a87c09efaa6d1db9c905d7
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2024-42149
https://security-tracker.debian.org/tracker/CVE-2024-42149	None	None	https://git.kernel.org/linus/2ae4db5647d807efb6a87c09efaa6d1db9c905d7

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

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

fs: don't misleadingly warn during thaw operations

The block device may have been frozen before it was claimed by a
filesystem. Concurrently another process might try to mount that
frozen block device and has temporarily claimed the block device for
that purpose causing a concurrent fs_bdev_thaw() to end up here. The
mounter is already about to abort mounting because they still saw an
elevanted bdev->bd_fsfreeze_count so get_bdev_super() will return
NULL in that case.

For example, P1 calls dm_suspend() which calls into bdev_freeze() before
the block device has been claimed by the filesystem. This brings
bdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() is
required.

Now P2 tries to mount that frozen block device. It claims it and checks
bdev->bd_fsfreeze_count. As it's elevated it aborts mounting.

In the meantime P3 called dm_resume(). P3 sees that the block device is
already claimed by a filesystem and calls into fs_bdev_thaw().

P3 takes a passive reference and realizes that the filesystem isn't
ready yet. P3 puts itself to sleep to wait for the filesystem to become
ready.

P2 now puts the last active reference to the filesystem and marks it as
dying. P3 gets woken, sees that the filesystem is dying and
get_bdev_super() fails.

The Linux kernel CVE team has assigned CVE-2024-42149 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:fs: don't misleadingly warn during thaw operationsThe block device may have been frozen before it was claimed by afilesystem. Concurrently another process might try to mount thatfrozen block device and has temporarily claimed the block device forthat purpose causing a concurrent fs_bdev_thaw() to end up here. Themounter is already about to abort mounting because they still saw anelevanted bdev->bd_fsfreeze_count so get_bdev_super() will returnNULL in that case.For example, P1 calls dm_suspend() which calls into bdev_freeze() beforethe block device has been claimed by the filesystem. This bringsbdev->bd_fsfreeze_count to 1 and no call into fs_bdev_freeze() isrequired.Now P2 tries to mount that frozen block device. It claims it and checksbdev->bd_fsfreeze_count. As it's elevated it aborts mounting.In the meantime P3 called dm_resume(). P3 sees that the block device isalready claimed by a filesystem and calls into fs_bdev_thaw().P3 takes a passive reference and realizes that the filesystem isn'tready yet. P3 puts itself to sleep to wait for the filesystem to becomeready.P2 now puts the last active reference to the filesystem and marks it asdying. P3 gets woken, sees that the filesystem is dying andget_bdev_super() fails.The Linux kernel CVE team has assigned CVE-2024-42149 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:否

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

src-openEuler/kernel

内容风险标识

评论 (5)

src-openEuler/kernel .gitee-modal { width: 500px !important; }

内容风险标识

CVE-2024-42149

评论 (5)

搜索帮助

src-openEuler/kernel