From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-74602: ring-buffer: Initialise reader page order in rb_allocate_cpu_buffer()
Date: Sat, 22 Aug 2026 17:31:26 +0200 [thread overview]
Message-ID: <2026082215-CVE-2026-74602-b084@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ring-buffer: Initialise reader page order in rb_allocate_cpu_buffer()
In rb_allocate_cpu_buffer(), bpage->order was omitted, leaving it as 0.
This is an issue for a ring-buffer with subbufs bigger than PAGE_SIZE if
when freed: free_buffer_page() relies on this value. Align the value
with the actual allocation size (buffer::subbuf_order).
The Linux kernel CVE team has assigned CVE-2026-74602 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.8 with commit f9b94daa542a8d2532f0930f01cd9aec2d19621b and fixed in 6.18.45 with commit 2e37f2bf111429fbfa4d985b12df3ba496ca70aa
Issue introduced in 6.8 with commit f9b94daa542a8d2532f0930f01cd9aec2d19621b and fixed in 7.1.9 with commit 3b3e0a6ee5bb3ac000f135beef26b2b7ed1a771a
Issue introduced in 6.8 with commit f9b94daa542a8d2532f0930f01cd9aec2d19621b and fixed in 7.2 with commit 6d014e44b68ddd43f71288d2a4dbb1a259869149
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-74602
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:
kernel/trace/ring_buffer.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/2e37f2bf111429fbfa4d985b12df3ba496ca70aa
https://git.kernel.org/stable/c/3b3e0a6ee5bb3ac000f135beef26b2b7ed1a771a
https://git.kernel.org/stable/c/6d014e44b68ddd43f71288d2a4dbb1a259869149
reply other threads:[~2026-08-22 15:34 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=2026082215-CVE-2026-74602-b084@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.