Race Condition Affecting python3-perf6.12-debuginfo package, versions <1:6.12.111-136.204.amzn2023
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
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-PYTHON3PERF612DEBUGINFO-20862447
- published13 Oct 2026
- disclosed25 Sept 2026
Introduced: 25 Sep 2026
NewCVE-2026-98071 (opens in a new tab)How to fix?
Upgrade Amazon-Linux:2023 python3-perf6.12-debuginfo to version 1:6.12.111-136.204.amzn2023 or higher.
This issue was patched in ALAS2023-2026-3193.
NVD Description
Note: Versions mentioned in the description apply only to the upstream python3-perf6.12-debuginfo package and not the python3-perf6.12-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:
net/rds: clear cp_flags bits individually in rds_conn_path_reset()
rds_conn_path_reset() wipes the whole flag word with a plain cp->cp_flags = 0 store. Every other accessor of that word uses atomic bitops, and some of them can run concurrently with the reset: RDS_LL_SEND_FULL is set from rds_send_xmit() and cleared from the transport completion paths, neither of which holds anything that excludes the shutdown worker. A plain store racing an atomic read-modify-write on the same word is a data race, and whichever side loses has its update silently discarded.
Clear the two bits the reset is actually responsible for instead. RDS_IN_XMIT and RDS_RECV_REFILL need no store at all here: they belong to the caller, rds_conn_shutdown(), which waits for both to be clear before calling the transport shutdown and this reset.
This also gives every bit in cp_flags a single well-defined writer discipline, which the following patches rely on when they turn RDS_IN_XMIT and RDS_RECV_REFILL into bit locks held across the teardown: a blanket store mid-teardown would destroy lock ownership that an atomic clear preserves.
Oracle UEK carries the same conversion ("net/rds: Preserve essential connection state flags"), motivated by its asynchronous shutdown state machine, whose progress and destroy flags must survive the reset. UEK's variant also clears RDS_IN_XMIT and RDS_RECV_REFILL because there the reset runs as the final step of a teardown that owns both bits, making those clears its unlock. Upstream that release belongs in rds_conn_shutdown(): once a later patch in this series turns the two bits into locks held across the teardown, ending ownership needs release semantics and a wake-up that a plain clear inside the reset would not provide.
Based on Oracle UEK commit "net/rds: Preserve essential connection state flags" by Gerd Rausch.
References
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-98071
- https://git.kernel.org/stable/c/103c4b13c4f50322910078d1c02f29334a574122
- https://git.kernel.org/stable/c/6b8d7563c28b8112e6e54abe413b028ef3f8c549
- https://git.kernel.org/stable/c/cb62aa8f04655a4df487913949719c0a1266ed73
- https://git.kernel.org/stable/c/ed3ee0ac4aafda50c2f4381eb973beefeb7879ac
- https://git.kernel.org/stable/c/b767b48614c38687d717082860de7aa46f3b142c
- https://git.kernel.org/stable/c/b7dc5da660eb5ffa7f7b4d33f2c74cb71c6edd6c
- https://git.kernel.org/stable/c/b8a8b6d25e7426a638c60eaba2129c0664131e84
- https://git.kernel.org/stable/c/c9a7c1eb0ad41dcf004a9e870e452cafedcd9172