In the Linux kernel, the following vulnerability has been resolved: net/tcp-ao: fix use-after-free of key in del_async path In tcp_ao_delete_key(), the del_async path skips the current_key and rnext_key validity checks present in the synchronous path, assuming these pointers are always NULL on LISTEN sockets. However, if a key was added with set_current=1/set_rnext=1 while the socket was in CLOSE state, current_key and rnext_key will be non-NULL after listen() transitions the socket to LISTEN. When such a key is deleted with del_async=1, hlist_del_rcu() and call_rcu() free the key without clearing the dangling pointers. After the RCU grace period, getsockopt(TCP_AO_INFO) dereferences current_key->sndid and rnext_key->rcvid from freed slab memory. Clear current_key and rnext_key in the del_async path when they reference the key being deleted.

An update of the linux package has been released.

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

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

    sctp: disable BH before calling udp_tunnel_xmit_skb() (CVE-2026-53070)

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

    bpf: Fix same-register dst/src OOB read and pointer leak in sock_ops (CVE-2026-53078)

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

    KVM: x86: Fix shadow paging use-after-free due to unexpected role (CVE-2026-53359)

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

    af_unix: Set gc_in_progress to true in unix_gc(). (CVE-2026-53361)

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

    virtiofs: fix UAF on submount umount

    iput() called from fuse_release_end() can Oops if the super block hasalready been destroyed.  Normally     this is prevented by waiting fornum_waiting to go down to zero before commencing with super block     shutdown.

    This only works, however, for the last submount instance, as the waitcounter is per connection, not per     superblock.

    Revert to using synchronous release requests for the auto_submounts case,which is virtiofs only at this     time. (CVE-2026-53381)

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

    vc_screen: fix null-ptr-deref in vcs_notifier() during concurrent vcs_write

    A KASAN null-ptr-deref was observed in vcs_notifier():

    BUG: KASAN: null-ptr-deref in vcs_notifier+0x98/0x130Read of size 2 at addr qmp_cmd_name:
    qmp_capabilities, arguments: {}

    The issue is a race condition in vcs_write(). When the console_lock istemporarily dropped (to copy data     from userspace), the vc_data pointerobtained from vcs_vc() may become stale. After re-acquiring the     lock,vcs_vc() is called again to re-validate the pointer. If the vc has beendeallocated in the meantime,     vcs_vc() returns NULL, and the while loopbreaks (with written > 0). However, after the loop,     vcs_scr_updated(vc)is still called with the now-NULL vc pointer, leading to a null pointerdereference in     the notifier chain (vcs_notifier dereferences param->vc).

    Fix this by adding a NULL check for vc before calling vcs_scr_updated(). (CVE-2026-53385)

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

    fuse: re-lock request before replacing page cache folio

    fuse_try_move_folio() unlocks the request on entry but does notre-lock it on the success path. This means     fuse_chan_abort() can end therequest and free the fuse_io_args (eg fuse_readpages_end()) while     thesubsequent copy chain logic after fuse_try_move_folio() accesses thefuse_io_args, leading to use-after-     free issues.

    Fix this by calling lock_request() before replace_page_cache_folio().This ensures the request is locked on     the success path which willprevent the fuse_io_args from being freed while the later copying logicruns,     and also ensures that the ap->folios[i]->mapping is never nullsince ap->folios[i] will always point to the     newfolio afterreplace_page_cache_folio(). (CVE-2026-53388)

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

    net/tcp-ao: fix use-after-free of key in del_async path (CVE-2026-53389)

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

    NFSv4/pNFS: reject zero-length r_addr in nfs4_decode_mp_ds_addr (CVE-2026-53391)

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

    NFSv4/flexfiles: reject zero filehandle version count (CVE-2026-53392)

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

    nfsd: reset write verifier on deferred writeback errors (CVE-2026-53393)

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

    nfsd: avoid leaking pre-allocated openowner on unconfirmed retry race (CVE-2026-53394)

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

    nfsd: fix posix_acl leak on SETACL decode failure (CVE-2026-53397)

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

    NFSD: Fix SECINFO_NO_NAME decode error cleanup (CVE-2026-53398)

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

    i2c: core: fix adapter registration race

    Adapters can be looked up based on their id using i2c_get_adapter()which takes a reference to the embedded     struct device.

    Make sure that the adapter (including its struct device) has beeninitialised before adding it to the IDR     to avoid accessing uninitialiseddata which could, for example, lead to NULL-pointer dereferences oruse-     after-free.

    Note that the i2c-dev chardev, which is registered from a bus notifier,currently uses i2c_get_adapter() so     the adapter needs to be added to theIDR before registration. (CVE-2026-53400)

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

    fbdev: Fix fb_new_modelist to prevent null-ptr-deref in fb_videomode_to_var

    info->var, a framebuffer's current mode, is expected to have a matchingentry in info->modelist.
    var_to_display() relies on this and treats afailed fb_match_mode() as This should not happen.
    fb_set_var() keeps ittrue by adding the mode to the list on every change, anddo_register_framebuffer()     does the same at registration.

    store_modes() replaces the modelist from userspace. fb_new_modelist()validates the new modes but does not     check that info->var still has amatch. It relies on fbcon_new_modelist() to re-point consoles, but     thatonly handles consoles mapped to the framebuffer. With fbcon unbound thereare none, so info->var is     left describing a mode that is no longer in thelist.

    A later console takeover runs var_to_display(), where fb_match_mode()returns NULL and leaves     fb_display[i].mode NULL. fbcon_switch() passes itto display_to_var(), and fb_videomode_to_var()     dereferences the NULL mode.

    Keep the current mode in the list in fb_new_modelist(), the same wayfb_set_var() does. (CVE-2026-53403)

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

    pNFS: Fix use-after-free in pnfs_update_layout() (CVE-2026-63800)

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

    tipc: fix slab-use-after-free Read in tipc_aead_decrypt_done (CVE-2026-63801)

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

    blk-cgroup: fix UAF in __blkcg_rstat_flush() (CVE-2026-63802)

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

    KVM: Replace guest-triggerable BUG_ON() in ioeventfd datamatch with get_unaligned() (CVE-2026-63806)

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

    KVM: x86/mmu: Ensure hugepage is in by slot before checking max mapping level (CVE-2026-63807)

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

    exfat: fix potential use-after-free in exfat_find_dir_entry() (CVE-2026-63808)

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

    bpf: use kvfree() for replaced sysctl write buffer (CVE-2026-63809)

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

    block: Avoid mounting the bdev pseudo-filesystem in userspace (CVE-2026-63810)

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

    keys: Pin request_key_auth payload in instantiate paths (CVE-2026-63823)

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

    KEYS: fix overflow in keyctl_pkey_params_get_2() (CVE-2026-63824)

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

    fbdev: fix use-after-free in store_modes() (CVE-2026-63826)

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

    apparmor: mediate the implicit connect of TCP fast open sendmsg (CVE-2026-63828)

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

    net: ip_gre: require CAP_NET_ADMIN in the device netns for changelink (CVE-2026-63829)

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

    net: skmsg: preserve sg.copy across SG transforms (CVE-2026-63830)

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

    drivers/base/memory: set mem->altmap after successful device registration (CVE-2026-64244)

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

    fbdev: modedb: fix a possible UAF in fb_find_mode() (CVE-2026-64245)

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

    KVM: x86: hyper-v: Bound the bank index when querying sparse banks (CVE-2026-64247)

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

    MIPS: smp: report dying CPU to RCU in stop_this_cpu() (CVE-2026-64248)

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

    LoongArch: Report dying CPU to RCU in stop_this_cpu() (CVE-2026-64250)

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

    kernel/fork: clear PF_BLOCK_TS in copy_process() (CVE-2026-64253)

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.

  - net/tcp-ao: fix use-after-free of key in del_async path In tcp_ao_delete_key(), the del_async path skips     the current_key and rnext_key validity checks present in the synchronous path, assuming these pointers are     always NULL on LISTEN sockets. However, if a key was added with set_current=1/set_rnext=1 while the socket     was in CLOSE state, current_key and rnext_key will be non-NULL after listen() transitions the socket to     LISTEN. When such a key is deleted with del_async=1, hlist_del_rcu() and call_rcu() free the key without     clearing the dangling pointers. After the RCU grace period, getsockopt(TCP_AO_INFO) dereferences     current_key->sndid and rnext_key->rcvid from freed slab memory. Clear current_key and rnext_key in the     del_async path when they reference the key being deleted. (CVE-2026-53389)

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

ID	Name	Product	Family	Type	Severity
333954	Photon OS 5.0: Linux PHSA-2026-5.0-92-0916	Nessus	PhotonOS Local Security Checks	Local	high
328468	Amazon Linux 2023 : bpftool6.18, kernel6.18, kernel6.18-devel (ALAS2023-2026-1969)	Nessus	Amazon Linux Local Security Checks	Local	medium
328209	Linux Distros Unpatched Vulnerability : CVE-2026-53389	Nessus	Misc.	Local	high
326038	Photon OS 5.0: Linux PHSA-2026-5.0-0916	Nessus	PhotonOS Local Security Checks	Local	high

Detections

Analytics

CVE-2026-53389

high

Tenable Plugins

high

medium

high

high