LiveActive security incident?Get immediate response
CVE Record

CVE-2025-21777: ring-buffer: Validate the persistent meta data subbuf array

In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Validate the persistent meta data subbuf array The meta data for a mapped ring buffer contains an array of indexes of all the subbuffers. The first entry is the reader page, and the rest of the entries lay out the order of the subbuffers in how the ring buffer link list is to be created. The validator currently makes sure that all the entries are within the range of 0 and nr_subbufs. But it does not check if there are any duplicates. While working on the ring buffer, I corrupted this array, where I added duplicates. The validator did not catch it and created the ring buffer link list on top of it. Luckily, the corruption was only that the reader page was also in the writer path and only presented corrupted data but did not crash the kernel. But if there were duplicates in the writer side, then it could corrupt the ring buffer link list and cause a crash. Create a bitmask array with the size of the number of subbuffers. Then clear it. When walking through the subbuf array checking to see if the entries are within the range, test if its bit is already set in the subbuf_mask. If it is, then there is duplicates and fail the validation. If not, set the corresponding bit and continue.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel ring-buffer validation flaw. Corrupted persistent ring-buffer metadata with duplicate subbuffer entries may be accepted, leading to corrupted trace data and possibly a kernel crash. The source bundle does not show active exploitation, CVSS, or a complete attack path.

Executive priority

Treat as a standard kernel maintenance item unless critical Linux hosts run affected kernels without vendor fixes. Business risk is mainly availability from possible kernel crash, but exploitability is not established in the provided evidence.

Technical view

The validator checks subbuffer indexes are in range but did not reject duplicates in the persistent metadata subbuffer array. Duplicate writer-side entries could corrupt the ring-buffer linked list and crash the kernel. The fix adds duplicate detection with a bitmask during validation.

Likely exposure

Exposure is limited to Linux systems running affected kernel builds that include the vulnerable ring-buffer metadata handling. The bundle lists Linux kernel version records around 6.12, 6.12.16, 6.13.4, and 6.14, but exact distro exposure requires vendor backport verification.

Exploitation context

KEV is false and the provided sources do not report exploitation in the wild. The description is based on corrupted metadata observed during ring-buffer work. The bundle does not establish whether an unprivileged, remote, or containerized attacker can trigger it.

Researcher notes

The key gap is triggerability. Sources describe malformed persistent ring-buffer metadata and potential linked-list corruption, but do not define attacker prerequisites, privilege level, or reachable interfaces. Validate patch presence before making exposure claims.

Mitigation direction

  • Update to a vendor-supported Linux kernel containing the referenced stable fixes.
  • Check distribution advisories for CVE-2025-21777 backport status.
  • Prioritize systems where kernel crashes would disrupt critical workloads.
  • Avoid relying on upstream version numbers alone; vendors may backport fixes.

Validation and detection

  • Inventory Linux kernel versions across servers, containers hosts, and appliances.
  • Compare installed kernels against vendor advisories for CVE-2025-21777.
  • Confirm whether the referenced stable commits are present in custom kernels.
  • Review crash or tracing anomalies only as supporting evidence, not proof of exploitation.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-21777 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxc76883f18e59b762247ee91d3e4224231711854e, c76883f18e59b762247ee91d3e4224231711854e, c76883f18e59b762247ee91d3e4224231711854eunaffected
LinuxLinux6.12, 0, 6.12.16, 6.13.4, 6.14affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.