Linux ·
Amazon Linux · Security advisory · May 8, 2026
Amazon Linux · Security advisory · May 8, 2026ALAS2023-2026-1694: Security update for 18 packages
ALAS2023-2026-1694, released May 8, 2026, fixes 16 CVEs across 18 products. None of them is reported as exploited. Patch Radar priority: Urgent.
Urgent
CVEs closed
16
1 rated Critical
Exploited
0
None reported
Highest CVSS
9.8
Base score, 0 to 10
Highest EPSS
0.9419
99th percentile
Priority of the 16 CVEs
Patch now 0
Urgent 1
High 10
Routine 5
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| bpftool | amzn 2023 | 1:6.1.170-210.320.amzn2023 |
| bpftool-debuginfo | amzn 2023 | 1:6.1.170-210.320.amzn2023 |
| kernel | amzn 2023 | 1:6.1.170-210.320.amzn2023 |
| kernel-debuginfo | amzn 2023 | 1:6.1.170-210.320.amzn2023 |
| kernel-debuginfo-common-aarch64 | amzn 2023 | 1:6.1.170-210.320.amzn2023 |
| kernel-debuginfo-common-x86_64 | amzn 2023 | 1:6.1.170-210.320.amzn2023 |
| kernel-devel | amzn 2023 | 1:6.1.170-210.320.amzn2023 |
| kernel-headers | amzn 2023 | 1:6.1.170-210.320.amzn2023 |
| kernel-livepatch-6.1.170-210.320 | amzn 2023 | 1:1.0-0.amzn2023 |
| kernel-modules-extra | amzn 2023 | 1:6.1.170-210.320.amzn2023 |
| kernel-modules-extra-common | amzn 2023 | 1:6.1.170-210.320.amzn2023 |
| kernel-tools | amzn 2023 | 1:6.1.170-210.320.amzn2023 |
| kernel-tools-debuginfo | amzn 2023 | 1:6.1.170-210.320.amzn2023 |
| kernel-tools-devel | amzn 2023 | 1:6.1.170-210.320.amzn2023 |
| perf | amzn 2023 | 1:6.1.170-210.320.amzn2023 |
| perf-debuginfo | amzn 2023 | 1:6.1.170-210.320.amzn2023 |
| python3-perf | amzn 2023 | 1:6.1.170-210.320.amzn2023 |
| python3-perf-debuginfo | amzn 2023 | 1:6.1.170-210.320.amzn2023 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| Urgent | CVE-2026-31533 | linux: In the Linux kernel, the following vulnerability has been resolved: net/tls: fix use-after-free in -EBUSY error path... | 9.8 | 0.0040 | None reported |
| High | CVE-2026-43284 | xfrm: esp: avoid in-place decrypt on shared skb frags | 8.8 | 0.9419 | None reported |
| High | CVE-2026-31669 | mptcp: fix slab-use-after-free in __inet_lookup_established | 9.8 | 0.0047 | None reported |
| High | CVE-2026-31668 | seg6: separate dst_cache for input and output paths in seg6 lwtunnel | 9.8 | 0.0044 | None reported |
| High | CVE-2026-43336 | linux: In the Linux kernel, the following vulnerability has been resolved: lib/crypto: chacha: Zeroize permuted_state befor... | 7.5 | 0.0043 | None reported |
| High | CVE-2026-31662 | tipc: fix bc_ackers underflow on duplicate GRP_ACK_MSG | 7.5 | 0.0039 | None reported |
| High | CVE-2026-31786 | kernel: In the Linux kernel, the following vulnerability has been resolved: Buffer overflow in drivers/xen/sys-hypervisor.c T... | 7.8 | 0.0020 | None reported |
| High | CVE-2026-31787 | kernel: In the Linux kernel, the following vulnerability has been resolved: xen/privcmd: fix double free via VMA splitting pr... | 7.8 | 0.0018 | None reported |
| High | CVE-2026-31665 | netfilter: nft_ct: fix use-after-free in timeout object destroy | 7.8 | 0.0012 | None reported |
| High | CVE-2026-31667 | Input: uinput - fix circular locking dependency with ff-core | 7.8 | 0.0010 | None reported |
| High | CVE-2026-31656 | drm/i915/gt: fix refcount underflow in intel_engine_park_heartbeat | 8.8 | 0.0009 | None reported |
| Routine | CVE-2026-31628 | x86/CPU: Fix FPDSS on Zen1 | 5.5 | 0.0013 | None reported |
| Routine | CVE-2026-31634 | rxrpc: fix reference count leak in rxrpc_server_keyring() | 5.5 | 0.0013 | None reported |
| Routine | CVE-2026-31664 | xfrm: clear trailing padding in build_polexpire() | 5.5 | 0.0012 | None reported |
| Routine | CVE-2026-31671 | xfrm_user: fix info leak in build_report() | 5.5 | 0.0012 | None reported |
| Routine | CVE-2026-31689 | EDAC/mc: Fix error path ordering in edac_mc_alloc() | 5.5 | 0.0012 | None reported |
Showing 1 to 16 of 16
1
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.