CVE-2026-89618: eventfs: Initialize ei->children and ei->list in init_ei()
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.17% (FIRST EPSS).
- Fixed version: Linux Linux 069729282fbecfaa8a54062266c338ed23f08005, 1704aaaf5d22bc765c168402350d191e24e245bc, 5333e18e6b425fcc39c7fea89e3949a2a98bc5e4.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 069729282fbecfaa8a54062266c338ed23f08005, 1704aaaf5d22bc765c168402350d191e24e245bc, 5333e18e6b425fcc39c7fea89e3949a2a98bc5e4 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: eventfs: Initialize ei->children and ei->list in init_ei() eventfs_create_dir() allocates the eventfs_inode and initializes it with init_ei(). But this does not initialize the eventfs_inode list_heads. If the eventfs_create_dir() fails due to memory pressure, it will call free_ei() before it initialized the lists, and that checks to make sure the eventfs_inode has no children. But because the list wasn't initialized, it will give a false warning. Fix it by moving the list initialization into init_ei(). [ Rewrote change log ]
- Published
- Sep 11, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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
- 6.7affected
- 35ee34c0f6d578c9d245438ca29bf2e7024a5a65 and later · before 069729282fbecfaa8a54062266c338ed23f08005affected · git
- 5790b1fb3d672d9a1fe3881a7181dfdbe741568f and later · before c480f8af173d5b19c6d9c4311df6bbe352face9eaffected · git
- 5790b1fb3d672d9a1fe3881a7181dfdbe741568f and later · before 5333e18e6b425fcc39c7fea89e3949a2a98bc5e4affected · git
- 5790b1fb3d672d9a1fe3881a7181dfdbe741568f and later · before 76e0f85f650738d768449dbccbc7c55d05f5b609affected · git
- 5790b1fb3d672d9a1fe3881a7181dfdbe741568f and later · before 1704aaaf5d22bc765c168402350d191e24e245bcaffected · git
- 6.6.18 and later · before 6.6.157affected · semver
- before 6.7not affected · semver
- 6.6.157 and later · up to and including 6.6.*not affected · semver
- 6.12.109 and later · up to and including 6.12.*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 |
|---|---|---|---|
| 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-89616Sep 11, 2026 · fs/ntfs3: fix info-leak on partial LZNT decompress in ni_read_frame()30Monitor
- ← EarlierCVE-2026-89617Sep 11, 2026 · fs/ntfs3: validate dirty page table on log replay31Monitor
- Later →CVE-2026-89619Sep 11, 2026 · HID: intel-thc-hid: intel-quickspi: bound GET_REPORT response to the caller buffer31Monitor
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 | 069729282fbecfaa8a54062266c338ed23f08005 | Vendor (CNA) |
| Linux Linux | 1704aaaf5d22bc765c168402350d191e24e245bc | Vendor (CNA) |
| Linux Linux | 5333e18e6b425fcc39c7fea89e3949a2a98bc5e4 | Vendor (CNA) |
| Linux Linux | 6.6.157 | Vendor (CNA) |
| Linux Linux | 76e0f85f650738d768449dbccbc7c55d05f5b609 | Vendor (CNA) |
| Linux Linux | c480f8af173d5b19c6d9c4311df6bbe352face9e | Vendor (CNA) |
| 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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1085 · Sep 14, 2026(Linux Kernel Güvenlik Bildirimi)
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.