CVE-2026-43065 (GCVE-0-2026-43065)
Vulnerability from cvelistv5 – Published: 2026-05-05 15:23 – Updated: 2026-05-05 15:23
VLAI?
Title
ext4: always drain queued discard work in ext4_mb_release()
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.
Severity ?
No CVSS data available.
Assigner
References
Impacted products
| Vendor | Product | Version | |||||||
|---|---|---|---|---|---|---|---|---|---|
| Linux | Linux |
Affected:
55cdd0af2bc5ffc92a2deb745627755aecd5db33 , < e96c2354b170aaa53300c8e8fd59e41b133160f7
(git)
Affected: 55cdd0af2bc5ffc92a2deb745627755aecd5db33 , < c360e9d0def4f4ae03254a67c683103908555b75 (git) Affected: 55cdd0af2bc5ffc92a2deb745627755aecd5db33 , < 1c82f863f090ab899085bdfade073313384b514b (git) Affected: 55cdd0af2bc5ffc92a2deb745627755aecd5db33 , < 9b4d9dda6a71ad3425c8109d27c4c6bfb9da97b8 (git) Affected: 55cdd0af2bc5ffc92a2deb745627755aecd5db33 , < 812b6a7cd3e7f3a3e8a24db85bc6313c26cb1098 (git) Affected: 55cdd0af2bc5ffc92a2deb745627755aecd5db33 , < b4737e26d4688b8aea88ad6ea4dbfeb6e78b0327 (git) Affected: 55cdd0af2bc5ffc92a2deb745627755aecd5db33 , < 9ee29d20aab228adfb02ca93f87fb53c56c2f3af (git) |
|||||||
|
|||||||||
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"fs/ext4/mballoc.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "e96c2354b170aaa53300c8e8fd59e41b133160f7",
"status": "affected",
"version": "55cdd0af2bc5ffc92a2deb745627755aecd5db33",
"versionType": "git"
},
{
"lessThan": "c360e9d0def4f4ae03254a67c683103908555b75",
"status": "affected",
"version": "55cdd0af2bc5ffc92a2deb745627755aecd5db33",
"versionType": "git"
},
{
"lessThan": "1c82f863f090ab899085bdfade073313384b514b",
"status": "affected",
"version": "55cdd0af2bc5ffc92a2deb745627755aecd5db33",
"versionType": "git"
},
{
"lessThan": "9b4d9dda6a71ad3425c8109d27c4c6bfb9da97b8",
"status": "affected",
"version": "55cdd0af2bc5ffc92a2deb745627755aecd5db33",
"versionType": "git"
},
{
"lessThan": "812b6a7cd3e7f3a3e8a24db85bc6313c26cb1098",
"status": "affected",
"version": "55cdd0af2bc5ffc92a2deb745627755aecd5db33",
"versionType": "git"
},
{
"lessThan": "b4737e26d4688b8aea88ad6ea4dbfeb6e78b0327",
"status": "affected",
"version": "55cdd0af2bc5ffc92a2deb745627755aecd5db33",
"versionType": "git"
},
{
"lessThan": "9ee29d20aab228adfb02ca93f87fb53c56c2f3af",
"status": "affected",
"version": "55cdd0af2bc5ffc92a2deb745627755aecd5db33",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"fs/ext4/mballoc.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "5.15"
},
{
"lessThan": "5.15",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.15.*",
"status": "unaffected",
"version": "5.15.203",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.1.*",
"status": "unaffected",
"version": "6.1.168",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.131",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.80",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.21",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.19.*",
"status": "unaffected",
"version": "6.19.11",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.0",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "5.15.203",
"versionStartIncluding": "5.15",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.1.168",
"versionStartIncluding": "5.15",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.6.131",
"versionStartIncluding": "5.15",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.12.80",
"versionStartIncluding": "5.15",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.21",
"versionStartIncluding": "5.15",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.19.11",
"versionStartIncluding": "5.15",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.0",
"versionStartIncluding": "5.15",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\next4: always drain queued discard work in ext4_mb_release()\n\nWhile reviewing recent ext4 patch[1], Sashiko raised the following\nconcern[2]:\n\n\u003e If the filesystem is initially mounted with the discard option,\n\u003e deleting files will populate sbi-\u003es_discard_list and queue\n\u003e s_discard_work. If it is then remounted with nodiscard, the\n\u003e EXT4_MOUNT_DISCARD flag is cleared, but the pending s_discard_work is\n\u003e neither cancelled nor flushed.\n\n[1] https://lore.kernel.org/r/20260319094545.19291-1-qiang.zhang@linux.dev/\n[2] https://sashiko.dev/#/patchset/20260319094545.19291-1-qiang.zhang%40linux.dev\n\nThe concern was valid, but it had nothing to do with the patch[1].\nOne of the problems with Sashiko in its current (early) form is that\nit will detect pre-existing issues and report it as a problem with the\npatch that it is reviewing.\n\nIn practice, it would be hard to hit deliberately (unless you are a\nmalicious syzkaller fuzzer), since it would involve mounting the file\nsystem with -o discard, and then deleting a large number of files,\nremounting the file system with -o nodiscard, and then immediately\nunmounting the file system before the queued discard work has a change\nto drain on its own.\n\nFix it because it\u0027s a real bug, and to avoid Sashiko from raising this\nconcern when analyzing future patches to mballoc.c."
}
],
"providerMetadata": {
"dateUpdated": "2026-05-05T15:23:25.326Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/e96c2354b170aaa53300c8e8fd59e41b133160f7"
},
{
"url": "https://git.kernel.org/stable/c/c360e9d0def4f4ae03254a67c683103908555b75"
},
{
"url": "https://git.kernel.org/stable/c/1c82f863f090ab899085bdfade073313384b514b"
},
{
"url": "https://git.kernel.org/stable/c/9b4d9dda6a71ad3425c8109d27c4c6bfb9da97b8"
},
{
"url": "https://git.kernel.org/stable/c/812b6a7cd3e7f3a3e8a24db85bc6313c26cb1098"
},
{
"url": "https://git.kernel.org/stable/c/b4737e26d4688b8aea88ad6ea4dbfeb6e78b0327"
},
{
"url": "https://git.kernel.org/stable/c/9ee29d20aab228adfb02ca93f87fb53c56c2f3af"
}
],
"title": "ext4: always drain queued discard work in ext4_mb_release()",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-43065",
"datePublished": "2026-05-05T15:23:25.326Z",
"dateReserved": "2026-05-01T14:12:55.981Z",
"dateUpdated": "2026-05-05T15:23:25.326Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"nvd": "{\"cve\":{\"id\":\"CVE-2026-43065\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2026-05-05T16:16:15.683\",\"lastModified\":\"2026-05-05T16:16:15.683\",\"vulnStatus\":\"Received\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\next4: always drain queued discard work in ext4_mb_release()\\n\\nWhile reviewing recent ext4 patch[1], Sashiko raised the following\\nconcern[2]:\\n\\n\u003e If the filesystem is initially mounted with the discard option,\\n\u003e deleting files will populate sbi-\u003es_discard_list and queue\\n\u003e s_discard_work. If it is then remounted with nodiscard, the\\n\u003e EXT4_MOUNT_DISCARD flag is cleared, but the pending s_discard_work is\\n\u003e neither cancelled nor flushed.\\n\\n[1] https://lore.kernel.org/r/20260319094545.19291-1-qiang.zhang@linux.dev/\\n[2] https://sashiko.dev/#/patchset/20260319094545.19291-1-qiang.zhang%40linux.dev\\n\\nThe concern was valid, but it had nothing to do with the patch[1].\\nOne of the problems with Sashiko in its current (early) form is that\\nit will detect pre-existing issues and report it as a problem with the\\npatch that it is reviewing.\\n\\nIn practice, it would be hard to hit deliberately (unless you are a\\nmalicious syzkaller fuzzer), since it would involve mounting the file\\nsystem with -o discard, and then deleting a large number of files,\\nremounting the file system with -o nodiscard, and then immediately\\nunmounting the file system before the queued discard work has a change\\nto drain on its own.\\n\\nFix it because it\u0027s a real bug, and to avoid Sashiko from raising this\\nconcern when analyzing future patches to mballoc.c.\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/1c82f863f090ab899085bdfade073313384b514b\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/812b6a7cd3e7f3a3e8a24db85bc6313c26cb1098\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/9b4d9dda6a71ad3425c8109d27c4c6bfb9da97b8\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/9ee29d20aab228adfb02ca93f87fb53c56c2f3af\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/b4737e26d4688b8aea88ad6ea4dbfeb6e78b0327\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/c360e9d0def4f4ae03254a67c683103908555b75\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/e96c2354b170aaa53300c8e8fd59e41b133160f7\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
}
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…