Linux ·
Amazon Linux · Security advisory · February 16, 2026
Amazon Linux · Security advisory · February 16, 2026ALAS2023-2026-1430: Security update for 22 packages
ALAS2023-2026-1430, released February 16, 2026, fixes 76 CVEs across 22 products. None of them is reported as exploited. Patch Radar priority: Urgent.
Urgent
CVEs closed
76
4 rated Critical
Exploited
0
None reported
Highest CVSS
9.8
Base score, 0 to 10
Highest EPSS
0.0071
53rd percentile
Priority of the 76 CVEs
Patch now 0
Urgent 4
High 43
Routine 29
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| bpftool6.12 | amzn 2023 | 1:6.12.63-84.121.amzn2023 |
| bpftool6.12-debuginfo | amzn 2023 | 1:6.12.63-84.121.amzn2023 |
| kernel-livepatch-6.12.63-84.121 | amzn 2023 | 1:1.0-0.amzn2023 |
| kernel6.12 | amzn 2023 | 1:6.12.63-84.121.amzn2023 |
| kernel6.12-debuginfo | amzn 2023 | 1:6.12.63-84.121.amzn2023 |
| kernel6.12-debuginfo-common-aarch64 | amzn 2023 | 1:6.12.63-84.121.amzn2023 |
| kernel6.12-debuginfo-common-x86_64 | amzn 2023 | 1:6.12.63-84.121.amzn2023 |
| kernel6.12-devel | amzn 2023 | 1:6.12.63-84.121.amzn2023 |
| kernel6.12-headers | amzn 2023 | 1:6.12.63-84.121.amzn2023 |
| kernel6.12-libbpf | amzn 2023 | 1:6.12.63-84.121.amzn2023 |
| kernel6.12-libbpf-debuginfo | amzn 2023 | 1:6.12.63-84.121.amzn2023 |
| kernel6.12-libbpf-devel | amzn 2023 | 1:6.12.63-84.121.amzn2023 |
| kernel6.12-libbpf-static | amzn 2023 | 1:6.12.63-84.121.amzn2023 |
| kernel6.12-modules-extra | amzn 2023 | 1:6.12.63-84.121.amzn2023 |
| kernel6.12-modules-extra-common | amzn 2023 | 1:6.12.63-84.121.amzn2023 |
| kernel6.12-tools | amzn 2023 | 1:6.12.63-84.121.amzn2023 |
| kernel6.12-tools-debuginfo | amzn 2023 | 1:6.12.63-84.121.amzn2023 |
| kernel6.12-tools-devel | amzn 2023 | 1:6.12.63-84.121.amzn2023 |
| perf6.12 | amzn 2023 | 1:6.12.63-84.121.amzn2023 |
| perf6.12-debuginfo | amzn 2023 | 1:6.12.63-84.121.amzn2023 |
| python3-perf6.12 | amzn 2023 | 1:6.12.63-84.121.amzn2023 |
| python3-perf6.12-debuginfo | amzn 2023 | 1:6.12.63-84.121.amzn2023 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| Urgent | CVE-2025-68341 | linux: In the Linux kernel, the following vulnerability has been resolved: veth: reduce XDP no_direct return section to fix... | 9.8 | 0.0044 | None reported |
| Urgent | CVE-2025-40212 | linux: In the Linux kernel, the following vulnerability has been resolved: nfsd: fix refcount leak in nfsd_set_fh_dentry()... | 9.8 | 0.0043 | None reported |
| Urgent | CVE-2025-68366 | linux: In the Linux kernel, the following vulnerability has been resolved: nbd: defer config unlock in nbd_genl_connect Th... | 8.8 | 0.0020 | None reported |
| Urgent | CVE-2025-40251 | devlink: rate: Unset parent pointer in devl_rate_nodes_destroy | 9.8 | 0.0017 | None reported |
| High | CVE-2025-68349 | linux: In the Linux kernel, the following vulnerability has been resolved: NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_m... | 7.5 | 0.0071 | None reported |
| High | CVE-2025-68284 | libceph: prevent potential out-of-bounds writes in handle_auth_session_key() | 9.8 | 0.0059 | None reported |
| High | CVE-2025-68285 | libceph: fix potential use-after-free in have_mon_and_osd_map() | 9.8 | 0.0059 | None reported |
| High | CVE-2025-68261 | ext4: add i_data_sem protection in ext4_destroy_inline_data_nolock() | 7.5 | 0.0055 | None reported |
| High | CVE-2025-68337 | linux: In the Linux kernel, the following vulnerability has been resolved: jbd2: avoid bug_on in jbd2_journal_get_create_ac... | 7.5 | 0.0055 | None reported |
| High | CVE-2025-68283 | libceph: replace BUG_ON with bounds check for map->max_osd | 7.5 | 0.0053 | None reported |
| High | CVE-2025-40257 | mptcp: fix a race in mptcp_pm_del_add_timer() | 9.8 | 0.0050 | None reported |
| High | CVE-2025-40258 | mptcp: fix race condition in mptcp_schedule_work() | 9.8 | 0.0050 | None reported |
| High | CVE-2025-40075 | tcp_metrics: use dst_dev_net_rcu() | 8.1 | 0.0049 | None reported |
| High | CVE-2025-40271 | linux: In the Linux kernel, the following vulnerability has been resolved: fs/proc: fix uaf in proc_readdir_de() Pde is er... | 7.8 | 0.0049 | None reported |
| High | CVE-2025-68241 | linux: In the Linux kernel, the following vulnerability has been resolved: ipv4: route: Prevent rt_bind_exception() from re... | 7.5 | 0.0047 | None reported |
| High | CVE-2025-40273 | NFSD: free copynotify stateid in nfs4_free_ol_stateid() | 8.8 | 0.0046 | None reported |
| High | CVE-2025-68369 | linux: In the Linux kernel, the following vulnerability has been resolved: ntfs3: init run lock for extend inode After set... | 7.5 | 0.0046 | None reported |
| High | CVE-2025-68226 | linux: In the Linux kernel, the following vulnerability has been resolved: smb: client: fix incomplete backport in cfids_in... | 8.8 | 0.0035 | None reported |
| High | CVE-2025-38678 | netfilter: nf_tables: reject duplicate device on updates | 7.1 | 0.0029 | None reported |
| High | CVE-2025-40277 | drm/vmwgfx: Validate command header size against SVGA_CMD_MAX_DATASIZE | 7.8 | 0.0025 | None reported |
| High | CVE-2025-40281 | sctp: prevent possible shift-out-of-bounds in sctp_transport_update_rto | 7.0 | 0.0023 | None reported |
| High | CVE-2025-68361 | linux: In the Linux kernel, the following vulnerability has been resolved: erofs: limit the level of fs stacking for file-b... | n/a | 0.0023 | None reported |
| High | CVE-2025-68227 | mptcp: Fix proto fallback detection with BPF | 7.8 | 0.0022 | None reported |
| High | CVE-2025-40259 | scsi: sg: Do not sleep in atomic context | 7.0 | 0.0022 | None reported |
| High | CVE-2025-68297 | ceph: fix crash in process_v2_sparse_read() for encrypted directories | 7.0 | 0.0021 | None reported |
Showing 1 to 25 of 76
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.