Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
  • Fixed version: Linux Linux 3392391b363a63ebb531d45318a729b1c998565b, 458776af0061afec1014cb3cd0061e282e482e83, 5959cad3cfa852ec07bbdaf9c17f4838a94a8e6c; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.

Low priority for now. Upgrade to Linux Linux 3392391b363a63ebb531d45318a729b1c998565b, 458776af0061afec1014cb3cd0061e282e482e83, 5959cad3cfa852ec07bbdaf9c17f4838a94a8e6c; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Sep 4, 2026
Updated
Oct 19, 2026
EPSS
0.1% · 6th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-80806

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.8affected
    • 043546e46dc70c25ff7e2cf6d09cbb0424fc9978 and later · before add98959b220935b243170214c787bc03044a44daffected · git
    • 043546e46dc70c25ff7e2cf6d09cbb0424fc9978 and later · before f53b325068bca0b238c3e0d2eb7de9b1f2268cabaffected · git
    • 043546e46dc70c25ff7e2cf6d09cbb0424fc9978 and later · before 5959cad3cfa852ec07bbdaf9c17f4838a94a8e6caffected · git
    • 043546e46dc70c25ff7e2cf6d09cbb0424fc9978 and later · before a13f61ba9b2a7a4ff1f140949ccfad23c5313757affected · git
    • 043546e46dc70c25ff7e2cf6d09cbb0424fc9978 and later · before ed1cd834da65db127f1c30ff67e78f14825a06c1affected · git
    • 043546e46dc70c25ff7e2cf6d09cbb0424fc9978 and later · before 458776af0061afec1014cb3cd0061e282e482e83affected · git
    • 043546e46dc70c25ff7e2cf6d09cbb0424fc9978 and later · before 3392391b363a63ebb531d45318a729b1c998565baffected · git
    • 043546e46dc70c25ff7e2cf6d09cbb0424fc9978 and later · before e27bae352158c007143d5bb50f3af33a177c0a37affected · git
    • 043546e46dc70c25ff7e2cf6d09cbb0424fc9978 and later · before da32af420d6d466e247c43ac0b829edeac7ae0adaffected · git

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.187-16.1.187-1
Debian:12linux-6.12before 6.12.111-1~deb12u16.12.111-1~deb12u1
Debian:13linuxbefore 6.12.111-16.12.111-1
Debian:14linuxbefore 7.1.12-17.1.12-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-80804Sep 4, 2026 · xfs: restore nofs context unconditionally in xfs_trans_roll
    0Monitor
  • ← EarlierCVE-2026-80805Sep 4, 2026 · xfs: validate attr entry pointer before field access
    0Monitor
  • Later →CVE-2026-80807Sep 4, 2026 · nilfs2: reject invalid block index in GC ioctl
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux3392391b363a63ebb531d45318a729b1c998565bVendor (CNA)
Linux Linux458776af0061afec1014cb3cd0061e282e482e83Vendor (CNA)
Linux Linux5959cad3cfa852ec07bbdaf9c17f4838a94a8e6cVendor (CNA)
Linux Linuxa13f61ba9b2a7a4ff1f140949ccfad23c5313757Vendor (CNA)
Linux Linuxadd98959b220935b243170214c787bc03044a44dVendor (CNA)
Linux Linuxda32af420d6d466e247c43ac0b829edeac7ae0adVendor (CNA)
Linux Linuxe27bae352158c007143d5bb50f3af33a177c0a37Vendor (CNA)
Linux Linuxed1cd834da65db127f1c30ff67e78f14825a06c1Vendor (CNA)
Linux Linuxf53b325068bca0b238c3e0d2eb7de9b1f2268cabVendor (CNA)
azl3 kernel 6.6.150.1-1 on Azure Linux 3.0—Microsoft (MSRC)
azl3 kernel 6.6.152.1-1 on Azure Linux 3.06.6.157.1-1 · Release NotesMicrosoft (MSRC)
debian:linux6.1.187-1 · Debian:12Package registry (OSV)
debian:linux-6.126.12.111-1~deb12u1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (8 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records