CVE-2026-43065

/// Technical 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/[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), sin

/// Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

/// References