Linux ·
Amazon Linux · Security advisory · November 7, 2026
Amazon Linux · Security advisory · November 7, 2026ALAS2023-2026-3197: Security update for 18 packages
ALAS2023-2026-3197, released November 7, 2026, fixes 202 CVEs across 18 products. None of them is reported as exploited. Patch Radar priority: Urgent.
Urgent
CVEs closed
202
24 rated Critical
Exploited
0
None reported
Highest CVSS
9.8
Base score, 0 to 10
Highest EPSS
0.0084
58th percentile
Priority of the 202 CVEs
Patch now 0
Urgent 24
High 119
Routine 59
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| bpftool | amzn 2023 | 1:6.1.188-233.385.amzn2023 |
| bpftool-debuginfo | amzn 2023 | 1:6.1.188-233.385.amzn2023 |
| kernel | amzn 2023 | 1:6.1.188-233.385.amzn2023 |
| kernel-debuginfo | amzn 2023 | 1:6.1.188-233.385.amzn2023 |
| kernel-debuginfo-common-aarch64 | amzn 2023 | 1:6.1.188-233.385.amzn2023 |
| kernel-debuginfo-common-x86_64 | amzn 2023 | 1:6.1.188-233.385.amzn2023 |
| kernel-devel | amzn 2023 | 1:6.1.188-233.385.amzn2023 |
| kernel-headers | amzn 2023 | 1:6.1.188-233.385.amzn2023 |
| kernel-livepatch-6.1.188-233.385 | amzn 2023 | 1:1.0-0.amzn2023 |
| kernel-modules-extra | amzn 2023 | 1:6.1.188-233.385.amzn2023 |
| kernel-modules-extra-common | amzn 2023 | 1:6.1.188-233.385.amzn2023 |
| kernel-tools | amzn 2023 | 1:6.1.188-233.385.amzn2023 |
| kernel-tools-debuginfo | amzn 2023 | 1:6.1.188-233.385.amzn2023 |
| kernel-tools-devel | amzn 2023 | 1:6.1.188-233.385.amzn2023 |
| perf | amzn 2023 | 1:6.1.188-233.385.amzn2023 |
| perf-debuginfo | amzn 2023 | 1:6.1.188-233.385.amzn2023 |
| python3-perf | amzn 2023 | 1:6.1.188-233.385.amzn2023 |
| python3-perf-debuginfo | amzn 2023 | 1:6.1.188-233.385.amzn2023 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| Urgent | CVE-2026-99999 | ipv4: validate checksum_start before completing checksum | 9.3 | 0.0079 | None reported |
| Urgent | CVE-2026-90151 | linux: In the Linux kernel, the following vulnerability has been resolved: NFSv4: remove callback IDR entry on client alloc... | 9.8 | 0.0075 | None reported |
| Urgent | CVE-2026-72323 | linux: In the Linux kernel, the following vulnerability has been resolved: ipv4: igmp: Fix potential UAF in igmp_gq_start_t... | 9.8 | 0.0072 | None reported |
| Urgent | CVE-2026-68476 | linux: In the Linux kernel, the following vulnerability has been resolved: ipvs: reload ip header after head reallocation... | 9.8 | 0.0071 | None reported |
| Urgent | CVE-2026-80976 | linux: In the Linux kernel, the following vulnerability has been resolved: seg6: reset IP6CB after IPv6 decapsulation deca... | 9.8 | 0.0071 | None reported |
| Urgent | CVE-2026-89485 | linux: In the Linux kernel, the following vulnerability has been resolved: lockd: pin next file across nlm_inspect_file loc... | 9.8 | 0.0071 | None reported |
| Urgent | CVE-2026-89655 | linux: In the Linux kernel, the following vulnerability has been resolved: ceph: fix UAF in __kick_flushing_caps() on cf en... | 9.8 | 0.0071 | None reported |
| Urgent | CVE-2026-89712 | linux: In the Linux kernel, the following vulnerability has been resolved: NFSD: restart ssc_expire_umount walk after dropp... | 9.8 | 0.0071 | None reported |
| Urgent | CVE-2026-89783 | xfrm6: fix out-of-bounds write in xfrm6_input_addr() when secpath is full | 9.8 | 0.0071 | None reported |
| Urgent | CVE-2026-89778 | isofs: fix out-of-bounds page array access on empty zisofs block | 9.8 | 0.0070 | None reported |
| Urgent | CVE-2026-89555 | linux: In the Linux kernel, the following vulnerability has been resolved: mpls: reload header after pskb_may_pull() mpls_... | 9.8 | 0.0069 | None reported |
| Urgent | CVE-2026-89634 | linux: In the Linux kernel, the following vulnerability has been resolved: smb: client: fix ALIGN() overflow in symlink_dat... | 9.8 | 0.0069 | None reported |
| Urgent | CVE-2026-89636 | linux: In the Linux kernel, the following vulnerability has been resolved: smb: client: clear ce->tgthint in free_tgts() W... | 9.8 | 0.0066 | None reported |
| Urgent | CVE-2026-90110 | linux: In the Linux kernel, the following vulnerability has been resolved: inetpeer: randomize RB-tree node comparison usin... | 9.4 | 0.0061 | None reported |
| Urgent | CVE-2026-89478 | linux: In the Linux kernel, the following vulnerability has been resolved: sctp: drop a chunk if its transport was removed... | 9.8 | 0.0051 | None reported |
| Urgent | CVE-2026-89541 | linux: In the Linux kernel, the following vulnerability has been resolved: SUNRPC: harden gss_unwrap_resp_priv length check... | 9.8 | 0.0051 | None reported |
| Urgent | CVE-2026-89542 | SUNRPC: harden gss_krb5_unwrap_v2 against short tokens | 9.8 | 0.0051 | None reported |
| Urgent | CVE-2026-89551 | SUNRPC: xdr_buf_trim: clamp buf->len to avoid underflow | 9.8 | 0.0051 | None reported |
| Urgent | CVE-2026-89653 | ceph: reject export_targets ranks >= CEPH_MAX_MDS in mdsmap decode | 9.8 | 0.0050 | None reported |
| Urgent | CVE-2026-89479 | sctp: stop processing a packet once its association is deleted | 9.8 | 0.0050 | None reported |
| Urgent | CVE-2026-64025 | linux: In the Linux kernel, the following vulnerability has been resolved: bpf, skmsg: fix verdict sk_data_ready racing wit... | 9.8 | 0.0037 | None reported |
| Urgent | CVE-2026-80671 | linux: In the Linux kernel, the following vulnerability has been resolved: perf sched: Fix register_pid() overflow, strcpy,... | 9.3 | 0.0016 | None reported |
| Urgent | CVE-2026-64078 | netfilter: x_tables: add and use xtables_unregister_table_exit | 9.8 | 0.0013 | None reported |
| Urgent | CVE-2026-64079 | netfilter: x_tables: allocate hook ops while under mutex | 9.8 | 0.0012 | None reported |
| High | CVE-2026-90011 | scsi: target: iscsi: Reserve a terminator byte for the login payload | 9.8 | 0.0084 | None reported |
Showing 1 to 25 of 202
1Next
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.