All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-99418: ovl: do not copy up an xattr value that was never read
Date: Thu, 19 Nov 2026 15:25:16 +0100	[thread overview]
Message-ID: <2026111900-CVE-2026-99418-131d@gregkh> (raw)

From: Greg Kroah-Hartman <gregkh@kernel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

ovl: do not copy up an xattr value that was never read

Copy-up stores uninitialized kernel memory in an xattr of the upper
file, where the user can read it.

ovl_copy_xattr() may only pass bytes to ovl_do_setxattr() that
ovl_do_getxattr() has read. When the read fails with -ERANGE the
function asks for the size again, and if the new size fits the buffer
it stores the buffer although nothing was read into it. The buffer
comes from kvmalloc(), or it still holds the value of the previous
xattr.

A FUSE lower layer that answers every sized GETXATTR with -ERANGE made
copy-up store 4096 bytes that the server never sent, with a kernel
pointer in them, as an xattr of the upper file.

Fix this by failing the copy-up with -EIO when the size that follows
-ERANGE fits the buffer.

The Linux kernel CVE team has assigned CVE-2026-99418 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 4.5 with commit e4ad29fa0d224d05e08b2858e65f112fd8edd4fe and fixed in 6.12.117 with commit 3b1f5a4652539014f0162944f1a5f71ee520188a
	Issue introduced in 4.5 with commit e4ad29fa0d224d05e08b2858e65f112fd8edd4fe and fixed in 6.18.61 with commit 628260a7204314ab5f1cd93bddb1721cc0226b38
	Issue introduced in 4.5 with commit e4ad29fa0d224d05e08b2858e65f112fd8edd4fe and fixed in 7.3.2 with commit e35c3b1dc69b8c8efe3d751fafb9b50a85f0e2f7
	Issue introduced in 4.5 with commit e4ad29fa0d224d05e08b2858e65f112fd8edd4fe and fixed in 7.4-rc1 with commit 755b5c5c9277be251a51623d6065abab948c61bc
	Issue introduced in 3.18.27 with commit f641fdbd8ca737df49e96d9d58206fb0a9d82512
	Issue introduced in 4.1.18 with commit 3c0a63d74b4a12a0a98cd85b195031d8d4b109a6
	Issue introduced in 4.4.3 with commit fa932190a5f332e1936ab0223c7c5d79b5596a9c

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-99418
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/overlayfs/copy_up.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/3b1f5a4652539014f0162944f1a5f71ee520188a
	https://git.kernel.org/stable/c/628260a7204314ab5f1cd93bddb1721cc0226b38
	https://git.kernel.org/stable/c/e35c3b1dc69b8c8efe3d751fafb9b50a85f0e2f7
	https://git.kernel.org/stable/c/755b5c5c9277be251a51623d6065abab948c61bc

                 reply	other threads:[~2026-11-19 14:45 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=2026111900-CVE-2026-99418-131d@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.