Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Use current_context for safe per-CPU buffer swap The… (CVE-2026-74601)

0
Medium
Published: 08/22/2026 (08/22/2026, 18:30:26 UTC)
Source: GCVE Database

Description

A vulnerability in the Linux kernel's ring buffer implementation allowed a race condition during per-CPU buffer swaps. The committing counter used to check if a buffer was actively written to could temporarily drop to zero during a write operation, enabling an unsafe swap and inconsistent buffer state. This issue has been resolved by replacing the committing counter check with a current_context check that reliably indicates buffer busy state throughout the write operation.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 08/22/2026, 23:26:05 UTC

Technical Analysis

The Linux kernel's ring_buffer_swap_cpu() function previously relied on a per-CPU committing counter to determine if a buffer was actively being written to before swapping. However, a race condition existed where the committing counter could temporarily drop to zero during a single write operation, allowing the swap to proceed despite ongoing writes. This led to inconsistent buffer states and triggered warnings in rb_commit(). The fix replaces the committing counter check with current_context checks set at the entry of ring_buffer_lock_reserve(), which remain valid for the entire write operation, ensuring safe buffer swaps.

Potential Impact

This vulnerability could cause inconsistent buffer states in the Linux kernel ring buffer due to unsafe buffer swaps during concurrent writes. While no direct exploit or active attacks are known, the issue could lead to kernel warnings and potential instability related to ring buffer operations.

Mitigation Recommendations

A fix has been implemented in the Linux kernel to replace the committing counter check with current_context checks for safe buffer swaps. Users should apply the official kernel updates that include this fix once available. Patch status is not yet confirmed from the vendor advisory; check the Linux kernel security advisories for current remediation guidance.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
GHSA-j5v7-fqrf-q39x
Osv Schema Version
1.4.0
Aliases
["CVE-2026-74601"]
Ecosystems
[]
Database Specific Severity
null
Cvss Version
null

Threat ID: 6a8a27f3acd9273b499bc884

Added to database: 08/22/2026, 22:51:31 UTC

Last enriched: 08/22/2026, 23:26:05 UTC

Last updated: 08/23/2026, 00:10:01 UTC

Views: 4

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses