NVD / CVE Program· CNA Linux

CVE-2026-100073: ext4: fix transaction overflow during writeback

MediumCVSS 5.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 22/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.10% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Linux Linux 46e8e31771f4f1c5e1cdec37a889a6730e42e9f1, 6.17, a22464c5df5827e884a5a7d3d8fb03870e5bb6c8.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 46e8e31771f4f1c5e1cdec37a889a6730e42e9f1, 6.17, a22464c5df5827e884a5a7d3d8fb03870e5bb6c8 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Denial of service

Published: Sep 25, 2026
Updated: Oct 21, 2026
EPSS: 0.1% · 0th percentile
CWE: CWE-617

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 22 / 40 · 5.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.1%

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
linux	linux kernel	cpe:2.3:o:linux:linux_kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

Linux Linux
- 2b6d39229bc783198222cddd31e2fbded93c8db7, 6.17affected
- 95ad8ee45cdbc321c135a2db895d48b374ef0f87 and later · before a22464c5df5827e884a5a7d3d8fb03870e5bb6c8affected · git
- 95ad8ee45cdbc321c135a2db895d48b374ef0f87 and later · before 46e8e31771f4f1c5e1cdec37a889a6730e42e9f1affected · git
- 6.16.3 and later · before 6.17affected · semver
- before 6.17not affected · semver
- 7.2.6 and later · up to and including 7.2.*not affected · semver
- 7.3 and laternot affected · original_commit_for_fix

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

linux linux kernel6.16.3 and later · before 6.17
linux linux kernel6.17 and later · before 7.2.6

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:14	linux	before 7.2.6-1	7.2.6-1
openSUSE:Tumbleweed	kernel-source	before 7.2.9-1.1	7.2.9-1.1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
90Now
CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
89Now
CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
85Now

Published before and after this one in the same product

← EarlierCVE-2026-100071Sep 25, 2026 · net: hsr: free learned nodes on device setup failure
22Monitor
← EarlierCVE-2026-100072Sep 25, 2026 · ACPI: platform: Use acpi_bus_get_primary_device()
31Monitor
Later →CVE-2026-100074Sep 25, 2026 · bpf: Mark bpf_refcount field as unique
22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Linux Linux	46e8e31771f4f1c5e1cdec37a889a6730e42e9f1	Vendor (CNA)
Linux Linux	6.17	Vendor (CNA)
Linux Linux	a22464c5df5827e884a5a7d3d8fb03870e5bb6c8	Vendor (CNA)
debian:linux	7.2.6-1 · Debian:14	Package registry (OSV)
opensuse:kernel-source	7.2.9-1.1 · openSUSE:Tumbleweed	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-5295293 days apartiommu: Fix WARN_ON in __iommu_group_set_domain_nofail() due to reset
35Monitor
CVE-2026-31739147 days apartcrypto: tegra - Add missing CRYPTO_ALG_ASYNC
35Monitor
CVE-2026-46117120 days apartRDMA/mana: Remove user triggerable WARN_ON() in mana_ib_create_qp_rss()
31Monitor
CVE-2026-31398175 days apartmm/rmap: fix incorrect pte restoration for lazyfree folios
31Monitor
CVE-2025-39803375 days apartscsi: ufs: core: Remove WARN_ON_ONCE() call from ufshcd_uic_cmd_compl()
31Monitor
CVE-2026-5295493 days apartlibceph: handle rbtree insertion error in decode_choose_args()
30Monitor