In the Linux kernel, the following vulnerability has been resolved: x86/mm/pat: Acquire init_mm read lock on attribute changes to avoid UAF A previous commit protected against races between ptdump and CPA collapse, however one still exists between attribute changes and collapse as reported by Denis V. Lunev (linked). When an attribute change arises, a lockless page table walker obtains a PTE entry, which is later written to via set_pte_atomic(): ... -> change_page_attr_set_clr() -> __change_page_attr_set_clr() -> __change_page_attr() -> _lookup_address_cpa() -> lookup_address_in_pgd_attr() -> [ lockless page table walker ] -> set_pte_atomic() There is nothing preventing a concurrent CPA collapse which can free the PTE that was retrieved here, resulting in a use-after-free. With the mmap write lock taken on init_mm over CPA collapse, resolve this race by acquiring an mmap read lock on init_mm over __change_page_attr_set_clr(). This locks across the whole operation over which the walk and the PTE entry write occurs, solving the race. It is safe to do this here, as no spinlocks are held upon entry to __change_page_attr_set_clr(). However, the lock must not be held over an allocation, as allocation can trigger reclaim and shrinkers may call into CPA recursively, making deadlocks possible (init_mm -> ... -> fs_reclaim -> init_mm). A page table is allocated when a huge page needs to be split: -> change_page_attr_set_clr() -> __change_page_attr_set_clr() -> __change_page_attr() -> split_large_page() [ pagetable_alloc() ] -> __split_large_page() Avoid deadlocks by dropping the mmap lock across pagetable_alloc() in split_large_page() and track whether this is needed by adding a new 'init_mm_read_locked' flag to struct cpa_data. This is safe as __split_large_page() (called with locks re-established) revalidates that the page table entry is the same as it was prior to the locks being dropped and __change_page_attr() repeats the entire page table walk whenever a split occurs, so concurrent split and collapse are accounted for. Concurrent ptdump is also safe as the lock is only dropped over page table allocation during which time the page table has not yet been modified. The CPA_COLLAPSE flag is only set by set_memory_rox(), which exclusively operates upon vmalloc ranges, and on x86 only within the module mapping space. This is important, because some callers directly invoke __change_page_attr_set_clr(), bypassing this lock. However, none of these operate within the module mapping space. * cpa_process_alias() - a recursive helper called by __change_page_attr_set_clr(). * __set_memory_enc_pgtable() - operates on the direct mapping and (via __vmbus_establish_gpadl()) the vmalloc mapping space. * __set_pages_[n]p() - called by set_direct_map_[invalid, default, valid]_noflush(), __kernel_map_pages() - operates on the direct map. * kernel_[un]map_pages_in_pgd() - operates on EFI ranges. This work is based upon Denis V. Lunev's excellent analysis of the bug with gratitude. [ dhansen: move to imperative voice in changelog ]

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - In the Linux kernel, the following vulnerability has been resolved: x86/mm/pat: Acquire init_mm read lock
    on attribute changes to avoid UAF A previous commit protected against races between ptdump and CPA
    collapse, however one still exists between attribute changes and collapse as reported by Denis V. Lunev
    (linked). When an attribute change arises, a lockless page table walker obtains a PTE entry, which is
    later written to via set_pte_atomic(): ... -> change_page_attr_set_clr() -> __change_page_attr_set_clr()
    -> __change_page_attr() -> _lookup_address_cpa() -> lookup_address_in_pgd_attr() -> [ lockless page table
    walker ] -> set_pte_atomic() There is nothing preventing a concurrent CPA collapse which can free the PTE
    that was retrieved here, resulting in a use-after-free. With the mmap write lock taken on init_mm over CPA
    collapse, resolve this race by acquiring an mmap read lock on init_mm over __change_page_attr_set_clr().
    This locks across the whole operation over which the walk and the PTE entry write occurs, solving the
    race. It is safe to do this here, as no spinlocks are held upon entry to __change_page_attr_set_clr().
    However, the lock must not be held over an allocation, as allocation can trigger reclaim and shrinkers may
    call into CPA recursively, making deadlocks possible (init_mm -> ... -> fs_reclaim -> init_mm). A page
    table is allocated when a huge page needs to be split: -> change_page_attr_set_clr() ->
    __change_page_attr_set_clr() -> __change_page_attr() -> split_large_page() [ pagetable_alloc() ] ->
    __split_large_page() Avoid deadlocks by dropping the mmap lock across pagetable_alloc() in
    split_large_page() and track whether this is needed by adding a new 'init_mm_read_locked' flag to struct
    cpa_data. This is safe as __split_large_page() (called with locks re-established) revalidates that the
    page table entry is the same as it was prior to the locks being dropped and __change_page_attr() repeats
    the entire page table walk whenever a split occurs, so concurrent split and collapse are accounted for.
    Concurrent ptdump is also safe as the lock is only dropped over page table allocation during which time
    the page table has not yet been modified. The CPA_COLLAPSE flag is only set by set_memory_rox(), which
    exclusively operates upon vmalloc ranges, and on x86 only within the module mapping space. This is
    important, because some callers directly invoke __change_page_attr_set_clr(), bypassing this lock.
    However, none of these operate within the module mapping space. * cpa_process_alias() - a recursive helper
    called by __change_page_attr_set_clr(). * __set_memory_enc_pgtable() - operates on the direct mapping and
    (via __vmbus_establish_gpadl()) the vmalloc mapping space. * __set_pages_[n]p() - called by
    set_direct_map_[invalid, default, valid]_noflush(), __kernel_map_pages() - operates on the direct map. *
    kernel_[un]map_pages_in_pgd() - operates on EFI ranges. This work is based upon Denis V. Lunev's excellent
    analysis of the bug with gratitude. [ dhansen: move to imperative voice in changelog ] (CVE-2026-97533)

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2026-3192 advisory.

    An issue in the Linux kernel's virtio-net/TAP networking path could allow an actor with privileged access     inside a guest virtual machine to send specially crafted network packets that corrupt host kernel memory     on KVM-based hypervisors running unpatched Linux kernel versions 4.4 through 6.18. This could result in     disclosure of host memory or a denial of service.



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

    sctp: fix err_chunk memory leaks in INIT handling (CVE-2026-72413)

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

    xfrm: Fix dev use-after-free in xfrm async resumption (CVE-2026-72463)

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

    bpf: Guard __get_user acesss with access_ok for uprobe_multi data (CVE-2026-74258)

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

    ipv4: fib: Don't dump dying fib_info in fib_leaf_notify(). (CVE-2026-74289)

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

    netfilter: cttimeout: detach dataplane timeout policy and repurpose refcount (CVE-2026-74347)

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

    fou: Fix use-after-free in fou_create() (CVE-2026-74496)

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

    vfio/pci: clear vdev->msi_perm after freeing it on init failure (CVE-2026-89777)

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

    isofs: fix out-of-bounds page array access on empty zisofs block (CVE-2026-89778)

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

    perf: Fix use-after-free when perf mmap() revival races with the last munmap() (CVE-2026-89791)

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

    nvme: skip the zoned limits update if the zone info query failed (CVE-2026-89971)

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

    tcp: reject non zerocopy devmem tx (CVE-2026-90051)

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

    net/sched: sch_htb: limit htb_classify inner-class filter hops (CVE-2026-90053)

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

    net/sched: bound qdisc_pkt_len to prevent qdisc soft lockup (CVE-2026-90058)

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

    virtio-net: Ensure that TCP packets don't overflow gso_segs (CVE-2026-90063)

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

    net/sched: sfq: clamp quantum to avoid signed overflow soft lockup (CVE-2026-90072)

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

    net/sched: hhf: clamp quantum before hhf_change() to avoid overflow (CVE-2026-90073)

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

    net/sched: fq_codel: clamp default quantum and mtu (CVE-2026-90075)

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

    net/sched: fq: add overflow bounds to quantum and initial quantum (CVE-2026-90076)

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

    NFSv4/pnfs: key the data server cache on the NFS version (CVE-2026-90102)

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

    NFSv4.2: fix LAYOUTSTATS send buffer exhaustion (CVE-2026-90103)

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

    xsk: fix NULL pointer dereference in __xsk_rcv() (CVE-2026-90115)

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

    vsock: don't check the listener's sk_err in vsock_accept() (CVE-2026-90138)

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

    null_blk: register configfs subsystem after creating default devices (CVE-2026-90189)

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

    fs/ntfs3: reject out-of-range evcn in mi_enum_attr() (CVE-2026-90199)

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

    nvme/ioctl: check SUBMIT_IO with nvme_cmd_allowed() (CVE-2026-90227)

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

    bpf: Check load-acquire src ptr type before the load (CVE-2026-90312)

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

    bpf, cgroup: Fix invalid storage access after __cgroup_bpf_attach failed (CVE-2026-90313)

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

    dm-integrity: replace forgeable discard filler with a keyed sector marker (CVE-2026-90333)

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

    bpf, x86: Fix trampoline stack size for 128-bit arguments (CVE-2026-90358)

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

    bpf: Fix potential UAF in bpf_netns_link_update_prog (CVE-2026-90393)

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

    iommu/tegra241-cmdqv: Synchronize the error ISR against VINTF (de)init (CVE-2026-90429)

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

    RDMA/mlx5: Fix integer overflow of user QP buffer size (CVE-2026-90435)

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

    RDMA/core: Fix potential use after free in ib_dealloc_pd_user() (CVE-2026-92507)

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

    software node: Fix software_node_get_reference_args() with index -1 (CVE-2026-93046)

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

    uio: Fix stale info pointer in failed registration path (CVE-2026-93054)

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

    bpf: Reject rdonly/rdwr_buf_size kfunc arguments that exceed u32 max (CVE-2026-93125)

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

    mm/secretmem: properly account locked pages (CVE-2026-93243)

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

    vxlan: mdb: Fix use-after-free in vxlan_mdb_flush() (CVE-2026-93250)

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

    ext4: skip extra isize expansion during mount to prevent deadlock (CVE-2026-93268)

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

    i2c: smbus: reject oversized block transfers in the common path (CVE-2026-93287)

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

    netfilter: nfnetlink_log: wait for rcu grace period before freeing pernet state (CVE-2026-93288)

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

    smb/client: zero-initialize stack-allocated cifs_open_info_data (CVE-2026-93801)

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

    btrfs: tree-checker: validate INODE_REF's namelen (CVE-2026-93813)

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

    perf: Fix addr_filter_ranges lifetime (CVE-2026-93817)

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

    tls: reject the combination of TLS and sockmap (CVE-2026-93824)

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

    virtio-fs: avoid double-free on failed queue setup (CVE-2026-93827)

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

    exfat: fix handling of damaged volume in exfat_create_upcase_table() (CVE-2026-93828)

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

    btrfs: tree-checker: validate names in ROOT_REF and ROOT_BACKREF (CVE-2026-97415)

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

    RDMA/umem: Be careful about boundary conditions in ib_umem_find_best_pgsz() (CVE-2026-97421)

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

    fs/ntfs3: validate index entry key bounds (CVE-2026-97438)

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

    fs/ntfs3: preserve non-DOS attribute bits in system.dos_attrib (CVE-2026-97439)

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

    ACPICA: Fix use-after-free in acpi_ds_terminate_control_method() (CVE-2026-97455)

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

    mptcp: avoid unneeded actions on subflow reset (CVE-2026-97524)

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

    x86/mm/pat: Acquire init_mm read lock on attribute changes to avoid UAF (CVE-2026-97533)

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

    smb: client: fix heap overflow in DACL owner/group rewrite (CVE-2026-97555)

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

    smb: client: reject short READ responses in CIFSSMBRead() (CVE-2026-97565)

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

    landlock: Fix use-after-free of the source's parent directory (CVE-2026-97594)

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

    ipvs: reject invalid states in connection template sync records (CVE-2026-97596)

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

    ipv6: flowlabel: cap duplicate leases per socket (CVE-2026-97597)

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

    inet: frags: invalidate queues before flushing them (CVE-2026-97602)

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

    net: openvswitch: fix use-after-free of the flow table mask array (CVE-2026-97611)

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

    ipv6: fix fib6 walker UAF on seq stop (CVE-2026-97940)

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

    x86/mm/pat: Acquire init_mm write lock on collapse to avoid UAF (CVE-2026-97943)

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

    configfs: unhash the dentry before dropping the item in rmdir (CVE-2026-97949)

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

    scsi: target: iscsi: Fix hang for aborted WRITE_PENDING commands (CVE-2026-97951)

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

    net/sched: drr: clamp quantum in change class (CVE-2026-98010)

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

    net/sched: hhf: clamp quantum in change and init paths (CVE-2026-98011)

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

    net/sched: sfq: clamp quantum in change path (CVE-2026-98012)

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

    net/mlx5: E-Switch: fix use-after-free in mlx5_eswitch_termtbl_put (CVE-2026-98015)

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

    net/mlx5e: Fix use-after-free race in sample_restore_put() (CVE-2026-98016)

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

    bpf: Reject untrusted allocated-object pointers (CVE-2026-98037)

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

    bpf: Require MEM_PERCPU for percpu kptr stores (CVE-2026-98039)

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

    bpf: Don't predict JMP32 pointer vs zero comparisons (CVE-2026-98041)

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

    bpf: Check ancestor frames for rbtree callbacks (CVE-2026-98047)

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

    nvme: remove stale namespaces by NSID range during scan (CVE-2026-98056)

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

    bpf: Reject resilient lock operations in rbtree callbacks (CVE-2026-98060)

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

    net/rds: acquire RDS_IN_XMIT in rds_tcp_reset_callbacks() (CVE-2026-98070)

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

    ipvs: fix reversed sequence option serialization (CVE-2026-98078)

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

    af_packet: Don't cast tpacket_hdr.tp_len to int in tpacket_parse_header(). (CVE-2026-98095)

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

    ipv6: sr: restore network header before routing and forwarding (CVE-2026-98096)

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

    net/sched: cls_u32: fix duplicate handle when node ID pool is exhausted (CVE-2026-98104)

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

    netfs: Fix subreq ref leak (CVE-2026-98120)

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

    vxlan: mdb: Fix use-after-free in vxlan_mdb_remote_src_del() (CVE-2026-98122)

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

    sctp: fix soft lockup from unpadded ASCONF-ACK parameter iteration (CVE-2026-98123)

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

    sctp: fix a TOCTOU race in SCTP_CMD_TIMER_START (CVE-2026-98130)

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

    drm/virtio: use the DMA API for resource backing on Xen (CVE-2026-98156)

    In the Linux kernel, the following vulnerability has been resolved: ipv4: validate checksum_start before     completing checksum If a packet with bad checksum metadata gets into the ipv4 stack, skb_checksum_help can     corrupt the network header and cause a bunch of mischief. This was discovered and reported by Paulos, and     has been reporoduced by others independently since. We really shouldn't allow such packets in, but as a     defence in depth measure, let's also check before we complete the checksum. A more complete validation at     input is forthcoming, but needs more work. (CVE-2026-99999)

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.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - x86/mm/pat: Acquire init_mm read lock on attribute changes to avoid UAF A previous commit protected     against races between ptdump and CPA collapse, however one still exists between attribute changes and     collapse as reported by Denis V. Lunev (linked). When an attribute change arises, a lockless page table     walker obtains a PTE entry, which is later written to via set_pte_atomic(): ... ->     change_page_attr_set_clr() -> __change_page_attr_set_clr() -> __change_page_attr() ->
    _lookup_address_cpa() -> lookup_address_in_pgd_attr() -> [ lockless page table walker ] ->     set_pte_atomic() There is nothing preventing a concurrent CPA collapse which can free the PTE that was     retrieved here, resulting in a use-after-free. With the mmap write lock taken on init_mm over CPA     collapse, resolve this race by acquiring an mmap read lock on init_mm over __change_page_attr_set_clr().
    This locks across the whole operation over which the walk and the PTE entry write occurs, solving the     race. It is safe to do this here, as no spinlocks are held upon entry to __change_page_attr_set_clr().
    However, the lock must not be held over an allocation, as allocation can trigger reclaim and shrinkers may     call into CPA recursively, making deadlocks possible (init_mm -> ... -> fs_reclaim -> init_mm). A page     table is allocated when a huge page needs to be split: -> change_page_attr_set_clr() ->
    __change_page_attr_set_clr() -> __change_page_attr() -> split_large_page() [ pagetable_alloc() ] ->
    __split_large_page() Avoid deadlocks by dropping the mmap lock across pagetable_alloc() in     split_large_page() and track whether this is needed by adding a new 'init_mm_read_locked' flag to struct     cpa_data. This is safe as __split_large_page() (called with locks re-established) revalidates that the     page table entry is the same as it was prior to the locks being dropped and __change_page_attr() repeats     the entire page table walk whenever a split occurs, so concurrent split and collapse are accounted for.
    Concurrent ptdump is also safe as the lock is only dropped over page table allocation during which time     the page table has not yet been modified. The CPA_COLLAPSE flag is only set by set_memory_rox(), which     exclusively operates upon vmalloc ranges, and on x86 only within the module mapping space. This is     important, because some callers directly invoke __change_page_attr_set_clr(), bypassing this lock.
    However, none of these operate within the module mapping space. * cpa_process_alias() - a recursive helper     called by __change_page_attr_set_clr(). * __set_memory_enc_pgtable() - operates on the direct mapping and     (via __vmbus_establish_gpadl()) the vmalloc mapping space. * __set_pages_[n]p() - called by     set_direct_map_[invalid, default, valid]_noflush(), __kernel_map_pages() - operates on the direct map. *     kernel_[un]map_pages_in_pgd() - operates on EFI ranges. This work is based upon Denis V. Lunev's excellent     analysis of the bug with gratitude. [ dhansen: move to imperative voice in changelog ] (CVE-2026-97533)

Note that Nessus relies on the presence of the package as reported by the vendor.

ID	Name	Product	Family	Type	Severity
475610	Google: sys-kernel/cchost-kernel-6_18, sys-kernel/csql-kernel-6_18, sys-kernel/lakitu-kernel-6_18, sys-kernel/lakitu-nc-kernel-6_18: security update to 19999.44.106	Tenable Cloud Security	Google COS Security Checks	Local	medium
475610	Google: sys-kernel/cchost-kernel-6_18, sys-kernel/csql-kernel-6_18, sys-kernel/lakitu-kernel-6_18, sys-kernel/lakitu-nc-kernel-6_18: security update to 19999.44.106	Tenable Self-Hosted Container Security	Google COS Security Checks	Local	medium
365258	Amazon Linux 2023 : bpftool6.18, kernel6.18, kernel6.18-devel (ALAS2023-2026-3192)	Nessus	Amazon Linux Local Security Checks	Local	medium
350561	Linux Distros Unpatched Vulnerability : CVE-2026-97533	Nessus	Misc.	Local	medium

Detections

Analytics

CVE-2026-97533

medium

Tenable Plugins

medium

medium

medium

medium