Menu

Star on GitHub · 3.5k

CVE-2026-92501

In the Linux kernel, the following vulnerability has been resolved: ext4: drain in-flight DIO before buffered write fallback generic/746 started failing intermittently on ext3 (no-extent inodes).

Published Sep 17, 2026EPSS 0.18%

Overview

CVE-2026-92501 is a known-severity vulnerability. It was published on September 17, 2026.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

ext4: drain in-flight DIO before buffered write fallback

generic/746 started failing intermittently on ext3 (no-extent inodes).

The test triggers 'Page cache invalidation failure on direct I/O'

warnings and subsequent fsync returns -EIO. Adding a 50ms delay

between ext4_buffered_write_iter() and filemap_write_and_wait_range()

in ext4_dio_write_iter() makes the race almost always reproducible.

On no-extent inodes, DIO writes to holes cannot use unwritten extents,

so ext4_iomap_alloc() leaves m_flags=0 and ext4_map_blocks() returns 0.

The iomap layer then returns -ENOTBLK, causing fallback to buffered I/O.

The fallback path in ext4_dio_write_iter() calls

ext4_buffered_write_iter() which dirties pages, then does flush and

invalidate. However, there's an unprotected window between

ext4_buffered_write_iter() returning (with inode lock released) and

the subsequent flush+invalidate.

Concurrent async DIO completions from

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-92501?

CVE-2026-92501 is a known-severity vulnerability. It was published on September 17, 2026.

How severe is CVE-2026-92501?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-92501?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-92501?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-92501 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

CyberStrike v2 is here — more intelligence, greater reach