CVE-2026-93269

ext4: fix circular lock dependency in ext4_ext_migrate

N/A
Published: September 24, 2026 at 03:52 PM UTC
Updated: October 19, 2026 at 10:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: ext4: fix circular lock dependency in ext4_ext_migrate Move iput(tmp_inode) after ext4_writepages_up_write() to avoid a circular lock dependency between s_writepages_rwsem and sb_internal (freeze protection). The deadlock scenario: CPU0 (EXT4_IOC_MIGRATE) CPU1 (orphan cleanup during mount) ---- ---- ext4_ext_migrate() ext4_writepages_down_write() s_writepages_rwsem (write) ext4_evict_inode() sb_start_intwrite() [sb_internal] ... ext4_writepages() s_writepages_rwsem (read) [BLOCKED] iput(tmp_inode) ext4_evict_inode() sb_start_intwrite() [BLOCKED] The tmp_inode is a temporary inode with nlink=0 created solely for building the extent tree. Its eviction does not require s_writepages_rwsem protection, so deferring iput() until after releasing the rwsem is safe.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.14.1724.19.1074.9.2155.4.235.5.75.669f8a7991fd93c49096ddd11574db3e7df238b7b8cf20fb73e73a4c4df0328b5297842c5ef34fdd9bcc1eab71a67c46b9e24544ac7923f44444174cecb85f4d23f794e24127f3e562cb3b54b0803f456e5d25003d059649e18a249635ed5ca7a7b1de5adeb799e163dc2bc1ea0a4820b66f79d32a5e907df
Vendor states this is fixed in 32f7ab52875ec7f800ca67e7176e5743a84baddf (fixed)
Vendor states this is fixed in 452950461241dfed8b1d32e94b227db38c99c5af (fixed)
Vendor states this is fixed in a897682793eba5de51ee6f3152760374afa629cf (fixed)
Vendor states this is fixed in ada23457d4748d6e9c36c6f871fc29a6f558c48c (fixed)
Vendor states this is fixed in e4223231b6860141813637a6413c2371ae4d6fa8 (fixed)
Affected range stops below 4.10, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.15, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.20, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.6 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card