ext4: don't enable DAX on new encrypted files
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.
CVE-2026-80806
Primary source · Revision 1
Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.
Security context
Source reference: cve:CVE-2026-80806
Linux
Source reference: /containers/cna/affected/0/product
- Affected versions
- Not stated in this record
- Fixed versions
- Not stated in this record
- Prerequisites
- Not stated in this record
Linux
Source reference: /containers/cna/affected/1/product
- Affected versions
- Not stated in this record
- Fixed versions
- Not stated in this record
- Prerequisites
- Not stated in this record
Structured affected-version data
Original package identities and version rules from this source.
[
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "043546e46dc70c25ff7e2cf6d09cbb0424fc9978",
"lessThan": "add98959b220935b243170214c787bc03044a44d",
"versionType": "git"
},
{
"status": "affected",
"version": "043546e46dc70c25ff7e2cf6d09cbb0424fc9978",
"lessThan": "f53b325068bca0b238c3e0d2eb7de9b1f2268cab",
"versionType": "git"
},
{
"status": "affected",
"version": "043546e46dc70c25ff7e2cf6d09cbb0424fc9978",
"lessThan": "5959cad3cfa852ec07bbdaf9c17f4838a94a8e6c",
"versionType": "git"
},
{
"status": "affected",
"version": "043546e46dc70c25ff7e2cf6d09cbb0424fc9978",
"lessThan": "a13f61ba9b2a7a4ff1f140949ccfad23c5313757",
"versionType": "git"
},
{
"status": "affected",
"version": "043546e46dc70c25ff7e2cf6d09cbb0424fc9978",
"lessThan": "ed1cd834da65db127f1c30ff67e78f14825a06c1",
"versionType": "git"
},
{
"status": "affected",
"version": "043546e46dc70c25ff7e2cf6d09cbb0424fc9978",
"lessThan": "458776af0061afec1014cb3cd0061e282e482e83",
"versionType": "git"
},
{
"status": "affected",
"version": "043546e46dc70c25ff7e2cf6d09cbb0424fc9978",
"lessThan": "3392391b363a63ebb531d45318a729b1c998565b",
"versionType": "git"
},
{
"status": "affected",
"version": "043546e46dc70c25ff7e2cf6d09cbb0424fc9978",
"lessThan": "e27bae352158c007143d5bb50f3af33a177c0a37",
"versionType": "git"
},
{
"status": "affected",
"version": "043546e46dc70c25ff7e2cf6d09cbb0424fc9978",
"lessThan": "da32af420d6d466e247c43ac0b829edeac7ae0ad",
"versionType": "git"
}
],
"programFiles": [
"fs/ext4/crypto.c",
"fs/ext4/ialloc.c"
],
"defaultStatus": "unaffected"
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "5.8"
},
{
"status": "unaffected",
"version": "0",
"lessThan": "5.8",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "5.10.269",
"versionType": "semver",
"lessThanOrEqual": "5.10.*"
},
{
"status": "unaffected",
"version": "5.15.220",
"versionType": "semver",
"lessThanOrEqual": "5.15.*"
},
{
"status": "unaffected",
"version": "6.1.187",
"versionType": "semver",
"lessThanOrEqual": "6.1.*"
},
{
"status": "unaffected",
"version": "6.6.156",
"versionType": "semver",
"lessThanOrEqual": "6.6.*"
},
{
"status": "unaffected",
"version": "6.12.108",
"versionType": "semver",
"lessThanOrEqual": "6.12.*"
},
{
"status": "unaffected",
"version": "6.18.47",
"versionType": "semver",
"lessThanOrEqual": "6.18.*"
},
{
"status": "unaffected",
"version": "7.1.11",
"versionType": "semver",
"lessThanOrEqual": "7.1.*"
},
{
"status": "unaffected",
"version": "7.2.1",
"versionType": "semver",
"lessThanOrEqual": "7.2.*"
},
{
"status": "unaffected",
"version": "7.3",
"versionType": "original_commit_for_fix",
"lessThanOrEqual": "*"
}
],
"programFiles": [
"fs/ext4/crypto.c",
"fs/ext4/ialloc.c"
],
"defaultStatus": "affected"
}
]- Related CVEs
- CVE-2026-80806
Source reference:
/cveMetadata/cveId
Publisher severity
No explicit severity was provided.
- Event
- #34823 · Revision 1
- Added to Heist Feed
- Publisher date