In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Use current_context for safe per-CPU buffer swap The ring

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:

 1ring_buffer_lock_reserve
 2    cpu_buffer = buffer->buffers[cpu];       // cpu_buffer_a
 3    rb_reserve_next_event
 4        rb_start_commit // inc committing
 5        if (unlikely(READ_ONCE(cpu_buffer->buffer) != buffer)) {...}
 6        __rb_reserve_next
 7            rb_move_tail
 8                rb_end_commit(cpu_buffer);   // dec committing => 0
 9                /* interrupt hits here, successfully swaps! */
10                local_inc(&cpu_buffer->committing);
11 
12ring_buffer_unlock_commit
13    cpu_buffer = buffer->buffers[cpu];      // cpu_buffer_b
14    rb_commit
15        rb_end_commit
16        RB_WARN_ON(cpu_buffer, !local_read(&cpu_buffer->committing))
17                                            // 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.