CVE-2026-80806
ext4: don't enable DAX on new encrypted files
Reported by linux · Published September 4, 2026
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.
EPSS 0.17% · 6.8th percentile
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| kernel-livepatch-6.12.110-135.201 | Amazon Linux | 1:1.0-0.amzn2023 |
| kernel6.12 | Amazon Linux | 1:6.12.110-135.201.amzn2023 |
| python3-perf | Amazon Linux | 1:6.1.188-233.385.amzn2023 |
| kernel6.18-devel | Amazon Linux | 1:6.18.48-107.148.amzn2023 |
| perf6.12 | Amazon Linux | 1:6.12.110-135.201.amzn2023 |
| python3-perf6.12 | Amazon Linux | 1:6.12.110-135.201.amzn2023 |
| perf6.18 | Amazon Linux | 1:6.18.48-107.148.amzn2023 |
| kernel6.18-tools-devel | Amazon Linux | 1:6.18.48-107.148.amzn2023 |
| kernel-headers | Amazon Linux | 1:6.1.188-233.385.amzn2023 |
| python3-perf6.18 | Amazon Linux | 1:6.18.48-107.148.amzn2023 |
| bpftool6.18 | Amazon Linux | 1:6.18.48-107.148.amzn2023 |
| kernel-modules-extra | Amazon Linux | 1:6.1.188-233.385.amzn2023 |
17 more packages have a fixed version. See every fix in Lookup.
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 043546e46dc70c25ff7e2cf6d09cbb0424fc9978, 043546e46dc70c25ff7e2cf6d09cbb0424fc9978, 043546e46dc70c25ff7e2cf6d09cbb0424fc9978 |
| Linux | Linux | 5.8, 0, 5.10.269 |
| amazon:2023 | kernel-livepatch-6.12.110-135.201 | 0 |
| amazon:2023 | kernel6.12 | 0 |
| amazon:2023 | python3-perf | 0 |
| amazon:2023 | kernel6.18-devel | 0 |
| amazon:2023 | perf6.12 | 0 |
| amazon:2023 | python3-perf6.12 | 0 |
| amazon:2023 | perf6.18 | 0 |
| amazon:2023 | kernel6.18-tools-devel | 0 |
| amazon:2023 | kernel-headers | 0 |
| amazon:2023 | python3-perf6.18 | 0 |
| amazon:2023 | bpftool6.18 | 0 |
| amazon:2023 | kernel-modules-extra | 0 |
| amazon:2023 | kernel-tools | 0 |
| amazon:2023 | kernel-modules-extra-common | 0 |
| amazon:2023 | kernel | 0 |
| amazon:2023 | kernel6.18-tools | 0 |
| amazon:2023 | kernel6.18 | 0 |
| amazon:2023 | kernel-livepatch-6.18.48-107.148 | 0 |
…and 18 more
Timeline
- Sep 4, 2026 Coalition ESS Score
- Sep 4, 2026 CVE Published
- Sep 5, 2026 EPSS Score (12 in total, the first dated here)
- Oct 19, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-80806
vulnetix vdb fixes CVE-2026-80806
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-80806/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart