CVE-2026-74601 Affecting ocfs2-kmp-default package, versions <6.4.0-150700.53.84.1


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.14% (3rd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-SLES157-OCFS2KMPDEFAULT-21166744
  • published17 Oct 2026
  • disclosed16 Oct 2026

Introduced: 16 Oct 2026

NewCVE-2026-74601  (opens in a new tab)

How to fix?

Upgrade SLES:15.7 ocfs2-kmp-default to version 6.4.0-150700.53.84.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream ocfs2-kmp-default package and not the ocfs2-kmp-default package as distributed by SLES. See How to fix? for SLES:15.7 relevant fixed versions and status.

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

ring-buffer: Use current_context for safe per-CPU buffer swap

The ring_buffer_swap_cpu() function currently checks the per-CPU committing counter to determine if a buffer is actively being written to before performing the swap. However, there exists a race window where this check can be bypassed:

ring_buffer_lock_reserve
    cpu_buffer = buffer-&gt;buffers[cpu];       // cpu_buffer_a
    rb_reserve_next_event
        rb_start_commit // inc committing
        if (unlikely(READ_ONCE(cpu_buffer-&gt;buffer) != buffer)) {...}
        __rb_reserve_next
            rb_move_tail
                rb_end_commit(cpu_buffer);   // dec committing =&gt; 0
                /* interrupt hits here, successfully swaps! */
                local_inc(&amp;cpu_buffer-&gt;committing);

ring_buffer_unlock_commit cpu_buffer = buffer-&gt;buffers[cpu]; // cpu_buffer_b rb_commit rb_end_commit RB_WARN_ON(cpu_buffer, !local_read(&amp;cpu_buffer-&gt;committing)) // triggers warning

The committing counter can temporarily drop to 0 during a single write operation (within rb_move_tail), creating a window where swap can succeed even though the write is still in progress. This leads to inconsistent buffer state and triggers the RB_WARN_ON in rb_commit().

Replace the committing counter check with current_context checks, which are set at the entry of ring_buffer_lock_reserve() and remain valid throughout the entire write operation, providing a reliable indicator of buffer busy state during swap.

CVSS Base Scores

version 3.1