CVE-2026-93268: ext4: skip extra isize expansion during mount to prevent deadlock
Noroxi assessment
Priority: Monitor (action score 0/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.20% (FIRST EPSS).
- Fixed version: Linux Linux 1dd4882dbdc8bfdf2182fa388883c143fac0902a, 2fb8ff81659a57c42bb7b49e8339a2be2a318ef8, 41897f1bcf4ace5f1f28d0be784b6f4f0e929641; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.157.1-1.
Low priority for now. Upgrade to Linux Linux 1dd4882dbdc8bfdf2182fa388883c143fac0902a, 2fb8ff81659a57c42bb7b49e8339a2be2a318ef8, 41897f1bcf4ace5f1f28d0be784b6f4f0e929641; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.157.1-1 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: skip extra isize expansion during mount to prevent deadlock ext4_try_to_expand_extra_isize() is called from __ext4_mark_inode_dirty() while holding an active jbd2 handle. During mount (!SB_ACTIVE), the expand path may move xattrs to external blocks and release ea_inodes via iput(). When !SB_ACTIVE, iput() calls write_inode_now() which acquires s_writepages_rwsem, creating a circular lock dependency: s_writepages_rwsem --> jbd2_handle --> xattr_sem --> s_writepages_rwsem This can be triggered via: ext4_process_orphan() -> ext4_truncate() -> ext4_mark_inode_dirty() -> ext4_try_to_expand_extra_isize() or: ext4_evict_inode() -> ext4_mark_inode_dirty() -> ext4_try_to_expand_extra_isize() Skip expansion when !SB_ACTIVE. This is a minor loss of functionality (extra isize won't grow for these inodes during mount), which e2fsck can resolve later if needed.
- Published
- Sep 24, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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 itNoroxi 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 helpAffected 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.
—
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
- 4.7affected
- c8585c6fcaf2011de54c3592e80a634a2b9e1a7f and later · before 41897f1bcf4ace5f1f28d0be784b6f4f0e929641affected · git
- c8585c6fcaf2011de54c3592e80a634a2b9e1a7f and later · before 9c3469377b1d8caba6bec6ef3c460810bbfb02ccaffected · git
- c8585c6fcaf2011de54c3592e80a634a2b9e1a7f and later · before 1dd4882dbdc8bfdf2182fa388883c143fac0902aaffected · git
- c8585c6fcaf2011de54c3592e80a634a2b9e1a7f and later · before 7ba09330d9ea6e996228316719eae812d7e04983affected · git
- c8585c6fcaf2011de54c3592e80a634a2b9e1a7f and later · before c5e6434cc55f30220b228be237bb666351f9f4ddaffected · git
- c8585c6fcaf2011de54c3592e80a634a2b9e1a7f and later · before 7ace189b9ea79cf78df9c32b940ce12735f9459aaffected · git
- c8585c6fcaf2011de54c3592e80a634a2b9e1a7f and later · before 2fb8ff81659a57c42bb7b49e8339a2be2a318ef8affected · git
- c8585c6fcaf2011de54c3592e80a634a2b9e1a7f and later · before 7461c60b9c6a839b13ad4c3490681a0cf5aa0637affected · git
- before 4.7not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-93266Sep 24, 2026 · arm64: RSI: fix field-spanning write warning in attestation token init0Monitor
- ← EarlierCVE-2026-93267Sep 24, 2026 · RDMA/core: Fix potential use after free in uverbs_free_dmah()0Monitor
- Later →CVE-2026-93269Sep 24, 2026 · ext4: fix circular lock dependency in ext4_ext_migrate0Monitor
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 | 1dd4882dbdc8bfdf2182fa388883c143fac0902a | Vendor (CNA) |
| Linux Linux | 2fb8ff81659a57c42bb7b49e8339a2be2a318ef8 | Vendor (CNA) |
| Linux Linux | 41897f1bcf4ace5f1f28d0be784b6f4f0e929641 | Vendor (CNA) |
| Linux Linux | 7461c60b9c6a839b13ad4c3490681a0cf5aa0637 | Vendor (CNA) |
| Linux Linux | 7ace189b9ea79cf78df9c32b940ce12735f9459a | Vendor (CNA) |
| Linux Linux | 7ba09330d9ea6e996228316719eae812d7e04983 | Vendor (CNA) |
| Linux Linux | 9c3469377b1d8caba6bec6ef3c460810bbfb02cc | Vendor (CNA) |
| Linux Linux | c5e6434cc55f30220b228be237bb666351f9f4dd | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/2fb8ff81659a57c42bb7b49e8339a2be2a318ef8
- git.kernel.org/stable/c/41897f1bcf4ace5f1f28d0be784b6f4f0e929641
- git.kernel.org/stable/c/7461c60b9c6a839b13ad4c3490681a0cf5aa0637
- git.kernel.org/stable/c/7ace189b9ea79cf78df9c32b940ce12735f9459a
- git.kernel.org/stable/c/7ba09330d9ea6e996228316719eae812d7e04983
- git.kernel.org/stable/c/9c3469377b1d8caba6bec6ef3c460810bbfb02cc
- git.kernel.org/stable/c/c5e6434cc55f30220b228be237bb666351f9f4dd
Vendor advisories and official records. Exploit/PoC links are deliberately left out.