Amazon Linux 2023 : bpftool6.12, kernel6.12, kernel6.12-devel (ALAS2023-2026-1894)

high Nessus Plugin ID 322107

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-1894 advisory.

In the Linux kernel, the following vulnerability has been resolved:

fs/ntfs3: handle attr_set_size() errors when truncating files (CVE-2025-71289)

In the Linux kernel, the following vulnerability has been resolved:

netfilter: nf_tables: unconditionally bump set->nelems before insertion (CVE-2026-23272)

In the Linux kernel, the following vulnerability has been resolved:

smb: client: fix OOB reads parsing symlink error response (CVE-2026-31613)

In the Linux kernel, the following vulnerability has been resolved:

xfrm: hold dev ref until after transport_finish NF_HOOK (CVE-2026-31663)

In the Linux kernel, the following vulnerability has been resolved:

rtnetlink: add missing netlink_ns_capable() check for peer netns (CVE-2026-31692)

In the Linux kernel, the following vulnerability has been resolved:

net: ioam6: fix OOB and missing lock (CVE-2026-43083)

In the Linux kernel, the following vulnerability has been resolved:

netfilter: ctnetlink: ensure safe access to master conntrack (CVE-2026-43116)

In the Linux kernel, the following vulnerability has been resolved:

ntfs: ->d_compare() must not block (CVE-2026-43245)

In the Linux kernel, the following vulnerability has been resolved:

bpf: fix end-of-list detection in cgroup_storage_get_next_key() (CVE-2026-45838)

In the Linux kernel, the following vulnerability has been resolved:

bpf: reject negative CO-RE accessor indices in bpf_core_parse_spec() (CVE-2026-45839)

In the Linux kernel, the following vulnerability has been resolved:

openvswitch: cap upcall PID array size and pre-size vport replies (CVE-2026-45840)

In the Linux kernel, the following vulnerability has been resolved:

netfilter: nfnetlink_osf: fix divide-by-zero in OSF_WSS_MODULO (CVE-2026-45841)

In the Linux kernel, the following vulnerability has been resolved:

slip: reject VJ receive packets on instances with no rstate array (CVE-2026-45842)

In the Linux kernel, the following vulnerability has been resolved:

slip: bound decode() reads against the compressed packet length (CVE-2026-45843)

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:

mptcp: pm: ADD_ADDR rtx: always decrease sk refcount (CVE-2026-46158)

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:

mptcp: pm: ADD_ADDR rtx: free sk if last (CVE-2026-46170)

In the Linux kernel, the following vulnerability has been resolved:

netfilter: nft_inner: Fix IPv6 inner_thoff desync (CVE-2026-46244)

In the Linux kernel, the following vulnerability has been resolved:

io-wq: check that the predecessor is hashed in io_wq_remove_pending() (CVE-2026-46274)

In the Linux kernel, the following vulnerability has been resolved:

io_uring/waitid: clear waitid info before copying it to userspace (CVE-2026-46315)

In the Linux kernel, the following vulnerability has been resolved:

KVM: arm64: vgic-its: Drop the translation cache reference only for the erased entry (CVE-2026-46316)

In the Linux kernel, the following vulnerability has been resolved:

netfilter: nf_queue: hold bridge skb->dev while queued (CVE-2026-52912)

In the Linux kernel, the following vulnerability has been resolved:

netfilter: ip6t_hbh: reject oversized option lists (CVE-2026-52915)

In the Linux kernel, the following vulnerability has been resolved:

netfilter: xt_policy: fix strict mode inbound policy matching (CVE-2026-52920)

In the Linux kernel, the following vulnerability has been resolved:

netfilter: ipset: stop hash:* range iteration at end (CVE-2026-52921)

In the Linux kernel, the following vulnerability has been resolved:

vrf: Fix a potential NPD when removing a port from a VRF (CVE-2026-52925)

In the Linux kernel, the following vulnerability has been resolved:

crypto: jitterentropy - replace long-held spinlock with mutex (CVE-2026-52936)

In the Linux kernel, the following vulnerability has been resolved:

libceph: handle rbtree insertion error in decode_choose_args() (CVE-2026-52954)

In the Linux kernel, the following vulnerability has been resolved:

libceph: Fix potential out-of-bounds access in crush_decode() (CVE-2026-52955)

In the Linux kernel, the following vulnerability has been resolved:

libceph: Fix potential null-ptr-deref in decode_choose_args() (CVE-2026-52957)

In the Linux kernel, the following vulnerability has been resolved:

libceph: Fix potential out-of-bounds access in osdmap_decode() (CVE-2026-52958)

In the Linux kernel, the following vulnerability has been resolved:

ceph: fix BUG_ON in __ceph_build_xattrs_blob() due to stale blob size (CVE-2026-52961)

In the Linux kernel, the following vulnerability has been resolved:

ceph: fix a buffer leak in __ceph_setxattr() (CVE-2026-52962)

In the Linux kernel, the following vulnerability has been resolved:

smb/client: fix possible infinite loop and oob read in symlink_data() (CVE-2026-52967)

In the Linux kernel, the following vulnerability has been resolved:

KVM: Reject wrapped offset in kvm_reset_dirty_gfn() (CVE-2026-52969)

In the Linux kernel, the following vulnerability has been resolved:

netfilter: nft_ct: fix missing expect put in obj eval (CVE-2026-52970)

In the Linux kernel, the following vulnerability has been resolved:

crypto: af_alg - Cap AEAD AD length to 0x80000000 (CVE-2026-52972)

In the Linux kernel, the following vulnerability has been resolved:

net: tls: fix strparser anchor skb leak on offload RX setup failure (CVE-2026-52974)

In the Linux kernel, the following vulnerability has been resolved:

futex: Prevent lockup in requeue-PI during signal/ timeout wakeup (CVE-2026-52977)

In the Linux kernel, the following vulnerability has been resolved:

sched/fair: Clear rel_deadline when initializing forked entities (CVE-2026-52980)

In the Linux kernel, the following vulnerability has been resolved:

neigh: let neigh_xmit take skb ownership (CVE-2026-52981)

In the Linux kernel, the following vulnerability has been resolved:

net/sched: netem: fix queue limit check to include reordered packets

The queue limit check in netem_enqueue() uses q->t_len which onlycounts packets in the internal tfifo.
Packets placed in sch->q bythe reorder path (__qdisc_enqueue_head) are not counted, allowingthe total queue occupancy to exceed sch->limit under reordering.

Include sch->q.qlen in the limit check. (CVE-2026-52984)

In the Linux kernel, the following vulnerability has been resolved:

netdevsim: zero initialize struct iphdr in dummy sk_buff (CVE-2026-52985)

In the Linux kernel, the following vulnerability has been resolved:

netfilter: nf_conntrack_sip: don't use simple_strtoul (CVE-2026-52986)

In the Linux kernel, the following vulnerability has been resolved:

fsnotify: fix inode reference leak in fsnotify_recalc_mask() (CVE-2026-52990)

In the Linux kernel, the following vulnerability has been resolved:

tipc: fix double-free in tipc_buf_append() (CVE-2026-52993)

In the Linux kernel, the following vulnerability has been resolved:

net/rds: zero per-item info buffer before handing it to visitors (CVE-2026-52995)

In the Linux kernel, the following vulnerability has been resolved:

netfilter: nfnetlink_osf: fix potential NULL dereference in ttl check (CVE-2026-52998)

In the Linux kernel, the following vulnerability has been resolved:

netfilter: nfnetlink_osf: fix out-of-bounds read on option matching (CVE-2026-52999)

In the Linux kernel, the following vulnerability has been resolved:

netfilter: xtables: restrict several matches to inet family (CVE-2026-53001)

In the Linux kernel, the following vulnerability has been resolved:

netfilter: conntrack: remove sprintf usage (CVE-2026-53002)

In the Linux kernel, the following vulnerability has been resolved:

pppoe: drop PFC frames (CVE-2026-53003)

In the Linux kernel, the following vulnerability has been resolved:

sctp: fix OOB write to userspace in sctp_getsockopt_peer_auth_chunks (CVE-2026-53004)

In the Linux kernel, the following vulnerability has been resolved:

ipv6: fix possible UAF in icmpv6_rcv() (CVE-2026-53006)

In the Linux kernel, the following vulnerability has been resolved:

ice: fix double-free of tx_buf skb (CVE-2026-53009)

In the Linux kernel, the following vulnerability has been resolved:

nexthop: fix IPv6 route referencing IPv4 nexthop (CVE-2026-53012)

In the Linux kernel, the following vulnerability has been resolved:

macvlan: fix macvlan_get_size() not reserving space for IFLA_MACVLAN_BC_CUTOFF (CVE-2026-53013)

In the Linux kernel, the following vulnerability has been resolved:

net/sched: act_mirred: fix wrong device for mac_header_xmit check in tcf_blockcast_redir (CVE-2026-53014)

In the Linux kernel, the following vulnerability has been resolved:

erofs: unify lcn as u64 for 32-bit platforms (CVE-2026-53015)

In the Linux kernel, the following vulnerability has been resolved:

scsi: target: core: Fix integer overflow in UNMAP bounds check (CVE-2026-53021)

In the Linux kernel, the following vulnerability has been resolved:

fs/ntfs3: terminate the cached volume label after UTF-8 conversion (CVE-2026-53023)

In the Linux kernel, the following vulnerability has been resolved:

bpf: Validate node_id in arena_alloc_pages() (CVE-2026-53031)

In the Linux kernel, the following vulnerability has been resolved:

bpf: Fix NULL deref in map_kptr_match_type for scalar regs (CVE-2026-53032)

In the Linux kernel, the following vulnerability has been resolved:

bpf, sockmap: Take state lock for af_unix iter (CVE-2026-53033)

In the Linux kernel, the following vulnerability has been resolved:

bpf, sockmap: Fix af_unix null-ptr-deref in proto update (CVE-2026-53034)

In the Linux kernel, the following vulnerability has been resolved:

bpf, sockmap: Fix af_unix iter deadlock (CVE-2026-53035)

In the Linux kernel, the following vulnerability has been resolved:

bpf, arm64: Fix off-by-one in check_imm signed range check (CVE-2026-53036)

In the Linux kernel, the following vulnerability has been resolved:

HID: usbhid: fix deadlock in hid_post_reset() (CVE-2026-53037)

In the Linux kernel, the following vulnerability has been resolved:

ima_fs: Correctly create securityfs files for unsupported hash algos (CVE-2026-53038)

In the Linux kernel, the following vulnerability has been resolved:

quota: Fix race of dquot_scan_active() with quota deactivation (CVE-2026-53050)

In the Linux kernel, the following vulnerability has been resolved:

iommu/amd: Fix clone_alias() to use the original device's devid (CVE-2026-53053)

In the Linux kernel, the following vulnerability has been resolved:

dm log: fix out-of-bounds write due to region_count overflow (CVE-2026-53059)

In the Linux kernel, the following vulnerability has been resolved:

dm cache metadata: fix memory leak on metadata abort retry (CVE-2026-53060)

In the Linux kernel, the following vulnerability has been resolved:

dm cache: fix dirty mapping checking in passthrough mode switching (CVE-2026-53061)

In the Linux kernel, the following vulnerability has been resolved:

dm cache policy smq: fix missing locks in invalidating cache blocks (CVE-2026-53062)

In the Linux kernel, the following vulnerability has been resolved:

dm cache: fix write hang in passthrough mode (CVE-2026-53063)

In the Linux kernel, the following vulnerability has been resolved:

dm cache: fix null-deref with concurrent writes in passthrough mode (CVE-2026-53064)

In the Linux kernel, the following vulnerability has been resolved:

net, bpf: fix null-ptr-deref in xdp_master_redirect() for down master (CVE-2026-53069)

In the Linux kernel, the following vulnerability has been resolved:

bpf: reject short IPv4/IPv6 inputs in bpf_prog_test_run_skb (CVE-2026-53074)

In the Linux kernel, the following vulnerability has been resolved:

ppp: require CAP_NET_ADMIN in target netns for unattached ioctls (CVE-2026-53075)

In the Linux kernel, the following vulnerability has been resolved:

bpf: Fix OOB in pcpu_init_value (CVE-2026-53076)

In the Linux kernel, the following vulnerability has been resolved:

net/rds: Restrict use of RDS/IB to the initial network namespace (CVE-2026-53077)

In the Linux kernel, the following vulnerability has been resolved:

bpf: Enforce regsafe base id consistency for BPF_ADD_CONST scalars (CVE-2026-53081)

In the Linux kernel, the following vulnerability has been resolved:

bpf: Fix RCU stall in bpf_fd_array_map_clear() (CVE-2026-53083)

In the Linux kernel, the following vulnerability has been resolved:

bpf: return VMA snapshot from task_vma iterator (CVE-2026-53084)

In the Linux kernel, the following vulnerability has been resolved:

bpf: fix mm lifecycle in open-coded task_vma iterator (CVE-2026-53085)

In the Linux kernel, the following vulnerability has been resolved:

bpf: Fix stale offload->prog pointer after constant blinding (CVE-2026-53094)

In the Linux kernel, the following vulnerability has been resolved:

bpf: Use RCU-safe iteration in dev_map_redirect_multi() SKB path (CVE-2026-53096)

In the Linux kernel, the following vulnerability has been resolved:

bpf: test_run: Fix the null pointer dereference issue in bpf_lwt_xmit_push_encap (CVE-2026-53111)

In the Linux kernel, the following vulnerability has been resolved:

platform/wmi: use generic driver_override infrastructure (CVE-2026-53119)

In the Linux kernel, the following vulnerability has been resolved:

PCI: use generic driver_override infrastructure (CVE-2026-53120)

In the Linux kernel, the following vulnerability has been resolved:

btrfs: fix deadlock between reflink and transaction commit when using flushoncommit (CVE-2026-53122)

In the Linux kernel, the following vulnerability has been resolved:

md: wake raid456 reshape waiters before suspend (CVE-2026-53123)

In the Linux kernel, the following vulnerability has been resolved:

blk-cgroup: fix disk reference leak in blkcg_maybe_throttle_current() (CVE-2026-53126)

In the Linux kernel, the following vulnerability has been resolved:

drbd: Balance RCU calls in drbd_adm_dump_devices() (CVE-2026-53128)

In the Linux kernel, the following vulnerability has been resolved:

fs/mbcache: cancel shrink work before destroying the cache (CVE-2026-53129)

In the Linux kernel, the following vulnerability has been resolved:

audit: fix incorrect inheritable capability in CAPSET records

__audit_log_capset() records the effective capability set into theinheritable field due to a copy-paste error. Every CAPSET auditrecord therefore reports cap_pi (process inheritable) with the valueof cap_effective instead of cap_inheritable.

This silently corrupts audit data used for compliance and forensicanalysis: an attacker who modifies inheritable capabilities toprepare for a privilege-escalating exec would have the change maskedin the audit trail.

The bug has been present since the original introduction of CAPSETaudit records in 2008. (CVE-2026-53287)

In the Linux kernel, the following vulnerability has been resolved:

arm64: Reserve an extra page for early kernel mapping (CVE-2026-53288)

In the Linux kernel, the following vulnerability has been resolved:

ice: fix NULL pointer dereference in ice_reset_all_vfs() (CVE-2026-53289)

In the Linux kernel, the following vulnerability has been resolved:

mailbox: add sanity check for channel array

Fail gracefully if there is no channel array attached to the mailboxcontroller. Otherwise the later dereference will cause an OOPS whichmight not be seen because mailbox controllers might instantiate veryearly. Remove the comment explaining the obvious while here. (CVE-2026-53295)

In the Linux kernel, the following vulnerability has been resolved:

scsi: sg: Resolve soft lockup issue when opening /dev/sgX (CVE-2026-53304)

In the Linux kernel, the following vulnerability has been resolved:

padata: Put CPU offline callback in ONLINE section to allow failure

syzbot reported the following warning:

DEAD callback error for CPU1WARNING: kernel/cpu.c:1463 at _cpu_down+0x759/0x1020 kernel/cpu.c:1463, CPU#0:
syz.0.1960/14614

at commit 4ae12d8bd9a8 (Merge tag 'kbuild-fixes-7.0-2' of git://git.kernel.org/pub/scm/linux/kernel/git/kbuild/linux)which tglx traced to padata_cpu_dead() given it's the onlysub-CPUHP_TEARDOWN_CPU callback that returns an error.

Failure isn't allowed in hotplug states before CPUHP_TEARDOWN_CPUso move the CPU offline callback to the ONLINE section where failure ispossible. (CVE-2026-53314)

In the Linux kernel, the following vulnerability has been resolved:

RDMA/core: Prefer NLA_NUL_STRING

These attributes are evaluated as c-string (passed to strcmp), butNLA_STRING doesn't check for the presence of a \0 terminator.

Either this needs to switch to nla_strcmp() and needs to adjust printf fmtspecifier to not use plain %s, or this needs to use NLA_NUL_STRING.

As the code has been this way for long time, it seems to me that userspacedoes include the terminating nul, even tough its not enforced so far, andthus NLA_NUL_STRING use is the simpler solution.
(CVE-2026-63860)

In the Linux kernel, the following vulnerability has been resolved:

bpf: Drop task_to_inode and inet_conn_established from lsm sleepable hooks (CVE-2026-63865)

In the Linux kernel, the following vulnerability has been resolved:

security/keys: fix missed RCU read section on lookup

Nicholas Carlini reports that the keyring code calls assoc_array_find()in find_key_to_update() without holding the RCU read lock, while theassoc_array_gc() code really is designed around removing the node fromthe tree and then freeing it after an RCU grace-period.

The regular key handling doesn't see this because holding the keyringsemaphore hides any lifetime issues, but the persistent key handlinguses a different model.

Instead of extending the keyring locking, just do the simple RCU lockingthat the assoc_array was designed for. (CVE-2026-64015)

In the Linux kernel, the following vulnerability has been resolved:

bpf, skmsg: fix verdict sk_data_ready racing with ktls rx

sk_psock_strp_data_ready() already checks tls_sw_has_ctx_rx() anddefers to psock->saved_data_ready when a TLS RX context is present,avoiding a conflict with the TLS strparser's ownership of the receivequeue (commit e91de6afa81c, bpf: Fix running sk_skb program typeswith ktls).

sk_psock_verdict_data_ready() has no equivalent guard. When a socketis inserted into a sockmap (BPF_SK_SKB_VERDICT) before TLS RX isconfigured, tls_sw_strparser_arm() saves sk_psock_verdict_data_readyas rx_ctx->saved_data_ready. On data arrival:

tls_data_ready -> tls_strp_data_ready -> tls_rx_msg_ready-> saved_data_ready() = sk_psock_verdict_data_ready()-> tcp_read_skb() drains sk_receive_queue via __skb_unlink()without calling tcp_eat_skb(), so copied_seq is not advanced.

tls_strp_msg_load() then finds tcp_inq() >= full_len (stale), callstcp_recv_skb() on the now-empty queue, hits WARN_ON_ONCE(!first), andreturns with rx_ctx->strp.anchor.frag_list pointing at a psock- owned(potentially freed) skb. tls_decrypt_sg() subsequently walks thatfrag_list: use-after-free.

Apply the same fix as sk_psock_strp_data_ready(): if a TLS RX contextis present, call psock->saved_data_ready (sock_def_readable) to wakerecv() waiters and return immediately, leaving the receive queueuntouched. TLS retains sole ownership of the queue and decrypts therecord normally through tls_sw_recvmsg(). (CVE-2026-64025)

In the Linux kernel, the following vulnerability has been resolved:

bridge: mcast: Fix a possible use-after-free when removing a bridge port (CVE-2026-64032)

In the Linux kernel, the following vulnerability has been resolved:

net: tls: prevent chain-after-chain in plain text SG (CVE-2026-64046)

In the Linux kernel, the following vulnerability has been resolved:

net: tls: fix off-by-one in sg_chain entry count for wrapped sk_msg ring

When an sk_msg scatterlist ring wraps (sg.end < sg.start),tls_push_record() chains the tail portion of the ring to the headusing sg_chain(). An extra entry in the sg array is reserved forthis:

struct sk_msg_sg {[...]/* The extra two elements:* 1) used for chaining the front and sections when the list becomes* partitioned (e.g. end < start). The crypto APIs require the* chaining;* 2) to chain tailer SG entries after the message.*/struct scatterlist data[MAX_MSG_FRAGS + 2];

The current code uses MAX_SKB_FRAGS + 1 as the ring size:

sg_chain(&msg_pl->sg.data[msg_pl->sg.start],MAX_SKB_FRAGS - msg_pl->sg.start + 1,msg_pl->sg.data);

This places the chain pointer at

sg_chain(data[start], (MAX_SKB_FRAGS - msg_start + 1) .. =&data[start] + (MAX_SKB_FRAGS - msg_start + 1) - 1 =data[start + (MAX_SKB_FRAGS - start + 1) - 1] =data[MAX_SKB_FRAGS]

instead of the true last entry. This is likely due to a race ofthe commit under Fixes landing close tocommit 031097d9e079 (bpf: sk_msg, zap ingress queue on psock down)

Convert to ARRAY_SIZE and drop the data[start] / - start (as suggestedby Sabrina). (CVE-2026-64047)

In the Linux kernel, the following vulnerability has been resolved:

block: bio-integrity: Fix null-ptr-deref in bio_integrity_map_user() (CVE-2026-64052)

In the Linux kernel, the following vulnerability has been resolved:

block: don't overwrite bip_vcnt in bio_integrity_copy_user() (CVE-2026-64053)

In the Linux kernel, the following vulnerability has been resolved:

netfs: Fix folio->private handling in netfs_perform_write() (CVE-2026-64059)

In the Linux kernel, the following vulnerability has been resolved:

netfs: Fix early put of sink folio in netfs_read_gaps() (CVE-2026-64061)

In the Linux kernel, the following vulnerability has been resolved:

netfs: Fix potential deadlock in write-through mode (CVE-2026-64062)

In the Linux kernel, the following vulnerability has been resolved:

netfs: Fix streaming write being overwritten (CVE-2026-64063)

In the Linux kernel, the following vulnerability has been resolved:

netfs: Fix netfs_invalidate_folio() to clear dirty bit if all changes gone (CVE-2026-64064)

In the Linux kernel, the following vulnerability has been resolved:

netfs: fix VM_BUG_ON_FOLIO() issue in netfs_write_begin() call (CVE-2026-64065)

In the Linux kernel, the following vulnerability has been resolved:

irq_work: Fix use-after-free in irq_work_single() on PREEMPT_RT (CVE-2026-64073)

In the Linux kernel, the following vulnerability has been resolved:

drm/virtio: use uninterruptible resv lock for plane updates (CVE-2026-64098)

In the Linux kernel, the following vulnerability has been resolved:

KVM: arm64: vgic: Free private_irqs when init fails after allocation (CVE-2026-64105)

In the Linux kernel, the following vulnerability has been resolved:

KVM: arm64: vgic-its: Reject restored DTE with out-of-range num_eventid_bits

Userspace can restore an ITS Device Table Entry whose Size field encodesmore EventID bits than the virtual ITS supports. The live MAPD pathrejects that state, but vgic_its_restore_dte() accepts it and stores theout-of-range value in dev->num_eventid_bits.

Reject restored DTEs with num_eventid_bits > VITS_TYPER_IDBITS beforeallocating the device. This mirrors the MAPD check and prevents therestored state from reaching vgic_its_restore_itt(), where the uncheckedvalue can be converted into an oversized scan_its_table() range. (CVE-2026-64106)

In the Linux kernel, the following vulnerability has been resolved:

cifs: Fix busy dentry used after unmounting (CVE-2026-64108)

In the Linux kernel, the following vulnerability has been resolved:

af_unix: Fix UAF read of tail->len in unix_stream_data_wait() (CVE-2026-64109)

In the Linux kernel, the following vulnerability has been resolved:

lsm: hold cred_guard_mutex for lsm_set_self_attr() (CVE-2026-64111)

In the Linux kernel, the following vulnerability has been resolved:

rbd: eliminate a race in lock_dwork draining on unmap (CVE-2026-64112)

In the Linux kernel, the following vulnerability has been resolved:

ixgbevf: fix use-after-free in VEPA multicast source pruning

ixgbevf_clean_rx_irq() prunes frames whose source MAC matches the VF'sown address (VEPA multicast workaround) by freeing the skb andcontinuing to the next descriptor:

dev_kfree_skb_irq(skb);continue;

The skb pointer is declared outside the while loop and persists acrossiterations. Because the continue skips the skb = NULL reset at thebottom of the loop, the next iteration enters the else if (skb) pathand calls ixgbevf_add_rx_frag() on the freed skb, dereferencingskb_shinfo(skb)->nr_frags - a use- after-free in NAPI softirq context.

The sibling driver iavf already handles this correctly by nulling thepointer before continuing. Apply the same pattern here.

I do not have ixgbevf hardware; the bug was found by static analysis(scan_drop_continue_loops.py + semgrep drop_continue_in_loop, multi-toolcorroboration with the highest score in the scan). The UAF was confirmedunder KASAN by loading a test module that reproduces the exact codepattern (alloc skb, kfree_skb, then read skb_shinfo(skb)->nr_frags):

BUG: KASAN: slab-use-after-free in ixgbevf_uaf_test_init+0x100/0x1000Read of size 8 at addr 000000006163ae78 by task insmod/30freed 208-byte region [000000006163adc0, 000000006163ae90)

QEMU emulates igb (82576) but not ixgbe (82599), and the igbvf VFdriver does not include the VEPA source pruning path, so a fullend-to-end reproduction with emulated hardware was not possible. (CVE-2026-64113)

In the Linux kernel, the following vulnerability has been resolved:

ipv4: raw: reject IP_HDRINCL packets with ihl < 5

raw_send_hdrinc() validates that the caller-supplied IPv4 headerfits within the message length:

iphlen = iph->ihl * 4;err = -EINVAL;if (iphlen > length)goto error_free;

if (iphlen >= sizeof(*iph)) {/* fix up saddr, tot_len, id, csum, transport_header */}

It does not, however, reject ihl < 5. For such a packet theif (iphlen >= sizeof(*iph)) branch is skipped, leaving thecrafted iphdr untouched, but the packet is still handed to__ip_local_out() and onward.
Downstream consumers that readiph->ihl assume a sane value: net/ipv4/ah4.c:ah_output() inparticular subtracts sizeof(struct iphdr) from top_iph->ihl * 4and passes the (signed-int-negative, then cast to size_t)result to memcpy(), producing an OOB access of length close toSIZE_MAX and a host kernel panic.

An IPv4 header with ihl < 5 is malformed by definition (RFC 791: ...

Please note that the description has been truncated due to length. Please refer to vendor advisory for the full description.

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 kernel6.12 --releasever 2023.12.20260622' or or 'dnf update --advisory ALAS2023-2026-1894 --releasever 2023.12.20260622' to update your system.

See Also

https://alas.aws.amazon.com//AL2023/ALAS2023-2026-1894.html

https://alas.aws.amazon.com/faqs.html

https://explore.alas.aws.amazon.com/CVE-2025-71289.html

https://explore.alas.aws.amazon.com/CVE-2026-23272.html

https://explore.alas.aws.amazon.com/CVE-2026-31613.html

https://explore.alas.aws.amazon.com/CVE-2026-31663.html

https://explore.alas.aws.amazon.com/CVE-2026-31692.html

https://explore.alas.aws.amazon.com/CVE-2026-43083.html

https://explore.alas.aws.amazon.com/CVE-2026-43116.html

https://explore.alas.aws.amazon.com/CVE-2026-43245.html

https://explore.alas.aws.amazon.com/CVE-2026-45838.html

https://explore.alas.aws.amazon.com/CVE-2026-45839.html

https://explore.alas.aws.amazon.com/CVE-2026-45840.html

https://explore.alas.aws.amazon.com/CVE-2026-45841.html

https://explore.alas.aws.amazon.com/CVE-2026-45842.html

https://explore.alas.aws.amazon.com/CVE-2026-45843.html

https://explore.alas.aws.amazon.com/CVE-2026-46137.html

https://explore.alas.aws.amazon.com/CVE-2026-46158.html

https://explore.alas.aws.amazon.com/CVE-2026-46160.html

https://explore.alas.aws.amazon.com/CVE-2026-46170.html

https://explore.alas.aws.amazon.com/CVE-2026-46244.html

https://explore.alas.aws.amazon.com/CVE-2026-46274.html

https://explore.alas.aws.amazon.com/CVE-2026-46315.html

https://explore.alas.aws.amazon.com/CVE-2026-46316.html

https://explore.alas.aws.amazon.com/CVE-2026-52912.html

https://explore.alas.aws.amazon.com/CVE-2026-52915.html

https://explore.alas.aws.amazon.com/CVE-2026-52920.html

https://explore.alas.aws.amazon.com/CVE-2026-52921.html

https://explore.alas.aws.amazon.com/CVE-2026-52925.html

https://explore.alas.aws.amazon.com/CVE-2026-52936.html

https://explore.alas.aws.amazon.com/CVE-2026-52954.html

https://explore.alas.aws.amazon.com/CVE-2026-52955.html

https://explore.alas.aws.amazon.com/CVE-2026-52957.html

https://explore.alas.aws.amazon.com/CVE-2026-52958.html

https://explore.alas.aws.amazon.com/CVE-2026-52961.html

https://explore.alas.aws.amazon.com/CVE-2026-52962.html

https://explore.alas.aws.amazon.com/CVE-2026-52967.html

https://explore.alas.aws.amazon.com/CVE-2026-52969.html

https://explore.alas.aws.amazon.com/CVE-2026-52970.html

https://explore.alas.aws.amazon.com/CVE-2026-52972.html

https://explore.alas.aws.amazon.com/CVE-2026-52974.html

https://explore.alas.aws.amazon.com/CVE-2026-52977.html

https://explore.alas.aws.amazon.com/CVE-2026-52980.html

https://explore.alas.aws.amazon.com/CVE-2026-52981.html

https://explore.alas.aws.amazon.com/CVE-2026-52984.html

https://explore.alas.aws.amazon.com/CVE-2026-52985.html

https://explore.alas.aws.amazon.com/CVE-2026-52986.html

https://explore.alas.aws.amazon.com/CVE-2026-52990.html

https://explore.alas.aws.amazon.com/CVE-2026-52993.html

https://explore.alas.aws.amazon.com/CVE-2026-52995.html

https://explore.alas.aws.amazon.com/CVE-2026-52998.html

https://explore.alas.aws.amazon.com/CVE-2026-52999.html

https://explore.alas.aws.amazon.com/CVE-2026-53001.html

https://explore.alas.aws.amazon.com/CVE-2026-53002.html

https://explore.alas.aws.amazon.com/CVE-2026-53003.html

https://explore.alas.aws.amazon.com/CVE-2026-53004.html

https://explore.alas.aws.amazon.com/CVE-2026-53006.html

https://explore.alas.aws.amazon.com/CVE-2026-53009.html

https://explore.alas.aws.amazon.com/CVE-2026-53012.html

https://explore.alas.aws.amazon.com/CVE-2026-53013.html

https://explore.alas.aws.amazon.com/CVE-2026-53014.html

https://explore.alas.aws.amazon.com/CVE-2026-53015.html

https://explore.alas.aws.amazon.com/CVE-2026-53021.html

https://explore.alas.aws.amazon.com/CVE-2026-53023.html

https://explore.alas.aws.amazon.com/CVE-2026-53031.html

https://explore.alas.aws.amazon.com/CVE-2026-53032.html

https://explore.alas.aws.amazon.com/CVE-2026-53033.html

https://explore.alas.aws.amazon.com/CVE-2026-53034.html

https://explore.alas.aws.amazon.com/CVE-2026-53035.html

https://explore.alas.aws.amazon.com/CVE-2026-53036.html

https://explore.alas.aws.amazon.com/CVE-2026-53037.html

https://explore.alas.aws.amazon.com/CVE-2026-53038.html

https://explore.alas.aws.amazon.com/CVE-2026-53050.html

https://explore.alas.aws.amazon.com/CVE-2026-53053.html

https://explore.alas.aws.amazon.com/CVE-2026-53059.html

https://explore.alas.aws.amazon.com/CVE-2026-53060.html

https://explore.alas.aws.amazon.com/CVE-2026-53061.html

https://explore.alas.aws.amazon.com/CVE-2026-53062.html

https://explore.alas.aws.amazon.com/CVE-2026-53063.html

https://explore.alas.aws.amazon.com/CVE-2026-53064.html

https://explore.alas.aws.amazon.com/CVE-2026-53069.html

https://explore.alas.aws.amazon.com/CVE-2026-53074.html

https://explore.alas.aws.amazon.com/CVE-2026-53075.html

https://explore.alas.aws.amazon.com/CVE-2026-53076.html

https://explore.alas.aws.amazon.com/CVE-2026-53077.html

https://explore.alas.aws.amazon.com/CVE-2026-53081.html

https://explore.alas.aws.amazon.com/CVE-2026-53083.html

https://explore.alas.aws.amazon.com/CVE-2026-53084.html

https://explore.alas.aws.amazon.com/CVE-2026-53085.html

https://explore.alas.aws.amazon.com/CVE-2026-53094.html

https://explore.alas.aws.amazon.com/CVE-2026-53096.html

https://explore.alas.aws.amazon.com/CVE-2026-53111.html

https://explore.alas.aws.amazon.com/CVE-2026-53119.html

https://explore.alas.aws.amazon.com/CVE-2026-53120.html

https://explore.alas.aws.amazon.com/CVE-2026-53122.html

https://explore.alas.aws.amazon.com/CVE-2026-53123.html

https://explore.alas.aws.amazon.com/CVE-2026-53126.html

https://explore.alas.aws.amazon.com/CVE-2026-53128.html

https://explore.alas.aws.amazon.com/CVE-2026-53129.html

https://explore.alas.aws.amazon.com/CVE-2026-53287.html

https://explore.alas.aws.amazon.com/CVE-2026-53288.html

https://explore.alas.aws.amazon.com/CVE-2026-53289.html

https://explore.alas.aws.amazon.com/CVE-2026-53295.html

https://explore.alas.aws.amazon.com/CVE-2026-53304.html

https://explore.alas.aws.amazon.com/CVE-2026-53314.html

https://explore.alas.aws.amazon.com/CVE-2026-63860.html

https://explore.alas.aws.amazon.com/CVE-2026-63865.html

https://explore.alas.aws.amazon.com/CVE-2026-64015.html

https://explore.alas.aws.amazon.com/CVE-2026-64025.html

https://explore.alas.aws.amazon.com/CVE-2026-64032.html

https://explore.alas.aws.amazon.com/CVE-2026-64046.html

https://explore.alas.aws.amazon.com/CVE-2026-64047.html

https://explore.alas.aws.amazon.com/CVE-2026-64052.html

https://explore.alas.aws.amazon.com/CVE-2026-64053.html

https://explore.alas.aws.amazon.com/CVE-2026-64059.html

https://explore.alas.aws.amazon.com/CVE-2026-64061.html

https://explore.alas.aws.amazon.com/CVE-2026-64062.html

https://explore.alas.aws.amazon.com/CVE-2026-64063.html

https://explore.alas.aws.amazon.com/CVE-2026-64064.html

https://explore.alas.aws.amazon.com/CVE-2026-64065.html

https://explore.alas.aws.amazon.com/CVE-2026-64073.html

https://explore.alas.aws.amazon.com/CVE-2026-64098.html

https://explore.alas.aws.amazon.com/CVE-2026-64105.html

https://explore.alas.aws.amazon.com/CVE-2026-64106.html

https://explore.alas.aws.amazon.com/CVE-2026-64108.html

https://explore.alas.aws.amazon.com/CVE-2026-64109.html

https://explore.alas.aws.amazon.com/CVE-2026-64111.html

https://explore.alas.aws.amazon.com/CVE-2026-64112.html

https://explore.alas.aws.amazon.com/CVE-2026-64113.html

https://explore.alas.aws.amazon.com/CVE-2026-64114.html

https://explore.alas.aws.amazon.com/CVE-2026-64115.html

https://explore.alas.aws.amazon.com/CVE-2026-64116.html

https://explore.alas.aws.amazon.com/CVE-2026-64121.html

https://explore.alas.aws.amazon.com/CVE-2026-64132.html

https://explore.alas.aws.amazon.com/CVE-2026-64136.html

https://explore.alas.aws.amazon.com/CVE-2026-64153.html

https://explore.alas.aws.amazon.com/CVE-2026-64157.html

https://explore.alas.aws.amazon.com/CVE-2026-64158.html

https://explore.alas.aws.amazon.com/CVE-2026-64163.html

https://explore.alas.aws.amazon.com/CVE-2026-64164.html

https://explore.alas.aws.amazon.com/CVE-2026-64166.html

https://explore.alas.aws.amazon.com/CVE-2026-64180.html

https://explore.alas.aws.amazon.com/CVE-2026-64182.html

https://explore.alas.aws.amazon.com/CVE-2026-64183.html

https://explore.alas.aws.amazon.com/CVE-2026-64184.html

https://explore.alas.aws.amazon.com/CVE-2026-64185.html

https://explore.alas.aws.amazon.com/CVE-2026-64217.html

Plugin Details

Severity: High

ID: 322107

File Name: al2023_ALAS2023-2026-1894.nasl

Version: 1.3

Type: Local

Agent: unix

Published: 6/22/2026

Updated: 7/31/2026

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

VPR

Risk Factor: High

Score: 7.9

Percentile: 99.35

CVSS v2

Risk Factor: Medium

Base Score: 6.8

Temporal Score: 5.3

Vector: CVSS2#AV:L/AC:L/Au:S/C:C/I:C/A:C

CVSS Score Source: CVE-2026-53129

CVSS v3

Risk Factor: High

Base Score: 7.8

Temporal Score: 7

Vector: CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:bpftool6.12-debuginfo, p-cpe:/a:amazon:linux:bpftool6.12, p-cpe:/a:amazon:linux:kernel-livepatch-6.12.92-122.166, p-cpe:/a:amazon:linux:kernel6.12-debuginfo-common-aarch64, p-cpe:/a:amazon:linux:kernel6.12-debuginfo-common-x86_64, p-cpe:/a:amazon:linux:kernel6.12-debuginfo, p-cpe:/a:amazon:linux:kernel6.12-devel, p-cpe:/a:amazon:linux:kernel6.12-headers, p-cpe:/a:amazon:linux:kernel6.12-modules-extra-common, p-cpe:/a:amazon:linux:kernel6.12-modules-extra, p-cpe:/a:amazon:linux:kernel6.12-tools-debuginfo, p-cpe:/a:amazon:linux:kernel6.12-tools-devel, p-cpe:/a:amazon:linux:kernel6.12-tools, p-cpe:/a:amazon:linux:kernel6.12, p-cpe:/a:amazon:linux:perf6.12-debuginfo, p-cpe:/a:amazon:linux:perf6.12, p-cpe:/a:amazon:linux:python3-perf6.12-debuginfo, p-cpe:/a:amazon:linux:python3-perf6.12

Required KB Items: Host/local_checks_enabled, Host/AmazonLinux/release, Host/AmazonLinux/rpm-list

Exploit Available: true

Exploit Ease: Exploits are available

Patch Publication Date: 6/22/2026

Vulnerability Publication Date: 4/24/2026

Reference Information

CVE: CVE-2025-71289, CVE-2026-23272, CVE-2026-31613, CVE-2026-31663, CVE-2026-31692, CVE-2026-43083, CVE-2026-43116, CVE-2026-43245, CVE-2026-45838, CVE-2026-45839, CVE-2026-45840, CVE-2026-45841, CVE-2026-45842, CVE-2026-45843, CVE-2026-46137, CVE-2026-46158, CVE-2026-46160, CVE-2026-46170, CVE-2026-46244, CVE-2026-46274, CVE-2026-46315, CVE-2026-46316, CVE-2026-52912, CVE-2026-52915, CVE-2026-52920, CVE-2026-52921, CVE-2026-52925, CVE-2026-52936, CVE-2026-52954, CVE-2026-52955, CVE-2026-52957, CVE-2026-52958, CVE-2026-52961, CVE-2026-52962, CVE-2026-52967, CVE-2026-52969, CVE-2026-52970, CVE-2026-52972, CVE-2026-52974, CVE-2026-52977, CVE-2026-52980, CVE-2026-52981, CVE-2026-52984, CVE-2026-52985, CVE-2026-52986, CVE-2026-52990, CVE-2026-52993, CVE-2026-52995, CVE-2026-52998, CVE-2026-52999, CVE-2026-53001, CVE-2026-53002, CVE-2026-53003, CVE-2026-53004, CVE-2026-53006, CVE-2026-53009, CVE-2026-53012, CVE-2026-53013, CVE-2026-53014, CVE-2026-53015, CVE-2026-53021, CVE-2026-53023, CVE-2026-53031, CVE-2026-53032, CVE-2026-53033, CVE-2026-53034, CVE-2026-53035, CVE-2026-53036, CVE-2026-53037, CVE-2026-53038, CVE-2026-53050, CVE-2026-53053, CVE-2026-53059, CVE-2026-53060, CVE-2026-53061, CVE-2026-53062, CVE-2026-53063, CVE-2026-53064, CVE-2026-53069, CVE-2026-53074, CVE-2026-53075, CVE-2026-53076, CVE-2026-53077, CVE-2026-53081, CVE-2026-53083, CVE-2026-53084, CVE-2026-53085, CVE-2026-53094, CVE-2026-53096, CVE-2026-53111, CVE-2026-53119, CVE-2026-53120, CVE-2026-53122, CVE-2026-53123, CVE-2026-53126, CVE-2026-53128, CVE-2026-53129, CVE-2026-53287, CVE-2026-53288, CVE-2026-53289, CVE-2026-53295, CVE-2026-53304, CVE-2026-53314, CVE-2026-63860, CVE-2026-63865, CVE-2026-64015, CVE-2026-64025, CVE-2026-64032, CVE-2026-64046, CVE-2026-64047, CVE-2026-64052, CVE-2026-64053, CVE-2026-64059, CVE-2026-64061, CVE-2026-64062, CVE-2026-64063, CVE-2026-64064, CVE-2026-64065, CVE-2026-64073, CVE-2026-64098, CVE-2026-64105, CVE-2026-64106, CVE-2026-64108, CVE-2026-64109, CVE-2026-64111, CVE-2026-64112, CVE-2026-64113, CVE-2026-64114, CVE-2026-64115, CVE-2026-64116, CVE-2026-64121, CVE-2026-64132, CVE-2026-64136, CVE-2026-64153, CVE-2026-64157, CVE-2026-64158, CVE-2026-64163, CVE-2026-64164, CVE-2026-64166, CVE-2026-64180, CVE-2026-64182, CVE-2026-64183, CVE-2026-64184, CVE-2026-64185, CVE-2026-64217