# CVE-2026-74358: ext4: fix fast commit wait/wake bit mapping on 64-bit

> A race condition in the Linux kernel ext4 fast commit path can cause system hangs or crashes due to incorrect wait/wake bit mapping on 64-bit systems.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-74358, DEBIAN-CVE-2026-74358, GHSA-pvr9-cffv-xgvv, UBUNTU-CVE-2026-74358

## What is CVE-2026-74358?

CVE-2026-74358 is a vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-74358?


## How do I fix CVE-2026-74358?

Apply the vendor's patch.

## Is CVE-2026-74358 being exploited?

There is no known exploitation of CVE-2026-74358 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-74358 and fix it if it is affected.

What it is: CVE-2026-74358 is a vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-74358 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-74358/ (Markdown: https://insights.sbomify.com/CVE-2026-74358/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-74358
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-74358
- OSV: https://osv.dev/vulnerability/CVE-2026-74358

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-74358/
Summaries are generated and may contain mistakes; the official description above is the record.