In the Linux kernel, the following vulnerability has been resolved: net: openvswitch: fix race on port output assume the following setup on a single machine: 1. An openvswitch instance with one bridge and default flows 2. two network namespaces "server" and "client" 3. two ovs interfaces "server" and "client" on the bridge 4. for each ovs interface a veth pair with a matching name and 32 rx and tx queues 5. move the ends of the veth pairs to the respective network namespaces 6. assign ip addresses to each of the veth ends in the namespaces (needs to be the same subnet) 7. start some http server on the server network namespace 8. test if a client in the client namespace can reach the http server when following the actions below the host has a chance of getting a cpu stuck in a infinite loop: 1. send a large amount of parallel requests to the http server (around 3000 curls should work) 2. in parallel delete the network namespace (do not delete interfaces or stop the server, just kill the namespace) there is a low chance that this will cause the below kernel cpu stuck message. If this does not happen just retry. Below there is also the output of bpftrace for the functions mentioned in the output. The series of events happening here is: 1. the network namespace is deleted calling `unregister_netdevice_many_notify` somewhere in the process 2. this sets first `NETREG_UNREGISTERING` on both ends of the veth and then runs `synchronize_net` 3. it then calls `call_netdevice_notifiers` with `NETDEV_UNREGISTER` 4. this is then handled by `dp_device_event` which calls `ovs_netdev_detach_dev` (if a vport is found, which is the case for the veth interface attached to ovs) 5. this removes the rx_handlers of the device but does not prevent packages to be sent to the device 6. `dp_device_event` then queues the vport deletion to work in background as a ovs_lock is needed that we do not hold in the unregistration path 7. `unregister_netdevice_many_notify` continues to call `netdev_unregister_kobject` which sets `real_num_tx_queues` to 0 8. port deletion continues (but details are not relevant for this issue) 9. at some future point the background task deletes the vport If after 7. but before 9. a packet is send to the ovs vport (which is not deleted at this point in time) which forwards it to the `dev_queue_xmit` flow even though the device is unregistering. In `skb_tx_hash` (which is called in the `dev_queue_xmit`) path there is a while loop (if the packet has a rx_queue recorded) that is infinite if `dev->real_num_tx_queues` is zero. To prevent this from happening we update `do_output` to handle devices without carrier the same as if the device is not found (which would be the code path after 9. is done). Additionally we now produce a warning in `skb_tx_hash` if we will hit the infinite loop. bpftrace (first word is function name): __dev_queue_xmit server: real_num_tx_queues: 1, cpu: 2, pid: 28024, tid: 28024, skb_addr: 0xffff9edb6f207000, reg_state: 1 netdev_core_pick_tx server: addr: 0xffff9f0a46d4a000 real_num_tx_queues: 1, cpu: 2, pid: 28024, tid: 28024, skb_addr: 0xffff9edb6f207000, reg_state: 1 dp_device_event server: real_num_tx_queues: 1 cpu 9, pid: 21024, tid: 21024, event 2, reg_state: 1 synchronize_rcu_expedited: cpu 9, pid: 21024, tid: 21024 synchronize_rcu_expedited: cpu 9, pid: 21024, tid: 21024 synchronize_rcu_expedited: cpu 9, pid: 21024, tid: 21024 synchronize_rcu_expedited: cpu 9, pid: 21024, tid: 21024 dp_device_event server: real_num_tx_queues: 1 cpu 9, pid: 21024, tid: 21024, event 6, reg_state: 2 ovs_netdev_detach_dev server: real_num_tx_queues: 1 cpu 9, pid: 21024, tid: 21024, reg_state: 2 netdev_rx_handler_unregister server: real_num_tx_queues: 1, cpu: 9, pid: 21024, tid: 21024, reg_state: 2 synchronize_rcu_expedited: cpu 9, pid: 21024, tid: 21024 netdev_rx_handler_unregister ret server: real_num_tx_queues: 1, cpu: 9, pid: 21024, tid: 21024, reg_state: 2 dp_ ---truncated---

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

  - net: openvswitch: fix race on port output assume the following setup on a single machine: 1. An     openvswitch instance with one bridge and default flows 2. two network namespaces server and client 3.
    two ovs interfaces server and client on the bridge 4. for each ovs interface a veth pair with a     matching name and 32 rx and tx queues 5. move the ends of the veth pairs to the respective network     namespaces 6. assign ip addresses to each of the veth ends in the namespaces (needs to be the same subnet)     7. start some http server on the server network namespace 8. test if a client in the client namespace can     reach the http server when following the actions below the host has a chance of getting a cpu stuck in a     infinite loop: 1. send a large amount of parallel requests to the http server (around 3000 curls should     work) 2. in parallel delete the network namespace (do not delete interfaces or stop the server, just kill     the namespace) there is a low chance that this will cause the below kernel cpu stuck message. If this does     not happen just retry. Below there is also the output of bpftrace for the functions mentioned in the     output. The series of events happening here is: 1. the network namespace is deleted calling     `unregister_netdevice_many_notify` somewhere in the process 2. this sets first `NETREG_UNREGISTERING` on     both ends of the veth and then runs `synchronize_net` 3. it then calls `call_netdevice_notifiers` with     `NETDEV_UNREGISTER` 4. this is then handled by `dp_device_event` which calls `ovs_netdev_detach_dev` (if a     vport is found, which is the case for the veth interface attached to ovs) 5. this removes the rx_handlers     of the device but does not prevent packages to be sent to the device 6. `dp_device_event` then queues the     vport deletion to work in background as a ovs_lock is needed that we do not hold in the unregistration     path 7. `unregister_netdevice_many_notify` continues to call `netdev_unregister_kobject` which sets     `real_num_tx_queues` to 0 8. port deletion continues (but details are not relevant for this issue) 9. at     some future point the background task deletes the vport If after 7. but before 9. a packet is send to the     ovs vport (which is not deleted at this point in time) which forwards it to the `dev_queue_xmit` flow even     though the device is unregistering. In `skb_tx_hash` (which is called in the `dev_queue_xmit`) path there     is a while loop (if the packet has a rx_queue recorded) that is infinite if `dev->real_num_tx_queues` is     zero. To prevent this from happening we update `do_output` to handle devices without carrier the same as     if the device is not found (which would be the code path after 9. is done). Additionally we now produce a     warning in `skb_tx_hash` if we will hit the infinite loop. bpftrace (first word is function name):
    __dev_queue_xmit server: real_num_tx_queues: 1, cpu: 2, pid: 28024, tid: 28024, skb_addr:
    0xffff9edb6f207000, reg_state: 1 netdev_core_pick_tx server: addr: 0xffff9f0a46d4a000 real_num_tx_queues:
    1, cpu: 2, pid: 28024, tid: 28024, skb_addr: 0xffff9edb6f207000, reg_state: 1 dp_device_event server:
    real_num_tx_queues: 1 cpu 9, pid: 21024, tid: 21024, event 2, reg_state: 1 synchronize_rcu_expedited: cpu     9, pid: 21024, tid: 21024 synchronize_rcu_expedited: cpu 9, pid: 21024, tid: 21024     synchronize_rcu_expedited: cpu 9, pid: 21024, tid: 21024 synchronize_rcu_expedited: cpu 9, pid: 21024,     tid: 21024 dp_device_event server: real_num_tx_queues: 1 cpu 9, pid: 21024, tid: 21024, event 6,     reg_state: 2 ovs_netdev_detach_dev server: real_num_tx_queues: 1 cpu 9, pid: 21024, tid: 21024, reg_state:
    2 netdev_rx_handler_unregister server: real_num_tx_queues: 1, cpu: 9, pid: 21024, tid: 21024, reg_state: 2     synchronize_rcu_expedited: cpu 9, pid: 21024, tid: 21024 netdev_rx_handler_unregister ret server:
    real_num_tx_queues: 1, cpu: 9, pid: 21024, tid: 21024, reg_state: 2 dp_ ---truncated--- (CVE-2023-53188)

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

The version of kernel installed on the remote host is prior to 5.15.184-125.190. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.15-2025-073 advisory.

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

    scsi: target: Fix WRITE_SAME No Data Buffer crash

    In newer version of the SBC specs, we have a NDOB bit that indicates thereis no data buffer that gets     written out. If this bit is set using commandslike sg_write_same --ndob we will crash in     target_core_iblock/file'sexecute_write_same handlers when we go to access the se_cmd->t_data_sgbecause its     NULL.

    This patch adds a check for the NDOB bit in the common WRITE SAME codebecause we don't support it. And, it     adds a check for zero SG elements ineach handler in case the initiator tries to send a normal WRITE SAME     withno data buffer. (CVE-2022-21546)

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

    drm/i915/gt: Cleanup partial engine discovery failures (CVE-2022-48893)

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

    cifs: Fix UAF in cifs_demultiplex_thread() (CVE-2023-52572)

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

    bpf: Check rcu_read_lock_trace_held() before calling bpf map helpers (CVE-2023-52621)

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

    smb: client: fix use-after-free bug in cifs_debug_data_proc_show() (CVE-2023-52752)

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

    smb: client: fix potential deadlock when releasing mids (CVE-2023-52757)

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

    net: openvswitch: fix race on port output (CVE-2023-53188)

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

    fs/proc: do_task_stat: use sig->stats_lock to gather the threads/children stats (CVE-2024-26686)

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

    net/sched: act_mirred: don't override retval if we already lost the skb (CVE-2024-26739)

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

    smb: client: fix potential UAF in cifs_dump_full_key() (CVE-2024-35866)

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

    smb: client: fix potential UAF in cifs_stats_proc_show() (CVE-2024-35867)

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

    blk-iocost: do not WARN if iocg was already offlined (CVE-2024-36908)

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

    of: module: add buffer overflow check in of_modalias() (CVE-2024-38541)

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

    ipvs: properly dereference pe in ip_vs_add_service (CVE-2024-42322)

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

    smb/server: fix potential null-ptr-deref of lease_ctx_info in smb2_open() (CVE-2024-46742)

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

    btrfs: don't BUG_ON() when 0 reference count at btrfs_lookup_extent_info() (CVE-2024-46751)

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

    net: mana: Fix error handling in mana_create_txq/rxq's NAPI cleanup (CVE-2024-46784)

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

    smb: client: fix UAF in async decryption (CVE-2024-50047)

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

    net: fix crash when config small gso_max_size/gso_ipv4_max_size (CVE-2024-50258)

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

    filemap: Fix bounds checking in filemap_read() (CVE-2024-50272)

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

    dm cache: fix flushing uninitialized delayed_work on cache_ctr error (CVE-2024-50280)

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

    sched/task_stack: fix object_is_on_stack() for KASAN tagged pointers (CVE-2024-53128)

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

    wifi: ath10k: avoid NULL pointer error during sdio remove (CVE-2024-56599)

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

    ipv6: release nexthop on device removal

    The CI is hitting some aperiodic hangup at device removal time in thepmtu.sh self-test:

    unregister_netdevice: waiting for veth_A-R1 to become free. Usage count = 6ref_tracker:
    veth_A-R1@ffff888013df15d8 has 1/5 users atdst_init+0x84/0x4a0dst_alloc+0x97/0x150ip6_dst_alloc+0x23/0x90i     p6_rt_pcpu_alloc+0x1e6/0x520ip6_pol_route+0x56f/0x840fib6_rule_lookup+0x334/0x630ip6_route_output_flags+0x     259/0x480ip6_dst_lookup_tail.constprop.0+0x5c2/0x940ip6_dst_lookup_flow+0x88/0x190udp_tunnel6_dst_lookup+0     x2a7/0x4c0vxlan_xmit_one+0xbde/0x4a50 [vxlan]vxlan_xmit+0x9ad/0xf20 [vxlan]dev_hard_start_xmit+0x10e/0x360
    __dev_queue_xmit+0xf95/0x18c0arp_solicit+0x4a2/0xe00neigh_probe+0xaa/0xf0

    While the first suspect is the dst_cache, explicitly tracking the dstowing the last device reference via     probes proved such dst is held bythe nexthop in the originating fib6_info.

    Similar to commit f5b51fe804ec (ipv6: route: purge exception onremoval), we need to explicitly release     the originating fib info whendisconnecting a to-be-removed device from a live ipv6 dst: move thefib6_info     cleanup into ip6_dst_ifdown().

    Tested running:

    ./pmtu.sh cleanup_ipv6_exception

    in a tight loop for more than 400 iterations with no spat, running anunpatched kernel  I observed a splat     every ~10 iterations. (CVE-2024-56751)

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

    bpf: avoid holding freeze_mutex during mmap operation (CVE-2025-21853)

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

    nvme-tcp: fix potential memory corruption in nvme_tcp_recv_pdu() (CVE-2025-21927)

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

    media: streamzap: fix race between device disconnection and urb callback (CVE-2025-22027)

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

    sctp: add mutual exclusion in proc_sctp_do_udp_port() (CVE-2025-22062)

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

    sctp: detect and prevent references to a freed transport in sendmsg (CVE-2025-23142)

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

    mptcp: fix NULL pointer in can_accept_new_subflow (CVE-2025-23145)

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

    i3c: Add NULL pointer check in i3c_master_queue_ibi() (CVE-2025-23147)

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

    ext4: fix off-by-one error in do_split (CVE-2025-23150)

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

    net: vlan: don't propagate flags on open (CVE-2025-23163)

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

    ext4: ignore xattrs past end (CVE-2025-37738)

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

    net: tls: explicitly disallow disconnect (CVE-2025-37756)

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

    virtiofs: add filesystem context source name check (CVE-2025-37773)

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

    isofs: Prevent the use of too small fid (CVE-2025-37780)

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

    net: openvswitch: fix nested key length validation in the set() action (CVE-2025-37789)

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

    net_sched: hfsc: Fix a UAF vulnerability in class handling (CVE-2025-37797)

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

    crypto: null - Use spin lock instead of mutex (CVE-2025-37808)

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

    irqchip/gic-v2m: Prevent use after free of gicv2m_get_fwnode() (CVE-2025-37819)

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

    net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too (CVE-2025-37823)

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

    PCI: Fix reference leak in pci_register_host_bridge() (CVE-2025-37836)

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

    jbd2: remove wrong sb->s_sequence check (CVE-2025-37839)

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

    cifs: avoid NULL pointer dereference in dbg call (CVE-2025-37844)

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

    scsi: st: Fix array overflow in st_setup() (CVE-2025-37857)

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

    page_pool: avoid infinite loop to schedule delayed worker (CVE-2025-37859)

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

    RDMA/core: Silence oversized kvmalloc() warning (CVE-2025-37867)

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

    nfsd: decrease sc_count directly if fail to queue dl_recall (CVE-2025-37871)

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

    KVM: x86: Reset IRTE to host control if *new* route isn't postable (CVE-2025-37885)

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

    net_sched: hfsc: Fix a UAF vulnerability in class with netem as child qdisc (CVE-2025-37890)

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

    net_sched: qfq: Fix double list add in class with netem as child qdisc (CVE-2025-37913)

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

    net_sched: ets: Fix double list add in class with netem as child qdisc (CVE-2025-37914)

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

    net_sched: drr: Fix double list add in class with netem as child qdisc (CVE-2025-37915)

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

    tracing: Fix oob write in trace_seq_to_buffer() (CVE-2025-37923)

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

    iommu/amd: Fix potential buffer overflow in parse_ivrs_acpihid (CVE-2025-37927)

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

    ftrace: Add cond_resched() to ftrace_graph_set_hash() (CVE-2025-37940)

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

    xenbus: Use kref to track req lifetime (CVE-2025-37949)

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

    x86/mm: Eliminate window where TLB flushes may be inadvertently skipped (CVE-2025-37964)

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

    net: phy: leds: fix memory leak (CVE-2025-37989)

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

    net_sched: Flush gso_skb list too during ->change() (CVE-2025-37992)

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

    module: ensure that kobject_put() is safe for module type kobjects (CVE-2025-37995)

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

    netfilter: ipset: fix region locking in hash types (CVE-2025-37997)

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

    openvswitch: Fix unsafe attribute parsing in output_userspace() (CVE-2025-37998)

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

    nfs: handle failure of nfs_get_lock_context in unlock path (CVE-2025-38023)

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 version of kernel installed on the remote host is prior to 5.4.293-211.419. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.4-2025-102 advisory.

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

    virtio-net: Add validation for used length (CVE-2021-47352)

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

    net: openvswitch: fix race on port output (CVE-2023-53188)

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

    RDMA/srpt: Support specifying the srpt_service_guid parameter (CVE-2024-26744)

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

    nvme-tcp: fix potential memory corruption in nvme_tcp_recv_pdu() (CVE-2025-21927)

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

    sctp: detect and prevent references to a freed transport in sendmsg (CVE-2025-23142)

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

    i3c: Add NULL pointer check in i3c_master_queue_ibi() (CVE-2025-23147)

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

    ext4: fix off-by-one error in do_split (CVE-2025-23150)

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

    net: vlan: don't propagate flags on open (CVE-2025-23163)

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

    ext4: ignore xattrs past end (CVE-2025-37738)

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

    net: ppp: Add bound checking for skb data on ppp_sync_txmung (CVE-2025-37749)

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

    tipc: fix memory leak in tipc_link_xmit (CVE-2025-37757)

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

    virtiofs: add filesystem context source name check (CVE-2025-37773)

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

    isofs: Prevent the use of too small fid (CVE-2025-37780)

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

    ext4: fix OOB read when checking dotdot dir (CVE-2025-37785)

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

    net: openvswitch: fix nested key length validation in the set() action (CVE-2025-37789)

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

    net_sched: hfsc: Fix a UAF vulnerability in class handling (CVE-2025-37797)

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

    crypto: null - Use spin lock instead of mutex (CVE-2025-37808)

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

    net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too (CVE-2025-37823)

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

    tipc: fix NULL pointer dereference in tipc_mon_reinit_self() (CVE-2025-37824)

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

    jbd2: remove wrong sb->s_sequence check (CVE-2025-37839)

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

    scsi: st: Fix array overflow in st_setup() (CVE-2025-37857)

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

    page_pool: avoid infinite loop to schedule delayed worker (CVE-2025-37859)

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

    HID: pidff: Fix null pointer dereference in pidff_find_fields (CVE-2025-37862)

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

    mtd: inftlcore: Add error check for inftl_read_oob() (CVE-2025-37892)

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

    ftrace: Add cond_resched() to ftrace_graph_set_hash() (CVE-2025-37940)

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

    net: phy: leds: fix memory leak (CVE-2025-37989)

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.

An update of the linux package has been released.

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

    An out-of-bounds memory access flaw was found in the Linux kernel's XFS file system in how a user restores     an XFS image after failure (with a dirty log journal). This flaw allows a local user to crash or     potentially escalate their privileges on the system. (CVE-2023-2124)

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

    skbuff: Fix a race between coalescing and releasing SKBs (CVE-2023-53186)

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

    net: openvswitch: fix race on port output (CVE-2023-53188)

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

    raw: Fix NULL deref in raw_get_next(). (CVE-2023-53198)

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

    nfsd: call op_release, even when op_func returns an error (CVE-2023-53241)

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

    Drivers: vmbus: Check for channel allocation before looking up relids (CVE-2023-53273)

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

    sctp: check send stream number after wait_for_sndbuf (CVE-2023-53296)

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

    sctp: fix a potential overflow in sctp_ifwdtsn_skip (CVE-2023-53372)

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

    tracing: Free error logs of tracing instances (CVE-2023-53375)

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

    cgroup,freezer: hold cpu_hotplug_lock before freezer_mutex (CVE-2023-53522)

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

    RDMA/cma: Allow UD qp_type to join multicast only (CVE-2023-53525)

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

    mm/swap: fix swap_info_struct race between swapoff and get_swap_pages() (CVE-2023-53623)

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

    bpf, arm64: Fixed a BTI error on returning to patched function (CVE-2023-53634)

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

    NFSD: Avoid calling OPDESC() with ops->opnum == OP_ILLEGAL (CVE-2023-53680)

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.

ID	Name	Product	Family	Severity
265046	Linux Distros Unpatched Vulnerability : CVE-2023-53188	Nessus	Misc.	medium
238031	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.15-2025-073 (ALASKERNEL-5.15-2025-073)	Nessus	Amazon Linux Local Security Checks	high
237516	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.4-2025-102 (ALASKERNEL-5.4-2025-102)	Nessus	Amazon Linux Local Security Checks	high
236993	Photon OS 4.0: Linux PHSA-2025-4.0-0801	Nessus	PhotonOS Local Security Checks	high
175085	Amazon Linux 2023 : bpftool, kernel, kernel-devel (ALAS2023-2023-169)	Nessus	Amazon Linux Local Security Checks	high

Detections

Analytics

CVE-2023-53188

medium

Tenable Plugins

medium

high

high

high

high