LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23224: erofs: fix UAF issue for file-backed mounts w/ directio option

In the Linux kernel, the following vulnerability has been resolved: erofs: fix UAF issue for file-backed mounts w/ directio option [ 9.269940][ T3222] Call trace: [ 9.269948][ T3222] ext4_file_read_iter+0xac/0x108 [ 9.269979][ T3222] vfs_iocb_iter_read+0xac/0x198 [ 9.269993][ T3222] erofs_fileio_rq_submit+0x12c/0x180 [ 9.270008][ T3222] erofs_fileio_submit_bio+0x14/0x24 [ 9.270030][ T3222] z_erofs_runqueue+0x834/0x8ac [ 9.270054][ T3222] z_erofs_read_folio+0x120/0x220 [ 9.270083][ T3222] filemap_read_folio+0x60/0x120 [ 9.270102][ T3222] filemap_fault+0xcac/0x1060 [ 9.270119][ T3222] do_pte_missing+0x2d8/0x1554 [ 9.270131][ T3222] handle_mm_fault+0x5ec/0x70c [ 9.270142][ T3222] do_page_fault+0x178/0x88c [ 9.270167][ T3222] do_translation_fault+0x38/0x54 [ 9.270183][ T3222] do_mem_abort+0x54/0xac [ 9.270208][ T3222] el0_da+0x44/0x7c [ 9.270227][ T3222] el0t_64_sync_handler+0x5c/0xf4 [ 9.270253][ T3222] el0t_64_sync+0x1bc/0x1c0 EROFS may encounter above panic when enabling file-backed mount w/ directio mount option, the root cause is it may suffer UAF in below race condition: - z_erofs_read_folio wq s_dio_done_wq - z_erofs_runqueue - erofs_fileio_submit_bio - erofs_fileio_rq_submit - vfs_iocb_iter_read - ext4_file_read_iter - ext4_dio_read_iter - iomap_dio_rw : bio was submitted and return -EIOCBQUEUED - dio_aio_complete_work - dio_complete - dio->iocb->ki_complete (erofs_fileio_ki_complete()) - kfree(rq) : it frees iocb, iocb.ki_filp can be UAF in file_accessed(). - file_accessed : access NULL file point Introduce a reference count in struct erofs_fileio_rq, and initialize it as two, both erofs_fileio_ki_complete() and erofs_fileio_rq_submit() will decrease reference count, the last one decreasing the reference count to zero will free rq.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A race condition in Linux EROFS file-backed mounts using the directio option can access memory after it is freed, causing a kernel panic. The supplied CVSS score is 7.8 (high), but exposure is limited to systems using this specific mount configuration.

Executive priority

Treat this as an expedited, configuration-dependent kernel update. Prioritize systems actually using file-backed EROFS with directio, especially multi-user or less-trusted environments. Systems without that configuration appear unlikely to reach the described vulnerable path, but version and configuration inventories should confirm this.

Technical view

Asynchronous direct I/O completion can free an erofs_fileio_rq while the submitting path still accesses its embedded I/O control block, producing a use-after-free in file_accessed(). The stable fix adds reference counting so the request is freed only after submission and completion paths release it.

Likely exposure

Likely exposure is concentrated on Linux systems using file-backed EROFS mounts with directio enabled. The supplied affected-version data lists multiple kernel versions but lacks clear range semantics, so administrators should verify distribution-specific builds and backports rather than relying only on version numbers.

Exploitation context

The CVSS vector describes local access, low privileges, low complexity, and no user interaction. The bundle provides evidence of a kernel panic and models high confidentiality, integrity, and availability impact. It contains no evidence of active exploitation, and the CVE is not listed as KEV.

Researcher notes

The demonstrated failure is a submit-versus-completion race: asynchronous completion frees the request before the submission path finishes using ki_filp. The fix initializes two references and releases one from each path. The bundle does not establish reliable exploitation beyond denial of service or clarify affected-version ranges.

Mitigation direction

  • Update to a vendor-supported kernel containing the referenced stable fix or an equivalent backport.
  • Verify the vendor advisory because the supplied affected-version boundaries are ambiguous.
  • Until patched, avoid file-backed EROFS mounts with directio where operationally safe and vendor-approved.
  • Prioritize systems where local, low-privileged users can interact with the affected storage configuration.

Validation and detection

  • Inventory kernel builds and compare them with distribution-specific advisories and backport records.
  • Identify file-backed EROFS mounts configured with the directio option.
  • Confirm the installed kernel contains the reference-counting fix or an equivalent vendor backport.
  • After updating, exercise legitimate EROFS workloads and monitor kernel logs for related panics or memory errors.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-23224 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2026-23224Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxfb176750266a3d7f42ebdcf28e8ba40350b27847, fb176750266a3d7f42ebdcf28e8ba40350b27847, fb176750266a3d7f42ebdcf28e8ba40350b27847, fb176750266a3d7f42ebdcf28e8ba40350b27847unaffected
LinuxLinux6.12, 0, 6.12.72, 6.18.11, 6.19.1, 7.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.