CVE-2026-100073

5.5 MEDIUM 0.1% exploit odds Fix listed Other OS & kernel

What it is

In the Linux kernel, the following vulnerability has been resolved: ext4: fix transaction overflow during writeback Commit 95ad8ee45cdb ("ext4: correct the reserved credits for extent conversion") was correct to note that we need to reserve enough credits for all extents possibly underlying a large folio. However it was too eager to reduce the number of reserved credits. Extent conversion may not only need to touch several leaf extent blocks, it may also need to split extents - for example a single large unwritten extent may need to be split into many small written ones in case of sparse folio dirtying. This can thus result not only in extent leaf modifications but also in a need to allocate new extent tree nodes. As a result the reserved transaction credits were not sufficient in some corner cases. Use ext4_meta_trans_blocks() for correct upper bound credit estimate.

At a glance

Exploitability: Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
Exploit odds: 0.1% chance of exploitation in the next 30 days (EPSS).
Fix: A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

2026-09-25 14:17 UTC PublishedDisclosed publicly on CVE.org and NVD
2026-10-21 18:57 UTC Last updatedMost recent change to the record

Why it ranks here

Exploited in the wild: no, CISA does not list it.
Exploit odds: 0.1% in the next 30 days (EPSS).
Severity: 5.5 MEDIUM (CVSS).
Fix: a patch or advisory is linked.

Details

Published: 2026-09-25 14:17 UTC
Last modified: 2026-10-21 18:57 UTC
Exploit probability: 0.1% · EPSS, next 30 days
Weakness: CWE-617
Record status: Analyzed

Affected

Linux Kernel < 6.17
Linux Kernel < 7.2.6

Attack profile CVSS 3.1 · 5.5

Attack vector: Local
Complexity: Low
Privileges needed: Low
User interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Raw vector

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

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-100073.md and follow it. Check whether this project is affected by CVE-2026-100073. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

· More options · Status badge

Download Square Reddit

Fix and advisories

References

NVD record · CVE.org record