CVE-2025-34457 is a stack-based buffer overflow vulnerability identified in the Dire Wolf software, a popular open-source software soundcard AX.25 packet modem/TNC and APRS encoder/decoder used primarily in amateur radio communications. The vulnerability resides in the kiss_rec_byte() function within src/kiss_frame.c. When processing KISS frames that reach the maximum allowed frame length (MAX_KISS_LEN), the function appends a terminating FEND byte without reserving sufficient space in the stack buffer. This results in an out-of-bounds write to the stack, followed by an out-of-bounds read during the subsequent call to kiss_unwrap(). The consequence is stack memory corruption, which can cause the application to crash or behave unpredictably. The flaw can be triggered remotely by sending crafted KISS frames, requiring no authentication or user interaction, making it a network-exploitable denial-of-service vulnerability. Although no exploits are currently known in the wild, the CVSS 4.0 base score of 8.7 reflects the high impact on availability and ease of exploitation. The vulnerability affects all Dire Wolf versions up to 1.8 prior to commit 694c954. No official patches are linked yet, so users must monitor vendor updates or apply code fixes manually. The vulnerability is classified under CWE-121 (stack-based buffer overflow), a common and dangerous software weakness.

The primary impact of CVE-2025-34457 is denial-of-service (DoS) through application crashes or memory corruption in Dire Wolf instances processing maliciously crafted KISS frames. This can disrupt amateur radio digital communications, APRS tracking, and related services relying on Dire Wolf, potentially affecting emergency communication channels or hobbyist networks. Since the vulnerability is remotely exploitable without authentication, attackers can cause widespread disruption with minimal effort. Confidentiality and integrity impacts are minimal as the vulnerability does not directly enable code execution or data leakage. However, the loss of availability can degrade operational capabilities for organizations and individuals dependent on Dire Wolf. The lack of known exploits reduces immediate risk but does not eliminate the threat, especially as proof-of-concept exploits may emerge. The vulnerability could be leveraged in targeted attacks against critical amateur radio infrastructure or during emergency events where communication reliability is vital.

1. Immediately update Dire Wolf to versions including the fix for commit 694c954 or later once available. 2. If patches are not yet released, apply manual code review and fixes to the kiss_rec_byte() function to ensure sufficient buffer space is reserved before appending the terminating FEND byte. 3. Implement network-level filtering to block or rate-limit suspicious KISS frames, especially those approaching the maximum allowed frame length, to reduce exposure to crafted packets. 4. Monitor network traffic for anomalous KISS frame sizes or malformed packets indicative of exploitation attempts. 5. Deploy application-level monitoring and automated restarts to quickly recover from crashes caused by exploitation attempts. 6. Engage with the Dire Wolf developer community to track patch releases and share mitigation strategies. 7. For critical deployments, consider isolating Dire Wolf instances within segmented networks to limit attack surface. 8. Educate users and operators about the vulnerability and the importance of timely updates.