Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CVE-2026-43065— ext4: always drain queued discard work in ext4_mb_release()

EPSS 0.02% · P7
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2026-43065

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
ext4: always drain queued discard work in ext4_mb_release()
Source: NVD (National Vulnerability Database)
Vulnerability Description
In 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/20260319094545.19291-1-qiang.zhang@linux.dev/ [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.
Source: NVD (National Vulnerability Database)
CVSS Information
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Type
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞,该漏洞源于ext4文件系统在重新挂载为nodiscard后未排空待处理的丢弃工作。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

VendorProductAffected VersionsCPESubscribe
LinuxLinux 55cdd0af2bc5ffc92a2deb745627755aecd5db33 ~ e96c2354b170aaa53300c8e8fd59e41b133160f7 -
LinuxLinux 5.15 -

II. Public POCs for CVE-2026-43065

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-43065

登录查看更多情报信息。

Same Patch Batch · Linux · 2026-05-05 · 15 CVEs total

CVE-2026-430679.8 CRITICALext4: handle wraparound when searching for blocks for indirect mapped blocks
CVE-2026-430719.1 CRITICALdcache: Limit the minimal number of bucket to two
CVE-2026-430707.8 HIGHbpf: Reset register ID for BPF_END value tracking
CVE-2026-430637.8 HIGHxfs: don't irele after failing to iget in xfs_attri_recover_work
CVE-2026-430607.8 HIGHnetfilter: nft_ct: drop pending enqueued packets on removal
CVE-2026-430627.1 HIGHBluetooth: L2CAP: Fix type confusion in l2cap_ecred_reconf_rsp()
CVE-2026-43073x86-64: rename misleadingly named '__copy_user_nocache()' function
CVE-2026-43072drm/vc4: platform_get_irq_byname() returns an int
CVE-2026-43069Bluetooth: hci_ll: Fix firmware leak on error path
CVE-2026-43068ext4: avoid allocate block from corrupted group in ext4_mb_find_by_goal()
CVE-2026-43066ext4: fix iloc.bh leak in ext4_fc_replay_inode() error paths
CVE-2026-43064dmaengine: idxd: Fix not releasing workqueue on .release()
CVE-2026-43061serial: 8250: Fix TX deadlock when using DMA
CVE-2026-43059Bluetooth: MGMT: Fix list corruption and UAF in command complete handlers

IV. Related Vulnerabilities

V. Comments for CVE-2026-43065

No comments yet


Leave a comment