Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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), 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.

Timeline

  1. ID reserved

    By Linux

  2. · 4 days later

    Published

  3. · 6 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-43065, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.12% · top 98% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 55cdd0af2bc5ffc92a2deb745627755aecd5db33 – < e96c2354b170aaa53300c8e8fd59e41b133160f7
    • affected 55cdd0af2bc5ffc92a2deb745627755aecd5db33 – < c360e9d0def4f4ae03254a67c683103908555b75
    • affected 55cdd0af2bc5ffc92a2deb745627755aecd5db33 – < 1c82f863f090ab899085bdfade073313384b514b
    • affected 55cdd0af2bc5ffc92a2deb745627755aecd5db33 – < 9b4d9dda6a71ad3425c8109d27c4c6bfb9da97b8
    • affected 55cdd0af2bc5ffc92a2deb745627755aecd5db33 – < 812b6a7cd3e7f3a3e8a24db85bc6313c26cb1098
    • affected 55cdd0af2bc5ffc92a2deb745627755aecd5db33 – < b4737e26d4688b8aea88ad6ea4dbfeb6e78b0327
    • affected 55cdd0af2bc5ffc92a2deb745627755aecd5db33 – < 9ee29d20aab228adfb02ca93f87fb53c56c2f3af
  • Linux · Linux

    • affected 5.15
    • unaffected < 5.15
    • unaffected 5.15.203 – ≤ 5.15.*
    • unaffected 6.1.168 – ≤ 6.1.*
    • unaffected 6.6.131 – ≤ 6.6.*
    • unaffected 6.12.80 – ≤ 6.12.*
    • unaffected 6.18.21 – ≤ 6.18.*
    • unaffected 6.19.11 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-43065 badge
[![CVE-2026-43065](https://cveledger.app/badge/CVE-2026-43065.svg)](https://cveledger.app/cve/CVE-2026-43065)

Record last updated .