From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-89618: eventfs: Initialize ei->children and ei->list in init_ei()
Date: Fri, 11 Sep 2026 21:45:07 +0200 [thread overview]
Message-ID: <2026091136-CVE-2026-89618-cf18@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
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 ]
The Linux kernel CVE team has assigned CVE-2026-89618 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.7 with commit 5790b1fb3d672d9a1fe3881a7181dfdbe741568f and fixed in 6.12.109 with commit c480f8af173d5b19c6d9c4311df6bbe352face9e
Issue introduced in 6.7 with commit 5790b1fb3d672d9a1fe3881a7181dfdbe741568f and fixed in 6.18.50 with commit 5333e18e6b425fcc39c7fea89e3949a2a98bc5e4
Issue introduced in 6.7 with commit 5790b1fb3d672d9a1fe3881a7181dfdbe741568f and fixed in 7.2.4 with commit 76e0f85f650738d768449dbccbc7c55d05f5b609
Issue introduced in 6.7 with commit 5790b1fb3d672d9a1fe3881a7181dfdbe741568f and fixed in 7.3-rc1 with commit 1704aaaf5d22bc765c168402350d191e24e245bc
Issue introduced in 6.6.18 with commit 35ee34c0f6d578c9d245438ca29bf2e7024a5a65
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-89618
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
fs/tracefs/event_inode.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/c480f8af173d5b19c6d9c4311df6bbe352face9e
https://git.kernel.org/stable/c/5333e18e6b425fcc39c7fea89e3949a2a98bc5e4
https://git.kernel.org/stable/c/76e0f85f650738d768449dbccbc7c55d05f5b609
https://git.kernel.org/stable/c/1704aaaf5d22bc765c168402350d191e24e245bc
reply other threads:[~2026-09-11 19:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026091136-CVE-2026-89618-cf18@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox