From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-89605: ecryptfs: release message context on send failure
Date: Fri, 11 Sep 2026 21:44:54 +0200 [thread overview]
Message-ID: <2026091133-CVE-2026-89605-fa13@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ecryptfs: release message context on send failure
ecryptfs_send_message_locked() moves a message context from the free
list to the allocated list before sending the request to the userspace
daemon.
If ecryptfs_send_miscdev() fails, the context is left on the
allocated list and cannot be reused. Move it back to the free list on
failure and clear the caller's pointer.
The Linux kernel CVE team has assigned CVE-2026-89605 to this issue.
Affected and fixed versions
===========================
Issue introduced in 2.6.26 with commit f66e883eb6186bc43a79581b67aff7d1a69d0ff1 and fixed in 6.12.109 with commit 47ce611cb13f0eefa550d5434c1afcd4217bfc3e
Issue introduced in 2.6.26 with commit f66e883eb6186bc43a79581b67aff7d1a69d0ff1 and fixed in 6.18.50 with commit 9319706316a8e79f374627554386d575a84b637f
Issue introduced in 2.6.26 with commit f66e883eb6186bc43a79581b67aff7d1a69d0ff1 and fixed in 7.2.4 with commit 654b7e79443f5ea90849f5c1cf70c0d94bd5b10e
Issue introduced in 2.6.26 with commit f66e883eb6186bc43a79581b67aff7d1a69d0ff1 and fixed in 7.3-rc1 with commit 219644a3ad5518217b2d62cad6d2c36a2308c949
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-89605
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/ecryptfs/messaging.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/47ce611cb13f0eefa550d5434c1afcd4217bfc3e
https://git.kernel.org/stable/c/9319706316a8e79f374627554386d575a84b637f
https://git.kernel.org/stable/c/654b7e79443f5ea90849f5c1cf70c0d94bd5b10e
https://git.kernel.org/stable/c/219644a3ad5518217b2d62cad6d2c36a2308c949
reply other threads:[~2026-09-11 19:58 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=2026091133-CVE-2026-89605-fa13@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