Improper Control of a Resource Through its Lifetime The advisory has been revoked - it doesn't affect any version of package rv (opens in a new tab)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-CENTOS10-RV-20908214
- published14 Oct 2026
- disclosed17 Sept 2026
Introduced: 17 Sep 2026
CVE-2026-90260 (opens in a new tab)Amendment
The Centos security team deemed this advisory irrelevant for Centos:10.
NVD Description
Note: Versions mentioned in the description apply only to the upstream rv package and not the rv package as distributed by Centos.
In the Linux kernel, the following vulnerability has been resolved:
btrfs: zoned: don't clobber the extent buffer when zeroing it out
On a zoned filesystem a freed-but-still-dirty tree block is written out as zeros (EXTENT_BUFFER_ZONED_ZEROOUT) only to keep the zone write pointer advancing. btree_csum_one_bio() implemented this by memzeroing the extent buffer's own folios before submission.
That destroys the in-memory buffer while it may still be referenced. In particular btrfs_free_tree_block() can run on it afterwards and reads the header to add a delayed reference; once the header has been zeroed it frees bytenr 0 and corrupts the extent tree (the btrfs_header_bytenr(buf) != 0 ASSERT in btrfs_free_tree_block(), or an "unable to find ref" abort). It is flaky and reproduces under fsstress, e.g. generic/461 and generic/013.
Write the zeros to disk from the shared zero page instead and leave the extent buffer content untouched, so any later reference - including the delayed reference from btrfs_free_tree_block() - still sees a valid header. end_bbio_meta_write() now clears writeback on the buffer's own folios, as the bio no longer carries them.
References
- https://bugzilla.redhat.com/show_bug.cgi?id=2536776
- https://access.redhat.com/security/cve/CVE-2026-90260
- https://git.kernel.org/stable/c/92484ad014f2e2b0e0e7bbc1610951e978cf557c
- https://git.kernel.org/stable/c/98e3747587f9f87f010d8d7e55786216249a94af
- https://git.kernel.org/stable/c/db4b9eefc8ee0bcaeee4d5e6a7313905f6a2fe7c
- https://git.kernel.org/stable/c/efa5084d08030aa557fdefa3e4a73b2501b7d207