Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-80806ext4: don't enable DAX on new encrypted files

Description

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. ID reserved

    By Linux

  2. · 9 days later

    Published

  3. · 45 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 043546e46dc70c25ff7e2cf6d09cbb0424fc9978 – < add98959b220935b243170214c787bc03044a44d
    • affected 043546e46dc70c25ff7e2cf6d09cbb0424fc9978 – < f53b325068bca0b238c3e0d2eb7de9b1f2268cab
    • affected 043546e46dc70c25ff7e2cf6d09cbb0424fc9978 – < 5959cad3cfa852ec07bbdaf9c17f4838a94a8e6c
    • affected 043546e46dc70c25ff7e2cf6d09cbb0424fc9978 – < a13f61ba9b2a7a4ff1f140949ccfad23c5313757
    • affected 043546e46dc70c25ff7e2cf6d09cbb0424fc9978 – < ed1cd834da65db127f1c30ff67e78f14825a06c1
    • affected 043546e46dc70c25ff7e2cf6d09cbb0424fc9978 – < 458776af0061afec1014cb3cd0061e282e482e83
    • affected 043546e46dc70c25ff7e2cf6d09cbb0424fc9978 – < 3392391b363a63ebb531d45318a729b1c998565b
    • affected 043546e46dc70c25ff7e2cf6d09cbb0424fc9978 – < e27bae352158c007143d5bb50f3af33a177c0a37
    • affected 043546e46dc70c25ff7e2cf6d09cbb0424fc9978 – < da32af420d6d466e247c43ac0b829edeac7ae0ad
  • Linux · Linux

    • affected 5.8
    • unaffected < 5.8
    • unaffected 5.10.269 – ≤ 5.10.*
    • unaffected 5.15.220 – ≤ 5.15.*
    • unaffected 6.1.187 – ≤ 6.1.*
    • unaffected 6.6.156 – ≤ 6.6.*
    • unaffected 6.12.108 – ≤ 6.12.*
    • unaffected 6.18.47 – ≤ 6.18.*
    • unaffected 7.1.11 – ≤ 7.1.*
    • unaffected 7.2.1 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-80806 badge
[![CVE-2026-80806](https://cveledger.app/badge/CVE-2026-80806.svg)](https://cveledger.app/cve/CVE-2026-80806)

Record last updated .