PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-31662 Linux CVE debrief

A vulnerability in the Linux kernel's TIPC (Transparent Inter-Process Communication) module has been identified, which could lead to a denial-of-service (DoS) condition. The issue arises from the improper handling of duplicate or stale acknowledgments (ACKs) in the GRP_ACK_MSG handler, causing an underflow in the bc_ackers counter. This underflow can result in incorrect congestion reporting and potentially block group broadcasts on the affected socket until the group is recreated.

Vendor
Linux
Product
Unknown
CVSS
HIGH 7.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-04-24
Original CVE updated
2026-10-19
Advisory published
2026-04-24
Advisory updated
2026-10-19

Who should care

Linux kernel developers and maintainers, Linux distribution vendors, and users of Linux-based systems that utilize TIPC for inter-process communication. System administrators and security teams responsible for monitoring and patching Linux systems should assess exposure and prioritize remediation.

Why it matters

The vulnerability in the Linux kernel's TIPC module can lead to a DoS condition and incorrect congestion reporting, affecting system availability and stability. Linux kernel developers, maintainers, and users should assess exposure and prioritize remediation.

  • Denial-of-service (DoS) condition due to blocked group broadcasts
  • Incorrect congestion reporting
  • Potential system instability or unavailability

Technical summary

The GRP_ACK_MSG handler in tipc_group_proto_rcv() decrements bc_ackers on every inbound group ACK, even when the same member has already acknowledged the current broadcast round. Because bc_ackers is a u16, a duplicate ACK received after the last legitimate ACK wraps the counter to 65535. Once wrapped, tipc_group_bc_cong() keeps reporting congestion and later group broadcasts on the affected socket stay blocked until the group is recreated.

Defensive priority

Medium

Recommended defensive actions

  • Review and apply the provided patches to the Linux kernel to fix the vulnerability
  • Monitor TIPC traffic and system logs for potential congestion and broadcast issues
  • Consider implementing additional monitoring and logging to detect potential exploitation attempts
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
  • Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The vulnerability is caused by the GRP_ACK_MSG handler in tipc_group_proto_rcv() decrementing bc_ackers on every inbound group ACK, even when the same member has already acknowledged the current broadcast round. This can lead to a counter underflow and incorrect congestion reporting.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-31662 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-31662

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-31662 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-31662

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • tipc: fix bc_ackers underflow on duplicate GRP_ACK_MSG

    Unverified legacy reference

    URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/31xxx/CVE-2026-31662.json

    cve_program_cvelist_v5

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/a7db57ccca21f5801609065473c89a38229ecb92

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/36ec4fdd6250dcd5e73eb09ea92ed92e9cc28412

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/575faea557f1a184a5f09661bd47ebd3ef3769f8

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/3bcf7aca63f0bcd679ae28e9b99823c608e59ce3

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/a2ea1ef0167d7a84730638d05c20ccdc421b14b6

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/1b6f13f626665cac67ba5a012765427680518711

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/e0bb732eaf77f9ac2f2638bdac9e39b81e0a9682

    Supplemental source

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.