Quick answers
- Is CVE-2026-93257 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93257 being exploited in the wild.
- How severe is CVE-2026-93257?
- Informational severity, published 24 September 2026.
- Which products and versions are affected?
- Unknown Linux kernel all versions with fs_bio_integrity helpers (from commit 0bde8a12b554 onwards).
- Is there a fix for CVE-2026-93257?
- A patch was published on 2026-08-04. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-93257 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-93257?
- Check whether you run Unknown Linux kernel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A logic error in the fs-integrity block layer helpers (fs_bio_integrity_generate and fs_bio_integrity_verify) failed to check BIP_CHECK_FLAGS before processing protection information, causing the functions to be called on non-PI metadata. This results in generation of incorrect metadata and crashes in the verification handler. The fix adds flag checks to match the behavior of the block layer's auto-generated metadata path.
Affected products
- <UNKNOWN> Linux kernel all versions with fs_bio_integrity helpers (from commit 0bde8a12b554 onwards)
Timeline
- 2026-09-24: disclosed
- 2026-08-04: patched