ext4: always drain queued discard work in ext4_mb_release()

MITRE NVD CVE.ORG JSON API Print: PDF PDF

Summary

CVECVE-2026-43065
StatePUBLISHED
AssignerLinux
Source PriorityCVE Program / NVD first with legacy fallback
Published2026-05-05 16:16:15 UTC
Updated2026-05-06 13:08:07 UTC
DescriptionIn the Linux kernel, the following vulnerability has been resolved: ext4: always drain queued discard work in ext4_mb_release() While reviewing recent ext4 patch[1], Sashiko raised the following concern[2]: > If the filesystem is initially mounted with the discard option, > deleting files will populate sbi->s_discard_list and queue > s_discard_work. If it is then remounted with nodiscard, the > EXT4_MOUNT_DISCARD flag is cleared, but the pending s_discard_work is > neither cancelled nor flushed. [1] https://lore.kernel.org/r/[email protected]/ [2] https://sashiko.dev/#/patchset/20260319094545.19291-1-qiang.zhang%40linux.dev The concern was valid, but it had nothing to do with the patch[1]. One of the problems with Sashiko in its current (early) form is that it will detect pre-existing issues and report it as a problem with the patch that it is reviewing. In practice, it would be hard to hit deliberately (unless you are a malicious syzkaller fuzzer), since it would involve mounting the file system with -o discard, and then deleting a large number of files, remounting the file system with -o nodiscard, and then immediately unmounting the file system before the queued discard work has a change to drain on its own. Fix it because it's a real bug, and to avoid Sashiko from raising this concern when analyzing future patches to mballoc.c.

Vendor Declared Affected Products

SourceVendorProductVersionPlatforms
CNA Linux Linux affected 55cdd0af2bc5ffc92a2deb745627755aecd5db33 e96c2354b170aaa53300c8e8fd59e41b133160f7 git Not specified
CNA Linux Linux affected 55cdd0af2bc5ffc92a2deb745627755aecd5db33 c360e9d0def4f4ae03254a67c683103908555b75 git Not specified
CNA Linux Linux affected 55cdd0af2bc5ffc92a2deb745627755aecd5db33 1c82f863f090ab899085bdfade073313384b514b git Not specified
CNA Linux Linux affected 55cdd0af2bc5ffc92a2deb745627755aecd5db33 9b4d9dda6a71ad3425c8109d27c4c6bfb9da97b8 git Not specified
CNA Linux Linux affected 55cdd0af2bc5ffc92a2deb745627755aecd5db33 812b6a7cd3e7f3a3e8a24db85bc6313c26cb1098 git Not specified
CNA Linux Linux affected 55cdd0af2bc5ffc92a2deb745627755aecd5db33 b4737e26d4688b8aea88ad6ea4dbfeb6e78b0327 git Not specified
CNA Linux Linux affected 55cdd0af2bc5ffc92a2deb745627755aecd5db33 9ee29d20aab228adfb02ca93f87fb53c56c2f3af git Not specified
CNA Linux Linux affected 5.15 Not specified
CNA Linux Linux unaffected 5.15 semver Not specified
CNA Linux Linux unaffected 5.15.203 5.15.* semver Not specified
CNA Linux Linux unaffected 6.1.168 6.1.* semver Not specified
CNA Linux Linux unaffected 6.6.131 6.6.* semver Not specified
CNA Linux Linux unaffected 6.12.80 6.12.* semver Not specified
CNA Linux Linux unaffected 6.18.21 6.18.* semver Not specified
CNA Linux Linux unaffected 6.19.11 6.19.* semver Not specified
CNA Linux Linux unaffected 7.0 * original_commit_for_fix Not specified

References

ReferenceSourceLinkTags
git.kernel.org/stable/c/e96c2354b170aaa53300c8e8fd59e41b133160f7 416baaa9-dc9f-4396-8d5f-8c081fb06d67 git.kernel.org
git.kernel.org/stable/c/c360e9d0def4f4ae03254a67c683103908555b75 416baaa9-dc9f-4396-8d5f-8c081fb06d67 git.kernel.org
git.kernel.org/stable/c/9b4d9dda6a71ad3425c8109d27c4c6bfb9da97b8 416baaa9-dc9f-4396-8d5f-8c081fb06d67 git.kernel.org
git.kernel.org/stable/c/b4737e26d4688b8aea88ad6ea4dbfeb6e78b0327 416baaa9-dc9f-4396-8d5f-8c081fb06d67 git.kernel.org
git.kernel.org/stable/c/1c82f863f090ab899085bdfade073313384b514b 416baaa9-dc9f-4396-8d5f-8c081fb06d67 git.kernel.org
git.kernel.org/stable/c/812b6a7cd3e7f3a3e8a24db85bc6313c26cb1098 416baaa9-dc9f-4396-8d5f-8c081fb06d67 git.kernel.org
git.kernel.org/stable/c/9ee29d20aab228adfb02ca93f87fb53c56c2f3af 416baaa9-dc9f-4396-8d5f-8c081fb06d67 git.kernel.org
CVE Program record CVE.ORG www.cve.org canonical
NVD vulnerability detail NVD nvd.nist.gov canonical, analysis
© CVE.report 2026 |

Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. It is the responsibility of user to evaluate the accuracy, completeness or usefulness of any information, opinion, advice or other content. EACH USER WILL BE SOLELY RESPONSIBLE FOR ANY consequences of his or her direct or indirect use of this web site. ALL WARRANTIES OF ANY KIND ARE EXPRESSLY DISCLAIMED. This site will NOT BE LIABLE FOR ANY DIRECT, INDIRECT or any other kind of loss.

CVE, CWE, and OVAL are registred trademarks of The MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. This site includes MITRE data granted under the following license.

Free CVE JSON API cve.report/api

CVE.report and Source URL Uptime Status status.cve.report