[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025041628-CVE-2025-22122-c2d1@gregkh>
Date: Wed, 16 Apr 2025 16:13:33 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2025-22122: block: fix adding folio to bio
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
block: fix adding folio to bio
>4GB folio is possible on some ARCHs, such as aarch64, 16GB hugepage
is supported, then 'offset' of folio can't be held in 'unsigned int',
cause warning in bio_add_folio_nofail() and IO failure.
Fix it by adjusting 'page' & trimming 'offset' so that `->bi_offset` won't
be overflow, and folio can be added to bio successfully.
The Linux kernel CVE team has assigned CVE-2025-22122 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.12 with commit ed9832bc08db29874600eb066b74918fe6fc2060 and fixed in 6.14.2 with commit b96e0af1b1c99cb7e6188b6fa4963a4e47beb01e
Issue introduced in 6.12 with commit ed9832bc08db29874600eb066b74918fe6fc2060 and fixed in 6.15-rc1 with commit 26064d3e2b4d9a14df1072980e558c636fb023ea
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-2025-22122
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:
block/bio.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/b96e0af1b1c99cb7e6188b6fa4963a4e47beb01e
https://git.kernel.org/stable/c/26064d3e2b4d9a14df1072980e558c636fb023ea
Powered by blists - more mailing lists