CVE-2024-56780

quota: flush quota_release_work upon quota writeback

MEDIUM
5.5
CVSS Score
Published: January 8, 2025 at 05:49 PM UTC
Updated: October 15, 2026 at 02:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.19.295 ≤ v < 4.205.10.195 ≤ v < 5.10.2315.15.132 ≤ v < 5.15.1745.4.257 ≤ v < 5.4.2876.1.53 ≤ v < 6.1.1206.4.16 ≤ v < 6.56.5.3 ≤ v < 6.6.646.7 ≤ v < 6.12.43027e200dd58d5b437f16634dbbd355b29ffe0a631bed65eecbc5ce57592cfe31947eaa64e3d678e4.19.2955.10.1955.15.1325.4.2576.1.536.136.13 rc16.4.166.5.386d89987f0998c98f57d641e308b40452a99404589602de9a2d7080b7a4029d5c1bf8f78d295ff5f903fc5d8cb48b0d2de7095ef40e39fd32bb27bd0d40c192e119892799dd4ddf94f5cea6fa93775efdabc8b20756601b9e1cc85a81d47d3f98ed4d13af3e9a2bbdeb8987508dd6bb2b701dea911d4daec
Vendor states this is fixed in 3e6ff207cd5bd924ad94cd1a7c633bcdac0ba1cb (fixed)
Vendor states this is fixed in 6f3821acd7c3143145999248087de5fb4b48cf26 (fixed)
Vendor states this is fixed in 8ea87e34792258825d290f4dc5216276e91cb224 (fixed)
Vendor states this is fixed in a5abba5e0e586e258ded3e798fe5f69c66fec198 (fixed)
Vendor states this is fixed in ab6cfcf8ed2c7496f55d020b65b1d8cd55d9a2cb (fixed)
Vendor states this is fixed in ac6f420291b3fee1113f21d612fa88b628afab5b (fixed)
Vendor states this is fixed in bcacb52a985f1b6d280f698a470b873dfe52728a (fixed)
Affected range stops below 4.20, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.10.231 (unaffected)
Vendor states this is fixed in 5.15.174 (unaffected)
Vendor states this is fixed in 5.4.287 (unaffected)
Vendor states this is fixed in 6.1.120 (unaffected)
Vendor states this is fixed in 6.12.4 (unaffected)
Vendor states this is fixed in 6.13 (unaffected)
Affected range stops below 6.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.6 (unaffected)
Vendor states this is fixed in 6.6.64 (unaffected)

References (11)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/3e6ff207cd5bd924ad94cd1a7c633bcdac0ba1cb
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/6f3821acd7c3143145999248087de5fb4b48cf26
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/8ea87e34792258825d290f4dc5216276e91cb224
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/a5abba5e0e586e258ded3e798fe5f69c66fec198
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/ab6cfcf8ed2c7496f55d020b65b1d8cd55d9a2cb
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/ac6f420291b3fee1113f21d612fa88b628afab5b
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/bcacb52a985f1b6d280f698a470b873dfe52728a
Source: af854a3a-2127-422b-91ae-364da2661108
https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.5MEDIUMCISA-ADP
Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card