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-99574: f2fs: bound the SIT/NAT bitmaps by the checkpoint pack
Date: Fri, 20 Nov 2026 06:49:20 +0100	[thread overview]
Message-ID: <2026112016-CVE-2026-99574-3e18@gregkh> (raw)

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

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

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

f2fs: bound the SIT/NAT bitmaps by the checkpoint pack

sit_ver_bitmap_bytesize and nat_ver_bitmap_bytesize are used as memcpy
lengths into and out of sbi->ckpt, which is sized from cp_payload alone,
and nothing compares either length against that allocation.

sanity_check_ckpt() has checked these two fields since c77ec61ca0a4, which
added them after a crafted image overran build_sit_info(). That check ties
each length to a segment count; it never compares either against the
allocation, which is the half this adds.

Mounting over-reads in build_sit_info() and build_node_manager(), and the
first checkpoint writes the same lengths back through the same pointers,
so the over-read's contents reach the on-disk checkpoint. An unmount is
enough; the filesystem does not have to be used.

Bound both ends the way __bitmap_ptr() lays them out. The three branches
differ, so a single sum of the two lengths would still admit a small
overflow when cp_payload is non-zero.

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


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

	Issue introduced in 3.8 with commit 39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 and fixed in 6.12.118 with commit ddb9848fd6b2f4e9ed5ef78b20c9720c65a29df5
	Issue introduced in 3.8 with commit 39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 and fixed in 6.18.64 with commit 9b08fc2d092171af388f83030d54488b87453155
	Issue introduced in 3.8 with commit 39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 and fixed in 7.3.5 with commit 7f88cd38394a16c326073c8813e7f1f1445bf3ba
	Issue introduced in 3.8 with commit 39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 and fixed in 7.4-rc1 with commit 080833a32fd5dc10b3acf2fa9af9b3213e6cb617

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-99574
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/f2fs/super.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/ddb9848fd6b2f4e9ed5ef78b20c9720c65a29df5
	https://git.kernel.org/stable/c/9b08fc2d092171af388f83030d54488b87453155
	https://git.kernel.org/stable/c/7f88cd38394a16c326073c8813e7f1f1445bf3ba
	https://git.kernel.org/stable/c/080833a32fd5dc10b3acf2fa9af9b3213e6cb617

                 reply	other threads:[~2026-11-20  5:53 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=2026112016-CVE-2026-99574-3e18@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.