cve.bz

CVE-2026-80806 linux linux

no score yetEPSS 0.2%Fix available

linux linux: no CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 7th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • Linux Linux: fixed in 5.10.269
  • Linux Linux: fixed in 5.15.220
  • Linux Linux: fixed in 6.1.187
  • Linux Linux: fixed in 6.6.156
  • Linux Linux: fixed in 6.12.108
  • Linux Linux: fixed in 6.18.47
  • Linux Linux: fixed in 7.1.11
  • Linux Linux: fixed in 7.2.1
  • Debian, Ubuntu, openSUSE, Azure Linux, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-80806 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-80806?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-80806?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-80806 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux5.8 and later

Fixed in

ProductRelease lineFixed in
Linux5.105.10.269
Linux5.155.15.220
Linux6.16.1.187
Linux6.66.6.156
Linux6.126.12.108
Linux6.186.18.47
Linux7.17.1.11
Linux7.27.2.1
Linuxlater releases7.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.187-1DEBIAN-CVE-2026-80806
Debian12linux-6.126.12.111-1~deb12u1DEBIAN-CVE-2026-80806
Debian13linux6.12.111-1DEBIAN-CVE-2026-80806
Debian14linux7.1.12-1DEBIAN-CVE-2026-80806
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-80806
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-80806
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-80806
Ubuntu22.04:LTSlinux5.15.0-202.212UBUNTU-CVE-2026-80806 USN-8961-1
Ubuntu22.04:LTSlinux-aws5.15.0-1119.126UBUNTU-CVE-2026-80806 USN-8961-1
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1069.74~22.04.1UBUNTU-CVE-2026-80806 USN-9024-1
Ubuntu22.04:LTSlinux-azure5.15.0-1125.134UBUNTU-CVE-2026-80806 USN-8961-1
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1073.82~22.04.1UBUNTU-CVE-2026-80806 USN-9026-1
Ubuntu22.04:LTSlinux-azure-fde5.15.0-1124.133UBUNTU-CVE-2026-80806 USN-8962-1
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1071.78~22.04.1UBUNTU-CVE-2026-80806 USN-9026-1
Ubuntu22.04:LTSlinux-gcp5.15.0-1120.130UBUNTU-CVE-2026-80806 USN-8961-1
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1073.81~22.04.1UBUNTU-CVE-2026-80806 USN-9024-1
78 more for Ubuntu in the JSON and on Ubuntu's page.
openSUSETumbleweedkernel-source7.2.5-1.1openSUSE-SU-2026:11773-1
Azure Linux3kernel6.6.157.1-1AZL-99669
Alpaquita23linux-lts6.1.189-r0BELL-CVE-2026-80806
Alpaquita25linux-lts6.12.111-r0BELL-CVE-2026-80806
Alpaquitastreamlinux-lts6.18.53-r0BELL-CVE-2026-80806

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A confidentiality issue in ext4 encrypted file creation can occur when the filesystem is mounted with dax always. A new encrypted regular file may incorrectly keep S_DAX because the encryption inode flag is set after the initial inode flag calculation, so DAX I/O can bypass the normal fscrypt encryption path and write plaintext data to storage. For the CVSS the PR:L is used because a local user who can create files in an affected encrypted directory can trigger the vulnerable behavior once the non default DAX configuration already exists. The issue is not network reachable and does not indicate memory corruption or kernel code execution. Impact is primarily confidentiality loss for data expected to be encrypted, with possible integrity policy impact because mount and encryption restrictions are not enforced as intended.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelFix deferred
Red Hat Enterprise Linux 6kernelOut of support scope
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelFix deferred
Red Hat Enterprise Linux 8kernel-rtFix deferred
Red Hat Enterprise Linux 9kernelFix deferred
Red Hat Enterprise Linux 9kernel-rtFix deferred
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Fix deferred
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Fix deferred
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Fix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-80806.

References

Check your stackJSON