Here's my understanding so far: In the upstream Linux kernel there were two fixes posted months from each other, one for direct io [0] and the other one for ex

Here's my understanding so far: In the upstream Linux kernel there were two fixes posted months from each other, one for direct io [0] and the other one for ext4 [1]. The ext4 one was marked for backport to stable (CC: stable@vger.kernel.org), the other was not. The problem is that these commits depend on each other for things to work properly. If you have both, you're fine. If you have only the backported one, you have a problem. Which versions are affected? We know for sure that 6.1.64 is affected, 6.1.55 is not (because it doesn't have the commit). As of right now, 6.1.64 is still marked as "stable" in Debian [2] but if you actually try to install it from the official mirrors (deb.debian.org), you will get error 403. The fix is included in version 6.1.66 which will soon be available. The issue seems to be only highlighted in the context of Debian but it is not specific to it. The issue is/was in the official upstream release. [0] https://github.com/torvalds/linux/commit/936e114a245b6e38e0dbf706a67e7611fc993da1 https://github.com/torvalds/linux/commit/936e114a245b6e38e0d... [1] https://github.com/torvalds/linux/commit/91562895f8030cb9a0470b1db49de79346a69f91 https://github.com/torvalds/linux/commit/91562895f8030cb9a04... [2] https://packages.debian.org/source/stable/linux https://packages.debian.org/source/stable/linux