In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix ACKALL packet handling rxrpc_input_ackall() accepts ACKALL packets… (CVE-2026-74430)
A vulnerability in the Linux kernel's rxrpc subsystem was resolved that involved improper handling of ACKALL packets. The function rxrpc_input_ackall() accepted ACKALL packets without verifying if the call state legitimately had outstanding transmit buffers. This could lead to a null-pointer dereference when a forged ACKALL packet triggers rxrpc_rotate_tx_window() with a NULL tx_queue. The fix introduced new call states to better track transmission status and refined the ACKALL packet handling to ignore packets received in inappropriate states.
AI Analysis
Technical Summary
The Linux kernel's rxrpc_input_ackall() function did not properly check the call state before accepting ACKALL packets, allowing a forged ACKALL to reach a new service call in RXRPC_CALL_SERVER_RECV_REQUEST state before any reply packets were queued. In this state, call->tx_top is zero and call->tx_queue is NULL, causing rxrpc_rotate_tx_window() to dereference a NULL pointer, resulting in a kernel null-pointer dereference. The patch added two new call states (RXRPC_CALL_CLIENT_PRE_SEND and RXRPC_CALL_CLIENT_AWAIT_ACK) to track transmission progress more accurately, adjusted the ACKALL handler to check for appropriate call states including AWAIT_ACK, and changed the handler to use call->tx_transmitted instead of call->tx_top for sequence tracking. These changes prevent processing ACKALL packets in invalid states and avoid the null-pointer dereference.
Potential Impact
This vulnerability can cause a kernel null-pointer dereference leading to a denial of service (system crash or kernel panic) if a forged ACKALL packet is processed in an invalid call state. There is no indication of privilege escalation or information disclosure. No known exploits are reported in the wild.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this issue by improving call state tracking and ACKALL packet validation. Users should update to the fixed kernel version once available. Patch status is not yet confirmed from the vendor advisory; check the official Linux kernel security advisories or distribution updates for the specific patch and remediation guidance.
In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix ACKALL packet handling rxrpc_input_ackall() accepts ACKALL packets… (CVE-2026-74430)
Description
A vulnerability in the Linux kernel's rxrpc subsystem was resolved that involved improper handling of ACKALL packets. The function rxrpc_input_ackall() accepted ACKALL packets without verifying if the call state legitimately had outstanding transmit buffers. This could lead to a null-pointer dereference when a forged ACKALL packet triggers rxrpc_rotate_tx_window() with a NULL tx_queue. The fix introduced new call states to better track transmission status and refined the ACKALL packet handling to ignore packets received in inappropriate states.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's rxrpc_input_ackall() function did not properly check the call state before accepting ACKALL packets, allowing a forged ACKALL to reach a new service call in RXRPC_CALL_SERVER_RECV_REQUEST state before any reply packets were queued. In this state, call->tx_top is zero and call->tx_queue is NULL, causing rxrpc_rotate_tx_window() to dereference a NULL pointer, resulting in a kernel null-pointer dereference. The patch added two new call states (RXRPC_CALL_CLIENT_PRE_SEND and RXRPC_CALL_CLIENT_AWAIT_ACK) to track transmission progress more accurately, adjusted the ACKALL handler to check for appropriate call states including AWAIT_ACK, and changed the handler to use call->tx_transmitted instead of call->tx_top for sequence tracking. These changes prevent processing ACKALL packets in invalid states and avoid the null-pointer dereference.
Potential Impact
This vulnerability can cause a kernel null-pointer dereference leading to a denial of service (system crash or kernel panic) if a forged ACKALL packet is processed in an invalid call state. There is no indication of privilege escalation or information disclosure. No known exploits are reported in the wild.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this issue by improving call state tracking and ACKALL packet validation. Users should update to the fixed kernel version once available. Patch status is not yet confirmed from the vendor advisory; check the official Linux kernel security advisories or distribution updates for the specific patch and remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-px3f-ghhp-7f3w
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-74430"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a808b67bf8831d5394f5066
Added to database: 08/15/2026, 15:53:11 UTC
Last enriched: 08/15/2026, 15:57:13 UTC
Last updated: 08/15/2026, 16:00:49 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.