Cloudanix VulnDB

CVE-2025-38101

None

CVSS

—

EPSS

0.2%

Published

Jul 3, 2025

CISA due date

—

Cloudanix analysis

Schedule a fix SSVC: Track

A locking mistake in the Linux kernel could let certain operations interfere with each other and damage internal data structures used for tracing.

Exploitation
Local Privilege
Attacker needs
Local User
Complexity
Moderate
Impact
Data Tampering
Component
OS kernel
Class
Race Condition
Remediation
Upgrade
Effort
Medium
Patch risk
Low

What it actually does

Insufficient locking around error paths in ring_buffer_subbuf_order_set allows concurrent modifications to per-CPU ring buffer lists without the per-buffer mutex held, resulting in list corruption and related concurrency failures.

Why it matters to the business

Systems running affected Linux kernels may experience instability, crashes, or corrupted tracing data under concurrent ring-buffer reconfiguration, increasing operational risk and potential downtime for workloads relying on kernel tracing or performance monitoring.

How an attack unfolds

An attacker with local access triggers multiple concurrent invocations of ring_buffer_subbuf_order_set while forcing error conditions in the critical section; without the mutex held during error handling, list pointers become inconsistent, enabling further corruption or denial of service.

How to fix it

Update to a fixed kernel containing commit e09c0600beea469b3ebf974464e526a02d59ad62 or later; Chainguard images cass-operator-fips-no-pvc-delete and cass-operator-fips-no-pvc-delete-compat require version 1.24.0-r1 or newer.

How to confirm the fix worked

Verify the running kernel contains the referenced commit or is built from a version after the fix; inspect ring_buffer_subbuf_order_set for the enlarged mutex-protected critical section covering error handling.

Typical attack path

  1. Obtain local code execution or unprivileged access on the target system
  2. Identify or trigger ring buffer reconfiguration via subbuf order changes
  3. Race multiple threads or processes against the function to hit error paths without proper locking
  4. Observe or exploit resulting list corruption for denial of service or further kernel manipulation

How to detect it

Review kernel logs for list corruption warnings or oopses involving ring buffer structures around times of subbuf order changes; audit for unexpected concurrent calls to ring_buffer_subbuf_order_set in system call traces.

What your security team should do

  • Prioritize patching production kernels to the fixed commit or package versions listed
  • Monitor EPSS trend and re-evaluate if exploit maturity increases
  • Restrict unprivileged local access where ring-buffer reconfiguration interfaces are exposed

The record

In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Fix buffer locking in ring_buffer_subbuf_order_set() Enlarge the critical section in ring_buffer_subbuf_order_set() to ensure that error handling takes place with per-buffer mutex held, thus preventing list corruption and other concurrency-related issues.

Affected packages

Ecosystem Package Introduced Fixed
Debian:13 linux 0 No fix
Linux Kernel 6.8.0 6.12.34
openSUSE:Leap 16.0 dtb-aarch64 0 6.12.0-160000.6.1
openSUSE:Leap 16.0 kernel-64kb 0 6.12.0-160000.6.1
openSUSE:Leap 16.0 kernel-default 0 6.12.0-160000.6.1
openSUSE:Leap 16.0 kernel-default-base 0 6.12.0-160000.6.1.160000.2.4
openSUSE:Leap 16.0 kernel-docs 0 6.12.0-160000.6.1
openSUSE:Leap 16.0 kernel-kvmsmall 0 6.12.0-160000.6.1
openSUSE:Leap 16.0 kernel-obs-build 0 6.12.0-160000.6.1
openSUSE:Leap 16.0 kernel-obs-qa 0 6.12.0-160000.6.1
openSUSE:Leap 16.0 kernel-rt 0 6.12.0-160000.6.1
openSUSE:Leap 16.0 kernel-source 0 6.12.0-160000.6.1
openSUSE:Leap 16.0 kernel-syms 0 6.12.0-160000.6.1
openSUSE:Leap 16.0 kernel-zfcpdump 0 6.12.0-160000.6.1

Related vulnerabilities