CVE-2026-74602: ring-buffer: Initialise reader page order in rb_allocate_cpu_buffer()

Published Aug 22, 2026
·
Updated

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

ring-buffer: Initialise reader page order in rballocatecpubuffer()

In rballocatecpubuffer(), bpage->order was omitted, leaving it as 0. This is an issue for a ring-buffer with subbufs bigger than PAGESIZE if when freed: freebufferpage() relies on this value. Align the value with the actual allocation size (buffer::subbuforder).

Affected Software

1 affected component
Linux Linux kernel

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    In rb_allocate_cpu_buffer(), initialize reader page order (bpage->order) using buffer::subbuf_order instead of leaving it as 0, so that free_buffer_page() uses the correct allocation size.

    Linux kernel ring-buffer bpage->order = buffer::subbuf_order

Event History

Aug 22, 2026
CVE Published
via MITRE·03:31 PM
Data Sourced
via MITRE·03:31 PM
Description
Data Sourced
via NVD·04:16 PM
Description

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203