In the Linux kernel, the following vulnerability has been resolved: pnode: terminate at peers of source The propagate_mnt() function handles mount propagation when creating mounts and propagates the source mount tree @source_mnt to all applicable nodes of the destination propagation mount tree headed by @dest_mnt. Unfortunately it contains a bug where it fails to terminate at peers of @source_mnt when looking up copies of the source mount that become masters for copies of the source mount tree mounted on top of slaves in the destination propagation tree causing a NULL dereference. Once the mechanics of the bug are understood it's easy to trigger. Because of unprivileged user namespaces it is available to unprivileged users. While fixing this bug we've gotten confused multiple times due to unclear terminology or missing concepts. So let's start this with some clarifications: * The terms "master" or "peer" denote a shared mount. A shared mount belongs to a peer group. * A peer group is a set of shared mounts that propagate to each other. They are identified by a peer group id. The peer group id is available in @shared_mnt->mnt_group_id. Shared mounts within the same peer group have the same peer group id. The peers in a peer group can be reached via @shared_mnt->mnt_share. * The terms "slave mount" or "dependent mount" denote a mount that receives propagation from a peer in a peer group. IOW, shared mounts may have slave mounts and slave mounts have shared mounts as their master. Slave mounts of a given peer in a peer group are listed on that peers slave list available at @shared_mnt->mnt_slave_list. * The term "master mount" denotes a mount in a peer group. IOW, it denotes a shared mount or a peer mount in a peer group. The term "master mount" - or "master" for short - is mostly used when talking in the context of slave mounts that receive propagation from a master mount. A master mount of a slave identifies the closest peer group a slave mount receives propagation from. The master mount of a slave can be identified via @slave_mount->mnt_master. Different slaves may point to different masters in the same peer group. * Multiple peers in a peer group can have non-empty ->mnt_slave_lists. Non-empty ->mnt_slave_lists of peers don't intersect. Consequently, to ensure all slave mounts of a peer group are visited the ->mnt_slave_lists of all peers in a peer group have to be walked. * Slave mounts point to a peer in the closest peer group they receive propagation from via @slave_mnt->mnt_master (see above). Together with these peers they form a propagation group (see below). The closest peer group can thus be identified through the peer group id @slave_mnt->mnt_master->mnt_group_id of the peer/master that a slave mount receives propagation from. * A shared-slave mount is a slave mount to a peer group pg1 while also a peer in another peer group pg2. IOW, a peer group may receive propagation from another peer group. If a peer group pg1 is a slave to another peer group pg2 then all peers in peer group pg1 point to the same peer in peer group pg2 via ->mnt_master. IOW, all peers in peer group pg1 appear on the same ->mnt_slave_list. IOW, they cannot be slaves to different peer groups. * A pure slave mount is a slave mount that is a slave to a peer group but is not a peer in another peer group. * A propagation group denotes the set of mounts consisting of a single peer group pg1 and all slave mounts and shared-slave mounts that point to a peer in that peer group via ->mnt_master. IOW, all slave mounts such that @slave_mnt->mnt_master->mnt_group_id is equal to @shared_mnt->mnt_group_id. The concept of a propagation group makes it easier to talk about a single propagation level in a propagation tree. For example, in propagate_mnt() the immediate peers of @dest_mnt and all slaves of @dest_mnt's peer group form a propagation group pr ---truncated---

The remote SUSE Linux SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2026:0029-1 advisory.

    The SUSE Linux Enterprise 15 SP4 kernel was updated to receive various security bugfixes.


    The following security bugs were fixed:

    - CVE-2022-50280: pnode: terminate at peers of source (bsc#1249806).
    - CVE-2023-53676: scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show() (bsc#1251786).
    - CVE-2025-40040: mm/ksm: fix flag-dropping behavior in ksm_madvise (bsc#1252780).
    - CVE-2025-40048: uio_hv_generic: Let userspace take care of interrupt mask (bsc#1252862).
    - CVE-2025-40121: ASoC: Intel: bytcr_rt5651: Fix invalid quirk input mapping (bsc#1253367).
    - CVE-2025-40154: ASoC: Intel: bytcr_rt5640: Fix invalid quirk input mapping (bsc#1253431).
    - CVE-2025-40204: sctp: Fix MAC comparison to be constant-time (bsc#1253436).
    - CVE-2025-39967: fbcon: fix integer overflow in fbcon_do_set_font (bsc#1252033)


Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

According to the versions of the kernel packages installed, the EulerOS Virtualization installation on the remote host is affected by the following vulnerabilities :

    x86/mce: Work around an erratum on fast string copy instructions(CVE-2022-49124)

    net: preserve skb_end_offset() in skb_unclone_keeptruesize()(CVE-2022-49142)

    scsi: qla2xxx: Fix premature hw access after PCI error(CVE-2022-49157)

    scsi: qla2xxx: Fix warning message due to adisc being flushed(CVE-2022-49158)

    scsi: qla2xxx: Implement ref count for SRB(CVE-2022-49159)

    USB: core: Prevent nested device-reset calls(CVE-2022-49936)

    mmc: vub300: fix return value check of mmc_add_host()(CVE-2022-50251)

    tracing: Fix reading strings from synthetic events(CVE-2022-50255)

    kprobes: Fix check for probe enabled in kill_kprobe()(CVE-2022-50266)

    mmc: rtsx_pci: fix return value check of mmc_add_host()(CVE-2022-50267)

    pnode: terminate at peers of source(CVE-2022-50280)

    ext4: fix delayed allocation bug in ext4_clu_mapped for bigalloc + inline(CVE-2022-50286)

    ext4: fix potential out of bound read in ext4_fc_replay_scan()(CVE-2022-50306)

    drivers: serial: jsm: fix some leaks in probe(CVE-2022-50312)

    erofs: fix order = MAX_ORDER warning due to crafted negative i_size(CVE-2022-50313)

    ata: ahci: Match EM_MAX_SLOTS with SATA_PMP_MAX_PORTS(CVE-2022-50315)

    perf/x86/intel/uncore: Fix reference count leak in hswep_has_limit_sbox()(CVE-2022-50318)

    net: do not sense pfmemalloc status in skb_append_pagefrags()(CVE-2022-50323)

    jbd2: fix potential use-after-free in jbd2_fc_wait_bufs(CVE-2022-50328)

    crypto: cavium - prevent integer overflow loading firmware(CVE-2022-50330)

    ext4: fix null-ptr-deref in ext4_write_info(CVE-2022-50344)

    ext4: init quota for 'old.inode' in 'ext4_rename'(CVE-2022-50346)

    scsi: target: iscsi: Fix a race condition between login_work and the login thread(CVE-2022-50350)

    Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering     Authority.(CVE-2022-50377)

    padata: Always leave BHs disabled when running -parallel()(CVE-2022-50382)

    nvme: fix multipath crash caused by flush request when blktrace is enabled(CVE-2022-50388)

    tpm: tpm_crb: Add the missed acpi_put_table() to fix memory leak(CVE-2022-50389)

    drm/ttm: fix undefined behavior in bit shift for TTM_TT_FLAG_PRIV_POPULATED(CVE-2022-50390)

    i2c: ismt: Fix an out-of-bounds bug in ismt_access()(CVE-2022-50394)

    ACPICA: Fix error code path in acpi_ds_call_control_method()(CVE-2022-50411)

    x86/fpu: Fix copy_xstate_to_uabi() to copy init states correctly(CVE-2022-50425)

    mmc: vub300: fix warning - do not call blocking ops when !TASK_RUNNING(CVE-2022-50430)

    drm/vmwgfx: Validate the box size for the snooped cursor(CVE-2022-50440)

    cpufreq: Init completion before kobject_init_and_add()(CVE-2022-50473)

    ext4: add EXT4_IGET_BAD flag to prevent unexpected bad inode(CVE-2022-50485)

    scsi: qla2xxx: Fix crash when I/O abort times out(CVE-2022-50493)

    binfmt_misc: fix shift-out-of-bounds in check_special_flags(CVE-2022-50497)

    perf/smmuv3: Fix hotplug callback leak in arm_smmu_pmu_init()(CVE-2022-50510)

    tracing/hist: Fix out-of-bound write on 'action_data.var_ref_idx'(CVE-2022-50553)

    ext4: avoid deadlock in fs reclaim with page writeback(CVE-2023-53149)

    tracing: Fix null pointer dereference in tracing_err_log_open()(CVE-2023-53167)

    vfio/type1: prevent underflow of locked_vm via exec()(CVE-2023-53171)

    serial: 8250: Reinit port-pm on port specific driver unbind(CVE-2023-53176)

    mm: fix zswap writeback race condition(CVE-2023-53178)

    sched/fair: Don't balance task to its current running CPU(CVE-2023-53215)

    arm64: efi: Make efi_rt_lock a raw_spinlock(CVE-2023-53216)

    media: az6007: Fix null-ptr-deref in az6007_i2c_xfer()(CVE-2023-53220)

    bpf: Fix memleak due to fentry attach failure(CVE-2023-53221)

    thermal/drivers/hisi: Drop second sensor hi3660(CVE-2023-53242)

    firmware: dmi-sysfs: Fix null-ptr-deref in dmi_sysfs_register_handle(CVE-2023-53250)

    VMCI: check context-notify_page after call to get_user_pages_fast() to avoid GPF(CVE-2023-53259)

    ext4: fix i_disksize exceeding i_size problem in paritally written case(CVE-2023-53270)

    scsi: qla2xxx: Remove unused nvme_ls_waitq wait queue(CVE-2023-53280)

    ext4: add bounds checking in get_max_inline_xattr_value_size()(CVE-2023-53285)

    drm/client: Fix memory leak in drm_client_modeset_probe(CVE-2023-53288)

    ext4: fix WARNING in mb_find_extent(CVE-2023-53317)

    recordmcount: Fix memory leaks in the uwrite function(CVE-2023-53318)

    genirq/ipi: Fix NULL pointer deref in irq_data_get_affinity_mask()(CVE-2023-53332)

    tracing: Fix race issue between cpu buffer write and swap(CVE-2023-53368)

    crypto: seqiv - Handle EBUSY correctly(CVE-2023-53373)

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

    ACPICA: Add AML_NO_OPERAND_RESOLVE flag to Timer(CVE-2023-53395)

    mm: kmem: fix a NULL pointer dereference in obj_stock_flush_required()(CVE-2023-53401)

    blk-cgroup: Reinit blkg_iostat_set after clearing in blkcg_reset_stats()(CVE-2023-53421)

    media: uvcvideo: Handle cameras with invalid descriptors(CVE-2023-53437)

    bpf: cpumap: Fix memory leak in cpu_map_update_elem(CVE-2023-53441)

    ext4: remove a BUG_ON in ext4_mb_release_group_pa()(CVE-2023-53450)

    scsi: qla4xxx: Add length check when parsing nlattrs(CVE-2023-53456)

    kobject: Add sanity check for kset-kobj.ktype in kset_register()(CVE-2023-53480)

    ext4: allow ext4_get_group_info() to fail(CVE-2023-53503)

    udf: Do not bother merging very long extents(CVE-2023-53506)

    virtio-mmio: don't break lifecycle of vm_dev(CVE-2023-53515)

    scsi: ses: Fix slab-out-of-bounds in ses_intf_remove()(CVE-2023-53521)

    scsi: qla2xxx: Use raw_smp_processor_id() instead of smp_processor_id()(CVE-2023-53530)

    tracing/histograms: Add histograms to hist_vars if they have referenced variables(CVE-2023-53560)

    null_blk: Always check queue mode setting from configfs(CVE-2023-53576)

    bpf, cpumap: Make sure kthread is running before map update returns(CVE-2023-53577)

    ring-buffer: Sync IRQ works before buffer destruction(CVE-2023-53587)

    ipmi_si: fix a memleak in try_smi_init()(CVE-2023-53611)

    ext4: fix possible double unlock when moving a directory(CVE-2023-53626)

    bnxt: avoid overflow in bnxt_get_nvram_directory()(CVE-2023-53661)

    ring-buffer: Fix deadloop issue on reading trace_pipe(CVE-2023-53668)

    A transient execution vulnerability in some AMD processors may allow an attacker to infer data in the L1D     cache, potentially resulting in the leakage of sensitive information across privileged     boundaries.(CVE-2024-36357)

    drm/dp_mst: Fix MST sideband message body length check(CVE-2024-56616)

    tls: stop recv() if initial process_rx_list gave us non-DATA(CVE-2024-58239)

    crypto: algif_hash - fix double free in hash_accept(CVE-2025-38079)

    thunderbolt: Do not double dequeue a configuration request(CVE-2025-38174)

    mm: fix uprobe pte be overwritten when expanding vma(CVE-2025-38207)

    scsi: lpfc: Use memcpy() for BIOS version(CVE-2025-38332)

    x86/sgx: Prevent attempts to reclaim poisoned pages(CVE-2025-38334)

    HID: core: do not bypass hid_hw_raw_request(CVE-2025-38494)

    clone_private_mnt(): make sure that caller has CAP_SYS_ADMIN in the right userns(CVE-2025-38499)

    bpf: Fix oob access in cgroup local storage(CVE-2025-38502)

    drm/sched: Increment job count before swapping tail spsc queue(CVE-2025-38515)

    pinctrl: qcom: msm: mark certain pins as invalid for interrupts(CVE-2025-38516)

    HID: quirks: Add quirk for 2 Chicony Electronics HP 5MP Cameras(CVE-2025-38540)

    net/sched: Restrict conditions for adding duplicating netems to qdisc tree(CVE-2025-38553)

    crypto: ccp - Fix crash when rebind ccp device for ccp.ko(CVE-2025-38581)

    padata: Fix pd UAF once and for all(CVE-2025-38584)

    net: drop UFO packets in udp_rcv_segment()(CVE-2025-38622)

    regulator: core: fix NULL dereference on unbind due to stale coupling data(CVE-2025-38668)

    media: uvcvideo: Fix 1-byte out-of-bounds read in uvc_parse_format()(CVE-2025-38680)

    fbdev: Fix vmalloc out-of-bounds write in fast_imageblit(CVE-2025-38685)

    media: dvb-frontends: w7090p: fix null-ptr-deref in w7090p_tuner_write_serpar and     w7090p_tuner_read_serpar(CVE-2025-38693)

    scsi: lpfc: Check for hdwq null ptr when cleaning up lpfc_vport structure(CVE-2025-38695)

    ext4: do not BUG when INLINE_DATA_FL lacks system.data xattr(CVE-2025-38701)

    x86/cpu/hygon: Add missing resctrl_cpu_detect() in bsp_init helper(CVE-2025-39681)

    tracing: Limit access to parser-buffer when trace_get_user failed(CVE-2025-39683)

    ftrace: Also allocate and copy hash for reading of filter files(CVE-2025-39689)

    fs/buffer: fix use-after-free when call bh_read() helper(CVE-2025-39691)

    serial: 8250: fix panic due to PSLVERR(CVE-2025-39724)

    rcu: Fix rcu_read_unlock() deadloop due to IRQ work(CVE-2025-39744)

    rcu: Protect -defer_qs_iw_pending from data race(CVE-2025-39749)

    usb: core: config: Prevent OOB read in SS endpoint companion parsing(CVE-2025-39760)

    jbd2: prevent softlockup in jbd2_log_do_checkpoint()(CVE-2025-39782)

    ftrace: Fix potential warning in trace_printk_seq during ftrace_dump(CVE-2025-39813)

    trace/fgraph: Fix the warning caused by missing unregister notifier(CVE-2025-39829)

    vxlan: Fix NPD in {arp,neigh}_reduce() when using nexthop objects(CVE-2025-39850)

    vxlan: Fix NPD when refreshing an FDB entry with a nexthop object(CVE-2025-39851)

    tee: fix NULL pointer dereference in tee_shm_put(CVE-2025-39865)

    fs: writeback: fix use-after-free in __mark_inode_dirty()(CVE-2025-39866)

    cgroup: split cgroup_destroy_wq into 3 workqueues(CVE-2025-39953)

    fbcon: fix integer overflow in fbcon_do_set_font(CVE-2025-39967)

    i40e: add max boundary check for VF filters(CVE-2025-39968)

    i40e: fix idx validation in config queues msg(CVE-2025-39971)

    i40e: add validation for ring_len param(CVE-2025-39973)

Tenable has extracted the preceding description block directly from the EulerOS Virtualization kernel 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 Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2025-993145 advisory.

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

    pnode: terminate at peers of source

    The propagate_mnt() function handles mount propagation when creating     mounts and propagates the source mount tree @source_mnt to all     applicable nodes of the destination propagation mount tree headed by     @dest_mnt.

    Unfortunately it contains a bug where it fails to terminate at peers of     @source_mnt when looking up copies of the source mount that become     masters for copies of the source mount tree mounted on top of slaves in     the destination propagation tree causing a NULL dereference.

    Once the mechanics of the bug are understood it's easy to trigger.
    Because of unprivileged user namespaces it is available to unprivileged     users.

    While fixing this bug we've gotten confused multiple times due to     unclear terminology or missing concepts. So let's start this with some     clarifications:

    * The terms master or peer denote a shared mount. A shared mount       belongs to a peer group.

    * A peer group is a set of shared mounts that propagate to each other.
      They are identified by a peer group id. The peer group id is available       in @shared_mnt->mnt_group_id.
      Shared mounts within the same peer group have the same peer group id.
      The peers in a peer group can be reached via @shared_mnt->mnt_share.

    * The terms slave mount or dependent mount denote a mount that       receives propagation from a peer in a peer group. IOW, shared mounts       may have slave mounts and slave mounts have shared mounts as their       master. Slave mounts of a given peer in a peer group are listed on       that peers slave list available at @shared_mnt->mnt_slave_list.

    * The term master mount denotes a mount in a peer group. IOW, it       denotes a shared mount or a peer mount in a peer group. The term       master mount - or master for short - is mostly used when talking       in the context of slave mounts that receive propagation from a master       mount. A master mount of a slave identifies the closest peer group a       slave mount receives propagation from. The master mount of a slave can       be identified via @slave_mount->mnt_master. Different slaves may point       to different masters in the same peer group.

    * Multiple peers in a peer group can have non-empty ->mnt_slave_lists.
      Non-empty ->mnt_slave_lists of peers don't intersect. Consequently, to       ensure all slave mounts of a peer group are visited the
      ->mnt_slave_lists of all peers in a peer group have to be walked.

    * Slave mounts point to a peer in the closest peer group they receive       propagation from via @slave_mnt->mnt_master (see above). Together with       these peers they form a propagation group (see below). The closest       peer group can thus be identified through the peer group id       @slave_mnt->mnt_master->mnt_group_id of the peer/master that a slave       mount receives propagation from.

    * A shared-slave mount is a slave mount to a peer group pg1 while also       a peer in another peer group pg2. IOW, a peer group may receive       propagation from another peer group.

      If a peer group pg1 is a slave to another peer group pg2 then all       peers in peer group pg1 point to the same peer in peer group pg2 via
      ->mnt_master. IOW, all peers in peer group pg1 appear on the same
      ->mnt_slave_list. IOW, they cannot be slaves to different peer groups.

    * A pure slave mount is a slave mount that is a slave to a peer group       but is not a peer in another peer group.

    * A propagation group denotes the set of mounts consisting of a single       peer group pg1 and all slave mounts and shared-slave mounts that point       to a peer in that peer group via ->mnt_master. IOW, all slave mounts       such that @slave_mnt->mnt_master->mnt_group_id is equal to       @shared_mnt->mnt_group_id.

      The concept of a propagation group makes it easier to talk about a       single propagation level in a propagation tree.

      For example, in propagate_mnt() the immediate peers of @dest_mnt and       all slaves of @dest_mnt's peer group form a propagation group pr
    ---truncated---

Tenable has extracted the preceding description block directly from the Unity Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2025-992274 advisory.

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

    pnode: terminate at peers of source

    The propagate_mnt() function handles mount propagation when creating     mounts and propagates the source mount tree @source_mnt to all     applicable nodes of the destination propagation mount tree headed by     @dest_mnt.

    Unfortunately it contains a bug where it fails to terminate at peers of     @source_mnt when looking up copies of the source mount that become     masters for copies of the source mount tree mounted on top of slaves in     the destination propagation tree causing a NULL dereference.

    Once the mechanics of the bug are understood it's easy to trigger.
    Because of unprivileged user namespaces it is available to unprivileged     users.

    While fixing this bug we've gotten confused multiple times due to     unclear terminology or missing concepts. So let's start this with some     clarifications:

    * The terms master or peer denote a shared mount. A shared mount       belongs to a peer group.

    * A peer group is a set of shared mounts that propagate to each other.
      They are identified by a peer group id. The peer group id is available       in @shared_mnt->mnt_group_id.
      Shared mounts within the same peer group have the same peer group id.
      The peers in a peer group can be reached via @shared_mnt->mnt_share.

    * The terms slave mount or dependent mount denote a mount that       receives propagation from a peer in a peer group. IOW, shared mounts       may have slave mounts and slave mounts have shared mounts as their       master. Slave mounts of a given peer in a peer group are listed on       that peers slave list available at @shared_mnt->mnt_slave_list.

    * The term master mount denotes a mount in a peer group. IOW, it       denotes a shared mount or a peer mount in a peer group. The term       master mount - or master for short - is mostly used when talking       in the context of slave mounts that receive propagation from a master       mount. A master mount of a slave identifies the closest peer group a       slave mount receives propagation from. The master mount of a slave can       be identified via @slave_mount->mnt_master. Different slaves may point       to different masters in the same peer group.

    * Multiple peers in a peer group can have non-empty ->mnt_slave_lists.
      Non-empty ->mnt_slave_lists of peers don't intersect. Consequently, to       ensure all slave mounts of a peer group are visited the
      ->mnt_slave_lists of all peers in a peer group have to be walked.

    * Slave mounts point to a peer in the closest peer group they receive       propagation from via @slave_mnt->mnt_master (see above). Together with       these peers they form a propagation group (see below). The closest       peer group can thus be identified through the peer group id       @slave_mnt->mnt_master->mnt_group_id of the peer/master that a slave       mount receives propagation from.

    * A shared-slave mount is a slave mount to a peer group pg1 while also       a peer in another peer group pg2. IOW, a peer group may receive       propagation from another peer group.

      If a peer group pg1 is a slave to another peer group pg2 then all       peers in peer group pg1 point to the same peer in peer group pg2 via
      ->mnt_master. IOW, all peers in peer group pg1 appear on the same
      ->mnt_slave_list. IOW, they cannot be slaves to different peer groups.

    * A pure slave mount is a slave mount that is a slave to a peer group       but is not a peer in another peer group.

    * A propagation group denotes the set of mounts consisting of a single       peer group pg1 and all slave mounts and shared-slave mounts that point       to a peer in that peer group via ->mnt_master. IOW, all slave mounts       such that @slave_mnt->mnt_master->mnt_group_id is equal to       @shared_mnt->mnt_group_id.

      The concept of a propagation group makes it easier to talk about a       single propagation level in a propagation tree.

      For example, in propagate_mnt() the immediate peers of @dest_mnt and       all slaves of @dest_mnt's peer group form a propagation group pr
    ---truncated---

Tenable has extracted the preceding description block directly from the Unity Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2025-992167 advisory.

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

    pnode: terminate at peers of source

    The propagate_mnt() function handles mount propagation when creating     mounts and propagates the source mount tree @source_mnt to all     applicable nodes of the destination propagation mount tree headed by     @dest_mnt.

    Unfortunately it contains a bug where it fails to terminate at peers of     @source_mnt when looking up copies of the source mount that become     masters for copies of the source mount tree mounted on top of slaves in     the destination propagation tree causing a NULL dereference.

    Once the mechanics of the bug are understood it's easy to trigger.
    Because of unprivileged user namespaces it is available to unprivileged     users.

    While fixing this bug we've gotten confused multiple times due to     unclear terminology or missing concepts. So let's start this with some     clarifications:

    * The terms master or peer denote a shared mount. A shared mount       belongs to a peer group.

    * A peer group is a set of shared mounts that propagate to each other.
      They are identified by a peer group id. The peer group id is available       in @shared_mnt->mnt_group_id.
      Shared mounts within the same peer group have the same peer group id.
      The peers in a peer group can be reached via @shared_mnt->mnt_share.

    * The terms slave mount or dependent mount denote a mount that       receives propagation from a peer in a peer group. IOW, shared mounts       may have slave mounts and slave mounts have shared mounts as their       master. Slave mounts of a given peer in a peer group are listed on       that peers slave list available at @shared_mnt->mnt_slave_list.

    * The term master mount denotes a mount in a peer group. IOW, it       denotes a shared mount or a peer mount in a peer group. The term       master mount - or master for short - is mostly used when talking       in the context of slave mounts that receive propagation from a master       mount. A master mount of a slave identifies the closest peer group a       slave mount receives propagation from. The master mount of a slave can       be identified via @slave_mount->mnt_master. Different slaves may point       to different masters in the same peer group.

    * Multiple peers in a peer group can have non-empty ->mnt_slave_lists.
      Non-empty ->mnt_slave_lists of peers don't intersect. Consequently, to       ensure all slave mounts of a peer group are visited the
      ->mnt_slave_lists of all peers in a peer group have to be walked.

    * Slave mounts point to a peer in the closest peer group they receive       propagation from via @slave_mnt->mnt_master (see above). Together with       these peers they form a propagation group (see below). The closest       peer group can thus be identified through the peer group id       @slave_mnt->mnt_master->mnt_group_id of the peer/master that a slave       mount receives propagation from.

    * A shared-slave mount is a slave mount to a peer group pg1 while also       a peer in another peer group pg2. IOW, a peer group may receive       propagation from another peer group.

      If a peer group pg1 is a slave to another peer group pg2 then all       peers in peer group pg1 point to the same peer in peer group pg2 via
      ->mnt_master. IOW, all peers in peer group pg1 appear on the same
      ->mnt_slave_list. IOW, they cannot be slaves to different peer groups.

    * A pure slave mount is a slave mount that is a slave to a peer group       but is not a peer in another peer group.

    * A propagation group denotes the set of mounts consisting of a single       peer group pg1 and all slave mounts and shared-slave mounts that point       to a peer in that peer group via ->mnt_master. IOW, all slave mounts       such that @slave_mnt->mnt_master->mnt_group_id is equal to       @shared_mnt->mnt_group_id.

      The concept of a propagation group makes it easier to talk about a       single propagation level in a propagation tree.

      For example, in propagate_mnt() the immediate peers of @dest_mnt and       all slaves of @dest_mnt's peer group form a propagation group pr
    ---truncated---

Tenable has extracted the preceding description block directly from the Unity Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2025:4530-1 advisory.

    The SUSE Linux Enterprise 15 SP3 kernel was updated to receive various security bugfixes.


    The following security bugs were fixed:

    - CVE-2022-50280: pnode: terminate at peers of source (bsc#1249806).
    - CVE-2023-53659: iavf: Fix out-of-bounds when setting channels on remove (bsc#1251247).
    - CVE-2023-53676: scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show() (bsc#1251786).
    - CVE-2023-53717: wifi: ath9k: Fix potential stack-out-of-bounds write in ath9k_wmi_rsp_callback()     (bsc#1252560).
    - CVE-2025-40040: mm/ksm: fix flag-dropping behavior in ksm_madvise (bsc#1252780).
    - CVE-2025-40121: ASoC: Intel: bytcr_rt5651: Fix invalid quirk input mapping (bsc#1253367).
    - CVE-2025-40154: ASoC: Intel: bytcr_rt5640: Fix invalid quirk input mapping (bsc#1253431).
    - CVE-2025-40204: sctp: Fix MAC comparison to be constant-time (bsc#1253436).


Tenable has extracted the preceding description block directly from the SUSE 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 remote SUSE Linux SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2025:4506-1 advisory.

    The SUSE Linux Enterprise 15 SP5 kernel was updated to receive various security bugfixes.


    The following security bugs were fixed:

    - CVE-2022-50280: pnode: terminate at peers of source (bsc#1249806).
    - CVE-2023-53676: scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show() (bsc#1251786).
    - CVE-2024-53093: nvme-multipath: defer partition scanning (bsc#1233640).
    - CVE-2025-40040: mm/ksm: fix flag-dropping behavior in ksm_madvise (bsc#1252780).
    - CVE-2025-40048: uio_hv_generic: Let userspace take care of interrupt mask (bsc#1252862).
    - CVE-2025-40121: ASoC: Intel: bytcr_rt5651: Fix invalid quirk input mapping (bsc#1253367).
    - CVE-2025-40154: ASoC: Intel: bytcr_rt5640: Fix invalid quirk input mapping (bsc#1253431).
    - CVE-2025-40204: sctp: Fix MAC comparison to be constant-time (bsc#1253436).


Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

According to the versions of the kernel packages installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

    x86/mce: Work around an erratum on fast string copy instructions(CVE-2022-49124)

    net: preserve skb_end_offset() in skb_unclone_keeptruesize()(CVE-2022-49142)

    scsi: qla2xxx: Fix premature hw access after PCI error(CVE-2022-49157)

    scsi: qla2xxx: Fix warning message due to adisc being flushed(CVE-2022-49158)

    scsi: qla2xxx: Implement ref count for SRB(CVE-2022-49159)

    USB: core: Prevent nested device-reset calls(CVE-2022-49936)

    mmc: vub300: fix return value check of mmc_add_host()(CVE-2022-50251)

    tracing: Fix reading strings from synthetic events(CVE-2022-50255)

    kprobes: Fix check for probe enabled in kill_kprobe()(CVE-2022-50266)

    mmc: rtsx_pci: fix return value check of mmc_add_host()(CVE-2022-50267)

    pnode: terminate at peers of source(CVE-2022-50280)

    ext4: fix delayed allocation bug in ext4_clu_mapped for bigalloc + inline(CVE-2022-50286)

    ext4: fix potential out of bound read in ext4_fc_replay_scan()(CVE-2022-50306)

    drivers: serial: jsm: fix some leaks in probe(CVE-2022-50312)

    erofs: fix order = MAX_ORDER warning due to crafted negative i_size(CVE-2022-50313)

    ata: ahci: Match EM_MAX_SLOTS with SATA_PMP_MAX_PORTS(CVE-2022-50315)

    perf/x86/intel/uncore: Fix reference count leak in hswep_has_limit_sbox()(CVE-2022-50318)

    net: do not sense pfmemalloc status in skb_append_pagefrags()(CVE-2022-50323)

    jbd2: fix potential use-after-free in jbd2_fc_wait_bufs(CVE-2022-50328)

    crypto: cavium - prevent integer overflow loading firmware(CVE-2022-50330)

    ext4: fix null-ptr-deref in ext4_write_info(CVE-2022-50344)

    ext4: init quota for 'old.inode' in 'ext4_rename'(CVE-2022-50346)

    scsi: target: iscsi: Fix a race condition between login_work and the login thread(CVE-2022-50350)

    Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering     Authority.(CVE-2022-50377)

    padata: Always leave BHs disabled when running -parallel()(CVE-2022-50382)

    nvme: fix multipath crash caused by flush request when blktrace is enabled(CVE-2022-50388)

    tpm: tpm_crb: Add the missed acpi_put_table() to fix memory leak(CVE-2022-50389)

    drm/ttm: fix undefined behavior in bit shift for TTM_TT_FLAG_PRIV_POPULATED(CVE-2022-50390)

    i2c: ismt: Fix an out-of-bounds bug in ismt_access()(CVE-2022-50394)

    ACPICA: Fix error code path in acpi_ds_call_control_method()(CVE-2022-50411)

    x86/fpu: Fix copy_xstate_to_uabi() to copy init states correctly(CVE-2022-50425)

    mmc: vub300: fix warning - do not call blocking ops when !TASK_RUNNING(CVE-2022-50430)

    drm/vmwgfx: Validate the box size for the snooped cursor(CVE-2022-50440)

    cpufreq: Init completion before kobject_init_and_add()(CVE-2022-50473)

    ext4: add EXT4_IGET_BAD flag to prevent unexpected bad inode(CVE-2022-50485)

    scsi: qla2xxx: Fix crash when I/O abort times out(CVE-2022-50493)

    binfmt_misc: fix shift-out-of-bounds in check_special_flags(CVE-2022-50497)

    perf/smmuv3: Fix hotplug callback leak in arm_smmu_pmu_init()(CVE-2022-50510)

    tracing/hist: Fix out-of-bound write on 'action_data.var_ref_idx'(CVE-2022-50553)

    ext4: avoid deadlock in fs reclaim with page writeback(CVE-2023-53149)

    tracing: Fix null pointer dereference in tracing_err_log_open()(CVE-2023-53167)

    vfio/type1: prevent underflow of locked_vm via exec()(CVE-2023-53171)

    serial: 8250: Reinit port-pm on port specific driver unbind(CVE-2023-53176)

    mm: fix zswap writeback race condition(CVE-2023-53178)

    sched/fair: Don't balance task to its current running CPU(CVE-2023-53215)

    arm64: efi: Make efi_rt_lock a raw_spinlock(CVE-2023-53216)

    media: az6007: Fix null-ptr-deref in az6007_i2c_xfer()(CVE-2023-53220)

    bpf: Fix memleak due to fentry attach failure(CVE-2023-53221)

    thermal/drivers/hisi: Drop second sensor hi3660(CVE-2023-53242)

    firmware: dmi-sysfs: Fix null-ptr-deref in dmi_sysfs_register_handle(CVE-2023-53250)

    VMCI: check context-notify_page after call to get_user_pages_fast() to avoid GPF(CVE-2023-53259)

    ext4: fix i_disksize exceeding i_size problem in paritally written case(CVE-2023-53270)

    scsi: qla2xxx: Remove unused nvme_ls_waitq wait queue(CVE-2023-53280)

    ext4: add bounds checking in get_max_inline_xattr_value_size()(CVE-2023-53285)

    drm/client: Fix memory leak in drm_client_modeset_probe(CVE-2023-53288)

    ext4: fix WARNING in mb_find_extent(CVE-2023-53317)

    recordmcount: Fix memory leaks in the uwrite function(CVE-2023-53318)

    genirq/ipi: Fix NULL pointer deref in irq_data_get_affinity_mask()(CVE-2023-53332)

    tracing: Fix race issue between cpu buffer write and swap(CVE-2023-53368)

    crypto: seqiv - Handle EBUSY correctly(CVE-2023-53373)

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

    ACPICA: Add AML_NO_OPERAND_RESOLVE flag to Timer(CVE-2023-53395)

    mm: kmem: fix a NULL pointer dereference in obj_stock_flush_required()(CVE-2023-53401)

    blk-cgroup: Reinit blkg_iostat_set after clearing in blkcg_reset_stats()(CVE-2023-53421)

    media: uvcvideo: Handle cameras with invalid descriptors(CVE-2023-53437)

    bpf: cpumap: Fix memory leak in cpu_map_update_elem(CVE-2023-53441)

    ext4: remove a BUG_ON in ext4_mb_release_group_pa()(CVE-2023-53450)

    scsi: qla4xxx: Add length check when parsing nlattrs(CVE-2023-53456)

    kobject: Add sanity check for kset-kobj.ktype in kset_register()(CVE-2023-53480)

    ext4: allow ext4_get_group_info() to fail(CVE-2023-53503)

    udf: Do not bother merging very long extents(CVE-2023-53506)

    virtio-mmio: don't break lifecycle of vm_dev(CVE-2023-53515)

    scsi: ses: Fix slab-out-of-bounds in ses_intf_remove()(CVE-2023-53521)

    scsi: qla2xxx: Use raw_smp_processor_id() instead of smp_processor_id()(CVE-2023-53530)

    tracing/histograms: Add histograms to hist_vars if they have referenced variables(CVE-2023-53560)

    null_blk: Always check queue mode setting from configfs(CVE-2023-53576)

    bpf, cpumap: Make sure kthread is running before map update returns(CVE-2023-53577)

    ring-buffer: Sync IRQ works before buffer destruction(CVE-2023-53587)

    ipmi_si: fix a memleak in try_smi_init()(CVE-2023-53611)

    ext4: fix possible double unlock when moving a directory(CVE-2023-53626)

    bnxt: avoid overflow in bnxt_get_nvram_directory()(CVE-2023-53661)

    ring-buffer: Fix deadloop issue on reading trace_pipe(CVE-2023-53668)

    A transient execution vulnerability in some AMD processors may allow an attacker to infer data in the L1D     cache, potentially resulting in the leakage of sensitive information across privileged     boundaries.(CVE-2024-36357)

    drm/dp_mst: Fix MST sideband message body length check(CVE-2024-56616)

    tls: stop recv() if initial process_rx_list gave us non-DATA(CVE-2024-58239)

    crypto: algif_hash - fix double free in hash_accept(CVE-2025-38079)

    thunderbolt: Do not double dequeue a configuration request(CVE-2025-38174)

    mm: fix uprobe pte be overwritten when expanding vma(CVE-2025-38207)

    scsi: lpfc: Use memcpy() for BIOS version(CVE-2025-38332)

    x86/sgx: Prevent attempts to reclaim poisoned pages(CVE-2025-38334)

    HID: core: do not bypass hid_hw_raw_request(CVE-2025-38494)

    clone_private_mnt(): make sure that caller has CAP_SYS_ADMIN in the right userns(CVE-2025-38499)

    bpf: Fix oob access in cgroup local storage(CVE-2025-38502)

    drm/sched: Increment job count before swapping tail spsc queue(CVE-2025-38515)

    pinctrl: qcom: msm: mark certain pins as invalid for interrupts(CVE-2025-38516)

    HID: quirks: Add quirk for 2 Chicony Electronics HP 5MP Cameras(CVE-2025-38540)

    net/sched: Restrict conditions for adding duplicating netems to qdisc tree(CVE-2025-38553)

    crypto: ccp - Fix crash when rebind ccp device for ccp.ko(CVE-2025-38581)

    padata: Fix pd UAF once and for all(CVE-2025-38584)

    net: drop UFO packets in udp_rcv_segment()(CVE-2025-38622)

    regulator: core: fix NULL dereference on unbind due to stale coupling data(CVE-2025-38668)

    media: uvcvideo: Fix 1-byte out-of-bounds read in uvc_parse_format()(CVE-2025-38680)

    fbdev: Fix vmalloc out-of-bounds write in fast_imageblit(CVE-2025-38685)

    media: dvb-frontends: w7090p: fix null-ptr-deref in w7090p_tuner_write_serpar and     w7090p_tuner_read_serpar(CVE-2025-38693)

    scsi: lpfc: Check for hdwq null ptr when cleaning up lpfc_vport structure(CVE-2025-38695)

    ext4: do not BUG when INLINE_DATA_FL lacks system.data xattr(CVE-2025-38701)

    x86/cpu/hygon: Add missing resctrl_cpu_detect() in bsp_init helper(CVE-2025-39681)

    tracing: Limit access to parser-buffer when trace_get_user failed(CVE-2025-39683)

    ftrace: Also allocate and copy hash for reading of filter files(CVE-2025-39689)

    fs/buffer: fix use-after-free when call bh_read() helper(CVE-2025-39691)

    serial: 8250: fix panic due to PSLVERR(CVE-2025-39724)

    rcu: Fix rcu_read_unlock() deadloop due to IRQ work(CVE-2025-39744)

    rcu: Protect -defer_qs_iw_pending from data race(CVE-2025-39749)

    usb: core: config: Prevent OOB read in SS endpoint companion parsing(CVE-2025-39760)

    jbd2: prevent softlockup in jbd2_log_do_checkpoint()(CVE-2025-39782)

    ftrace: Fix potential warning in trace_printk_seq during ftrace_dump(CVE-2025-39813)

    trace/fgraph: Fix the warning caused by missing unregister notifier(CVE-2025-39829)

    vxlan: Fix NPD in {arp,neigh}_reduce() when using nexthop objects(CVE-2025-39850)

    vxlan: Fix NPD when refreshing an FDB entry with a nexthop object(CVE-2025-39851)

    tee: fix NULL pointer dereference in tee_shm_put(CVE-2025-39865)

    fs: writeback: fix use-after-free in __mark_inode_dirty()(CVE-2025-39866)

    cgroup: split cgroup_destroy_wq into 3 workqueues(CVE-2025-39953)

    fbcon: fix integer overflow in fbcon_do_set_font(CVE-2025-39967)

    i40e: add max boundary check for VF filters(CVE-2025-39968)

    i40e: fix idx validation in config queues msg(CVE-2025-39971)

    i40e: add validation for ring_len param(CVE-2025-39973)

Tenable has extracted the preceding description block directly from the EulerOS kernel 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 remote SUSE Linux SLES12 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2025:4189-1 advisory.

    The SUSE Linux Enterprise 12 SP5 kernel was updated to fix various security issues

    The following security issues were fixed:

    - CVE-2021-4460: drm/amdkfd: Fix UBSAN shift-out-of-bounds warning (bsc#1250764).
    - CVE-2022-48631: ext4: fix bug in extents parsing when eh_entries == 0 and eh_depth > 0 (bsc#1223475).
    - CVE-2022-50236: iommu/mediatek: Fix crash on isr after kexec() (bsc#1249702).
    - CVE-2022-50249: memory: of: Fix refcount leak bug in of_get_ddr_timings() (bsc#1249747).
    - CVE-2022-50280: pnode: terminate at peers of source (bsc#1249806).
    - CVE-2022-50293: btrfs: do not BUG_ON() on ENOMEM when dropping extent items for a range (bsc#1249752).
    - CVE-2022-50327: ACPI: processor: idle: Check acpi_fetch_acpi_dev() return value (bsc#1249859).
    - CVE-2022-50350: scsi: target: iscsi: Fix a race condition between login_work and the login thread     (bsc#1250261).
    - CVE-2022-50356: net: sched: sfb: fix null pointer access issue when sfb_init() fails (bsc#1250040).
    - CVE-2022-50367: fs: fix UAF/GPF bug in nilfs_mdt_destroy (bsc#1250277).
    - CVE-2022-50394: i2c: ismt: Fix an out-of-bounds bug in ismt_access() (bsc#1250107).
    - CVE-2022-50395: integrity: Fix memory leakage in keyring allocation error path (bsc#1250211).
    - CVE-2022-50423: ACPICA: Fix use-after-free in acpi_ut_copy_ipackage_to_ipackage() (bsc#1250784).
    - CVE-2022-50443: drm/rockchip: lvds: fix PM usage counter unbalance in poweron (bsc#1250768).
    - CVE-2022-50459: scsi: iscsi: iscsi_tcp: Fix null-ptr-deref while calling getpeername() (bsc#1250850).
    - CVE-2022-50481: cxl: fix possible null-ptr-deref in cxl_guest_init_afu|adapter() (bsc#1251051).
    - CVE-2022-50485: ext4: add EXT4_IGET_BAD flag to prevent unexpected bad inode (bsc#1251197).
    - CVE-2022-50505: iommu/amd: Fix pci device refcount leak in ppr_notifier() (bsc#1251086).
    - CVE-2022-50516: fs: dlm: fix invalid derefence of sb_lvbptr (bsc#1251741).
    - CVE-2022-50542: media: si470x: Fix use-after-free in si470x_int_in_callback() (bsc#1251330).
    - CVE-2022-50571: btrfs: call __btrfs_remove_free_space_cache_locked on cache load failure (bsc#1252487).
    - CVE-2023-53183: btrfs: exit gracefully if reloc roots don't match (bsc#1249863).
    - CVE-2023-53185: wifi: ath9k: don't allow to overwrite ENDPOINT0 attributes (bsc#1249820).
    - CVE-2023-53188: net: openvswitch: fix race on port output (bsc#1249854).
    - CVE-2023-53191: irqchip/alpine-msi: Fix refcount leak in alpine_msix_init_domains (bsc#1249721).
    - CVE-2023-53204: af_unix: Fix data-races around user->unix_inflight (bsc#1249682).
    - CVE-2023-53271: ubi: Fix unreferenced object reported by kmemleak in ubi_resize_volume() (bsc#1249916).
    - CVE-2023-53282: scsi: lpfc: Fix use-after-free KFENCE violation during sysfs firmware write     (bsc#1250311).
    - CVE-2023-53289: media: bdisp: Add missing check for create_workqueue (bsc#1249941).
    - CVE-2023-53292: blk-mq: protect q->elevator by ->sysfs_lock in blk_mq_elv_switch_none (bsc#1250163).
    - CVE-2023-53338: lwt: Fix return values of BPF xmit ops (bsc#1250074).
    - CVE-2023-53339: btrfs: fix BUG_ON condition in btrfs_cancel_balance (bsc#1250329).
    - CVE-2023-53373: crypto: seqiv - Handle EBUSY correctly (bsc#1250137).
    - CVE-2023-53433: net: add vlan_get_protocol_and_depth() helper (bsc#1250164).
    - CVE-2023-53476: iw_cxgb4: Fix potential NULL dereference in c4iw_fill_res_cm_id_entry() (bsc#1250839).
    - CVE-2023-53477: ipv6: Add lwtunnel encap size of all siblings in nexthop calculation (bsc#1250840).
    - CVE-2023-53484: lib: cpu_rmap: Avoid use after free on rmap->obj array entries (bsc#1250895).
    - CVE-2023-53517: tipc: do not update mtu if msg_max is too small in mtu negotiation (bsc#1250919).
    - CVE-2023-53519: media: v4l2-mem2mem: add lock to protect parameter num_rdy (bsc#1250964).
    - CVE-2023-53540: wifi: cfg80211: reject auth/assoc to AP with our address (bsc#1251053).
    - CVE-2023-53548: net: usbnet: Fix WARNING in usbnet_start_xmit/usb_submit_urb (bsc#1251066).
    - CVE-2023-53556: iavf: Fix use-after-free in free_netdev (bsc#1251059).
    - CVE-2023-53559: ip_vti: fix potential slab-use-after-free in decode_session6 (bsc#1251052).
    - CVE-2023-53582: wifi: brcmfmac: ensure CLM version is null-terminated to prevent stack-out-of-bounds     (bsc#1251061).
    - CVE-2023-53589: wifi: iwlwifi: mvm: don't trust firmware n_channels (bsc#1251129).
    - CVE-2023-53593: cifs: Release folio lock on fscache read hit (bsc#1251132).
    - CVE-2023-53594: driver core: fix resource leak in device_add() (bsc#1251166).
    - CVE-2023-53596: drivers: base: Free devm resources when unregistering a device (bsc#1251161).
    - CVE-2023-53619: netfilter: conntrack: Avoid nf_ct_helper_hash uses after free (bsc#1251743).
    - CVE-2023-53620: md: fix soft lockup in status_resync.
    - CVE-2023-53624: net/sched: sch_fq: fix integer overflow of 'credit' (bsc#1251333).
    - CVE-2023-53635: netfilter: conntrack: fix wrong ct->timeout value (bsc#1251524).
    - CVE-2023-53648: ALSA: ac97: Fix possible NULL dereference in snd_ac97_mixer (bsc#1251750).
    - CVE-2023-53687: tty: serial: samsung_tty: Fix a memory leak in s3c24xx_serial_getclk() when iterating     clk (bsc#1251772).
    - CVE-2023-53695: udf: Detect system inodes linked into directory hierarchy (bsc#1252539).
    - CVE-2023-53705: ipv6: Fix out-of-bounds access in ipv6_find_tlv() (bsc#1252554).
    - CVE-2023-53707: drm/amdgpu: Fix integer overflow in amdgpu_cs_pass1 (bsc#1252632).
    - CVE-2023-53715: wifi: brcmfmac: cfg80211: Pass the PMK in binary instead of hex (bsc#1252545).
    - CVE-2023-53717: wifi: ath9k: Fix potential stack-out-of-bounds write in ath9k_wmi_rsp_callback()     (bsc#1252560).
    - CVE-2023-53733: net: sched: cls_u32: Undo tcf_bind_filter if u32_replace_hw_knode (bsc#1252685).
    - CVE-2025-38539: trace/fgraph: Fix the warning caused by missing unregister notifier (bsc#1248211).
    - CVE-2025-38680: media: uvcvideo: Fix 1-byte out-of-bounds read in uvc_parse_format() (bsc#1249203).
    - CVE-2025-38691: pNFS: Fix uninited ptr deref in block/scsi layout (bsc#1249215).
    - CVE-2025-38695: scsi: lpfc: Check for hdwq null ptr when cleaning up lpfc_vport structure (bsc#1249285).
    - CVE-2025-38699: scsi: bfa: Double-free fix (bsc#1249224).
    - CVE-2025-38700: scsi: libiscsi: Initialize iscsi_conn->dd_data only if memory is allocated     (bsc#1249182).
    - CVE-2025-38714: hfsplus: fix slab-out-of-bounds in hfsplus_bnode_read() (bsc#1249260).
    - CVE-2025-38718: sctp: linearize cloned gso packets in sctp_rcv (bsc#1249161).
    - CVE-2025-38724: nfsd: handle get_client_locked() failure in nfsd4_setclientid_confirm() (bsc#1249169).
    - CVE-2025-39676: scsi: qla4xxx: Prevent a potential error pointer dereference (bsc#1249302).
    - CVE-2025-39702: ipv6: sr: Fix MAC comparison to be constant-time (bsc#1249317).
    - CVE-2025-39724: serial: 8250: fix panic due to PSLVERR (bsc#1249265).
    - CVE-2025-39756: fs: Prevent file descriptor table allocations exceeding INT_MAX (bsc#1249512).
    - CVE-2025-39772: drm/hisilicon/hibmc: fix the hibmc loaded failed bug (bsc#1249506).
    - CVE-2025-39812: sctp: initialize more fields in sctp_v6_from_sk() (bsc#1250202).
    - CVE-2025-39813: ftrace: Fix potential warning in trace_printk_seq during ftrace_dump (bsc#1250032).
    - CVE-2025-39841: scsi: lpfc: Fix buffer free/clear order in deferred receive path (bsc#1250274).
    - CVE-2025-39866: fs: writeback: fix use-after-free in __mark_inode_dirty() (bsc#1250455).
    - CVE-2025-39876: net: fec: Fix possible NPD in fec_enet_phy_reset_after_clk_enable() (bsc#1250400).
    - CVE-2025-39911: i40e: fix IRQ freeing in i40e_vsi_request_irq_msix error path (bsc#1250704).
    - CVE-2025-39923: dmaengine: qcom: bam_dma: Fix DT error handling for num-channels/ees (bsc#1250741).
    - CVE-2025-39929: smb: client: fix smbdirect_recv_io leak in smbd_negotiate() error path (bsc#1251036).
    - CVE-2025-39931: crypto: af_alg - Set merge to zero early in af_alg_sendmsg (bsc#1251100).
    - CVE-2025-39945: cnic: Fix use-after-free bugs in cnic_delete_task (bsc#1251230).
    - CVE-2025-39949: qed: Don't collect too many protection override GRC elements (bsc#1251177).
    - CVE-2025-39955: tcp: Clear tcp_sk(sk)->fastopen_rsk in tcp_disconnect() (bsc#1251804).
    - CVE-2025-39968: i40e: add max boundary check for VF filters (bsc#1252047).
    - CVE-2025-39970: i40e: Fix filter input checks to prevent config with invalid values (bsc#1252051).
    - CVE-2025-39971: i40e: Add bounds check for ch[] array (bsc#1252052).
    - CVE-2025-39972: i40e: fix idx validation in i40e_validate_queue_map (bsc#1252039).
    - CVE-2025-39973: i40e: add validation for ring_len param (bsc#1252035).
    - CVE-2025-39997: ALSA: usb-audio: fix race condition to UAF in snd_usbmidi_free (bsc#1252056).
    - CVE-2025-40018: ipvs: Defer ip_vs_ftp unregister during netns cleanup (bsc#1252688).
    - CVE-2025-40044: fs: udf: fix OOB read in lengthAllocDescs handling (bsc#1252785).
    - CVE-2025-40049: Squashfs: fix uninit-value in squashfs_get_parent (bsc#1252822).
    - CVE-2025-40078: bpf: Explicitly check accesses to bpf_sock_addr (bsc#1252789).
    - CVE-2025-40082: hfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc() (bsc#1252775).
    - CVE-2025-40088: hfsplus: fix slab-out-of-bounds read in hfsplus_strcasecmp() (bsc#1252904).

    The following non security issues were fixed:

    - NFSv4.1: fix backchannel max_resp_sz verification check (bsc#1247518).
    - net: hv_netvsc: fix loss of early receive events from host during channel open (bsc#1252265).
    - openvswitch: fix lockup on tx to unregistering netdev with carrier (bsc#1249854)

Tenable has extracted the preceding description block directly from the SUSE 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.

  - pnode: terminate at peers of source The propagate_mnt() function handles mount propagation when creating     mounts and propagates the source mount tree @source_mnt to all applicable nodes of the destination     propagation mount tree headed by @dest_mnt. Unfortunately it contains a bug where it fails to terminate at     peers of @source_mnt when looking up copies of the source mount that become masters for copies of the     source mount tree mounted on top of slaves in the destination propagation tree causing a NULL dereference.
    Once the mechanics of the bug are understood it's easy to trigger. Because of unprivileged user namespaces     it is available to unprivileged users. While fixing this bug we've gotten confused multiple times due to     unclear terminology or missing concepts. So let's start this with some clarifications: * The terms     master or peer denote a shared mount. A shared mount belongs to a peer group. * A peer group is a set     of shared mounts that propagate to each other. They are identified by a peer group id. The peer group id     is available in @shared_mnt->mnt_group_id. Shared mounts within the same peer group have the same peer     group id. The peers in a peer group can be reached via @shared_mnt->mnt_share. * The terms slave mount     or dependent mount denote a mount that receives propagation from a peer in a peer group. IOW, shared     mounts may have slave mounts and slave mounts have shared mounts as their master. Slave mounts of a given     peer in a peer group are listed on that peers slave list available at @shared_mnt->mnt_slave_list. * The     term master mount denotes a mount in a peer group. IOW, it denotes a shared mount or a peer mount in a     peer group. The term master mount - or master for short - is mostly used when talking in the context     of slave mounts that receive propagation from a master mount. A master mount of a slave identifies the     closest peer group a slave mount receives propagation from. The master mount of a slave can be identified     via @slave_mount->mnt_master. Different slaves may point to different masters in the same peer group. *     Multiple peers in a peer group can have non-empty ->mnt_slave_lists. Non-empty ->mnt_slave_lists of peers     don't intersect. Consequently, to ensure all slave mounts of a peer group are visited the
    ->mnt_slave_lists of all peers in a peer group have to be walked. * Slave mounts point to a peer in the     closest peer group they receive propagation from via @slave_mnt->mnt_master (see above). Together with     these peers they form a propagation group (see below). The closest peer group can thus be identified     through the peer group id @slave_mnt->mnt_master->mnt_group_id of the peer/master that a slave mount     receives propagation from. * A shared-slave mount is a slave mount to a peer group pg1 while also a peer     in another peer group pg2. IOW, a peer group may receive propagation from another peer group. If a peer     group pg1 is a slave to another peer group pg2 then all peers in peer group pg1 point to the same peer in     peer group pg2 via ->mnt_master. IOW, all peers in peer group pg1 appear on the same ->mnt_slave_list.
    IOW, they cannot be slaves to different peer groups. * A pure slave mount is a slave mount that is a slave     to a peer group but is not a peer in another peer group. * A propagation group denotes the set of mounts     consisting of a single peer group pg1 and all slave mounts and shared-slave mounts that point to a peer in     that peer group via ->mnt_master. IOW, all slave mounts such that @slave_mnt->mnt_master->mnt_group_id is     equal to @shared_mnt->mnt_group_id. The concept of a propagation group makes it easier to talk about a     single propagation level in a propagation tree. For example, in propagate_mnt() the immediate peers of     @dest_mnt and all slaves of @dest_mnt's peer group form a propagation group pr ---truncated---     (CVE-2022-50280)

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.4.231-137.341. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.4-2023-042 advisory.

    A flaw was found in the Linux kernel's Layer 2 Tunneling Protocol (L2TP). A missing lock when clearing     sk_user_data can lead to a race condition and NULL pointer dereference. A local user could use this flaw     to potentially crash the system causing a denial of service. (CVE-2022-4129)

    In the Linux kernel before 6.1.6, a NULL pointer dereference bug in the traffic control subsystem allows     an unprivileged user to trigger a denial of service (system crash) via a crafted traffic control     configuration that is set up with tc qdisc and tc class commands. This affects qdisc_graft in     net/sched/sch_api.c. (CVE-2022-47929)

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

    efi: fix NULL-deref in init error path (CVE-2022-48879)

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

    ixgbe: fix pci device refcount leak (CVE-2022-48896)

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

    drm/virtio: Fix GEM handle creation UAF (CVE-2022-48899)

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

    udf: Fix preallocation discarding at indirect extent boundary (CVE-2022-48946)

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

    igb: Initialize mailbox message for VF reset (CVE-2022-48949)

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

    perf/x86/amd: fix potential integer overflow on shift of a int (CVE-2022-49748)

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

    dmaengine: Fix double increment of client_count in dma_chan_get() (CVE-2022-49753)

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

    drivers: net: qlcnic: Fix potential memory leak in qlcnic_sriov_init() (CVE-2022-50242)

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

    regulator: core: fix use_count leakage when handling boot-on (CVE-2022-50250)

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

    mmc: vub300: fix return value check of mmc_add_host() (CVE-2022-50251)

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

    igb: Do not free q_vector unless new one was allocated (CVE-2022-50252)

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

    bpf: make sure skb->len != 0 when redirecting to a tunneling device (CVE-2022-50253)

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

    bpf, sockmap: fix race in sock_map_free() (CVE-2022-50259)

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

    drm/radeon: Add the missed acpi_put_table() to fix memory leak (CVE-2022-50275)

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

    power: supply: fix null pointer dereferencing in power_supply_get_battery_info (CVE-2022-50276)

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

    PNP: fix name memory leak in pnp_alloc_dev() (CVE-2022-50278)

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

    pnode: terminate at peers of source (CVE-2022-50280)

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

    chardev: fix error handling in cdev_device_add() (CVE-2022-50282)

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

    ext4: fix delayed allocation bug in ext4_clu_mapped for bigalloc + inline (CVE-2022-50286)

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

    qlcnic: prevent ->dcb use-after-free on qlcnic_dcb_enable() failure (CVE-2022-50288)

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

    perf/x86/intel/uncore: Fix reference count leak in hswep_has_limit_sbox() (CVE-2022-50318)

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

    fs: jfs: fix shift-out-of-bounds in dbDiscardAG (CVE-2022-50333)

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

    hugetlbfs: fix null-ptr-deref in hugetlbfs_parse_param() (CVE-2022-50334)

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

    cifs: fix oops during encryption (CVE-2022-50341)

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

    rapidio: fix possible name leaks when rio_add_device() fails (CVE-2022-50343)

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

    ext4: init quota for 'old.inode' in 'ext4_rename' (CVE-2022-50346)

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

    misc: tifm: fix possible memory leak in tifm_7xx1_switch_media() (CVE-2022-50349)

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

    skbuff: Account for tail adjustment during pull operations (CVE-2022-50365)

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

    md: fix a crash in mempool_free (CVE-2022-50381)

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

    tpm: tpm_crb: Add the missed acpi_put_table() to fix memory leak (CVE-2022-50389)

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

    integrity: Fix memory leakage in keyring allocation error path (CVE-2022-50395)

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

    net: sched: fix memory leak in tcindex_set_parms (CVE-2022-50396)

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

    nfsd: under NFSv4.1, fix double svc_xprt_put on rpc_create failure (CVE-2022-50401)

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

    drivers/md/md-bitmap: check the return value of md_bitmap_get_counter() (CVE-2022-50402)

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

    net/tunnel: wait until all sk_user_data reader finish before releasing the sock (CVE-2022-50405)

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

    ACPICA: Fix error code path in acpi_ds_call_control_method() (CVE-2022-50411)

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

    scsi: fcoe: Fix transport not deattached when fcoe_if_init() fails (CVE-2022-50414)

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

    ACPICA: Fix use-after-free in acpi_ut_copy_ipackage_to_ipackage() (CVE-2022-50423)

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

    mmc: vub300: fix warning - do not call blocking ops when !TASK_RUNNING (CVE-2022-50430)

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

    blk-mq: fix possible memleak when register 'hctx' failed (CVE-2022-50434)

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

    btrfs: fix resolving backrefs for inline extent followed by prealloc (CVE-2022-50456)

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

    MIPS: vpe-mt: fix possible memory leak while module exiting (CVE-2022-50462)

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

    cpufreq: Init completion before kobject_init_and_add() (CVE-2022-50473)

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

    macintosh: fix possible memory leak in macio_add_one_device() (CVE-2022-50474)

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

    nilfs2: fix shift-out-of-bounds/overflow in nilfs_sb2_bad_offset() (CVE-2022-50478)

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

    ext4: add EXT4_IGET_BAD flag to prevent unexpected bad inode (CVE-2022-50485)

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

    dm cache: Fix UAF in destroy() (CVE-2022-50496)

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

    binfmt_misc: fix shift-out-of-bounds in check_special_flags (CVE-2022-50497)

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

    mtd: lpddr2_nvm: Fix possible null-ptr-deref (CVE-2022-50503)

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

    lib/fonts: fix undefined behavior in bit shift for get_default_font (CVE-2022-50511)

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

    drm/radeon: Fix PCI device refcount leak in radeon_atrm_get_bios() (CVE-2022-50520)

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

    mcb: mcb-parse: fix error handing in chameleon_parse_gdd() (CVE-2022-50522)

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

    scsi: mpt3sas: Fix possible resource leaks in mpt3sas_transport_port_add() (CVE-2022-50532)

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

    dm thin: Use last transaction's pmd->root when commit failed (CVE-2022-50534)

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

    bpf, sockmap: Fix repeated calls to sock_put() when msg has more_data (CVE-2022-50536)

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

    dm thin: Fix ABBA deadlock between shrink_slab and dm_pool_abort_metadata (CVE-2022-50549)

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

    dm thin: Fix UAF in run_timer_softirq() (CVE-2022-50563)

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

    mtd: Fix device name leak when register device failed in add_mtd_device() (CVE-2022-50566)

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

    fs: jfs: fix shift-out-of-bounds in dbAllocAG (CVE-2022-50567)

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

    xen/privcmd: Fix a possible warning in privcmd_ioctl_mmap_resource() (CVE-2022-50575)

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

    class: fix possible memory leak in __class_register() (CVE-2022-50578)

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

    hfs: fix OOB Read in __hfs_brec_find (CVE-2022-50581)

    The Linux kernel does not correctly mitigate SMT attacks, as discovered through a strange pattern in the     kernel API using STIBP as a mitigation, leaving the process exposed for a short period of time after a     syscall. The kernel also does not issue an IBPB immediately during the syscall. (CVE-2023-0045)

    A NULL pointer dereference flaw was found in rawv6_push_pending_frames in net/ipv6/raw.c in the network     subcomponent in the Linux kernel. This flaw causes the system to crash. (CVE-2023-0394)

    Detected a few exploitable gadgets that could leak secret memory through a side-channel such as MDS as     well as insufficient hardening of the usercopy functions against spectre-v1. (CVE-2023-0459)

    There is a use-after-free vulnerability in the Linux Kernel which can be exploited to achieve local     privilege escalation. To reach the vulnerability kernel configuration flag CONFIG_TLS or     CONFIG_XFRM_ESPINTCP has to be configured, but the operation does not require any privilege.

    There is a use-after-free bug of icsk_ulp_data of a struct inet_connection_sock.

    When CONFIG_TLS is enabled, user can install a tls context (struct tls_context) on a connected tcp socket.
    The context is not cleared if this socket is disconnected and reused as a listener. If a new socket is     created from the listener, the context is inherited and vulnerable.

    The setsockopt TCP_ULP operation does not require any privilege.

    We recommend upgrading past commit 2c02d41d71f90a5168391b6a5f2954112ba2307c (CVE-2023-0461)

    A memory corruption flaw was found in the Linux kernel's human interface device (HID) subsystem in how a     user inserts a malicious USB device. This flaw allows a local user to crash or potentially escalate their     privileges on the system. (CVE-2023-1073)

    cbq_classify in net/sched/sch_cbq.c in the Linux kernel through 6.1.4 allows attackers to cause a denial     of service (slab-out-of-bounds read) because of type confusion (non-negative numbers can sometimes     indicate a TC_ACT_SHOT condition rather than valid classification results). (CVE-2023-23454)

    atm_tc_enqueue in net/sched/sch_atm.c in the Linux kernel through 6.1.4 allows attackers to cause a denial     of service because of type confusion (non-negative numbers can sometimes indicate a TC_ACT_SHOT condition     rather than valid classification results). (CVE-2023-23455)

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

    btrfs: fix race between quota rescan and disable leading to NULL pointer deref (CVE-2023-52896)

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

    xhci: Fix null pointer dereference when host dies (CVE-2023-52898)

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

    nilfs2: fix general protection fault in nilfs_btree_insert() (CVE-2023-52900)

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

    usb: xhci: Check endpoint is valid before dereferencing it (CVE-2023-52901)

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

    net/sched: act_mpls: Fix warning during failed attribute validation (CVE-2023-52906)

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

    bpf: Skip task with pid=1 in send_signal_common() (CVE-2023-52992)

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

    x86/i8259: Mark legacy PIC interrupts with IRQ_LEVEL (CVE-2023-52993)

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

    ipv4: prevent potential spectre v1 gadget in fib_metrics_match() (CVE-2023-52996)

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

    ipv4: prevent potential spectre v1 gadget in ip_metrics_convert() (CVE-2023-52997)

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

    net: fix UaF in netns ops registration error path (CVE-2023-52999)

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

    netlink: prevent potential spectre v1 gadgets (CVE-2023-53000)

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

    cifs: Fix oops due to uncleared server->smbd_conn in reconnect (CVE-2023-53006)

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

    tracing: Make sure trace_printk() can output as soon as it can be used (CVE-2023-53007)

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

    HID: betop: check shape of output reports (CVE-2023-53015)

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

    net: mdio: validate parameter addr in mdiobus_get_phy() (CVE-2023-53019)

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

    net/sched: sch_taprio: fix possible use-after-free (CVE-2023-53021)

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

    bpf: Fix pointer-leak due to insufficient speculative store bypass mitigation (CVE-2023-53024)

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

    RDMA/core: Fix ib block iterator counter overflow (CVE-2023-53026)

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

    netfilter: ipset: Fix overflow before widen in the bitmap_ip_create() function. (CVE-2023-53032)

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 4.14.304-226.531. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2-2023-1932 advisory.

    Guests can trigger NIC interface reset/abort/crash via netback It is possible for a guest to trigger a NIC     interface reset/abort/crash in a Linux based network backend by sending certain kinds of packets. It     appears to be an (unwritten?) assumption in the rest of the Linux network stack that packet protocol     headers are all contained within the linear section of the SKB and some NICs behave badly if this is not     the case. This has been reported to occur with Cisco (enic) and Broadcom NetXtrem II BCM5780 (bnx2x)     though it may be an issue with other NICs/drivers as well. In case the frontend is sending requests with     split headers, netback will forward those violating above mentioned assumption to the networking core,     resulting in said misbehavior. (CVE-2022-3643)

    Guests can trigger deadlock in Linux netback driver T[his CNA information record relates to multiple CVEs;
    the text explains which aspects/vulnerabilities correspond to which CVE.] The patch for XSA-392 introduced     another issue which might result in a deadlock when trying to free the SKB of a packet dropped due to the     XSA-392 handling (CVE-2022-42328). Additionally when dropping packages for other reasons the same deadlock     could occur in case of netpoll being active for the interface the xen-netback driver is connected to     (CVE-2022-42329). (CVE-2022-42328)

    Guests can trigger deadlock in Linux netback driver T[his CNA information record relates to multiple CVEs;
    the text explains which aspects/vulnerabilities correspond to which CVE.] The patch for XSA-392 introduced     another issue which might result in a deadlock when trying to free the SKB of a packet dropped due to the     XSA-392 handling (CVE-2022-42328). Additionally when dropping packages for other reasons the same deadlock     could occur in case of netpoll being active for the interface the xen-netback driver is connected to     (CVE-2022-42329). (CVE-2022-42329)

    An issue was discovered in the Linux kernel through 6.0.10. l2cap_config_req in net/bluetooth/l2cap_core.c     has an integer wraparound via L2CAP_CONF_REQ packets. (CVE-2022-45934)

    In the Linux kernel before 6.1.6, a NULL pointer dereference bug in the traffic control subsystem allows     an unprivileged user to trigger a denial of service (system crash) via a crafted traffic control     configuration that is set up with tc qdisc and tc class commands. This affects qdisc_graft in     net/sched/sch_api.c. (CVE-2022-47929)

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

    udf: Fix preallocation discarding at indirect extent boundary (CVE-2022-48946)

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

    Bluetooth: L2CAP: Fix u8 overflow (CVE-2022-48947)

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

    igb: Initialize mailbox message for VF reset (CVE-2022-48949)

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

    ipv6: avoid use-after-free in ip6_fragment() (CVE-2022-48956)

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

    mac802154: fix missing INIT_LIST_HEAD in ieee802154_if_add() (CVE-2022-48972)

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

    HID: core: fix shift-out-of-bounds in hid_report_raw_event (CVE-2022-48978)

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

    media: v4l2-dv-timings.c: fix too strict blanking sanity checks (CVE-2022-48987)

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

    memcg: fix possible use-after-free in memcg_write_event_control() (CVE-2022-48988)

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

    mm/khugepaged: invoke MMU notifiers in shmem/file collapse paths (CVE-2022-48991)

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

    mmc: vub300: fix return value check of mmc_add_host() (CVE-2022-50251)

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

    igb: Do not free q_vector unless new one was allocated (CVE-2022-50252)

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

    bpf: make sure skb->len != 0 when redirecting to a tunneling device (CVE-2022-50253)

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

    drm/radeon: Add the missed acpi_put_table() to fix memory leak (CVE-2022-50275)

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

    PNP: fix name memory leak in pnp_alloc_dev() (CVE-2022-50278)

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

    pnode: terminate at peers of source (CVE-2022-50280)

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

    chardev: fix error handling in cdev_device_add() (CVE-2022-50282)

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

    fs: jfs: fix shift-out-of-bounds in dbDiscardAG (CVE-2022-50333)

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

    rapidio: fix possible name leaks when rio_add_device() fails (CVE-2022-50343)

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

    ext4: init quota for 'old.inode' in 'ext4_rename' (CVE-2022-50346)

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

    misc: tifm: fix possible memory leak in tifm_7xx1_switch_media() (CVE-2022-50349)

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

    skbuff: Account for tail adjustment during pull operations (CVE-2022-50365)

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

    md: fix a crash in mempool_free (CVE-2022-50381)

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

    tpm: tpm_crb: Add the missed acpi_put_table() to fix memory leak (CVE-2022-50389)

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

    nfsd: under NFSv4.1, fix double svc_xprt_put on rpc_create failure (CVE-2022-50401)

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

    net/tunnel: wait until all sk_user_data reader finish before releasing the sock (CVE-2022-50405)

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

    ACPICA: Fix error code path in acpi_ds_call_control_method() (CVE-2022-50411)

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

    scsi: fcoe: Fix transport not deattached when fcoe_if_init() fails (CVE-2022-50414)

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

    ACPICA: Fix use-after-free in acpi_ut_copy_ipackage_to_ipackage() (CVE-2022-50423)

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

    mmc: vub300: fix warning - do not call blocking ops when !TASK_RUNNING (CVE-2022-50430)

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

    blk-mq: fix possible memleak when register 'hctx' failed (CVE-2022-50434)

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

    MIPS: vpe-mt: fix possible memory leak while module exiting (CVE-2022-50462)

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

    macintosh: fix possible memory leak in macio_add_one_device() (CVE-2022-50474)

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

    nilfs2: fix shift-out-of-bounds/overflow in nilfs_sb2_bad_offset() (CVE-2022-50478)

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

    dm cache: Fix UAF in destroy() (CVE-2022-50496)

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

    binfmt_misc: fix shift-out-of-bounds in check_special_flags (CVE-2022-50497)

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

    mtd: lpddr2_nvm: Fix possible null-ptr-deref (CVE-2022-50503)

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

    iommu/amd: Fix pci device refcount leak in ppr_notifier() (CVE-2022-50505)

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

    drm/radeon: Fix PCI device refcount leak in radeon_atrm_get_bios() (CVE-2022-50520)

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

    mcb: mcb-parse: fix error handing in chameleon_parse_gdd() (CVE-2022-50522)

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

    dm thin: Use last transaction's pmd->root when commit failed (CVE-2022-50534)

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

    dm thin: Fix UAF in run_timer_softirq() (CVE-2022-50563)

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

    mtd: Fix device name leak when register device failed in add_mtd_device() (CVE-2022-50566)

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

    fs: jfs: fix shift-out-of-bounds in dbAllocAG (CVE-2022-50567)

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

    class: fix possible memory leak in __class_register() (CVE-2022-50578)

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

    hfs: fix OOB Read in __hfs_brec_find (CVE-2022-50581)

    The Linux kernel does not correctly mitigate SMT attacks, as discovered through a strange pattern in the     kernel API using STIBP as a mitigation, leaving the process exposed for a short period of time after a     syscall. The kernel also does not issue an IBPB immediately during the syscall. (CVE-2023-0045)

    A NULL pointer dereference flaw was found in rawv6_push_pending_frames in net/ipv6/raw.c in the network     subcomponent in the Linux kernel. This flaw causes the system to crash. (CVE-2023-0394)

    Detected a few exploitable gadgets that could leak secret memory through a side-channel such as MDS as     well as insufficient hardening of the usercopy functions against spectre-v1. (CVE-2023-0459)

    There is a use-after-free vulnerability in the Linux Kernel which can be exploited to achieve local     privilege escalation. To reach the vulnerability kernel configuration flag CONFIG_TLS or     CONFIG_XFRM_ESPINTCP has to be configured, but the operation does not require any privilege.

    There is a use-after-free bug of icsk_ulp_data of a struct inet_connection_sock.

    When CONFIG_TLS is enabled, user can install a tls context (struct tls_context) on a connected tcp socket.
    The context is not cleared if this socket is disconnected and reused as a listener. If a new socket is     created from the listener, the context is inherited and vulnerable.

    The setsockopt TCP_ULP operation does not require any privilege.

    We recommend upgrading past commit 2c02d41d71f90a5168391b6a5f2954112ba2307c (CVE-2023-0461)

    atm_tc_enqueue in net/sched/sch_atm.c in the Linux kernel through 6.1.4 allows attackers to cause a denial     of service because of type confusion (non-negative numbers can sometimes indicate a TC_ACT_SHOT condition     rather than valid classification results). (CVE-2023-23455)

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

    nilfs2: fix general protection fault in nilfs_btree_insert() (CVE-2023-52900)

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

    usb: xhci: Check endpoint is valid before dereferencing it (CVE-2023-52901)

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

    netfilter: ipset: Fix overflow before widen in the bitmap_ip_create() function. (CVE-2023-53032)

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.15.90-54.138. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.15-2023-013 advisory.

    In the Linux kernel before 6.1.6, a NULL pointer dereference bug in the traffic control subsystem allows     an unprivileged user to trigger a denial of service (system crash) via a crafted traffic control     configuration that is set up with tc qdisc and tc class commands. This affects qdisc_graft in     net/sched/sch_api.c. (CVE-2022-47929)

    A flaw NULL Pointer Dereference in the Linux kernel NTFS3 driver function attr_punch_hole() was found. A     local user could use this flaw to crash the system. (CVE-2022-4842)

    In the Linux kernel before 6.1.3, fs/ntfs3/inode.c does not validate the attribute name offset. An     unhandled page fault may occur. (CVE-2022-48424)

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

    efi: fix NULL-deref in init error path (CVE-2022-48879)

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

    sched/core: Fix use-after-free bug in dup_user_cpus_ptr() (CVE-2022-48892)

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

    fs/ntfs3: Validate BOOT record_size (CVE-2022-50262)

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

    pnode: terminate at peers of source (CVE-2022-50280)

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

    ext4: fix delayed allocation bug in ext4_clu_mapped for bigalloc + inline (CVE-2022-50286)

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

    btrfs: fix extent map use-after-free when handling missing device in read_one_chunk (CVE-2022-50300)

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

    ext4: fix potential out of bound read in ext4_fc_replay_scan() (CVE-2022-50306)

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

    block, bfq: fix uaf for bfqq in bfq_exit_icq_bfqq (CVE-2022-50329)

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

    fs/ntfs3: Add null pointer check to attr_load_runs_vcn (CVE-2022-50336)

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

    cifs: fix oops during encryption (CVE-2022-50341)

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

    ext4: init quota for 'old.inode' in 'ext4_rename' (CVE-2022-50346)

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

    md: fix a crash in mempool_free (CVE-2022-50381)

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

    nvme: fix multipath crash caused by flush request when blktrace is enabled (CVE-2022-50388)

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

    tpm: tpm_crb: Add the missed acpi_put_table() to fix memory leak (CVE-2022-50389)

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

    net: sched: fix memory leak in tcindex_set_parms (CVE-2022-50396)

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

    ext4: fix off-by-one errors in fast-commit block filling (CVE-2022-50428)

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

    ext4: don't set up encryption key during jbd2 transaction (CVE-2022-50436)

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

    fs/ntfs3: Validate buffer length while parsing index (CVE-2022-50442)

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

    fs/ntfs3: Fix memory leak on ntfs_fill_super() error path (CVE-2022-50451)

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

    btrfs: fix resolving backrefs for inline extent followed by prealloc (CVE-2022-50456)

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

    ext4: fix leaking uninitialized memory in fast-commit journal (CVE-2022-50465)

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

    cpufreq: Init completion before kobject_init_and_add() (CVE-2022-50473)

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

    ext4: add EXT4_IGET_BAD flag to prevent unexpected bad inode (CVE-2022-50485)

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

    dm cache: Fix UAF in destroy() (CVE-2022-50496)

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

    fs/ntfs3: Validate data run offset (CVE-2022-50507)

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

    dm thin: Use last transaction's pmd->root when commit failed (CVE-2022-50534)

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

    ext4: fix uninititialized value in 'ext4_evict_inode' (CVE-2022-50546)

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

    dm thin: Fix ABBA deadlock between shrink_slab and dm_pool_abort_metadata (CVE-2022-50549)

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

    tpm: acpi: Call acpi_put_table() to fix memory leak (CVE-2022-50562)

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

    dm thin: Fix UAF in run_timer_softirq() (CVE-2022-50563)

    The Linux kernel does not correctly mitigate SMT attacks, as discovered through a strange pattern in the     kernel API using STIBP as a mitigation, leaving the process exposed for a short period of time after a     syscall. The kernel also does not issue an IBPB immediately during the syscall. (CVE-2023-0045)

    A buffer overflow vulnerability was found in the Netfilter subsystem in the Linux Kernel. This issue could     allow the leakage of both stack and heap addresses, and potentially allow Local Privilege Escalation to     the root user via arbitrary code execution. (CVE-2023-0179)

    A NULL pointer dereference flaw was found in rawv6_push_pending_frames in net/ipv6/raw.c in the network     subcomponent in the Linux kernel. This flaw causes the system to crash. (CVE-2023-0394)

    Detected a few exploitable gadgets that could leak secret memory through a side-channel such as MDS as     well as insufficient hardening of the usercopy functions against spectre-v1. (CVE-2023-0459)

    There is a use-after-free vulnerability in the Linux Kernel which can be exploited to achieve local     privilege escalation. To reach the vulnerability kernel configuration flag CONFIG_TLS or     CONFIG_XFRM_ESPINTCP has to be configured, but the operation does not require any privilege.

    There is a use-after-free bug of icsk_ulp_data of a struct inet_connection_sock.

    When CONFIG_TLS is enabled, user can install a tls context (struct tls_context) on a connected tcp socket.
    The context is not cleared if this socket is disconnected and reused as a listener. If a new socket is     created from the listener, the context is inherited and vulnerable.

    The setsockopt TCP_ULP operation does not require any privilege.

    We recommend upgrading past commit 2c02d41d71f90a5168391b6a5f2954112ba2307c (CVE-2023-0461)

    cbq_classify in net/sched/sch_cbq.c in the Linux kernel through 6.1.4 allows attackers to cause a denial     of service (slab-out-of-bounds read) because of type confusion (non-negative numbers can sometimes     indicate a TC_ACT_SHOT condition rather than valid classification results). (CVE-2023-23454)

    atm_tc_enqueue in net/sched/sch_atm.c in the Linux kernel through 6.1.4 allows attackers to cause a denial     of service because of type confusion (non-negative numbers can sometimes indicate a TC_ACT_SHOT condition     rather than valid classification results). (CVE-2023-23455)

    In the Linux kernel 6.0.8, there is a use-after-free in run_unpack in fs/ntfs3/run.c, related to a     difference between NTFS sector size and media sector size. (CVE-2023-26544)

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

    btrfs: fix race between quota rescan and disable leading to NULL pointer deref (CVE-2023-52896)

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

    xhci: Fix null pointer dereference when host dies (CVE-2023-52898)

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

    usb: xhci: Check endpoint is valid before dereferencing it (CVE-2023-52901)

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

    io_uring: lock overflowing for IOPOLL (CVE-2023-52903)

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

    net/sched: act_mpls: Fix warning during failed attribute validation (CVE-2023-52906)

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

    iommu/iova: Fix alloc iova overflows issue (CVE-2023-52910)

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

    netfilter: ipset: Fix overflow before widen in the bitmap_ip_create() function. (CVE-2023-53032)

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

    netfilter: nft_payload: incorrect arithmetics when fetching VLAN header bits (CVE-2023-53033)

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

    fs/ntfs3: don't hold ni_lock when calling truncate_setsize() (CVE-2023-53163)

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

    netfilter: ipset: Rework long task execution when adding/deleting entries (CVE-2023-53549)

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.10.165-143.735. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.10-2023-026 advisory.

    In the Linux kernel before 6.1.6, a NULL pointer dereference bug in the traffic control subsystem allows     an unprivileged user to trigger a denial of service (system crash) via a crafted traffic control     configuration that is set up with tc qdisc and tc class commands. This affects qdisc_graft in     net/sched/sch_api.c. (CVE-2022-47929)

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

    efi: fix NULL-deref in init error path (CVE-2022-48879)

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

    ixgbe: fix pci device refcount leak (CVE-2022-48896)

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

    drm/virtio: Fix GEM handle creation UAF (CVE-2022-48899)

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

    rtc: cmos: Fix event handler registration ordering issue (CVE-2022-48953)

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

    drivers: net: qlcnic: Fix potential memory leak in qlcnic_sriov_init() (CVE-2022-50242)

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

    regulator: core: fix use_count leakage when handling boot-on (CVE-2022-50250)

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

    mmc: vub300: fix return value check of mmc_add_host() (CVE-2022-50251)

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

    igb: Do not free q_vector unless new one was allocated (CVE-2022-50252)

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

    bpf: make sure skb->len != 0 when redirecting to a tunneling device (CVE-2022-50253)

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

    bpf, sockmap: fix race in sock_map_free() (CVE-2022-50259)

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

    drm/radeon: Add the missed acpi_put_table() to fix memory leak (CVE-2022-50275)

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

    power: supply: fix null pointer dereferencing in power_supply_get_battery_info (CVE-2022-50276)

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

    PNP: fix name memory leak in pnp_alloc_dev() (CVE-2022-50278)

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

    pnode: terminate at peers of source (CVE-2022-50280)

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

    chardev: fix error handling in cdev_device_add() (CVE-2022-50282)

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

    ext4: fix delayed allocation bug in ext4_clu_mapped for bigalloc + inline (CVE-2022-50286)

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

    qlcnic: prevent ->dcb use-after-free on qlcnic_dcb_enable() failure (CVE-2022-50288)

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

    perf/x86/intel/uncore: Fix reference count leak in hswep_has_limit_sbox() (CVE-2022-50318)

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

    fs: jfs: fix shift-out-of-bounds in dbDiscardAG (CVE-2022-50333)

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

    hugetlbfs: fix null-ptr-deref in hugetlbfs_parse_param() (CVE-2022-50334)

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

    cifs: fix oops during encryption (CVE-2022-50341)

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

    rapidio: fix possible name leaks when rio_add_device() fails (CVE-2022-50343)

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

    ext4: init quota for 'old.inode' in 'ext4_rename' (CVE-2022-50346)

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

    misc: tifm: fix possible memory leak in tifm_7xx1_switch_media() (CVE-2022-50349)

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

    skbuff: Account for tail adjustment during pull operations (CVE-2022-50365)

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

    md: fix a crash in mempool_free (CVE-2022-50381)

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

    padata: Always leave BHs disabled when running ->parallel() (CVE-2022-50382)

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

    NFS: Fix an Oops in nfs_d_automount() (CVE-2022-50385)

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

    nvme: fix multipath crash caused by flush request when blktrace is enabled (CVE-2022-50388)

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

    tpm: tpm_crb: Add the missed acpi_put_table() to fix memory leak (CVE-2022-50389)

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

    integrity: Fix memory leakage in keyring allocation error path (CVE-2022-50395)

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

    net: sched: fix memory leak in tcindex_set_parms (CVE-2022-50396)

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

    nfsd: under NFSv4.1, fix double svc_xprt_put on rpc_create failure (CVE-2022-50401)

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

    drivers/md/md-bitmap: check the return value of md_bitmap_get_counter() (CVE-2022-50402)

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

    net/tunnel: wait until all sk_user_data reader finish before releasing the sock (CVE-2022-50405)

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

    ACPICA: Fix error code path in acpi_ds_call_control_method() (CVE-2022-50411)

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

    scsi: fcoe: Fix transport not deattached when fcoe_if_init() fails (CVE-2022-50414)

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

    ACPICA: Fix use-after-free in acpi_ut_copy_ipackage_to_ipackage() (CVE-2022-50423)

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

    mmc: vub300: fix warning - do not call blocking ops when !TASK_RUNNING (CVE-2022-50430)

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

    blk-mq: fix possible memleak when register 'hctx' failed (CVE-2022-50434)

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

    ext4: don't set up encryption key during jbd2 transaction (CVE-2022-50436)

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

    gpiolib: cdev: fix NULL-pointer dereferences (CVE-2022-50453)

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

    btrfs: fix resolving backrefs for inline extent followed by prealloc (CVE-2022-50456)

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

    MIPS: vpe-mt: fix possible memory leak while module exiting (CVE-2022-50462)

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

    ext4: fix leaking uninitialized memory in fast-commit journal (CVE-2022-50465)

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

    cpufreq: Init completion before kobject_init_and_add() (CVE-2022-50473)

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

    macintosh: fix possible memory leak in macio_add_one_device() (CVE-2022-50474)

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

    nilfs2: fix shift-out-of-bounds/overflow in nilfs_sb2_bad_offset() (CVE-2022-50478)

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

    ext4: add EXT4_IGET_BAD flag to prevent unexpected bad inode (CVE-2022-50485)

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

    dm cache: Fix UAF in destroy() (CVE-2022-50496)

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

    binfmt_misc: fix shift-out-of-bounds in check_special_flags (CVE-2022-50497)

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

    mtd: lpddr2_nvm: Fix possible null-ptr-deref (CVE-2022-50503)

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

    iommu/amd: Fix pci device refcount leak in ppr_notifier() (CVE-2022-50505)

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

    lib/fonts: fix undefined behavior in bit shift for get_default_font (CVE-2022-50511)

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

    drm/radeon: Fix PCI device refcount leak in radeon_atrm_get_bios() (CVE-2022-50520)

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

    mcb: mcb-parse: fix error handing in chameleon_parse_gdd() (CVE-2022-50522)

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

    scsi: mpt3sas: Fix possible resource leaks in mpt3sas_transport_port_add() (CVE-2022-50532)

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

    dm thin: Use last transaction's pmd->root when commit failed (CVE-2022-50534)

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

    bpf, sockmap: Fix repeated calls to sock_put() when msg has more_data (CVE-2022-50536)

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

    dm thin: Fix ABBA deadlock between shrink_slab and dm_pool_abort_metadata (CVE-2022-50549)

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

    tpm: acpi: Call acpi_put_table() to fix memory leak (CVE-2022-50562)

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

    dm thin: Fix UAF in run_timer_softirq() (CVE-2022-50563)

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

    mtd: Fix device name leak when register device failed in add_mtd_device() (CVE-2022-50566)

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

    fs: jfs: fix shift-out-of-bounds in dbAllocAG (CVE-2022-50567)

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

    xen/privcmd: Fix a possible warning in privcmd_ioctl_mmap_resource() (CVE-2022-50575)

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

    class: fix possible memory leak in __class_register() (CVE-2022-50578)

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

    hfs: fix OOB Read in __hfs_brec_find (CVE-2022-50581)

    The Linux kernel does not correctly mitigate SMT attacks, as discovered through a strange pattern in the     kernel API using STIBP as a mitigation, leaving the process exposed for a short period of time after a     syscall. The kernel also does not issue an IBPB immediately during the syscall. (CVE-2023-0045)

    A buffer overflow vulnerability was found in the Netfilter subsystem in the Linux Kernel. This issue could     allow the leakage of both stack and heap addresses, and potentially allow Local Privilege Escalation to     the root user via arbitrary code execution. (CVE-2023-0179)

    There is a logic error in io_uring's implementation which can be used to trigger a use-after-free     vulnerability leading to privilege escalation. In the io_prep_async_work function the assumption that the     last io_grab_identity call cannot return false is not true, and in this case the function will use the     init_cred or the previous linked requests identity to do operations instead of using the current identity.
    This can lead to reference counting issues causing use-after-free. We recommend upgrading past version     5.10.161. (CVE-2023-0240)

    A NULL pointer dereference flaw was found in rawv6_push_pending_frames in net/ipv6/raw.c in the network     subcomponent in the Linux kernel. This flaw causes the system to crash. (CVE-2023-0394)

    Detected a few exploitable gadgets that could leak secret memory through a side-channel such as MDS as     well as insufficient hardening of the usercopy functions against spectre-v1. (CVE-2023-0459)

    There is a use-after-free vulnerability in the Linux Kernel which can be exploited to achieve local     privilege escalation. To reach the vulnerability kernel configuration flag CONFIG_TLS or     CONFIG_XFRM_ESPINTCP has to be configured, but the operation does not require any privilege.

    There is a use-after-free bug of icsk_ulp_data of a struct inet_connection_sock.

    When CONFIG_TLS is enabled, user can install a tls context (struct tls_context) on a connected tcp socket.
    The context is not cleared if this socket is disconnected and reused as a listener. If a new socket is     created from the listener, the context is inherited and vulnerable.

    The setsockopt TCP_ULP operation does not require any privilege.

    We recommend upgrading past commit 2c02d41d71f90a5168391b6a5f2954112ba2307c (CVE-2023-0461)

    efi: rt-wrapper: Add missing include (CVE-2023-21102)

    cbq_classify in net/sched/sch_cbq.c in the Linux kernel through 6.1.4 allows attackers to cause a denial     of service (slab-out-of-bounds read) because of type confusion (non-negative numbers can sometimes     indicate a TC_ACT_SHOT condition rather than valid classification results). (CVE-2023-23454)

    atm_tc_enqueue in net/sched/sch_atm.c in the Linux kernel through 6.1.4 allows attackers to cause a denial     of service because of type confusion (non-negative numbers can sometimes indicate a TC_ACT_SHOT condition     rather than valid classification results). (CVE-2023-23455)

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

    btrfs: fix race between quota rescan and disable leading to NULL pointer deref (CVE-2023-52896)

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

    xhci: Fix null pointer dereference when host dies (CVE-2023-52898)

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

    nilfs2: fix general protection fault in nilfs_btree_insert() (CVE-2023-52900)

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

    usb: xhci: Check endpoint is valid before dereferencing it (CVE-2023-52901)

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

    io_uring: lock overflowing for IOPOLL (CVE-2023-52903)

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

    net/sched: act_mpls: Fix warning during failed attribute validation (CVE-2023-52906)

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

    netfilter: ipset: Fix overflow before widen in the bitmap_ip_create() function. (CVE-2023-53032)

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

    netfilter: nft_payload: incorrect arithmetics when fetching VLAN header bits (CVE-2023-53033)

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

    netfilter: ipset: Rework long task execution when adding/deleting entries (CVE-2023-53549)

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.

ID	Name	Product	Family	Severity
281862	SUSE SLES15 Security Update : kernel (SUSE-SU-2026:0029-1)	Nessus	SuSE Local Security Checks	medium
281579	EulerOS Virtualization 2.13.0 : kernel (EulerOS-SA-2025-2609)	Nessus	Huawei Local Security Checks	high
281563	EulerOS Virtualization 2.13.1 : kernel (EulerOS-SA-2025-2623)	Nessus	Huawei Local Security Checks	high
281257	Unity Linux 20.1060a / 20.1070a Security Update: kernel (UTSA-2025-993145)	Nessus	Unity Linux Local Security Checks	medium
280250	Unity Linux 20.1060e / 20.1070e Security Update: kernel (UTSA-2025-992274)	Nessus	Unity Linux Local Security Checks	medium
280199	Unity Linux 20.1060e / 20.1070e Security Update: kernel (UTSA-2025-992167)	Nessus	Unity Linux Local Security Checks	medium
280143	SUSE SLES15 Security Update : kernel (SUSE-SU-2025:4530-1)	Nessus	SuSE Local Security Checks	medium
279676	SUSE SLES15 Security Update : kernel (SUSE-SU-2025:4506-1)	Nessus	SuSE Local Security Checks	medium
278484	EulerOS 2.0 SP13 : kernel (EulerOS-SA-2025-2501)	Nessus	Huawei Local Security Checks	high
278473	EulerOS 2.0 SP13 : kernel (EulerOS-SA-2025-2522)	Nessus	Huawei Local Security Checks	high
276910	SUSE SLES12 Security Update : kernel (SUSE-SU-2025:4189-1)	Nessus	SuSE Local Security Checks	high
265146	Linux Distros Unpatched Vulnerability : CVE-2022-50280	Nessus	Misc.	low
171848	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.4-2023-042 (ALASKERNEL-5.4-2023-042)	Nessus	Amazon Linux Local Security Checks	high
171229	Amazon Linux 2 : kernel, --advisory ALAS2-2023-1932 (ALAS-2023-1932)	Nessus	Amazon Linux Local Security Checks	high
171227	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.15-2023-013 (ALASKERNEL-5.15-2023-013)	Nessus	Amazon Linux Local Security Checks	high
171216	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.10-2023-026 (ALASKERNEL-5.10-2023-026)	Nessus	Amazon Linux Local Security Checks	high
153035	Photon OS 4.0: Linux PHSA-2021-4.0-0095	Nessus	PhotonOS Local Security Checks	high

Detections

Analytics

CVE-2022-50280

medium

Tenable Plugins

medium

high

high

medium

medium

medium

medium

medium

high

high

high

low

high

high

high

high

high