CVE-2026-93269

Unknown

Last modified

CVE-2026-93269 is a vulnerability of currently unknown severity. 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..

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 Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= cb85f4d23f794e24127f3e562cb3b54b0803f456, < 452950461241dfed8b1d32e94b227db38c99c5af; >= cb85f4d23f794e24127f3e562cb3b54b0803f456, < ada23457d4748d6e9c36c6f871fc29a6f558c48c; >= cb85f4d23f794e24127f3e562cb3b54b0803f456, < e4223231b6860141813637a6413c2371ae4d6fa8; >= cb85f4d23f794e24127f3e562cb3b54b0803f456, < 32f7ab52875ec7f800ca67e7176e5743a84baddf; >= cb85f4d23f794e24127f3e562cb3b54b0803f456, < a897682793eba5de51ee6f3152760374afa629cf; eb799e163dc2bc1ea0a4820b66f79d32a5e907df; bcc1eab71a67c46b9e24544ac7923f44444174ce; 8cf20fb73e73a4c4df0328b5297842c5ef34fdd9; e5d25003d059649e18a249635ed5ca7a7b1de5ad; 69f8a7991fd93c49096ddd11574db3e7df238b7b; >= 4.9.215, < 4.10; >= 4.14.172, < 4.15; >= 4.19.107, < 4.20; >= 5.4.23, < 5.5; >= 5.5.7, < 5.6
LinuxLinux5.6

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-93269?
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.
How severe is CVE-2026-93269?
Severity scoring for CVE-2026-93269 is pending analysis.
How do I fix CVE-2026-93269?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-93269?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST