Integer Underflow Affecting python3-perf6.18-debuginfo package, versions <1:6.18.25-55.108.amzn2023


Severity

Recommended
high

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.07% (23rd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-AMZN2023-PYTHON3PERF618DEBUGINFO-16736617
  • published18 May 2026
  • disclosed24 Apr 2026

Introduced: 24 Apr 2026

CVE-2026-31662  (opens in a new tab)
CWE-191  (opens in a new tab)

How to fix?

Upgrade Amazon-Linux:2023 python3-perf6.18-debuginfo to version 1:6.18.25-55.108.amzn2023 or higher.
This issue was patched in ALAS2023-2026-1693.

NVD Description

Note: Versions mentioned in the description apply only to the upstream python3-perf6.18-debuginfo package and not the python3-perf6.18-debuginfo package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2023 relevant fixed versions and status.

In the Linux kernel, the following vulnerability has been resolved:

tipc: fix bc_ackers underflow on duplicate GRP_ACK_MSG

The GRP_ACK_MSG handler in tipc_group_proto_rcv() currently 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.

Fix this by ignoring duplicate or stale ACKs before touching bc_acked or bc_ackers. This makes repeated GRP_ACK_MSG handling idempotent and prevents the underflow path.

CVSS Base Scores

version 3.1