Skip to main content
cve.nowby Sazabi
← All vulnerabilities
CVE-2026-80806

ext4: don't enable DAX on new encrypted files

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 5.10.269, 5.15.220, 6.1.187, 6.6.156, 6.12.108, and 3 more
None on Exploit-DB, Metasploit or GitHub

Summary

In the Linux kernel, the following vulnerability has been resolved: ext4: don't enable DAX on new encrypted files Currently, when a new encrypted regular file is created, the call to ext4_set_inode_flags(inode, init=true) in __ext4_new_inode() is made before EXT4_INODE_ENCRYPT is set. As a result, it can set S_DAX if the filesystem is mounted with "-o dax=always". EXT4_INODE_ENCRYPT then actually gets set a bit later in __ext4_new_inode(), when it calls fscrypt_set_context() which calls ext4_set_context(). ext4_set_context() sets EXT4_INODE_ENCRYPT and calls ext4_set_inode_flags(inode, init=false) to set S_ENCRYPTED too. This was intended to clear S_DAX as well. However, this was broken by commit 043546e46dc7 ("fs/ext4: Only change S_DAX on inode load"). This causes data written to the file to bypass encryption, also causing xfstests failures such as generic/548 (when "-o dax=always" is used). Fix this by simplifying the flow by making __ext4_new_inode() set EXT4_INODE_ENCRYPT earlier. This makes it take effect in ext4_set_inode_flags(inode, init=true), making S_DAX never be set. Similarly, make EXT4_STATE_MAY_INLINE_DATA never be set in the first place on new encrypted inodes. Then it doesn't need to be cleared. As a result of these simplifications, ext4_set_context() no longer needs to change inode flags or state when 'handle != NULL'. Remove that too.

Timeline

  1. CVE published
  2. Record last updated

Affected versions

  • Linux Linux

    From 043546e46dc70c25ff7e2cf6d09cbb0424fc9978 · fixed in add98959b220935b243170214c787bc03044a44d; From 043546e46dc70c25ff7e2cf6d09cbb0424fc9978 · fixed in f53b325068bca0b238c3e0d2eb7de9b1f2268cab; From 043546e46dc70c25ff7e2cf6d09cbb0424fc9978 · fixed in 5959cad3cfa852ec07bbdaf9c17f4838a94a8e6c; From 043546e46dc70c25ff7e2cf6d09cbb0424fc9978 · fixed in a13f61ba9b2a7a4ff1f140949ccfad23c5313757; From 043546e46dc70c25ff7e2cf6d09cbb0424fc9978 · fixed in ed1cd834da65db127f1c30ff67e78f14825a06c1; From 043546e46dc70c25ff7e2cf6d09cbb0424fc9978 · fixed in 458776af0061afec1014cb3cd0061e282e482e83; From 043546e46dc70c25ff7e2cf6d09cbb0424fc9978 · fixed in 3392391b363a63ebb531d45318a729b1c998565b; From 043546e46dc70c25ff7e2cf6d09cbb0424fc9978 · fixed in e27bae352158c007143d5bb50f3af33a177c0a37; From 043546e46dc70c25ff7e2cf6d09cbb0424fc9978 · fixed in da32af420d6d466e247c43ac0b829edeac7ae0ad

  • Linux Linux

    5.8

  • KernelLinux

    From 5.8.0 · fixed in 5.10.269; From 5.11.0 · fixed in 5.15.220; From 5.16.0 · fixed in 6.1.187; From 6.2.0 · fixed in 6.6.156; From 6.7.0 · fixed in 6.12.108; From 6.13.0 · fixed in 6.18.47; From 6.19.0 · fixed in 7.1.11; From 7.2.0 · fixed in 7.2.1

References 9

git.kernel.org