CVE-2025-68261: ext4: add i_data_sem protection in ext4_destroy_inline_data_nolock()
Noroxi assessment
Priority: Monitor (action score 30/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.55% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0cd8feea8777f8d9b9a862b89c688b049a5c8475, 144c48da33a01d92995aeccd8208eb47d2a8e659, 22a76b0861ae61a299c8e126c1aca8c4fda820fd.
Low priority for now. Upgrade to Linux Linux 0cd8feea8777f8d9b9a862b89c688b049a5c8475, 144c48da33a01d92995aeccd8208eb47d2a8e659, 22a76b0861ae61a299c8e126c1aca8c4fda820fd 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: add i_data_sem protection in ext4_destroy_inline_data_nolock() Fix a race between inline data destruction and block mapping. The function ext4_destroy_inline_data_nolock() changes the inode data layout by clearing EXT4_INODE_INLINE_DATA and setting EXT4_INODE_EXTENTS. At the same time, another thread may execute ext4_map_blocks(), which tests EXT4_INODE_EXTENTS to decide whether to call ext4_ext_map_blocks() or ext4_ind_map_blocks(). Without i_data_sem protection, ext4_ind_map_blocks() may receive inode with EXT4_INODE_EXTENTS flag and triggering assert. kernel BUG at fs/ext4/indirect.c:546! EXT4-fs (loop2): unmounting filesystem. invalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014 RIP: 0010:ext4_ind_map_blocks.cold+0x2b/0x5a fs/ext4/indirect.c:546 Call Trace: <TASK> ext4_map_blocks+0xb9b/0x16f0 fs/ext4/inode.c:681 _ext4_get_block+0x242/0x590 fs/ext4/inode.c:822 ext4_block_write_begin+0x48b/0x12c0 fs/ext4/inode.c:1124 ext4_write_begin+0x598/0xef0 fs/ext4/inode.c:1255 ext4_da_write_begin+0x21e/0x9c0 fs/ext4/inode.c:3000 generic_perform_write+0x259/0x5d0 mm/filemap.c:3846 ext4_buffered_write_iter+0x15b/0x470 fs/ext4/file.c:285 ext4_file_write_iter+0x8e0/0x17f0 fs/ext4/file.c:679 call_write_iter include/linux/fs.h:2271 [inline] do_iter_readv_writev+0x212/0x3c0 fs/read_write.c:735 do_iter_write+0x186/0x710 fs/read_write.c:861 vfs_iter_write+0x70/0xa0 fs/read_write.c:902 iter_file_splice_write+0x73b/0xc90 fs/splice.c:685 do_splice_from fs/splice.c:763 [inline] direct_splice_actor+0x10f/0x170 fs/splice.c:950 splice_direct_to_actor+0x33a/0xa10 fs/splice.c:896 do_splice_direct+0x1a9/0x280 fs/splice.c:1002 do_sendfile+0xb13/0x12c0 fs/read_write.c:1255 __do_sys_sendfile64 fs/read_write.c:1323 [inline] __se_sys_sendfile64 fs/read_write.c:1309 [inline] __x64_sys_sendfile64+0x1cf/0x210 fs/read_write.c:1309 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x35/0x80 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x6e/0xd8
- Published
- Dec 16, 2025
- Updated
- Oct 15, 2026
- EPSS
- 0.5% · 45th percentile
- CWE
- —
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.5
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
Running WordPress? Scan your site free with WP Lens
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 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
- 3e96c3fdcfccb321a9e1623f78cc71b44593e965, 5781ac24bbd998ebb1ff30143bb06244d847af48, 9b06cce3ca4d60d442c39bfa7c058b71b1cee6c2, da1e40237f8f3516581b534c484c236a79ccfd14, 7cf6b709b6412afd1d93b2c4b37163c3602e3b95, 4.11affected
- c755e251357a0cee0679081f08c3f4ba797a8009 and later · before b322bac9f01d03190b5abc52be5d9dd9f22a2b41affected · git
- c755e251357a0cee0679081f08c3f4ba797a8009 and later · before 61e03dc3794ebf77a706b85e5a36c9c6d70be6deaffected · git
- c755e251357a0cee0679081f08c3f4ba797a8009 and later · before 5b266cf6851ce72b11b067fe02adf5a8687104adaffected · git
- c755e251357a0cee0679081f08c3f4ba797a8009 and later · before 144c48da33a01d92995aeccd8208eb47d2a8e659affected · git
- c755e251357a0cee0679081f08c3f4ba797a8009 and later · before 22a76b0861ae61a299c8e126c1aca8c4fda820fdaffected · git
- c755e251357a0cee0679081f08c3f4ba797a8009 and later · before ba8aeff294ac7ff6dfe293663d815c54c5ee218caffected · git
- c755e251357a0cee0679081f08c3f4ba797a8009 and later · before 5cad18e527ba8a9ca5463cc170073eeb5a4826f4affected · git
- c755e251357a0cee0679081f08c3f4ba797a8009 and later · before 0cd8feea8777f8d9b9a862b89c688b049a5c8475affected · git
- 3.16.44 and later · before 3.17affected · 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.162-1 | 6.1.162-1 |
| Debian:13 | linux | before 6.12.63-1 | 6.12.63-1 |
| Debian:14 | linux | before 6.17.12-1 | 6.17.12-1 |
| openSUSE:Tumbleweed | kernel-source | before 6.18.2-1.1 | 6.18.2-1.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-2025-68259Dec 16, 2025 · KVM: SVM: Don't skip unrelated instruction if INT3/INTO is replaced0Monitor
- ← EarlierCVE-2025-68260Dec 16, 2025 · rust_binder: fix race condition on death_list31Monitor
- Later →CVE-2025-68262Dec 16, 2025 · crypto: zstd - fix double-free in per-CPU stream cleanup0Monitor
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 | 0cd8feea8777f8d9b9a862b89c688b049a5c8475 | Vendor (CNA) |
| Linux Linux | 144c48da33a01d92995aeccd8208eb47d2a8e659 | Vendor (CNA) |
| Linux Linux | 22a76b0861ae61a299c8e126c1aca8c4fda820fd | Vendor (CNA) |
| Linux Linux | 3.17 | Vendor (CNA) |
| Linux Linux | 3.19 | Vendor (CNA) |
| Linux Linux | 4.10 | Vendor (CNA) |
| Linux Linux | 4.11 | Vendor (CNA) |
| Linux Linux | 4.5 | Vendor (CNA) |
| Linux Linux | 5b266cf6851ce72b11b067fe02adf5a8687104ad | Vendor (CNA) |
| Linux Linux | 5cad18e527ba8a9ca5463cc170073eeb5a4826f4 | Vendor (CNA) |
| Linux Linux | 61e03dc3794ebf77a706b85e5a36c9c6d70be6de | Vendor (CNA) |
| Linux Linux | b322bac9f01d03190b5abc52be5d9dd9f22a2b41 | Vendor (CNA) |
| Linux Linux | ba8aeff294ac7ff6dfe293663d815c54c5ee218c | Vendor (CNA) |
| debian:linux | 6.1.162-1 · Debian:12 | Package registry (OSV) |
| opensuse:kernel-source | 6.18.2-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.
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
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-secondary
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 (9 more)Show less
- git.kernel.org/stable/c/144c48da33a01d92995aeccd8208eb47d2a8e659
- git.kernel.org/stable/c/22a76b0861ae61a299c8e126c1aca8c4fda820fd
- git.kernel.org/stable/c/5b266cf6851ce72b11b067fe02adf5a8687104ad
- git.kernel.org/stable/c/5cad18e527ba8a9ca5463cc170073eeb5a4826f4
- git.kernel.org/stable/c/61e03dc3794ebf77a706b85e5a36c9c6d70be6de
- git.kernel.org/stable/c/b322bac9f01d03190b5abc52be5d9dd9f22a2b41
- git.kernel.org/stable/c/ba8aeff294ac7ff6dfe293663d815c54c5ee218c
- cert-portal.siemens.com/productcert/html/ssa-019113.html
- cert-portal.siemens.com/productcert/html/ssa-457936.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.