Synopsis
The remote Amazon Linux 2023 host is missing a security update.
Description
It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2026-1924 advisory.
In the Linux kernel, the following vulnerability has been resolved:
mm/page_alloc: clear page->private in free_pages_prepare() (CVE-2026-43303)
In the Linux kernel, the following vulnerability has been resolved:
lib/crypto: mpi: Fix integer underflow in mpi_read_raw_from_sgl() (CVE-2026-43492)
In the Linux kernel, the following vulnerability has been resolved:
ipvs: skip ipv6 extension headers for csum checks (CVE-2026-45850)
In the Linux kernel, the following vulnerability has been resolved:
udf: fix partition descriptor append bookkeeping (CVE-2026-45991)
In the Linux kernel, the following vulnerability has been resolved:
erofs: fix unsigned underflow in z_erofs_lz4_handle_overlap() (CVE-2026-45999)
In the Linux kernel, the following vulnerability has been resolved:
xfs: fix a resource leak in xfs_alloc_buftarg() (CVE-2026-46005)
In the Linux kernel, the following vulnerability has been resolved:
thermal: core: Fix thermal zone governor cleanup issues (CVE-2026-46021)
In the Linux kernel, the following vulnerability has been resolved:
ceph: only d_add() negative dentries when they are unhashed (CVE-2026-46052)
In the Linux kernel, the following vulnerability has been resolved:
fbdev: defio: Disconnect deferred I/O from the lifetime of struct fb_info (CVE-2026-46065)
In the Linux kernel, the following vulnerability has been resolved:
net: bridge: use a stable FDB dst snapshot in RCU readers (CVE-2026-46086)
In the Linux kernel, the following vulnerability has been resolved:
xfrm: defensively unhash xfrm_state lists in __xfrm_state_delete (CVE-2026-46116)
In the Linux kernel, the following vulnerability has been resolved:
mptcp: pm: ADD_ADDR rtx: fix potential data-race (CVE-2026-46137)
In the Linux kernel, the following vulnerability has been resolved:
btrfs: fix btrfs_ioctl_space_info() slot_count TOCTOU which can lead to info-leak (CVE-2026-46159)
In the Linux kernel, the following vulnerability has been resolved:
btrfs: fix missing last_unlink_trans update when removing a directory (CVE-2026-46160)
In the Linux kernel, the following vulnerability has been resolved:
xfrm: ah: account for ESN high bits in async callbacks (CVE-2026-46193)
In the Linux kernel, the following vulnerability has been resolved:
smb: client: validate dacloffset before building DACL pointers (CVE-2026-46195)
In the Linux kernel, the following vulnerability has been resolved:
tracepoint: balance regfunc() on func_add() failure in tracepoint_add_func() (CVE-2026-46196)
In the Linux kernel, the following vulnerability has been resolved:
pmdomain: core: Fix detach procedure for virtual devices in genpd (CVE-2026-46292)
In the Linux kernel, the following vulnerability has been resolved:
tap: free page on error paths in tap_get_user_xdp() (CVE-2026-46320)
In the Linux kernel, the following vulnerability has been resolved:
tun: free page on short-frame rejection in tun_xdp_one() (CVE-2026-46321)
In the Linux kernel, the following vulnerability has been resolved:
tun: free page on build_skb failure in tun_xdp_one() (CVE-2026-46322)
In the Linux kernel, the following vulnerability has been resolved:
bpf: Free reuseport cBPF prog after RCU grace period. (CVE-2026-52910)
In the Linux kernel, the following vulnerability has been resolved:
ipc: limit next_id allocation to the valid ID range (CVE-2026-52923)
In the Linux kernel, the following vulnerability has been resolved:
sctp: purge outqueue on stale COOKIE-ECHO handling (CVE-2026-52924)
In the Linux kernel, the following vulnerability has been resolved:
netfilter: ebtables: fix OOB read in compat_mtw_from_user (CVE-2026-52927)
In the Linux kernel, the following vulnerability has been resolved:
sctp: stream: fully roll back denied add-stream state (CVE-2026-52929)
In the Linux kernel, the following vulnerability has been resolved:
ipc/shm: serialize orphan cleanup with shm_nattch updates (CVE-2026-52930)
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nf_log: validate MAC header was set before dumping it (CVE-2026-52942)
In the Linux kernel, the following vulnerability has been resolved:
net: skbuff: fix missing zerocopy reference in pskb_carve helpers (CVE-2026-52943)
In the Linux kernel, the following vulnerability has been resolved:
fs/fcntl: fix SOFTIRQ-unsafe lock order in fasync signaling (CVE-2026-52946)
In the Linux kernel, the following vulnerability has been resolved:
netfilter: require Ethernet MAC header before using eth_hdr() (CVE-2026-53131)
In the Linux kernel, the following vulnerability has been resolved:
RDMA/umem: Fix truncation for block sizes >= 4G (CVE-2026-53133)
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nft_fib: fix stale stack leak via the OIFNAME register (CVE-2026-53134)
In the Linux kernel, the following vulnerability has been resolved:
fuse: reject fuse_notify() pagecache ops on directories (CVE-2026-53168)
In the Linux kernel, the following vulnerability has been resolved:
mptcp: allow subflow rcv wnd to shrink (CVE-2026-53183)
In the Linux kernel, the following vulnerability has been resolved:
udp: clear skb->dev before running a sockmap verdict (CVE-2026-53184)
In the Linux kernel, the following vulnerability has been resolved:
mm/huge_memory: update file PMD counter before folio_put() (CVE-2026-53189)
In the Linux kernel, the following vulnerability has been resolved:
hv_netvsc: use kmap_local_page in netvsc_copy_to_send_buf (CVE-2026-53199)
In the Linux kernel, the following vulnerability has been resolved:
mm/memory-failure: fix hugetlb_lock AA deadlock in get_huge_page_for_hwpoison (CVE-2026-53207)
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nft_tunnel: fix use-after-free on object destroy (CVE-2026-53212)
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nft_exthdr: fix register tracking for F_PRESENT flag (CVE-2026-53218)
In the Linux kernel, the following vulnerability has been resolved:
netfilter: x_tables: avoid leaking percpu counter pointers (CVE-2026-53219)
In the Linux kernel, the following vulnerability has been resolved:
ip6_vti: fix incorrect tunnel matching in vti6_tnl_lookup() (CVE-2026-53221)
In the Linux kernel, the following vulnerability has been resolved:
net: guard timestamp cmsgs to real error queue skbs (CVE-2026-53223)
In the Linux kernel, the following vulnerability has been resolved:
sctp: fix uninit-value in __sctp_rcv_asconf_lookup() (CVE-2026-53225)
In the Linux kernel, the following vulnerability has been resolved:
net: openvswitch: fix possible kfree_skb of ERR_PTR (CVE-2026-53227)
In the Linux kernel, the following vulnerability has been resolved:
ipv6: sit: reload inner IPv6 header after GSO offloads (CVE-2026-53228)
In the Linux kernel, the following vulnerability has been resolved:
tcp: restrict SO_ATTACH_FILTER to priv users (CVE-2026-53236)
In the Linux kernel, the following vulnerability has been resolved:
netlabel: validate unlabeled address and mask attribute lengths (CVE-2026-53238)
In the Linux kernel, the following vulnerability has been resolved:
xfrm: policy: fix use-after-free on inexact bin in xfrm_policy_bysel_ctx() (CVE-2026-53239)
In the Linux kernel, the following vulnerability has been resolved:
net/802/mrp: fix vector attribute parsing in mrp_pdu_parse_vecattr (CVE-2026-53245)
In the Linux kernel, the following vulnerability has been resolved:
ipv4: restrict IPOPT_SSRR and IPOPT_LSRR options (CVE-2026-53249)
In the Linux kernel, the following vulnerability has been resolved:
net/sched: act_api: use RCU with deferred freeing for action lifecycle (CVE-2026-53264)
In the Linux kernel, the following vulnerability has been resolved:
netfilter: bridge: make ebt_snat ARP rewrite writable (CVE-2026-53266)
In the Linux kernel, the following vulnerability has been resolved:
netfilter: conntrack_irc: fix possible out-of-bounds read (CVE-2026-53268)
In the Linux kernel, the following vulnerability has been resolved:
netfilter: synproxy: add mutex to guard hook reference counting (CVE-2026-53269)
In the Linux kernel, the following vulnerability has been resolved:
ipvs: clear the svc scheduler ptr early on edit (CVE-2026-53270)
In the Linux kernel, the following vulnerability has been resolved:
ipv6: mcast: Fix use-after-free when processing MLD queries (CVE-2026-53275)
In the Linux kernel, the following vulnerability has been resolved:
net: bonding: fix NULL pointer dereference in bond_do_ioctl()
In bond_do_ioctl(), slave_dev is obtained via __dev_get_by_name() whichcan return NULL if the requested interface name does not exist. However,the subsequent slave_dbg() call is placed before the NULL check:
slave_dev = __dev_get_by_name(net, ifr->ifr_slave);slave_dbg(bond_dev, slave_dev, slave_dev=%p:\n, slave_dev); //hereif (!slave_dev)return -ENODEV;
The slave_dbg() macro expands to netdev_dbg(bond_dev, (slave %s): fmt,(slave_dev)->name, ...) which unconditionally dereferences slave_dev->namebefore the NULL check is performed. This results in a NULL pointerdereference kernel oops when a user calls bonding ioctl (e.g.SIOCBONDENSLAVE, SIOCBONDRELEASE, etc.) with a non-existent slaveinterface name.
This is reachable from userspace via the bonding ioctl interface withCAP_NET_ADMIN capability, making it a potential local denial-of-servicevector.
Fix by moving the slave_dbg() call after the NULL check. (CVE-2026-53337)
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nf_conntrack: destroy stale expectfn expectations on unregister
NAT helpers such as nf_nat_h323 store a raw pointer to module text inexp->expectfn (e.g.
ip_nat_q931_expect). nf_ct_helper_expectfn_unregister()only unlinks the callback descriptor and never walks the expectation table,so an expectation pending at module removal survives with a danglingexp->expectfn into freed module text.
When the expected connection arrives, init_conntrack() invokesexp->expectfn(), now a stale pointer into the unloaded module. Reproducedon a KASAN build by loading the H.323 helpers, creating a Q.931expectation, unloading nf_nat_h323, then connecting to the expected port:
Oops: int3: 0000 [#1] SMP KASAN NOPTIRIP: 0010:0xffffffffa06102d1init_conntrack.isra.0 (net/netfilter/nf_conntrack_core.c:1862)nf_conntrack_in (net/netfilter/nf_conntrack_core.c:2049)ipv4_conntrack_local (net/netfilter/nf_conntrack_proto.c:223)nf_hook_slow (net/netfilter/core.c:619)__ip_local_out (net/ipv4/ip_output.c:120)__tcp_transmit_skb (net/ipv4/tcp_output.c:1715)tcp_connect (net/ipv4/tcp_output.c:4374)tcp_v4_connect (net/ipv4/tcp_ipv4.c:345)__sys_connect (net/socket.c:2167)Modules linked in: nf_conntrack_h323 [last unloaded: nf_nat_h323]
Reaching the dangling state requires CAP_SYS_MODULE in the initial usernamespace to remove a NAT helper that still has live expectations, so thisis a robustness fix; leaving an expectation pointing at freed text is wrongregardless.
Add nf_ct_helper_expectfn_destroy(), which walks the expectation table anddrops every expectation whose
->expectfn matches the descriptor being torndown. Call it from each NAT helper's exit path after the existing RCU graceperiod, so no expectation outlives the code it points at and no extrasynchronize_rcu() is introduced. With the fix, the same reproducer runs tocompletion without the Oops. (CVE-2026-53349)
In the Linux kernel, the following vulnerability has been resolved:
signal: clear JOBCTL_PENDING_MASK for caller in zap_other_threads()
When a multi-threaded process receives a stop signal (e.g., SIGSTOP),do_signal_stop() sets JOBCTL_STOP_PENDING and JOBCTL_STOP_CONSUME on allthreads and sets signal->group_stop_count to the number of threads. Ifone of the threads concurrently calls execve(), de_thread() invokeszap_other_threads() to kill all other threads. zap_other_threads()aborts the pending group stop by resetting signal->group_stop_count to 0and clears the JOBCTL_PENDING_MASK for all other threads. However, itfails to clear the job control flags for the calling thread.
When execve() completes, the calling thread returns to user mode andchecks for pending signals. Seeing the stale JOBCTL_STOP_PENDING flag,it calls do_signal_stop(), which invokes task_participate_group_stop().Since JOBCTL_STOP_CONSUME is still set, it attempts to decrement thealready- zero signal->group_stop_count, triggering a warning:
sig->group_stop_count == 0WARNING: CPU: 1 PID: 6475 at kernel/signal.c:373task_participate_group_stop+0x215/0x2d0Call Trace:<TASK>do_signal_stop+0x3be/0x5c0 kernel/signal.c:2619get_signal+0xa8c/0x1330 kernel/signal.c:2884arch_do_signal_or_restart+0xbc/0x840 arch/x86/kernel/signal.c:337exit_to_user_mode_loop+0x8c/0x4d0 kernel/entry/common.c:98do_syscall_64+0x33e/0xf80 arch/x86/entry/syscall_64.c:100entry_SYSCALL_64_after_hwframe+0x77/0x7f</TASK>
Fix this race condition by clearing the JOBCTL_PENDING_MASK for thecalling thread in zap_other_threads(), ensuring it does not retain anystale job control state after the thread group is destroyed. This alignswith other functions that tear down a thread group and abort groupstops, such as zap_process() and complete_signal(), which correctlyclear these flags for all threads including the current one.
(CVE-2026-53352)
In the Linux kernel, the following vulnerability has been resolved:
arm64: errata: Mitigate TLBI errata on various Arm CPUs
A number of CPUs developed by Arm suffer from errata whereby a broadcastTLBI;DSB sequence may complete before the global observation of writeswhich are translated by an affected TLB entry.
These errata ONLY affect the completion of memory accesses which havebeen translated by an invalidated TLB entry, and these errata DO NOTaffect the actual invalidation of TLB entries. TLB entries are removedcorrectly.
This issue has been assigned CVE ID CVE-2025-10263.
To mitigate this issue, Arm recommends that software follows anyaffected TLBI;DSB sequence with an additional TLBI;DSB, which willensure that all memory write effects affected by the first TLBI havebeen globally observed. The additional TLBI can use any operation thatis broadcast to affected CPUs, and the additional DSB can use any optionthat is sufficient to complete the additional TLBI.
The ARM64_WORKAROUND_REPEAT_TLBI workaround is sufficient to mitigatethe issue. Enable this workaround for affected CPUs, and update thesilicon errata documentation accordingly.
Note that due to the manner in which Arm develops IP and tracks errata,some CPUs share a common erratum number. (CVE-2026-53354)
In the Linux kernel, the following vulnerability has been resolved:
drm/i915/gem: Fix phys BO pread/pwrite with offset (CVE-2026-53356)
In the Linux kernel, the following vulnerability has been resolved:
mptcp: close TOCTOU race while computing rcv_wnd (CVE-2026-63867)
In the Linux kernel, the following vulnerability has been resolved:
net: garp: fix unsigned integer underflow in garp_pdu_parse_attr
The receive-side GARP attribute parser computes dlen with reversedoperands:
dlen = sizeof(*ga) - ga->len;
ga->len is the on-wire attribute length and includes the GARP attributeheader. For normal attributes with data, ga->len is larger thansizeof(*ga), so the subtraction underflows in unsigned arithmetic.
The resulting value is later passed to garp_attr_lookup(), whose lengthargument is u8. After truncation, the parsed data length usually nolonger matches the length stored for locally registered attributes, soreceived Join/Leave events are ignored. This breaks the GARP receive pathfor common attributes, such as GVRP VLAN registration attributes.
Compute the data length as the attribute length minus the header length. (CVE-2026-63868)
In the Linux kernel, the following vulnerability has been resolved:
arm64: tlb: Flush walk cache when unsharing PMD tables (CVE-2026-63875)
In the Linux kernel, the following vulnerability has been resolved:
drm/i915: Fix potential UAF in TTM object purge (CVE-2026-63884)
In the Linux kernel, the following vulnerability has been resolved:
scsi: scsi_transport_fc: Widen FPIN pname walker counter to u32 (CVE-2026-63889)
In the Linux kernel, the following vulnerability has been resolved:
xfrm: esp: restore combined single-frag length gate
The ESP out-of-place fast path appends the trailer in esp_output_head()before esp_output_tail() allocates the destination page frag. Thehead-side gate currently checks skb->data_len and tailen separately, butthe tail code allocates a single destination frag from the combinedpost-trailer skb->data_len.
Reject the page-frag fast path when the combined aligned length exceeds apage. Otherwise skb_page_frag_refill() may fall back to a single page whilethe destination sg still spans the combined skb->data_len.
Restore this combined-length page gate for both IPv4 and IPv6. (CVE-2026-63912)
In the Linux kernel, the following vulnerability has been resolved:
netfilter: conntrack: tcp: do not force CLOSE on invalid-seq RST without direction check (CVE-2026-63913)
In the Linux kernel, the following vulnerability has been resolved:
xfrm: route MIGRATE notifications to caller's netns (CVE-2026-63914)
In the Linux kernel, the following vulnerability has been resolved:
ip6: vti: Use ip6_tnl.net in vti6_changelink(). (CVE-2026-63917)
In the Linux kernel, the following vulnerability has been resolved:
xfrm: input: hold netns during deferred transport reinjection (CVE-2026-63919)
In the Linux kernel, the following vulnerability has been resolved:
ipv6: validate extension header length before copying to cmsg (CVE-2026-63920)
In the Linux kernel, the following vulnerability has been resolved:
ip6: vti: Use ip6_tnl.net in vti6_siocdevprivate().
After patch 1/2 in this series, vti6_update() unlinks and relinksthe tunnel through t->net.
vti6_siocdevprivate() still usesdev_net(dev) for the collision lookup. For a tunnel moved throughIFLA_NET_NS_FD, dev_net(dev) is the new netns, not t->net.
SIOCCHGTUNNEL on a migrated tunnel then runs:
net = dev_net(dev) /* migrated netns */t = vti6_locate(net, &p1, false) /* misses target in t->net */...t = netdev_priv(dev)vti6_update(t, &p1, false) /* mutates t->net's hash
*/
A caller in the migrated netns picks params that match a tunnelin the creation netns. The lookup in dev_net(dev) finds nothing.vti6_update() prepends the migrated tunnel at the head of thecreation netns hash bucket for those params. Later lookups inthe creation netns resolve to the migrated device. xfrm receivedelivers the matched packets through a device the caller controls.
Reachable from an unprivileged user namespace (unshare --user--map-root-user --net). Cross tenant scope on container hosts.
Switch the SIOCCHGTUNNEL path on a non fallback device to uset->net for the lookup. The lookup now matches the netnsvti6_update() operates on.
Also add ns_capable(self->net->user_ns, CAP_NET_ADMIN) beforethe lookup. The check at the top of the case is againstdev_net(dev)->user_ns, which after migration is the attacker'snetns. A caller there can pick params absent from self->net,the lookup returns NULL, t becomes self, and vti6_update()inserts the device into the creation netns hash. The new checkrequires CAP_NET_ADMIN in the creation netns user_ns too.
SIOCADDTUNNEL and SIOCCHGTUNNEL on the fallback device keepdev_net(dev), which equals init_net there.
(CVE-2026-63921)
In the Linux kernel, the following vulnerability has been resolved:
ipv6: exthdrs: refresh nh after handling HAO option (CVE-2026-63922)
In the Linux kernel, the following vulnerability has been resolved:
ipv6: exthdrs: refresh nh pointer after ipv6_hop_jumbo()
ipv6_hop_jumbo() calls pskb_trim_rcsum(), which can change skb pointers.Let's recompute nh pointer to make sure any change won't mess things up. (CVE-2026-63924)
In the Linux kernel, the following vulnerability has been resolved:
macsec: fix replay protection at XPN lower-PN wrap (CVE-2026-63925)
In the Linux kernel, the following vulnerability has been resolved:
bpf: sockmap: fix tail fragment offset in bpf_msg_push_data
When bpf_msg_push_data() inserts data in the middle of a scatterlistentry, it splits the original entry into a left fragment and a rightfragment.
The right fragment offset is page-local, but the code advances it with`start`, which is the message-global insertion point. For inserts into anon-first SG entry, this over-advances the offset and leaves the splitlayout inconsistent.
Advance the right fragment offset by the fragment-local delta,`start - offset`, which matches the length removed from the front of theoriginal entry. (CVE-2026-63926)
In the Linux kernel, the following vulnerability has been resolved:
ipv6: fix possible infinite loop in fib6_select_path() (CVE-2026-63968)
In the Linux kernel, the following vulnerability has been resolved:
ipv6: fix possible infinite loop in rt6_fill_node() (CVE-2026-63969)
In the Linux kernel, the following vulnerability has been resolved:
sctp: fix race between sctp_wait_for_connect and peeloff
sctp_wait_for_connect() drops and re-acquires the socket lock whilewaiting for the association to reach ESTABLISHED state. During thiswindow, another thread can peeloff the association to a new socket viagetsockopt(SCTP_SOCKOPT_PEELOFF), changing asoc->base.sk. Afterre-acquiring the old socket lock, sctp_wait_for_connect() returnssuccess without noticing the migration -- the caller then accessesthe association under the wrong lock in sctp_datamsg_from_user().
Add the same sk != asoc->base.sk check that sctp_wait_for_sndbuf()already has, returning an error if the association was migrated whilewe slept. (CVE-2026-63971)
In the Linux kernel, the following vulnerability has been resolved:
ipv6: rpl: fix hdrlen overflow in ipv6_rpl_srh_decompress() (CVE-2026-63984)
In the Linux kernel, the following vulnerability has been resolved:
ethtool: eeprom: add more safeties to EEPROM Netlink fallback (CVE-2026-63985)
In the Linux kernel, the following vulnerability has been resolved:
bonding: refuse to enslave CAN devices (CVE-2026-63990)
In the Linux kernel, the following vulnerability has been resolved:
tunnels: do not assume transport header in iptunnel_pmtud_check_icmp() (CVE-2026-63992)
In the Linux kernel, the following vulnerability has been resolved:
vxlan: do not reuse cached ip_hdr() value after skb_tunnel_check_pmtu() (CVE-2026-63993)
In the Linux kernel, the following vulnerability has been resolved:
tunnels: load network headers after skb_cow() in iptunnel_pmtud_build_icmp[v6]() (CVE-2026-63994)
In the Linux kernel, the following vulnerability has been resolved:
net/smc: Do not re-initialize smc hashtables (CVE-2026-64005)
In the Linux kernel, the following vulnerability has been resolved:
netfilter: synproxy: refresh tcphdr after skb_ensure_writable
synproxy_tstamp_adjust() rewrites the TCP timestamp option in placeand then patches the TCP checksum via inet_proto_csum_replace4() onthe caller-supplied tcphdr pointer. Both ipv4_synproxy_hook() andipv6_synproxy_hook() obtain that pointer with skb_header_pointer()before calling in, so it may either alias skb->head directly orpoint at the caller's on-stack _tcph buffer.
Between obtaining the pointer and using it, the function callsskb_ensure_writable(skb, optend), which on a cloned or non-linearskb invokes pskb_expand_head() and frees the old skb->head. Afterthat point the cached th is stale:
caller (ipv[46]_synproxy_hook)th = skb_header_pointer(skb, ..., &_tcph)synproxy_tstamp_adjust(skb, protoff, th, ...)skb_ensure_writable(skb, optend)pskb_expand_head() /* kfree(old skb->head)
*/...inet_proto_csum_replace4(&th->check, ...)/* writes into freed head, orinto the caller's stack copyleaving the on-wire checksumstale */
The option bytes are written through skb->data and are fine; onlythe checksum update goes through th and so lands in the wrongplace. The result is either a write into freed slab memory or apacket leaving with a checksum that does not match its payload.
Fix by re-deriving th from skb->data + protoff immediately afterskb_ensure_writable() succeeds, so the subsequent checksum updatetargets the linear, writable header. (CVE-2026-64007)
In the Linux kernel, the following vulnerability has been resolved:
xfrm: Check for underflow in xfrm_state_mtu (CVE-2026-64009)
In the Linux kernel, the following vulnerability has been resolved:
net/sched: sch_sfb: Replace direct dequeue call with peek and qdisc_dequeue_peeked (CVE-2026-64012)
In the Linux kernel, the following vulnerability has been resolved:
ipv6: ioam: add NULL check for idev in ipv6_hop_ioam() (CVE-2026-64116)
In the Linux kernel, the following vulnerability has been resolved:
mm/memory: fix spurious warning when unmapping device-private/exclusive pages (CVE-2026-64131)
Tenable has extracted the preceding description block directly from the tested product security advisory.
Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.
Solution
Run 'dnf update kernel --releasever 2023.12.20260706' or or 'dnf update --advisory ALAS2023-2026-1924 --releasever 2023.12.20260706' to update your system.
Plugin Details
File Name: al2023_ALAS2023-2026-1924.nasl
Agent: unix
Supported Sensors: Agentless Assessment, Continuous Assessment, Frictionless Assessment Agent, Frictionless Assessment AWS, Nessus Agent, Tenable Cloud Security, Tenable Self-Hosted Container Security, Nessus
Risk Information
Vector: CVSS2#AV:L/AC:L/Au:S/C:N/I:N/A:C
Vector: CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Temporal Vector: CVSS:3.0/E:P/RL:O/RC:C
Vulnerability Information
CPE: cpe:/o:amazon:linux:2023, p-cpe:/a:amazon:linux:bpftool-debuginfo, p-cpe:/a:amazon:linux:bpftool, p-cpe:/a:amazon:linux:kernel-debuginfo-common-aarch64, p-cpe:/a:amazon:linux:kernel-debuginfo-common-x86_64, p-cpe:/a:amazon:linux:kernel-debuginfo, p-cpe:/a:amazon:linux:kernel-devel, p-cpe:/a:amazon:linux:kernel-headers, p-cpe:/a:amazon:linux:kernel-livepatch-6.1.176-220.358, p-cpe:/a:amazon:linux:kernel-modules-extra-common, p-cpe:/a:amazon:linux:kernel-modules-extra, p-cpe:/a:amazon:linux:kernel-tools-debuginfo, p-cpe:/a:amazon:linux:kernel-tools-devel, p-cpe:/a:amazon:linux:kernel-tools, p-cpe:/a:amazon:linux:kernel, p-cpe:/a:amazon:linux:perf-debuginfo, p-cpe:/a:amazon:linux:perf, p-cpe:/a:amazon:linux:python3-perf-debuginfo, p-cpe:/a:amazon:linux:python3-perf
Required KB Items: Host/local_checks_enabled, Host/AmazonLinux/release, Host/AmazonLinux/rpm-list
Exploit Ease: Exploits are available
Patch Publication Date: 7/7/2026
Vulnerability Publication Date: 5/8/2026
Reference Information
CVE: CVE-2026-43303, CVE-2026-43492, CVE-2026-45850, CVE-2026-45991, CVE-2026-45999, CVE-2026-46005, CVE-2026-46021, CVE-2026-46052, CVE-2026-46065, CVE-2026-46086, CVE-2026-46116, CVE-2026-46137, CVE-2026-46159, CVE-2026-46160, CVE-2026-46193, CVE-2026-46195, CVE-2026-46196, CVE-2026-46292, CVE-2026-46320, CVE-2026-46321, CVE-2026-46322, CVE-2026-52910, CVE-2026-52923, CVE-2026-52924, CVE-2026-52927, CVE-2026-52929, CVE-2026-52930, CVE-2026-52942, CVE-2026-52943, CVE-2026-52946, CVE-2026-53131, CVE-2026-53133, CVE-2026-53134, CVE-2026-53168, CVE-2026-53183, CVE-2026-53184, CVE-2026-53189, CVE-2026-53199, CVE-2026-53207, CVE-2026-53212, CVE-2026-53218, CVE-2026-53219, CVE-2026-53221, CVE-2026-53223, CVE-2026-53225, CVE-2026-53227, CVE-2026-53228, CVE-2026-53236, CVE-2026-53238, CVE-2026-53239, CVE-2026-53245, CVE-2026-53249, CVE-2026-53264, CVE-2026-53266, CVE-2026-53268, CVE-2026-53269, CVE-2026-53270, CVE-2026-53275, CVE-2026-53337, CVE-2026-53349, CVE-2026-53352, CVE-2026-53354, CVE-2026-53356, CVE-2026-63867, CVE-2026-63868, CVE-2026-63875, CVE-2026-63884, CVE-2026-63889, CVE-2026-63912, CVE-2026-63913, CVE-2026-63914, CVE-2026-63917, CVE-2026-63919, CVE-2026-63920, CVE-2026-63921, CVE-2026-63922, CVE-2026-63924, CVE-2026-63925, CVE-2026-63926, CVE-2026-63968, CVE-2026-63969, CVE-2026-63971, CVE-2026-63984, CVE-2026-63985, CVE-2026-63990, CVE-2026-63992, CVE-2026-63993, CVE-2026-63994, CVE-2026-64005, CVE-2026-64007, CVE-2026-64009, CVE-2026-64012, CVE-2026-64116, CVE-2026-64131