linux-ext4 - Please apply "ext4: don't allow journal inode to have encrypt flag" to 5.15 and earlier

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <Y7nWexWBpMWKwdeB@sol.localdomain>
Date:   Sat, 7 Jan 2023 12:30:51 -0800
From:   Eric Biggers <ebiggers@...nel.org>
To:     stable@...r.kernel.org
Cc:     linux-ext4@...r.kernel.org
Subject: Please apply "ext4: don't allow journal inode to have encrypt flag"
 to 5.15 and earlier

Please apply commit 105c78e12468 ("ext4: don't allow journal inode to have
encrypt flag") to the 5.15, 5.10, 5.4, and 4.19 LTS kernels, where it applies
cleanly.

It didn't get applied automatically because for the Fixes tag, I used a commit
in 5.18.  However, that was the commit that exposed the problem, not the root
cause.  IMO it makes sense to apply this to earlier kernels too, especially
because some people have backported the 5.18 commit.

- Eric