libcrypt-sysrandom-xs-perl: Crypt::SysRandom::XS versions before 0.010 for Perl is vulnerable to a heap buffer overflow in the XS function random...
CVE-2026-2597 is fixed in 5 products on 1 platform, first by DEBIAN-CVE-2026-2597, released February 27, 2026. It is not reported as exploited. Patch Radar priority: High.
Crypt::SysRandom::XS versions before 0.010 for Perl is vulnerable to a heap buffer overflow in the XS function random_bytes(). The function does not validate that the length parameter is non-negative. If a negative value (e.g. -1) is supplied, the expression length + 1u causes an integer wraparound, resulting in a zero-byte allocation. The subsequent call to chosen random function (e.g. getrandom) passes the original negative value, which is implicitly converted to a large unsigned value (typically SIZE_MAX). This can result in writes beyond the allocated buffer, leading to heap memory corruption and application crash (denial of service). In common usage, the length argument is typically hardcoded by the caller, which reduces the likelihood of attacker-controlled exploitation. Applications that pass untrusted input to this parameter may be affected.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| libcrypt-sysrandom-xs-perl · Debian 14 | 0.011-1 | DEBIAN-CVE-2026-2597 | Feb 27, 2026 |
| perl-Crypt-SysRandom-XS · Fedora 43 | 0.011-1.fc43 | FEDORA-2026-7B9874A01F | Mar 2, 2026 |
| perl-Crypt-SysRandom-XS-debuginfo · Fedora 43 | 0.011-1.fc43 | FEDORA-2026-7B9874A01F | Mar 2, 2026 |
| perl-Crypt-SysRandom-XS-debugsource · Fedora 43 | 0.011-1.fc43 | FEDORA-2026-7B9874A01F | Mar 2, 2026 |
| perl-Crypt-SysRandom-XS-tests · Fedora 43 | 0.011-1.fc43 | FEDORA-2026-7B9874A01F | Mar 2, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.