Menu

Star on GitHub · 3.2k

CVE-2026-74358

In the Linux kernel, the following vulnerability has been resolved: ext4: fix fast commit wait/wake bit mapping on 64-bit On 64-bit, ext4 dynamic inode states live in the upper half of i_flags, a…

Published Aug 15, 2026EPSS 0.21%

Overview

CVE-2026-74358 is a known-severity vulnerability. It was published on August 15, 2026.

Technical description

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

ext4: fix fast commit wait/wake bit mapping on 64-bit

On 64-bit, ext4 dynamic inode states live in the upper half of i_flags,

and ext4_test_inode_state() applies the corresponding +32 offset.

The fast-commit wait and wake paths open-coded the wait key with the raw

EXT4_STATE_* value. Add small helpers for the state wait word and bit,

and use them for the FC_COMMITTING and FC_FLUSHING_DATA waits so the wait

key follows the same mapping as the state helpers.

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-74358?

CVE-2026-74358 is a known-severity vulnerability. It was published on August 15, 2026.

How severe is CVE-2026-74358?

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-74358?

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-74358?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-74358 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.