已开启
CVE-2024-56780 #1404
AtomGit-Bot创建于  2025年1月13日
AtomGit-Bot
2025年1月13日 创建

一、漏洞信息
漏洞编号:CVE-2024-56780
漏洞归属组件:kernel
漏洞归属的版本:4.19.140,4.19.194,4.19.90,5.10.0,6.1.19,6.1.8,6.4.0,6.6.0
CVSS评分:
BaseScore:5.5 Medium
Vector:CVSS:3.1/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:quota: flush quota_release_work upon quota writebackOne of the paths quota writeback is called from is:freeze_super() sync_filesystem() ext4_sync_fs() dquot_writeback_dquots()Since we currently don t always flush the quota_release_work queue inthis path, we can end up with the following race: 1. dquot are added to releasing_dquots list during regular operations. 2. FS Freeze starts, however, this does not flush the quota_release_work queue. 3. Freeze completes. 4. Kernel eventually tries to flush the workqueue while FS is frozen which hits a WARN_ON since transaction gets started during frozen state: ext4_journal_check_start+0x28/0x110 [ext4] (unreliable) __ext4_journal_start_sb+0x64/0x1c0 [ext4] ext4_release_dquot+0x90/0x1d0 [ext4] quota_release_workfn+0x43c/0x4d0Which is the following line: WARN_ON(sb->s_writers.frozen == SB_FREEZE_COMPLETE);Which ultimately results in generic/390 failing due to dmesgnoise. This was detected on powerpc machine 15 cores.To avoid this, make sure to flush the workqueue duringdquot_writeback_dquots() so we dont have any pending workitems afterfreeze.
漏洞公开时间:2025-01-09 02:15:18
漏洞创建时间:2025-01-13 10:26:30
漏洞详情参考链接:
https://nvd.nist.gov/vuln/detail/CVE-2024-56780

更多参考(点击展开)
参考来源 参考链接 来源链接
416baaa9-dc9f-4396-8d5f-8c081fb06d67 https://git.kernel.org/stable/c/3e6ff207cd5bd924ad94cd1a7c633bcdac0ba1cb
416baaa9-dc9f-4396-8d5f-8c081fb06d67 https://git.kernel.org/stable/c/6f3821acd7c3143145999248087de5fb4b48cf26
416baaa9-dc9f-4396-8d5f-8c081fb06d67 https://git.kernel.org/stable/c/8ea87e34792258825d290f4dc5216276e91cb224
416baaa9-dc9f-4396-8d5f-8c081fb06d67 https://git.kernel.org/stable/c/a5abba5e0e586e258ded3e798fe5f69c66fec198
416baaa9-dc9f-4396-8d5f-8c081fb06d67 https://git.kernel.org/stable/c/ab6cfcf8ed2c7496f55d020b65b1d8cd55d9a2cb
416baaa9-dc9f-4396-8d5f-8c081fb06d67 https://git.kernel.org/stable/c/ac6f420291b3fee1113f21d612fa88b628afab5b
416baaa9-dc9f-4396-8d5f-8c081fb06d67 https://git.kernel.org/stable/c/bcacb52a985f1b6d280f698a470b873dfe52728a
suse_bugzilla http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-56780 https://bugzilla.suse.com/show_bug.cgi?id=1235650
suse_bugzilla https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-56780.mbox https://bugzilla.suse.com/show_bug.cgi?id=1235650
suse_bugzilla https://git.kernel.org/stable/c/a5abba5e0e586e258ded3e798fe5f69c66fec198 https://bugzilla.suse.com/show_bug.cgi?id=1235650
suse_bugzilla https://git.kernel.org/stable/c/6f3821acd7c3143145999248087de5fb4b48cf26 https://bugzilla.suse.com/show_bug.cgi?id=1235650
suse_bugzilla https://git.kernel.org/stable/c/ab6cfcf8ed2c7496f55d020b65b1d8cd55d9a2cb https://bugzilla.suse.com/show_bug.cgi?id=1235650
suse_bugzilla https://git.kernel.org/stable/c/3e6ff207cd5bd924ad94cd1a7c633bcdac0ba1cb https://bugzilla.suse.com/show_bug.cgi?id=1235650
suse_bugzilla https://git.kernel.org/stable/c/bcacb52a985f1b6d280f698a470b873dfe52728a https://bugzilla.suse.com/show_bug.cgi?id=1235650
suse_bugzilla https://git.kernel.org/stable/c/8ea87e34792258825d290f4dc5216276e91cb224 https://bugzilla.suse.com/show_bug.cgi?id=1235650
suse_bugzilla https://git.kernel.org/stable/c/ac6f420291b3fee1113f21d612fa88b628afab5b https://bugzilla.suse.com/show_bug.cgi?id=1235650
suse_bugzilla https://www.cve.org/CVERecord?id=CVE-2024-56780 https://bugzilla.suse.com/show_bug.cgi?id=1235650
suse_bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=2336549 https://bugzilla.suse.com/show_bug.cgi?id=1235650
redhat_bugzilla https://lore.kernel.org/linux-cve-announce/2025010813-CVE-2024-56780-6b91@gregkh/T https://bugzilla.redhat.com/show_bug.cgi?id=2336549
debian https://security-tracker.debian.org/tracker/CVE-2024-56780
anolis https://anas.openanolis.cn/cves/detail/CVE-2024-56780
osv https://git.kernel.org/stable/c/3e6ff207cd5bd924ad94cd1a7c633bcdac0ba1cb https://osv.dev/vulnerability/CVE-2024-56780
osv https://git.kernel.org/stable/c/6f3821acd7c3143145999248087de5fb4b48cf26 https://osv.dev/vulnerability/CVE-2024-56780
osv https://git.kernel.org/stable/c/8ea87e34792258825d290f4dc5216276e91cb224 https://osv.dev/vulnerability/CVE-2024-56780
osv https://git.kernel.org/stable/c/a5abba5e0e586e258ded3e798fe5f69c66fec198 https://osv.dev/vulnerability/CVE-2024-56780
osv https://git.kernel.org/stable/c/ab6cfcf8ed2c7496f55d020b65b1d8cd55d9a2cb https://osv.dev/vulnerability/CVE-2024-56780
osv https://git.kernel.org/stable/c/ac6f420291b3fee1113f21d612fa88b628afab5b https://osv.dev/vulnerability/CVE-2024-56780
osv https://git.kernel.org/stable/c/bcacb52a985f1b6d280f698a470b873dfe52728a https://osv.dev/vulnerability/CVE-2024-56780
osv https://security-tracker.debian.org/tracker/CVE-2024-56780 https://osv.dev/vulnerability/CVE-2024-56780

漏洞分析指导链接:
https://atomgit.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
漏洞数据来源:
openBrain开源漏洞感知系统
漏洞补丁信息:

详情(点击展开)
影响的包 修复版本 修复补丁 问题引入补丁 来源
https://git.kernel.org/stable/c/3e6ff207cd5bd924ad94cd1a7c633bcdac0ba1cb nvd
https://git.kernel.org/stable/c/6f3821acd7c3143145999248087de5fb4b48cf26 nvd
https://git.kernel.org/stable/c/8ea87e34792258825d290f4dc5216276e91cb224 nvd
https://git.kernel.org/stable/c/a5abba5e0e586e258ded3e798fe5f69c66fec198 nvd
https://git.kernel.org/stable/c/ab6cfcf8ed2c7496f55d020b65b1d8cd55d9a2cb nvd
https://git.kernel.org/stable/c/ac6f420291b3fee1113f21d612fa88b628afab5b nvd
https://git.kernel.org/stable/c/bcacb52a985f1b6d280f698a470b873dfe52728a nvd
linux_kernel 5.4.287 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a5abba5e0e586e258ded3e798fe5f69c66fec198Issue https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d40c192e119892799dd4ddf94f5cea6fa93775ef linuxkernelcves
linux_kernel 5.10.231 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=6f3821acd7c3143145999248087de5fb4b48cf26Issue https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d40c192e119892799dd4ddf94f5cea6fa93775ef linuxkernelcves
linux_kernel 5.15.174 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ab6cfcf8ed2c7496f55d020b65b1d8cd55d9a2cbIssue https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d40c192e119892799dd4ddf94f5cea6fa93775ef linuxkernelcves
linux_kernel 6.1.120 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=3e6ff207cd5bd924ad94cd1a7c633bcdac0ba1cbIssue https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d40c192e119892799dd4ddf94f5cea6fa93775ef linuxkernelcves
linux_kernel 6.6.64 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=bcacb52a985f1b6d280f698a470b873dfe52728aIssue https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d40c192e119892799dd4ddf94f5cea6fa93775ef linuxkernelcves
linux_kernel 6.12.4 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=8ea87e34792258825d290f4dc5216276e91cb224Issue https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d40c192e119892799dd4ddf94f5cea6fa93775ef linuxkernelcves
linux_kernel 6.13-rc2 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ac6f420291b3fee1113f21d612fa88b628afab5bIssue https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d40c192e119892799dd4ddf94f5cea6fa93775ef linuxkernelcves

二、漏洞分析结构反馈
影响性分析说明:
In the Linux kernel, the following vulnerability has been resolved:quota: flush quota_release_work upon quota writebackOne of the paths quota writeback is called from is:freeze_super() sync_filesystem() ext4_sync_fs() dquot_writeback_dquots()Since we currently don t always flush the quota_release_work queue inthis path, we can end up with the following race: 1. dquot are added to releasing_dquots list during regular operations. 2. FS Freeze starts, however, this does not flush the quota_release_work queue. 3. Freeze completes. 4. Kernel eventually tries to flush the workqueue while FS is frozen which hits a WARN_ON since transaction gets started during frozen state: ext4_journal_check_start+0x28/0x110 [ext4] (unreliable) __ext4_journal_start_sb+0x64/0x1c0 [ext4] ext4_release_dquot+0x90/0x1d0 [ext4] quota_release_workfn+0x43c/0x4d0Which is the following line: WARN_ON(sb->s_writers.frozen == SB_FREEZE_COMPLETE);Which ultimately results in generic/390 failing due to dmesgnoise. This was detected on powerpc machine 15 cores.To avoid this, make sure to flush the workqueue duringdquot_writeback_dquots() so we dont have any pending workitems afterfreeze.
openEuler评分:
5.5
Vector:CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
受影响版本排查(受影响/不受影响):
1.master(6.18.40):不受影响
2.openEuler-20.03-LTS-SP4(4.19.90):受影响
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.openEuler-24.03-LTS-Next(6.6.0):不受影响
7.openEuler-24.03-LTS-SP1(6.6.0):受影响
8.openEuler-24.03-LTS-SP2(6.6.0):受影响
9.openEuler-24.03-LTS-SP3(6.6.0):不受影响
10.openEuler-24.03-LTS-SP4(6.6.0):不受影响

修复是否涉及abi变化(是/否):
1.master(6.18.40):否
2.openEuler-20.03-LTS-SP4(4.19.90):否
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.openEuler-24.03-LTS-Next(6.6.0):否
7.openEuler-24.03-LTS-SP1(6.6.0):否
8.openEuler-24.03-LTS-SP2(6.6.0):否
9.openEuler-24.03-LTS-SP3(6.6.0):否
10.openEuler-24.03-LTS-SP4(6.6.0):否

原因说明:
1.master(6.18.40):不受影响-漏洞代码不能被攻击者触发
2.openEuler-20.03-LTS-SP4(4.19.90):正常修复
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.openEuler-24.03-LTS-Next(6.6.0):不受影响-漏洞代码不能被攻击者触发
7.openEuler-24.03-LTS-SP1(6.6.0):正常修复
8.openEuler-24.03-LTS-SP2(6.6.0):不修复-超出修复范围
9.openEuler-24.03-LTS-SP3(6.6.0):不受影响-漏洞代码不能被攻击者触发
10.openEuler-24.03-LTS-SP4(6.6.0):不受影响-漏洞代码不能被攻击者触发

likedislike
AAtomGit-Bot
2025年1月13日 创建了内核缺陷
openeuler-ci-bot
openeuler-ci-bot成员
2025年1月13日 评论:

Hi guo-mengqi, 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.

likedislike
openeuler-ci-botopeneuler-ci-bot成员
2025年1月13日 添加了   sig/Kernel 标签
openeuler-ci-botopeneuler-ci-bot成员
2025年1月13日 将负责人设置为sanglipeng
openeuler-ci-botopeneuler-ci-bot成员
2025年1月13日 修改了描述
此处折叠了73条消息 查看更多
openeuler-ci-bot
openeuler-ci-bot成员
1 天前 评论:

经过cve-manager解析,部分分支PR未合入,如红色字体所示:

原因说明:
1.master:不受影响-漏洞代码不能被攻击者触发
2.openEuler-20.03-LTS-SP4:正常修复
3.openEuler-22.03-LTS-SP3:不修复-超出修复范围
4.openEuler-22.03-LTS-SP4:正常修复
5.openEuler-24.03-LTS:不修复-超出修复范围
6.openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发
7.openEuler-24.03-LTS-SP1:正常修复(PR未合入)
8.openEuler-24.03-LTS-SP2:不修复-超出修复范围
9.openEuler-24.03-LTS-SP3:不受影响-漏洞代码不能被攻击者触发
10.openEuler-24.03-LTS-SP4:不受影响-漏洞代码不能被攻击者触发

likedislike
openeuler-ci-botopeneuler-ci-bot成员
23 小时前 issue优先级由 次要 改变为 次要
openeuler-ci-bot
openeuler-ci-bot成员
23 小时前 评论:

source: @hulk-ci-bot

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

quota: flush quota_release_work upon quota writeback

One of the paths quota writeback is called from is:

freeze_super()
sync_filesystem()
ext4_sync_fs()
dquot_writeback_dquots()

Since we currently don't always flush the quota_release_work queue in
this path, we can end up with the following race:

  1. dquot are added to releasing_dquots list during regular operations.
  2. FS Freeze starts, however, this does not flush the quota_release_work queue.
  3. Freeze completes.
  4. Kernel eventually tries to flush the workqueue while FS is frozen which
    hits a WARN_ON since transaction gets started during frozen state:

ext4_journal_check_start+0x28/0x110 [ext4] (unreliable)
__ext4_journal_start_sb+0x64/0x1c0 [ext4]
ext4_release_dquot+0x90/0x1d0 [ext4]
quota_release_workfn+0x43c/0x4d0

Which is the following line:

WARN_ON(sb->s_writers.frozen == SB_FREEZE_COMPLETE);

Which ultimately results in generic/390 failing due to dmesg
noise. This was detected on powerpc machine 15 cores.

To avoid this, make sure to flush the workqueue during
dquot_writeback_dquots() so we dont have any pending workitems after
freeze.

openEuler评分:
5.5
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

受影响版本排查(受影响/不受影响):
1.master:不受影响
2.openEuler-20.03-LTS-SP4:受影响
3.openEuler-22.03-LTS-SP3:受影响
4.openEuler-22.03-LTS-SP4:受影响
5.openEuler-24.03-LTS:受影响
6.openEuler-24.03-LTS-Next:不受影响
7.openEuler-24.03-LTS-SP1:受影响
8.openEuler-24.03-LTS-SP2:受影响
9.openEuler-24.03-LTS-SP3:不受影响
10.openEuler-24.03-LTS-SP4:不受影响

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

原因说明:
1.master:不受影响-漏洞代码不能被攻击者触发
2.openEuler-20.03-LTS-SP4:正常修复
3.openEuler-22.03-LTS-SP3:不修复-超出修复范围
4.openEuler-22.03-LTS-SP4:正常修复
5.openEuler-24.03-LTS:不修复-超出修复范围
6.openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发
7.openEuler-24.03-LTS-SP1:正常修复
8.openEuler-24.03-LTS-SP2:不修复-超出修复范围
9.openEuler-24.03-LTS-SP3:不受影响-漏洞代码不能被攻击者触发
10.openEuler-24.03-LTS-SP4:不受影响-漏洞代码不能被攻击者触发

likedislike
openeuler-ci-bot
openeuler-ci-bot成员
23 小时前 评论:

@robinorg 经过 cve-manager 解析, 已分析的内容如下表所示:

状态 分析项目 内容
已分析 1.影响性分析说明 In the Linux kernel, the following vulnerability has been resolved:quota: flush quota_release_work upon quota writebackOne of the paths quota writeback is called from is:freeze_super() sync_filesystem() ext4_sync_fs() dquot_writeback_dquots()Since we currently don't always flush the quota_release_work queue inthis path, we can end up with the following race: 1. dquot are added to releasing_dquots list during regular operations. 2. FS Freeze starts, however, this does not flush the quota_release_work queue. 3. Freeze completes. 4. Kernel eventually tries to flush the workqueue while FS is frozen which hits a WARN_ON since transaction gets started during frozen state: ext4_journal_check_start+0x28/0x110 [ext4] (unreliable) __ext4_journal_start_sb+0x64/0x1c0 [ext4] ext4_release_dquot+0x90/0x1d0 [ext4] quota_release_workfn+0x43c/0x4d0Which is the following line: WARN_ON(sb->s_writers.frozen == SB_FREEZE_COMPLETE);Which ultimately results in generic/390 failing due to dmesgnoise. This was detected on powerpc machine 15 cores.To avoid this, make sure to flush the workqueue duringdquot_writeback_dquots() so we dont have any pending workitems afterfreeze.
已分析 2.openEulerScore 5.5
已分析 3.openEulerVector AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
已分析 4.受影响版本排查 master:不受影响,openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP3:受影响,openEuler-22.03-LTS-SP4:受影响,openEuler-24.03-LTS:受影响,openEuler-24.03-LTS-Next:不受影响,openEuler-24.03-LTS-SP1:受影响,openEuler-24.03-LTS-SP2:受影响,openEuler-24.03-LTS-SP3:不受影响,openEuler-24.03-LTS-SP4:不受影响
已分析 5.是否涉及abi变化 master:否,openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS-SP3:否,openEuler-22.03-LTS-SP4:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否,openEuler-24.03-LTS-SP1:否,openEuler-24.03-LTS-SP2:否,openEuler-24.03-LTS-SP3:否,openEuler-24.03-LTS-SP4:否
已分析 6.原因说明 master:不受影响-漏洞代码不能被攻击者触发,openEuler-20.03-LTS-SP4:正常修复,openEuler-22.03-LTS-SP3:不修复-超出修复范围,openEuler-22.03-LTS-SP4:正常修复,openEuler-24.03-LTS:不修复-超出修复范围,openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发,openEuler-24.03-LTS-SP1:正常修复,openEuler-24.03-LTS-SP2:不修复-超出修复范围,openEuler-24.03-LTS-SP3:不受影响-漏洞代码不能被攻击者触发,openEuler-24.03-LTS-SP4:不受影响-漏洞代码不能被攻击者触发

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

likedislike
openeuler-ci-bot
openeuler-ci-bot成员
23 小时前 评论:

经过cve-manager解析,部分分支PR未合入,如红色字体所示:

原因说明:
1.master:不受影响-漏洞代码不能被攻击者触发
2.openEuler-20.03-LTS-SP4:正常修复
3.openEuler-22.03-LTS-SP3:不修复-超出修复范围
4.openEuler-22.03-LTS-SP4:正常修复
5.openEuler-24.03-LTS:不修复-超出修复范围
6.openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发
7.openEuler-24.03-LTS-SP1:正常修复(PR未合入)
8.openEuler-24.03-LTS-SP2:不修复-超出修复范围
9.openEuler-24.03-LTS-SP3:不受影响-漏洞代码不能被攻击者触发
10.openEuler-24.03-LTS-SP4:不受影响-漏洞代码不能被攻击者触发

likedislike