Bug 2500854 (CVE-2026-15813) - CVE-2026-15813 kronosnet: kronosnet: memory corruption and out-of-bounds access via malformed network packet defragmentation
Summary: CVE-2026-15813 kronosnet: kronosnet: memory corruption and out-of-bounds acce...
Keywords:
Status: NEW
Alias: CVE-2026-15813
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2500864
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-07-15 11:01 UTC by OSIDB Bzimport
Modified: 2026-07-20 07:32 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-07-15 11:01:11 UTC
Vulnerability Reference: A flaw was found in kronosnet's network packet processing layer, where improper validation during fragment reassembly can trigger memory corruption or out-of-bounds memory access.

Component / Vulnerable Part: kronosnet -> Core network packet de-fragmentation engine (https://github.com/kronosnet/kronosnet/).

Technical Analysis & Root Cause: When kronosnet reassembles fragmented network payloads, it tracks individual chunks using sequence numbers. The defragmentation subsystem lacks rigid boundary and validation logic when ordering these incoming fragments. A network adversary can craft and inject fragments with overlapping, out-of-order, or invalid sequence numbers. When the parser tries to reassemble the payload using these deceptive offsets, it writes data beyond the limits of the allocated reassembly buffer, leading to memory corruption or an out-of-bounds memory access condition.

Impact: A remote attacker can weaponize this structural flaw to deliberately destabilize or crash the kronosnet process (Denial of Service). Depending on the heap layout and data overwriting context, it could potentially be leveraged for arbitrary code execution within the daemon context.


Note You need to log in before you can comment on or make changes to this bug.