ext4: fix use-after-free in ext4_orphan_cleanup
Noroxi assessment
Priority: Monitor (action score 31/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).
- Someone with local access to the system can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 026a4490b5381229a30f23d073b58e8e35ee6858, 7223d5e75f26352354ea2c0ccf8b579821b52adf, 7908b8a541b1578cc61b4da7f19b604a931441da.
Low priority for now. Upgrade to Linux Linux 026a4490b5381229a30f23d073b58e8e35ee6858, 7223d5e75f26352354ea2c0ccf8b579821b52adf, 7908b8a541b1578cc61b4da7f19b604a931441da 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: fix use-after-free in ext4_orphan_cleanup I caught a issue as follows: ================================================================== BUG: KASAN: use-after-free in __list_add_valid+0x28/0x1a0 Read of size 8 at addr ffff88814b13f378 by task mount/710 CPU: 1 PID: 710 Comm: mount Not tainted 6.1.0-rc3-next #370 Call Trace: <TASK> dump_stack_lvl+0x73/0x9f print_report+0x25d/0x759 kasan_report+0xc0/0x120 __asan_load8+0x99/0x140 __list_add_valid+0x28/0x1a0 ext4_orphan_cleanup+0x564/0x9d0 [ext4] __ext4_fill_super+0x48e2/0x5300 [ext4] ext4_fill_super+0x19f/0x3a0 [ext4] get_tree_bdev+0x27b/0x450 ext4_get_tree+0x19/0x30 [ext4] vfs_get_tree+0x49/0x150 path_mount+0xaae/0x1350 do_mount+0xe2/0x110 __x64_sys_mount+0xf0/0x190 do_syscall_64+0x35/0x80 entry_SYSCALL_64_after_hwframe+0x63/0xcd </TASK> [...] ================================================================== Above issue may happen as follows: ------------------------------------- ext4_fill_super ext4_orphan_cleanup --- loop1: assume last_orphan is 12 --- list_add(&EXT4_I(inode)->i_orphan, &EXT4_SB(sb)->s_orphan) ext4_truncate --> return 0 ext4_inode_attach_jinode --> return -ENOMEM iput(inode) --> free inode<12> --- loop2: last_orphan is still 12 --- list_add(&EXT4_I(inode)->i_orphan, &EXT4_SB(sb)->s_orphan); // use inode<12> and trigger UAF To solve this issue, we need to propagate the return value of ext4_inode_attach_jinode() appropriately.
- Published
- Dec 9, 2025
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- 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
- 4.10affected
- 2c98eb5ea249767bbc11cf4e70e91d5b0458ed13 and later · before 7f801a1593cb957f73659732836b2dafbdfc7709affected · git
- 2c98eb5ea249767bbc11cf4e70e91d5b0458ed13 and later · before 026a4490b5381229a30f23d073b58e8e35ee6858affected · git
- 2c98eb5ea249767bbc11cf4e70e91d5b0458ed13 and later · before 7223d5e75f26352354ea2c0ccf8b579821b52adfaffected · git
- 2c98eb5ea249767bbc11cf4e70e91d5b0458ed13 and later · before cf0e0817b0f925b70d101d7014ea81b7094e1159affected · git
- 2c98eb5ea249767bbc11cf4e70e91d5b0458ed13 and later · before c2bdbd4c69308835d1b6f6ba74feeccbfe113478affected · git
- 2c98eb5ea249767bbc11cf4e70e91d5b0458ed13 and later · before 7908b8a541b1578cc61b4da7f19b604a931441daaffected · git
- 2c98eb5ea249767bbc11cf4e70e91d5b0458ed13 and later · before a71248b1accb2b42e4980afef4fa4a27fa0e36f5affected · git
- before 4.10not affected · semver
- 4.19.270 and later · up to and including 4.19.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | bpftool | before 4.18.0-553.104.1.el8_10 | 4.18.0-553.104.1.el8_10 |
| AlmaLinux:8 | kernel | before 4.18.0-553.104.1.el8_10 | 4.18.0-553.104.1.el8_10 |
| AlmaLinux:8 | kernel-abi-stablelists | before 4.18.0-553.104.1.el8_10 | 4.18.0-553.104.1.el8_10 |
| AlmaLinux:8 | kernel-core | before 4.18.0-553.104.1.el8_10 | 4.18.0-553.104.1.el8_10 |
| AlmaLinux:8 | kernel-cross-headers | before 4.18.0-553.104.1.el8_10 | 4.18.0-553.104.1.el8_10 |
| AlmaLinux:8 | kernel-debug | before 4.18.0-553.104.1.el8_10 | 4.18.0-553.104.1.el8_10 |
| AlmaLinux:8 | kernel-debug-core | before 4.18.0-553.104.1.el8_10 | 4.18.0-553.104.1.el8_10 |
| AlmaLinux:8 | kernel-debug-devel | before 4.18.0-553.104.1.el8_10 | 4.18.0-553.104.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules | before 4.18.0-553.104.1.el8_10 | 4.18.0-553.104.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules-extra | before 4.18.0-553.104.1.el8_10 | 4.18.0-553.104.1.el8_10 |
| AlmaLinux:8 | kernel-devel | before 4.18.0-553.104.1.el8_10 | 4.18.0-553.104.1.el8_10 |
| AlmaLinux:8 | kernel-doc | before 4.18.0-553.104.1.el8_10 | 4.18.0-553.104.1.el8_10 |
| AlmaLinux:8 | kernel-headers | before 4.18.0-553.104.1.el8_10 | 4.18.0-553.104.1.el8_10 |
| AlmaLinux:8 | kernel-modules | before 4.18.0-553.104.1.el8_10 | 4.18.0-553.104.1.el8_10 |
| AlmaLinux:8 | kernel-modules-extra | before 4.18.0-553.104.1.el8_10 | 4.18.0-553.104.1.el8_10 |
| AlmaLinux:8 | kernel-rt | before 4.18.0-553.104.1.rt7.445.el8_10 | 4.18.0-553.104.1.rt7.445.el8_10 |
| AlmaLinux:8 | kernel-rt-core | before 4.18.0-553.104.1.rt7.445.el8_10 | 4.18.0-553.104.1.rt7.445.el8_10 |
| AlmaLinux:8 | kernel-rt-debug | before 4.18.0-553.104.1.rt7.445.el8_10 | 4.18.0-553.104.1.rt7.445.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-core | before 4.18.0-553.104.1.rt7.445.el8_10 | 4.18.0-553.104.1.rt7.445.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-devel | before 4.18.0-553.104.1.rt7.445.el8_10 | 4.18.0-553.104.1.rt7.445.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules | before 4.18.0-553.104.1.rt7.445.el8_10 | 4.18.0-553.104.1.rt7.445.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules-extra | before 4.18.0-553.104.1.rt7.445.el8_10 | 4.18.0-553.104.1.rt7.445.el8_10 |
| AlmaLinux:8 | kernel-rt-devel | before 4.18.0-553.104.1.rt7.445.el8_10 | 4.18.0-553.104.1.rt7.445.el8_10 |
| AlmaLinux:8 | kernel-rt-modules | before 4.18.0-553.104.1.rt7.445.el8_10 | 4.18.0-553.104.1.rt7.445.el8_10 |
+96
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
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
- CVE-2026-72421ipv4: fib: Don't ignore error route in local/main tables.40Plan
- CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler40Plan
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 | 026a4490b5381229a30f23d073b58e8e35ee6858 | Vendor (CNA) |
| Linux Linux | 7223d5e75f26352354ea2c0ccf8b579821b52adf | Vendor (CNA) |
| Linux Linux | 7908b8a541b1578cc61b4da7f19b604a931441da | Vendor (CNA) |
| Linux Linux | 7f801a1593cb957f73659732836b2dafbdfc7709 | Vendor (CNA) |
| Linux Linux | a71248b1accb2b42e4980afef4fa4a27fa0e36f5 | Vendor (CNA) |
| Linux Linux | c2bdbd4c69308835d1b6f6ba74feeccbfe113478 | Vendor (CNA) |
| Linux Linux | cf0e0817b0f925b70d101d7014ea81b7094e1159 | Vendor (CNA) |
| almalinux:bpftool | 4.18.0-553.104.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel | 4.18.0-553.104.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-abi-stablelists | 4.18.0-553.104.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-core | 4.18.0-553.104.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-cross-headers | 4.18.0-553.104.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug | 4.18.0-553.104.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-core | 4.18.0-553.104.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-devel | 4.18.0-553.104.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-modules | 4.18.0-553.104.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-modules-extra | 4.18.0-553.104.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-devel | 4.18.0-553.104.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-doc | 4.18.0-553.104.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| debian:linux | 6.1.4-1 · Debian:12 | Package registry (OSV) |
| red hat:bpftool | 0:4.18.0-553.104.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:4.18.0-553.104.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel | 0:4.18.0-553.104.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-abi-stablelists | 0:4.18.0-553.104.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-core | 0:4.18.0-553.104.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug | 0:4.18.0-553.104.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug-core | 0:4.18.0-553.104.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:4.18.0-553.104.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:4.18.0-553.104.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug-modules | 0:4.18.0-553.104.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
+3
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
- Someone with local access to the system can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 (6 more)Show less
- git.kernel.org/stable/c/7223d5e75f26352354ea2c0ccf8b579821b52adf
- git.kernel.org/stable/c/7908b8a541b1578cc61b4da7f19b604a931441da
- git.kernel.org/stable/c/7f801a1593cb957f73659732836b2dafbdfc7709
- git.kernel.org/stable/c/a71248b1accb2b42e4980afef4fa4a27fa0e36f5
- git.kernel.org/stable/c/c2bdbd4c69308835d1b6f6ba74feeccbfe113478
- git.kernel.org/stable/c/cf0e0817b0f925b70d101d7014ea81b7094e1159
Vendor advisories and official records. Exploit/PoC links are deliberately left out.