CVE-2026-45985: Linux kernel · ext4: don't set EXT4_GET_BLOCKS_CONVERT when splitting before submitting I/O
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in feaf2a80e78f89ee8a3464126077ba8683b62791 : patch Linux kernel soon.
Data as of 30 Oct 2026, 12:49 UTC
Rated High by Threat Radar's AI analysis · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- Patch
- Available – fixed in feaf2a80e78f89ee8a3464126077ba8683b62791, 37555690f39f78ef69af347d9aff897e07445949, 2698731d25823267c29190cb578da9296a0c0d7b +5
Exploitation evidence
Disclosed: evidence found.
CVE published 27 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix has been implemented in the Linux kernel to address this issue by not passing the EXT4_GET_BLOCKS_CONVERT flag when splitting unwritten extents before submitting I/O and by zeroing out the entire extent range for consistency. Users should update to a Linux kernel version that includes the fix identified by the listed commit hashes to mitigate this vulnerability.
Description
A vulnerability in the Linux kernel ext4 filesystem code could cause stale data exposure due to improper handling of extent splitting during direct I/O and writeback operations. The flaw occurs when the EXT4_GET_BLOCKS_CONVERT flag is incorrectly set during extent splitting, leading to inconsistent extent status and potential exposure of stale data if a write operation fails. This issue has been fixed by changing the handling of the flag and ensuring zeroing of the entire extent range before I/O submission.
References
- git.kernel.org/stable/c/77e407967cd872cd75d7e4a691908e49c8e6b4d4 (opens in a new tab)
- git.kernel.org/stable/c/37555690f39f78ef69af347d9aff897e07445949 (opens in a new tab)
- git.kernel.org/stable/c/6d8fa684b42724d74a77f980f5ee47cfd1ec7e74 (opens in a new tab)
- git.kernel.org/stable/c/67cdb7bd7442bd3cdc6d6088bbb2df9be2fe936c (opens in a new tab)
- git.kernel.org/stable/c/2920ec61c98b9476781359f05b94da84e80f54d4 (opens in a new tab)
- git.kernel.org/stable/c/2698731d25823267c29190cb578da9296a0c0d7b (opens in a new tab)
- git.kernel.org/stable/c/716e7439a5a9b18c3ff882c2f8c834b9ced1aaec (opens in a new tab)
- git.kernel.org/stable/c/feaf2a80e78f89ee8a3464126077ba8683b62791 (opens in a new tab)