Unknown

CVE-2026-80806 — 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.

Published Sep 4, 2026 · Updated Oct 19, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: Linux

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.2% (30-day exploitation probability)+1

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.17%

ahead of 7% of scored CVEs · Oct 25, 2026

Affects

Linux

CVSS base

—

Score not published yet.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Linux	Linux	≥ 043546e46dc70c25ff7e2cf6d09cbb0424fc9978 and < add98959b220935b243170214c787bc03044a44d≥ 043546e46dc70c25ff7e2cf6d09cbb0424fc9978 and < f53b325068bca0b238c3e0d2eb7de9b1f2268cab≥ 043546e46dc70c25ff7e2cf6d09cbb0424fc9978 and < 5959cad3cfa852ec07bbdaf9c17f4838a94a8e6c≥ 043546e46dc70c25ff7e2cf6d09cbb0424fc9978 and < a13f61ba9b2a7a4ff1f140949ccfad23c5313757≥ 043546e46dc70c25ff7e2cf6d09cbb0424fc9978 and < ed1cd834da65db127f1c30ff67e78f14825a06c1≥ 043546e46dc70c25ff7e2cf6d09cbb0424fc9978 and < 458776af0061afec1014cb3cd0061e282e482e83≥ 043546e46dc70c25ff7e2cf6d09cbb0424fc9978 and < 3392391b363a63ebb531d45318a729b1c998565b≥ 043546e46dc70c25ff7e2cf6d09cbb0424fc9978 and < e27bae352158c007143d5bb50f3af33a177c0a37 and 2 more ≥ 043546e46dc70c25ff7e2cf6d09cbb0424fc9978 and < da32af420d6d466e247c43ac0b829edeac7ae0adversion 5.8	Vulnerable	CVE Program (cve.org) e CISA ADP

EPSS over time FIRST

Oct 15, 2026 → Oct 25, 2026 · 10 reading(s) · max 0.17%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Not enough vector or weakness data: use the affected application’s logs as a starting point.

application logs

Timeline

What happened to this CVE, newest first.

2026
Record published
Oct 15, 2026
Affected products added · linux/linux
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
Source status changed · → Received
Oct 15, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 15, 2026 · NIST National Vulnerability Database
CVE published
Sep 4, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

1× References added · Oct 19, 2026 – Oct 19, 2026
1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

11 on the record

nvd.nist.gov/vuln/detail/CVE-2026-80806
GitHub Security Advisories
git.kernel.org/stable/c/e27bae352158c007143d5bb50f3af33a177c0a37
NIST National Vulnerability Database
github.com/advisories/GHSA-jqxc-3f8r-hc2f
GitHub Security Advisories
git.kernel.org/stable/c/da32af420d6d466e247c43ac0b829edeac7ae0ad
NIST National Vulnerability Database
git.kernel.org/stable/c/3392391b363a63ebb531d45318a729b1c998565b
NIST National Vulnerability Database
git.kernel.org/stable/c/ed1cd834da65db127f1c30ff67e78f14825a06c1
NIST National Vulnerability Database
git.kernel.org/stable/c/add98959b220935b243170214c787bc03044a44d
NIST National Vulnerability Database
git.kernel.org/stable/c/458776af0061afec1014cb3cd0061e282e482e83
NIST National Vulnerability Database
git.kernel.org/stable/c/5959cad3cfa852ec07bbdaf9c17f4838a94a8e6c
NIST National Vulnerability Database
git.kernel.org/stable/c/f53b325068bca0b238c3e0d2eb7de9b1f2268cab
NIST National Vulnerability Database
git.kernel.org/stable/c/a13f61ba9b2a7a4ff1f140949ccfad23c5313757
NIST National Vulnerability Database

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

Unknown CVE-2026-99092 riscv: patch: fix handling of bpf-jit execmem addresses 10h
Unknown CVE-2026-99093 mm: don't schedule deferred kernel page table freeing while booting 10h
Unknown CVE-2026-99095 drm/vc4: drain the hangcheck timer and works on V3D unbind 10h
Unknown CVE-2026-99096 io_uring/register: don't exempt disabled rings from task restrictions 10h
Unknown CVE-2026-99097 tee: shm: reject zero-sized allocations in tee_dyn_shm_alloc_helper() 10h
Unknown CVE-2026-99098 dm-integrity: fix buffer overflow in inline mode with large tag size 10h

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No CVSS score published by NVD, the CNA, CISA or GitHub so far.
No fixed version, patch or mitigation documented.
No CISA SSVC assessment.
No CWE classification.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-80806 is "ext4: don't enable DAX on new encrypted files", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.17% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.