From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-72244: gpu/buddy: bail out of try_harder when alignment cannot be honoured
Date: Sat, 15 Aug 2026 15:05:23 +0900 [thread overview]
Message-ID: <2026081551-CVE-2026-72244-983d@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
gpu/buddy: bail out of try_harder when alignment cannot be honoured
The try_harder contiguous fallback could return a range whose start
offset did not match the caller's min_block_size. When a candidate's
start is misaligned, realign it: free the misaligned run and reallocate
exactly @size at the next lower min_block_size boundary. This keeps the
returned size unchanged with no surplus to trim, and rejects the request
only when no aligned candidate fits.
v2: align misaligned candidates down to min_block_size instead of
bailing out, for both the RHS and LHS paths (Matthew).
The Linux kernel CVE team has assigned CVE-2026-72244 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.7 with commit 0a1844bf0b532d84324453374ad6845f64066c28 and fixed in 6.12.101 with commit 4289531106ee175a6eb45db7d4f2734d1dae9887
Issue introduced in 6.7 with commit 0a1844bf0b532d84324453374ad6845f64066c28 and fixed in 6.18.42 with commit 7185c5262435b93e5eeffa647008992256b9c51a
Issue introduced in 6.7 with commit 0a1844bf0b532d84324453374ad6845f64066c28 and fixed in 7.1.5 with commit 419d7d9306491f3e0e417cf794844c73cabee090
Issue introduced in 6.7 with commit 0a1844bf0b532d84324453374ad6845f64066c28 and fixed in 7.2-rc3 with commit 56bc6384314fb9ae98975fb2af8b143097ede3dc
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-72244
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:
drivers/gpu/buddy.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/4289531106ee175a6eb45db7d4f2734d1dae9887
https://git.kernel.org/stable/c/7185c5262435b93e5eeffa647008992256b9c51a
https://git.kernel.org/stable/c/419d7d9306491f3e0e417cf794844c73cabee090
https://git.kernel.org/stable/c/56bc6384314fb9ae98975fb2af8b143097ede3dc
reply other threads:[~2026-08-15 6:18 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=2026081551-CVE-2026-72244-983d@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.