ext4: fix circular lock dependency in ext4_ext_migrate
Summary
| CVE | CVE-2026-93269 |
|---|
| State | PUBLISHED |
|---|
| Assigner | Linux |
|---|
| Source Priority | CVE Program / NVD first with legacy fallback |
|---|
| Published | 2026-09-24 16:17:23 UTC |
|---|
| Updated | 2026-09-24 16:17:23 UTC |
|---|
| 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. |
|---|
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected cb85f4d23f794e24127f3e562cb3b54b0803f456 452950461241dfed8b1d32e94b227db38c99c5af git |
Not specified |
| CNA |
Linux |
Linux |
affected cb85f4d23f794e24127f3e562cb3b54b0803f456 ada23457d4748d6e9c36c6f871fc29a6f558c48c git |
Not specified |
| CNA |
Linux |
Linux |
affected cb85f4d23f794e24127f3e562cb3b54b0803f456 e4223231b6860141813637a6413c2371ae4d6fa8 git |
Not specified |
| CNA |
Linux |
Linux |
affected cb85f4d23f794e24127f3e562cb3b54b0803f456 32f7ab52875ec7f800ca67e7176e5743a84baddf git |
Not specified |
| CNA |
Linux |
Linux |
affected cb85f4d23f794e24127f3e562cb3b54b0803f456 a897682793eba5de51ee6f3152760374afa629cf git |
Not specified |
| CNA |
Linux |
Linux |
affected eb799e163dc2bc1ea0a4820b66f79d32a5e907df git |
Not specified |
| CNA |
Linux |
Linux |
affected bcc1eab71a67c46b9e24544ac7923f44444174ce git |
Not specified |
| CNA |
Linux |
Linux |
affected 8cf20fb73e73a4c4df0328b5297842c5ef34fdd9 git |
Not specified |
| CNA |
Linux |
Linux |
affected e5d25003d059649e18a249635ed5ca7a7b1de5ad git |
Not specified |
| CNA |
Linux |
Linux |
affected 69f8a7991fd93c49096ddd11574db3e7df238b7b git |
Not specified |
| CNA |
Linux |
Linux |
affected 4.9.215 4.10 semver |
Not specified |
| CNA |
Linux |
Linux |
affected 4.14.172 4.15 semver |
Not specified |
| CNA |
Linux |
Linux |
affected 4.19.107 4.20 semver |
Not specified |
| CNA |
Linux |
Linux |
affected 5.4.23 5.5 semver |
Not specified |
| CNA |
Linux |
Linux |
affected 5.5.7 5.6 semver |
Not specified |
| CNA |
Linux |
Linux |
affected 5.6 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.6 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.157 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.110 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.52 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2.6 7.2.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.3-rc1 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/e4223231b6860141813637a6413c2371ae4d6fa8 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/452950461241dfed8b1d32e94b227db38c99c5af |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/32f7ab52875ec7f800ca67e7176e5743a84baddf |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/ada23457d4748d6e9c36c6f871fc29a6f558c48c |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/a897682793eba5de51ee6f3152760374afa629cf |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.