CVE-2026-43065 json
ext4: always drain queued discard work in ext4_mb_release()
published 2026-05-05 6 mo ago modified 2026-11-06 2 d ago also EUVD-2026-27363
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 1%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 5.15.203, 6.1.168, 6.6.131, 6.12.80, 6.18.21, 6.19.11, 7.0
- linux Debian 12 6.1.170-1
- linux Debian 13 6.12.85-1
- linux Debian 14 6.19.11-1
debian advisories DEBIAN-CVE-2026-43065
- linux Ubuntu 22.04 LTS 5.15.0-186.196
- linux Ubuntu 24.04 LTS 6.8.0-136.136
- linux-aws Ubuntu 22.04 LTS 5.15.0-1112.119
- linux-aws Ubuntu 24.04 LTS 6.8.0-1061.64
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1112.122
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1064.72
- linux-gke Ubuntu 22.04 LTS 5.15.0-1108.114
- linux-gke Ubuntu 24.04 LTS 6.8.0-1059.67
ubuntu advisories UBUNTU-CVE-2026-43065
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-rt Linux Micro 6.1, Linux Micro 6.0 6.4.0-48.1
- kernel-source-rt Linux Micro 6.1, Linux Micro 6.0 6.4.0-48.1
- kernel-rt Real Time Module 15 SP7 6.4.0-150700.7.59.2
- kernel-syms-rt Real Time Module 15 SP7 6.4.0-150700.7.59.1
- kernel-source-rt Real Time Module 15 SP7 6.4.0-150700.7.59.2
- kernel-64kb SLE Module for Basesystem 15 SP7 6.4.0-150700.53.60.1
- kernel-syms SLE Module for Development Tools 15 SP7 6.4.0-150700.53.60.1
- kernel-azure SLE Module for Public Cloud 15 SP7 6.4.0-150700.53.60.1
suse advisories SUSE-SU-2026:22433-1SUSE-SU-2026:22458-1SUSE-SU-2026:2591-1SUSE-SU-2026:2482-1SUSE-SU-2026:22108-1SUSE-SU-2026:22137-1
- kernel-rt openSUSE Leap 16.0 6.12.0-160000.35.1
- dtb-aarch64 openSUSE Leap 16.0 6.12.0-160000.35.1
- kernel-64kb openSUSE Leap 16.0 6.12.0-160000.35.1
- kernel-syms openSUSE Leap 16.0 6.12.0-160000.35.1
- kernel-azure openSUSE Leap 16.0 6.12.0-160000.35.1
- kernel-obs-qa openSUSE Leap 16.0 6.12.0-160000.35.1
- kernel-source openSUSE Leap 16.0 6.12.0-160000.35.1
- kernel-default openSUSE Leap 16.0 6.12.0-160000.35.1
opensuse advisories openSUSE-SU-2026:20965-1
- git.kernel.org/stable/c/e96c2354b170aaa53300c8e8fd59e41b133160f7 commit
- git.kernel.org/stable/c/c360e9d0def4f4ae03254a67c683103908555b75 commit
- git.kernel.org/stable/c/1c82f863f090ab899085bdfade073313384b514b commit
- git.kernel.org/stable/c/9b4d9dda6a71ad3425c8109d27c4c6bfb9da97b8 commit
- git.kernel.org/stable/c/812b6a7cd3e7f3a3e8a24db85bc6313c26cb1098 commit
- git.kernel.org/stable/c/b4737e26d4688b8aea88ad6ea4dbfeb6e78b0327 commit
- git.kernel.org/stable/c/9ee29d20aab228adfb02ca93f87fb53c56c2f3af commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-43065 updated cvss 5.5
kernel: ext4: always drain queued discard work in ext4_mb_release()
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelaffected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 d ago
Exploit prediction
0.12% chance of exploitation in the next 30 days, higher than 1% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
-
git.kernel.org
/stable/c/e96c2354b170aaa53300c8e8fd59e41b133160f7
patch
-
git.kernel.org
/stable/c/c360e9d0def4f4ae03254a67c683103908555b75
patch
-
git.kernel.org
/stable/c/1c82f863f090ab899085bdfade073313384b514b
patch
-
git.kernel.org
/stable/c/9b4d9dda6a71ad3425c8109d27c4c6bfb9da97b8
patch
-
git.kernel.org
/stable/c/812b6a7cd3e7f3a3e8a24db85bc6313c26cb1098
patch
-
git.kernel.org
/stable/c/b4737e26d4688b8aea88ad6ea4dbfeb6e78b0327
patch
-
git.kernel.org
/stable/c/9ee29d20aab228adfb02ca93f87fb53c56c2f3af
patch
Sources
- CVE List CVE-2026-43065
- NVD CVE-2026-43065
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.