CVE-2025-21777
published 2025-02-27CVE-2025-21777: 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…
PriorityP422medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.20%
10.2th percentile
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.
Affected
10 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.12.16-1 (forky) | linux 6.12.16-1 (forky) |
| linux | linux | — | — |
| linux | linux | >= c76883f18e59b762247ee91d3e4224231711854e < 3ec743d558f111d8999aea24577ba66c65ee2eeb | 3ec743d558f111d8999aea24577ba66c65ee2eeb |
| linux | linux | >= c76883f18e59b762247ee91d3e4224231711854e < 0d547a6f5e8fad26ebc12f501d7d19fccdbad6bf | 0d547a6f5e8fad26ebc12f501d7d19fccdbad6bf |
| linux | linux | >= c76883f18e59b762247ee91d3e4224231711854e < f5b95f1fa2ef3a03f49eeec658ba97e721412b32 | f5b95f1fa2ef3a03f49eeec658ba97e721412b32 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 6.12.16-1 | 6.12.16-1 |
| linux | linux_kernel | >= 0 < 6.12.16-1 | 6.12.16-1 |
| linux | linux_kernel | >= 6.12 < 6.12.16 | 6.12.16 |
| linux | linux_kernel | >= 6.13 < 6.13.4 | 6.13.4 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5LOW
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
CVE-2025-21777: In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Validate the persistent meta data subbuf array The meta data for a ma
osv·2025-02-27·CVSS 5.5
CVE-2025-21777 [MEDIUM] CVE-2025-21777: In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Validate the persistent meta data subbuf array The meta data for a ma
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 dat
GHSA
GHSA-g8qj-5wmw-7w59: In the Linux kernel, the following vulnerability has been resolved:
ring-buffer: Validate the persistent meta data subbuf array
The meta data for a
ghsa_unreviewed·2025-02-27
CVE-2025-21777 [MEDIUM] GHSA-g8qj-5wmw-7w59: In the Linux kernel, the following vulnerability has been resolved:
ring-buffer: Validate the persistent meta data subbuf array
The meta data for a
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
Red Hat
kernel: ring-buffer: Validate the persistent meta data subbuf array
vendor_redhat·2025-02-27·CVSS 5.5
CVE-2025-21777 [MEDIUM] CWE-694 kernel: ring-buffer: Validate the persistent meta data subbuf array
kernel: 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 rea
Debian
CVE-2025-21777: linux - In the Linux kernel, the following vulnerability has been resolved: ring-buffer...
vendor_debian·2025·CVSS 5.5
CVE-2025-21777 [MEDIUM] CVE-2025-21777: linux - In the Linux kernel, the following vulnerability has been resolved: ring-buffer...
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 dat
No detection rules found.
No public exploits indexed.
2025-02-27
Published