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-99311: udf: fix return value for non-recorded-allocated extents in udf_map_block()
Date: Mon, 16 Nov 2026 11:00:00 +0100	[thread overview]
Message-ID: <2026111642-CVE-2026-99311-e887@gregkh> (raw)

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

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

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

udf: fix return value for non-recorded-allocated extents in udf_map_block()

When someone creates a corrupted UDF filesystem where symlink contains
other extent type than EXT_RECORDED_ALLOCATED, it can leads to a crash
like:

 Oops: general protection fault
 KASAN: maybe wild-memory-access
 RIP: 0010:page_get_link (fs/namei.c:6503)
 Call Trace:
  vfs_readlink (fs/namei.c:6419)
  do_readlinkat (fs/stat.c:583)
  __x64_sys_readlink (fs/stat.c:605 fs/stat.c:602 fs/stat.c:602)

This is because in this case udf_map_block() fails to convert return
value of inode_bmap() from 1 to 0. Returned '1' propagates through
udf_bread() all the way up to __page_get_link() where it ends up being
treated as a folio pointer with obvious results.

Move the reset to 0 line outside the if, so udf_map_block() returns either
0 or -errno, even if the extent type is not EXT_RECORDED_ALLOCATED.

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


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

	Issue introduced in 6.12 with commit c226964ec786f3797ed389a16392ce4357697d24 and fixed in 6.12.117 with commit 0d7f6c2b3c07fa239ebc169280eba9932cc56f46
	Issue introduced in 6.12 with commit c226964ec786f3797ed389a16392ce4357697d24 and fixed in 6.18.61 with commit df713b82b4b9671c16b52b60f3412c677719e2b8
	Issue introduced in 6.12 with commit c226964ec786f3797ed389a16392ce4357697d24 and fixed in 7.3.2 with commit f022984a4a1c18aa9c506790eb47da000dce95a7
	Issue introduced in 6.12 with commit c226964ec786f3797ed389a16392ce4357697d24 and fixed in 7.4-rc1 with commit 0f242ca0878896df30292f4922700a32e8fdd039
	Issue introduced in 6.6.59 with commit 493447dd8336607fce426f7879e581095f6c606e
	Issue introduced in 6.11.6 with commit b22d9a5698abf04341f8fbc30141e0673863c3a6

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-99311
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/udf/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/0d7f6c2b3c07fa239ebc169280eba9932cc56f46
	https://git.kernel.org/stable/c/df713b82b4b9671c16b52b60f3412c677719e2b8
	https://git.kernel.org/stable/c/f022984a4a1c18aa9c506790eb47da000dce95a7
	https://git.kernel.org/stable/c/0f242ca0878896df30292f4922700a32e8fdd039

                 reply	other threads:[~2026-11-16 10:00 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=2026111642-CVE-2026-99311-e887@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.