In the Linux kernel, the following vulnerability has been resolved: ext4: block range must be validated before use in ext4_mb_clear_bb() Block range to free is validated in ext4_free_blocks() using ext4_inode_block_valid() and then it's passed to ext4_mb_clear_bb(). However in some situations on bigalloc file system the range might be adjusted after the validation in ext4_free_blocks() which can lead to troubles on corrupted file systems such as one found by syzkaller that resulted in the following BUG kernel BUG at fs/ext4/ext4.h:3319! PREEMPT SMP NOPTI CPU: 28 PID: 4243 Comm: repro Kdump: loaded Not tainted 5.19.0-rc6+ #1 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1.fc35 04/01/2014 RIP: 0010:ext4_free_blocks+0x95e/0xa90 Call Trace: <TASK> ? lock_timer_base+0x61/0x80 ? __es_remove_extent+0x5a/0x760 ? __mod_timer+0x256/0x380 ? ext4_ind_truncate_ensure_credits+0x90/0x220 ext4_clear_blocks+0x107/0x1b0 ext4_free_data+0x15b/0x170 ext4_ind_truncate+0x214/0x2c0 ? _raw_spin_unlock+0x15/0x30 ? ext4_discard_preallocations+0x15a/0x410 ? ext4_journal_check_start+0xe/0x90 ? __ext4_journal_start_sb+0x2f/0x110 ext4_truncate+0x1b5/0x460 ? __ext4_journal_start_sb+0x2f/0x110 ext4_evict_inode+0x2b4/0x6f0 evict+0xd0/0x1d0 ext4_enable_quotas+0x11f/0x1f0 ext4_orphan_cleanup+0x3de/0x430 ? proc_create_seq_private+0x43/0x50 ext4_fill_super+0x295f/0x3ae0 ? snprintf+0x39/0x40 ? sget_fc+0x19c/0x330 ? ext4_reconfigure+0x850/0x850 get_tree_bdev+0x16d/0x260 vfs_get_tree+0x25/0xb0 path_mount+0x431/0xa70 __x64_sys_mount+0xe2/0x120 do_syscall_64+0x5b/0x80 ? do_user_addr_fault+0x1e2/0x670 ? exc_page_fault+0x70/0x170 entry_SYSCALL_64_after_hwframe+0x46/0xb0 RIP: 0033:0x7fdf4e512ace Fix it by making sure that the block range is properly validated before used every time it changes in ext4_free_blocks() or ext4_mb_clear_bb().

The CentOS Linux 8.5 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare CENTOS8.5:CLSA-2026:1782146775 advisory.

  - Linux kernel CIFS implementation, version 4.9.0 is vulnerable to a relative paths injection in directory     entry lists. (CVE-2019-10220)

  - The KVM implementation in the Linux kernel through 4.20.5 has a Use-after-Free. (CVE-2019-7221)

  - Improper input validation in BlueZ may allow an unauthenticated user to potentially enable escalation of     privilege via adjacent access. (CVE-2020-12351)

  - Improper access control in BlueZ may allow an unauthenticated user to potentially enable information     disclosure via adjacent access. (CVE-2020-12352)

  - Improper buffer restrictions in BlueZ may allow an unauthenticated user to potentially enable denial of     service via adjacent access. This affects all Linux kernel versions that support BlueZ. (CVE-2020-24490)

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

The CentOS Linux 7 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare CENTOS7:CLSA-2026:1782148320 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: media: ngene: Fix out-of-bounds bug in     ngene_command_config_free_buf() Fix an 11-year old bug in ngene_command_config_free_buf() while addressing     the following warnings caught with -Warray-bounds: arch/alpha/include/asm/string.h:22:16: warning:
    '__builtin_memcpy' offset [12, 16] from the object at 'com' is out of the bounds of referenced subobject     'config' with type 'unsigned char' at offset 10 [-Warray-bounds] arch/x86/include/asm/string_32.h:182:25:
    warning: '__builtin_memcpy' offset [12, 16] from the object at 'com' is out of the bounds of referenced     subobject 'config' with type 'unsigned char' at offset 10 [-Warray-bounds] The problem is that the     original code is trying to copy 6 bytes of data into a one-byte size member _config_ of the wrong structue     FW_CONFIGURE_BUFFERS, in a single call to memcpy(). This causes a legitimate compiler warning because     memcpy() overruns the length of &com.cmd.ConfigureBuffers.config. It seems that the right structure is     FW_CONFIGURE_FREE_BUFFERS, instead, because it contains 6 more members apart from the header _hdr_. Also,     the name of the function ngene_command_config_free_buf() suggests that the actual intention is to     ConfigureFreeBuffers, instead of ConfigureBuffers (which takes place in the function     ngene_command_config_buf(), above). Fix this by enclosing those 6 members of struct     FW_CONFIGURE_FREE_BUFFERS into new struct config, and use &com.cmd.ConfigureFreeBuffers.config as the     destination address, instead of &com.cmd.ConfigureBuffers.config, when calling memcpy(). This also helps     with the ongoing efforts to globally enable -Warray-bounds and get us closer to being able to tighten the     FORTIFY_SOURCE routines on memcpy(). (CVE-2021-47288)

  - In the Linux kernel, the following vulnerability has been resolved: nvme: fix a possible use-after-free in     controller reset during load Unlike .queue_rq, in .submit_async_event drivers may not check the ctrl     readiness for AER submission. This may lead to a use-after-free condition that was observed with nvme-tcp.
    The race condition may happen in the following scenario: 1. driver executes its reset_ctrl_work 2. ->     nvme_stop_ctrl - flushes ctrl async_event_work 3. ctrl sends AEN which is received by the host, which in     turn schedules AEN handling 4. teardown admin queue (which releases the queue socket) 5. AEN processed,     submits another AER, calling the driver to submit 6. driver attempts to send the cmd ==> use-after-free In     order to fix that, add ctrl state check to validate the ctrl is actually able to accept the AER     submission. This addresses the above race in controller resets because the driver during teardown should:
    1. change ctrl state to RESETTING 2. flush async_event_work (as well as other async work elements) So     after 1,2, any other AER command will find the ctrl state to be RESETTING and bail out without submitting     the AER. (CVE-2022-48790)

  - In the Linux kernel, the following vulnerability has been resolved: scsi: pm8001: Fix use-after-free for     aborted TMF sas_task Currently a use-after-free may occur if a TMF sas_task is aborted before we handle     the IO completion in mpi_ssp_completion(). The abort occurs due to timeout. When the timeout occurs, the     SAS_TASK_STATE_ABORTED flag is set and the sas_task is freed in pm8001_exec_internal_tmf_task(). However,     if the I/O completion occurs later, the I/O completion still thinks that the sas_task is available. Fix     this by clearing the ccb->task if the TMF times out - the I/O completion handler does nothing if this     pointer is cleared. (CVE-2022-48791)

  - In the Linux kernel, the following vulnerability has been resolved: tracing: Free buffers when a used     dynamic event is removed After 65536 dynamic events have been added and removed, the type field of the     event then uses the first type number that is available (not currently used by other events). A type     number is the identifier of the binary blobs in the tracing ring buffer (known as events) to map them to     logic that can parse the binary blob. The issue is that if a dynamic event (like a kprobe event) is traced     and is in the ring buffer, and then that event is removed (because it is dynamic, which means it can be     created and destroyed), if another dynamic event is created that has the same number that new event's     logic on parsing the binary blob will be used. To show how this can be an issue, the following can crash     the kernel: # cd /sys/kernel/tracing # for i in `seq 65536`; do echo 'p:kprobes/foo do_sys_openat2     $arg1:u32' > kprobe_events # done For every iteration of the above, the writing to the kprobe_events will     remove the old event and create a new one (with the same format) and increase the type number to the next     available on until the type number reaches over 65535 which is the max number for the 16 bit type. After     it reaches that number, the logic to allocate a new number simply looks for the next available number.
    When an dynamic event is removed, that number is then available to be reused by the next dynamic event     created. That is, once the above reaches the max number, the number assigned to the event in that loop     will remain the same. Now that means deleting one dynamic event and created another will reuse the     previous events type number. This is where bad things can happen. After the above loop finishes, the     kprobes/foo event which reads the do_sys_openat2 function call's first parameter as an integer. # echo 1 >     kprobes/foo/enable # cat /etc/passwd > /dev/null # cat trace cat-2211 [005] .... 2007.849603: foo:
    (do_sys_openat2+0x0/0x130) arg1=4294967196 cat-2211 [005] .... 2007.849620: foo:
    (do_sys_openat2+0x0/0x130) arg1=4294967196 cat-2211 [005] .... 2007.849838: foo:
    (do_sys_openat2+0x0/0x130) arg1=4294967196 cat-2211 [005] .... 2007.849880: foo:
    (do_sys_openat2+0x0/0x130) arg1=4294967196 # echo 0 > kprobes/foo/enable Now if we delete the kprobe and     create a new one that reads a string: # echo 'p:kprobes/foo do_sys_openat2 +0($arg2):string' >     kprobe_events And now we can the trace: # cat trace sendmail-1942 [002] ..... 530.136320: foo:
    (do_sys_openat2+0x0/0x240) arg1= cat-2046 [004] ..... 530.930817: foo: (do_sys_openat2+0x0/0x240)     arg1=     cat-2046 [004] ..... 530.930961: foo: (do_sys_openat2+0x0/0x240)     arg1=     cat-2046 [004] ..... 530.934278: foo: (do_sys_openat2+0x0/0x240)     arg1=     cat-2046 [004] ..... 530.934563: foo: (do_sys_openat2+0x0/0x240)     arg1= ---truncated--- (CVE-2022-49006)

  - In the Linux kernel, the following vulnerability has been resolved: dm raid: fix accesses beyond end of     raid member array On dm-raid table load (using raid_ctr), dm-raid allocates an array     rs->devs[rs->raid_disks] for the raid device members. rs->raid_disks is defined by the number of raid     metadata and image tupples passed into the target's constructor. In the case of RAID layout changes being     requested, that number can be different from the current number of members for existing raid sets as     defined in their superblocks. Example RAID layout changes include: - raid1 legs being added/removed -     raid4/5/6/10 number of stripes changed (stripe reshaping) - takeover to higher raid level (e.g. raid5 ->     raid6) When accessing array members, rs->raid_disks must be used in control loops instead of the     potentially larger value in rs->md.raid_disks. Otherwise it will cause memory access beyond the end of the     rs->devs array. Fix this by changing code that is prone to out-of-bounds access. Also fix     validate_raid_redundancy() to validate all devices that are added. Also, use braces to help clean up     raid_iterate_devices(). The out-of-bounds memory accesses was discovered using KASAN. This commit was     verified to pass all LVM2 RAID tests (with KASAN enabled). (CVE-2022-49674)

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

The CentOS Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare CENTOS-STREAM8:CLSA-2026:1783790425 advisory.

  - A flaw in netfilter could allow a network-connected attacker to infer openvpn connection endpoint     information for further use in traditional network attacks. (CVE-2021-3773)

  - A flaw was found in the Linux kernel implementation of proxied virtualized TPM devices. On a system where     virtualized TPM devices are configured (this is not the default) a local attacker can create a use-after-     free and create a situation where it may be possible to escalate privileges on the system. (CVE-2022-2977)

  - In the Linux kernel, the following vulnerability has been resolved: tracing: Free buffers when a used     dynamic event is removed After 65536 dynamic events have been added and removed, the type field of the     event then uses the first type number that is available (not currently used by other events). A type     number is the identifier of the binary blobs in the tracing ring buffer (known as events) to map them to     logic that can parse the binary blob. The issue is that if a dynamic event (like a kprobe event) is traced     and is in the ring buffer, and then that event is removed (because it is dynamic, which means it can be     created and destroyed), if another dynamic event is created that has the same number that new event's     logic on parsing the binary blob will be used. To show how this can be an issue, the following can crash     the kernel: # cd /sys/kernel/tracing # for i in `seq 65536`; do echo 'p:kprobes/foo do_sys_openat2     $arg1:u32' > kprobe_events # done For every iteration of the above, the writing to the kprobe_events will     remove the old event and create a new one (with the same format) and increase the type number to the next     available on until the type number reaches over 65535 which is the max number for the 16 bit type. After     it reaches that number, the logic to allocate a new number simply looks for the next available number.
    When an dynamic event is removed, that number is then available to be reused by the next dynamic event     created. That is, once the above reaches the max number, the number assigned to the event in that loop     will remain the same. Now that means deleting one dynamic event and created another will reuse the     previous events type number. This is where bad things can happen. After the above loop finishes, the     kprobes/foo event which reads the do_sys_openat2 function call's first parameter as an integer. # echo 1 >     kprobes/foo/enable # cat /etc/passwd > /dev/null # cat trace cat-2211 [005] .... 2007.849603: foo:
    (do_sys_openat2+0x0/0x130) arg1=4294967196 cat-2211 [005] .... 2007.849620: foo:
    (do_sys_openat2+0x0/0x130) arg1=4294967196 cat-2211 [005] .... 2007.849838: foo:
    (do_sys_openat2+0x0/0x130) arg1=4294967196 cat-2211 [005] .... 2007.849880: foo:
    (do_sys_openat2+0x0/0x130) arg1=4294967196 # echo 0 > kprobes/foo/enable Now if we delete the kprobe and     create a new one that reads a string: # echo 'p:kprobes/foo do_sys_openat2 +0($arg2):string' >     kprobe_events And now we can the trace: # cat trace sendmail-1942 [002] ..... 530.136320: foo:
    (do_sys_openat2+0x0/0x240) arg1= cat-2046 [004] ..... 530.930817: foo: (do_sys_openat2+0x0/0x240)     arg1=     cat-2046 [004] ..... 530.930961: foo: (do_sys_openat2+0x0/0x240)     arg1=     cat-2046 [004] ..... 530.934278: foo: (do_sys_openat2+0x0/0x240)     arg1=     cat-2046 [004] ..... 530.934563: foo: (do_sys_openat2+0x0/0x240)     arg1= ---truncated--- (CVE-2022-49006)

  - In the Linux kernel, the following vulnerability has been resolved: tracing: Fix wild-memory-access in     register_synth_event() In register_synth_event(), if set_synth_event_print_fmt() failed, then both     trace_remove_event_call() and unregister_trace_event() will be called, which means the trace_event_call     will call __unregister_trace_event() twice. As the result, the second unregister will causes the wild-     memory-access. register_synth_event set_synth_event_print_fmt failed trace_remove_event_call event_remove     if call->event.funcs then __unregister_trace_event (first call) unregister_trace_event
    __unregister_trace_event (second call) Fix the bug by avoiding to call the second
    __unregister_trace_event() by checking if the first one is called. general protection fault, probably for     non-canonical address 0xfbd59c0000000024: 0000 [#1] SMP KASAN PTI KASAN: maybe wild-memory-access in range     [0xdead000000000120-0xdead000000000127] CPU: 0 PID: 3807 Comm: modprobe Not tainted     6.1.0-rc1-00186-g76f33a7eedb4 #299 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS     rel-1.15.0-0-g2dd4b9b3f840-prebuilt.qemu.org 04/01/2014 RIP: 0010:unregister_trace_event+0x6e/0x280 Code:
    00 fc ff df 4c 89 ea 48 c1 ea 03 80 3c 02 00 0f 85 0e 02 00 00 48 b8 00 00 00 00 00 fc ff df 4c 8b 63 08     4c 89 e2 48 c1 ea 03 <80> 3c 02 00 0f 85 e2 01 00 00 49 89 2c 24 48 85 ed 74 28 e8 7a 9b RSP:
    0018:ffff88810413f370 EFLAGS: 00010a06 RAX: dffffc0000000000 RBX: ffff888105d050b0 RCX: 0000000000000000     RDX: 1bd5a00000000024 RSI: ffff888119e276e0 RDI: ffffffff835a8b20 RBP: dead000000000100 R08:
    0000000000000000 R09: fffffbfff0913481 R10: ffffffff8489a407 R11: fffffbfff0913480 R12: dead000000000122     R13: ffff888105d050b8 R14: 0000000000000000 R15: ffff888105d05028 FS: 00007f7823e8d540(0000)     GS:ffff888119e00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2:
    00007f7823e7ebec CR3: 000000010a058002 CR4: 0000000000330ef0 DR0: 0000000000000000 DR1: 0000000000000000     DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK>
    __create_synth_event+0x1e37/0x1eb0 create_or_delete_synth_event+0x110/0x250     synth_event_run_command+0x2f/0x110 test_gen_synth_cmd+0x170/0x2eb [synth_event_gen_test]     synth_event_gen_test_init+0x76/0x9bc [synth_event_gen_test] do_one_initcall+0xdb/0x480     do_init_module+0x1cf/0x680 load_module+0x6a50/0x70a0 __do_sys_finit_module+0x12f/0x1c0     do_syscall_64+0x3f/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd (CVE-2022-49799)

  - In the Linux kernel, the following vulnerability has been resolved: ata: libata-transport: fix double     ata_host_put() in ata_tport_add() In the error path in ata_tport_add(), when calling put_device(),     ata_tport_release() is called, it will put the refcount of 'ap->host'. And then ata_host_put() is called     again, the refcount is decreased to 0, ata_host_release() is called, all ports are freed and set to null.
    When unbinding the device after failure, ata_host_stop() is called to release the resources, it leads a     null-ptr-deref(), because all the ports all freed and null. Unable to handle kernel NULL pointer     dereference at virtual address 0000000000000008 CPU: 7 PID: 18671 Comm: modprobe Kdump: loaded Tainted: G     E 6.1.0-rc3+ #8 pstate: 80400009 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc :
    ata_host_stop+0x3c/0x84 [libata] lr : release_nodes+0x64/0xd0 Call trace: ata_host_stop+0x3c/0x84 [libata]     release_nodes+0x64/0xd0 devres_release_all+0xbc/0x1b0 device_unbind_cleanup+0x20/0x70     really_probe+0x158/0x320 __driver_probe_device+0x84/0x120 driver_probe_device+0x44/0x120
    __driver_attach+0xb4/0x220 bus_for_each_dev+0x78/0xdc driver_attach+0x2c/0x40 bus_add_driver+0x184/0x240     driver_register+0x80/0x13c __pci_register_driver+0x4c/0x60 ahci_pci_driver_init+0x30/0x1000 [ahci] Fix     this by removing redundant ata_host_put() in the error path. (CVE-2022-49826)

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

The CentOS Linux 8.4 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare CENTOS8.4:CLSA-2026:1783414634 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: KVM: x86/mmu: Don't advance iterator     after restart due to yielding After dropping mmu_lock in the TDP MMU, restart the iterator during     tdp_iter_next() and do not advance the iterator. Advancing the iterator results in skipping the top-level     SPTE and all its children, which is fatal if any of the skipped SPTEs were not visited before yielding.
    When zapping all SPTEs, i.e. when min_level == root_level, restarting the iter and then invoking     tdp_iter_next() is always fatal if the current gfn has as a valid SPTE, as advancing the iterator results     in try_step_side() skipping the current gfn, which wasn't visited before yielding. Sprinkle WARNs on     iter->yielded being true in various helpers that are often used in conjunction with yielding, and tag the     helper with __must_check to reduce the probabily of improper usage. Failing to zap a top-level SPTE     manifests in one of two ways. If a valid SPTE is skipped by both kvm_tdp_mmu_zap_all() and     kvm_tdp_mmu_put_root(), the shadow page will be leaked and KVM will WARN accordingly. WARNING: CPU: 1 PID:
    3509 at arch/x86/kvm/mmu/tdp_mmu.c:46 [kvm] RIP: 0010:kvm_mmu_uninit_tdp_mmu+0x3e/0x50 [kvm] Call Trace:
    <TASK> kvm_arch_destroy_vm+0x130/0x1b0 [kvm] kvm_destroy_vm+0x162/0x2a0 [kvm] kvm_vcpu_release+0x34/0x60     [kvm] __fput+0x82/0x240 task_work_run+0x5c/0x90 do_exit+0x364/0xa10 ? futex_unqueue+0x38/0x60     do_group_exit+0x33/0xa0 get_signal+0x155/0x850 arch_do_signal_or_restart+0xed/0x750     exit_to_user_mode_prepare+0xc5/0x120 syscall_exit_to_user_mode+0x1d/0x40 do_syscall_64+0x48/0xc0     entry_SYSCALL_64_after_hwframe+0x44/0xae If kvm_tdp_mmu_zap_all() skips a gfn/SPTE but that SPTE is then     zapped by kvm_tdp_mmu_put_root(), KVM triggers a use-after-free in the form of marking a struct page as     dirty/accessed after it has been put back on the free list. This directly triggers a WARN due to     encountering a page with page_count() == 0, but it can also lead to data corruption and additional errors     in the kernel. WARNING: CPU: 7 PID: 1995658 at arch/x86/kvm/../../../virt/kvm/kvm_main.c:171 RIP:
    0010:kvm_is_zone_device_pfn.part.0+0x9e/0xd0 [kvm] Call Trace: <TASK> kvm_set_pfn_dirty+0x120/0x1d0 [kvm]
    __handle_changed_spte+0x92e/0xca0 [kvm] __handle_changed_spte+0x63c/0xca0 [kvm]
    __handle_changed_spte+0x63c/0xca0 [kvm] __handle_changed_spte+0x63c/0xca0 [kvm] zap_gfn_range+0x549/0x620     [kvm] kvm_tdp_mmu_put_root+0x1b6/0x270 [kvm] mmu_free_root_page+0x219/0x2c0 [kvm]     kvm_mmu_free_roots+0x1b4/0x4e0 [kvm] kvm_mmu_unload+0x1c/0xa0 [kvm] kvm_arch_destroy_vm+0x1f2/0x5c0 [kvm]     kvm_put_kvm+0x3b1/0x8b0 [kvm] kvm_vcpu_release+0x4e/0x70 [kvm] __fput+0x1f7/0x8c0 task_work_run+0xf8/0x1a0     do_exit+0x97b/0x2230 do_group_exit+0xda/0x2a0 get_signal+0x3be/0x1e50     arch_do_signal_or_restart+0x244/0x17f0 exit_to_user_mode_prepare+0xcb/0x120     syscall_exit_to_user_mode+0x1d/0x40 do_syscall_64+0x4d/0x90 entry_SYSCALL_64_after_hwframe+0x44/0xae Note,     the underlying bug existed even before commit 1af4a96025b3 (KVM: x86/mmu: Yield in TDU MMU iter even if     no SPTES changed) moved calls to tdp_mmu_iter_cond_resched() to the beginning of loops, as KVM could     still incorrectly advance past a top-level entry when yielding on a lower-level entry. But with respect to     leaking shadow pages, the bug was introduced by yielding before processing the current gfn. Alternatively,     tdp_mmu_iter_cond_resched() could simply fall through, or callers could jump to their retry label. The     downside of that approach is that tdp_mmu_iter_cond_resched() _must_ be called before anything else in the     loop, and there's no easy way to enfornce that requirement. Ideally, KVM would handling the cond_resched()     fully within the iterator macro (the code is actually quite clean) and avoid this entire class of bugs,     but that is extremely difficult do wh ---truncated--- (CVE-2021-47094)

  - In the Linux kernel, the following vulnerability has been resolved: net: bridge: fix vlan tunnel dst     refcnt when egressing The egress tunnel code uses dst_clone() and directly sets the result which is wrong     because the entry might have 0 refcnt or be already deleted, causing number of problems. It also triggers     the WARN_ON() in dst_hold()[1] when a refcnt couldn't be taken. Fix it by using dst_hold_safe() and     checking if a reference was actually taken before setting the dst. [1] dmesg WARN_ON log and following     refcnt errors WARNING: CPU: 5 PID: 38 at include/net/dst.h:230 br_handle_egress_vlan_tunnel+0x10b/0x134     [bridge] Modules linked in: 8021q garp mrp bridge stp llc bonding ipv6 virtio_net CPU: 5 PID: 38 Comm:
    ksoftirqd/5 Kdump: loaded Tainted: G W 5.13.0-rc3+ #360 Hardware name: QEMU Standard PC (i440FX + PIIX,     1996), BIOS 1.14.0-1.fc33 04/01/2014 RIP: 0010:br_handle_egress_vlan_tunnel+0x10b/0x134 [bridge] Code: e8     85 bc 01 e1 45 84 f6 74 90 45 31 f6 85 db 48 c7 c7 a0 02 19 a0 41 0f 94 c6 31 c9 31 d2 44 89 f6 e8 64 bc     01 e1 85 db 75 02 <0f> 0b 31 c9 31 d2 44 89 f6 48 c7 c7 70 02 19 a0 e8 4b bc 01 e1 49 RSP:
    0018:ffff8881003d39e8 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000     RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffffffffa01902a0 RBP: ffff8881040c6700 R08:
    0000000000000000 R09: 0000000000000001 R10: 2ce93d0054fe0d00 R11: 54fe0d00000e0000 R12: ffff888109515000     R13: 0000000000000000 R14: 0000000000000001 R15: 0000000000000401 FS: 0000000000000000(0000)     GS:ffff88822bf40000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2:
    00007f42ba70f030 CR3: 0000000109926000 CR4: 00000000000006e0 Call Trace: br_handle_vlan+0xbc/0xca [bridge]
    __br_forward+0x23/0x164 [bridge] deliver_clone+0x41/0x48 [bridge] br_handle_frame_finish+0x36f/0x3aa     [bridge] ? skb_dst+0x2e/0x38 [bridge] ? br_handle_ingress_vlan_tunnel+0x3e/0x1c8 [bridge] ?     br_handle_frame_finish+0x3aa/0x3aa [bridge] br_handle_frame+0x2c3/0x377 [bridge] ? __skb_pull+0x33/0x51 ?     vlan_do_receive+0x4f/0x36a ? br_handle_frame_finish+0x3aa/0x3aa [bridge]
    __netif_receive_skb_core+0x539/0x7c6 ? __list_del_entry_valid+0x16e/0x1c2
    __netif_receive_skb_list_core+0x6d/0xd6 netif_receive_skb_list_internal+0x1d9/0x1fa     gro_normal_list+0x22/0x3e dev_gro_receive+0x55b/0x600 ? detach_buf_split+0x58/0x140     napi_gro_receive+0x94/0x12e virtnet_poll+0x15d/0x315 [virtio_net] __napi_poll+0x2c/0x1c9     net_rx_action+0xe6/0x1fb __do_softirq+0x115/0x2d8 run_ksoftirqd+0x18/0x20 smpboot_thread_fn+0x183/0x19c ?     smpboot_unregister_percpu_thread+0x66/0x66 kthread+0x10a/0x10f ? kthread_mod_delayed_work+0xb6/0xb6     ret_from_fork+0x22/0x30 ---[ end trace 49f61b07f775fd2b ]--- dst_release: dst:00000000c02d677a refcnt:-1     dst_release underflow (CVE-2021-47222)

  - In the Linux kernel, the following vulnerability has been resolved: IB/mlx5: Fix initializing CQ fragments     buffer The function init_cq_frag_buf() can be called to initialize the current CQ fragments buffer     cq->buf, or the temporary cq->resize_buf that is filled during CQ resize operation. However, the offending     commit started to use function get_cqe() for getting the CQEs, the issue with this change is that     get_cqe() always returns CQEs from cq->buf, which leads us to initialize the wrong buffer, and in case of     enlarging the CQ we try to access elements beyond the size of the current cq->buf and eventually hit a     kernel panic. [exception RIP: init_cq_frag_buf+103] [ffff9f799ddcbcd8] mlx5_ib_resize_cq at     ffffffffc0835d60 [mlx5_ib] [ffff9f799ddcbdb0] ib_resize_cq at ffffffffc05270df [ib_core]     [ffff9f799ddcbdc0] llt_rdma_setup_qp at ffffffffc0a6a712 [llt] [ffff9f799ddcbe10] llt_rdma_cc_event_action     at ffffffffc0a6b411 [llt] [ffff9f799ddcbe98] llt_rdma_client_conn_thread at ffffffffc0a6bb75 [llt]     [ffff9f799ddcbec8] kthread at ffffffffa66c5da1 [ffff9f799ddcbf50] ret_from_fork_nospec_begin at     ffffffffa6d95ddd Fix it by getting the needed CQE by calling mlx5_frag_buf_get_wqe() that takes the     correct source buffer as a parameter. (CVE-2021-47261)

  - In the Linux kernel, the following vulnerability has been resolved: blk-cgroup: fix UAF by grabbing blkcg     lock before destroying blkg pd KASAN reports a use-after-free report when doing fuzz test: [693354.104835]     ================================================================== [693354.105094] BUG: KASAN: use-after-     free in bfq_io_set_weight_legacy+0xd3/0x160 [693354.105336] Read of size 4 at addr ffff888be0a35664 by     task sh/1453338 [693354.105607] CPU: 41 PID: 1453338 Comm: sh Kdump: loaded Not tainted 4.18.0-147     [693354.105610] Hardware name: Huawei 2288H V5/BC11SPSCB0, BIOS 0.81 07/02/2018 [693354.105612] Call     Trace: [693354.105621] dump_stack+0xf1/0x19b [693354.105626] ? show_regs_print_info+0x5/0x5     [693354.105634] ? printk+0x9c/0xc3 [693354.105638] ? cpumask_weight+0x1f/0x1f [693354.105648]     print_address_description+0x70/0x360 [693354.105654] kasan_report+0x1b2/0x330 [693354.105659] ?     bfq_io_set_weight_legacy+0xd3/0x160 [693354.105665] ? bfq_io_set_weight_legacy+0xd3/0x160 [693354.105670]     bfq_io_set_weight_legacy+0xd3/0x160 [693354.105675] ? bfq_cpd_init+0x20/0x20 [693354.105683]     cgroup_file_write+0x3aa/0x510 [693354.105693] ? ___slab_alloc+0x507/0x540 [693354.105698] ?     cgroup_file_poll+0x60/0x60 [693354.105702] ? 0xffffffff89600000 [693354.105708] ? usercopy_abort+0x90/0x90     [693354.105716] ? mutex_lock+0xef/0x180 [693354.105726] kernfs_fop_write+0x1ab/0x280 [693354.105732] ?     cgroup_file_poll+0x60/0x60 [693354.105738] vfs_write+0xe7/0x230 [693354.105744] ksys_write+0xb0/0x140     [693354.105749] ? __ia32_sys_read+0x50/0x50 [693354.105760] do_syscall_64+0x112/0x370 [693354.105766] ?     syscall_return_slowpath+0x260/0x260 [693354.105772] ? do_page_fault+0x9b/0x270 [693354.105779] ?     prepare_exit_to_usermode+0xf9/0x1a0 [693354.105784] ? enter_from_user_mode+0x30/0x30 [693354.105793]     entry_SYSCALL_64_after_hwframe+0x65/0xca [693354.105875] Allocated by task 1453337: [693354.106001]     kasan_kmalloc+0xa0/0xd0 [693354.106006] kmem_cache_alloc_node_trace+0x108/0x220 [693354.106010]     bfq_pd_alloc+0x96/0x120 [693354.106015] blkcg_activate_policy+0x1b7/0x2b0 [693354.106020]     bfq_create_group_hierarchy+0x1e/0x80 [693354.106026] bfq_init_queue+0x678/0x8c0 [693354.106031]     blk_mq_init_sched+0x1f8/0x460 [693354.106037] elevator_switch_mq+0xe1/0x240 [693354.106041]     elevator_switch+0x25/0x40 [693354.106045] elv_iosched_store+0x1a1/0x230 [693354.106049]     queue_attr_store+0x78/0xb0 [693354.106053] kernfs_fop_write+0x1ab/0x280 [693354.106056]     vfs_write+0xe7/0x230 [693354.106060] ksys_write+0xb0/0x140 [693354.106064] do_syscall_64+0x112/0x370     [693354.106069] entry_SYSCALL_64_after_hwframe+0x65/0xca [693354.106114] Freed by task 1453336:
    [693354.106225] __kasan_slab_free+0x130/0x180 [693354.106229] kfree+0x90/0x1b0 [693354.106233]     blkcg_deactivate_policy+0x12c/0x220 [693354.106238] bfq_exit_queue+0xf5/0x110 [693354.106241]     blk_mq_exit_sched+0x104/0x130 [693354.106245] __elevator_exit+0x45/0x60 [693354.106249]     elevator_switch_mq+0xd6/0x240 [693354.106253] elevator_switch+0x25/0x40 [693354.106257]     elv_iosched_store+0x1a1/0x230 [693354.106261] queue_attr_store+0x78/0xb0 [693354.106264]     kernfs_fop_write+0x1ab/0x280 [693354.106268] vfs_write+0xe7/0x230 [693354.106271] ksys_write+0xb0/0x140     [693354.106275] do_syscall_64+0x112/0x370 [693354.106280] entry_SYSCALL_64_after_hwframe+0x65/0xca     [693354.106329] The buggy address belongs to the object at ffff888be0a35580 which belongs to the cache     kmalloc-1k of size 1024 [693354.106736] The buggy address is located 228 bytes inside of 1024-byte region     [ffff888be0a35580, ffff888be0a35980) [693354.107114] The buggy address belongs to the page:
    [693354.107273] page:ffffea002f828c00 count:1 mapcount:0 mapping:ffff888107c17080 index:0x0     compound_mapcount: 0 [693354.107606] flags: 0x17ffffc0008100(slab|head) [693354.107760] raw:
    0017ffffc0008100 ffffea002fcbc808 ffffea0030bd3a08 ffff888107c17080 [693354.108020] r ---truncated---     (CVE-2021-47379)

  - In the Linux kernel, the following vulnerability has been resolved: ext4: block range must be validated     before use in ext4_mb_clear_bb() Block range to free is validated in ext4_free_blocks() using     ext4_inode_block_valid() and then it's passed to ext4_mb_clear_bb(). However in some situations on     bigalloc file system the range might be adjusted after the validation in ext4_free_blocks() which can lead     to troubles on corrupted file systems such as one found by syzkaller that resulted in the following BUG     kernel BUG at fs/ext4/ext4.h:3319! PREEMPT SMP NOPTI CPU: 28 PID: 4243 Comm: repro Kdump: loaded Not     tainted 5.19.0-rc6+ #1 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1.fc35 04/01/2014     RIP: 0010:ext4_free_blocks+0x95e/0xa90 Call Trace: <TASK> ? lock_timer_base+0x61/0x80 ?
    __es_remove_extent+0x5a/0x760 ? __mod_timer+0x256/0x380 ? ext4_ind_truncate_ensure_credits+0x90/0x220     ext4_clear_blocks+0x107/0x1b0 ext4_free_data+0x15b/0x170 ext4_ind_truncate+0x214/0x2c0 ?
    _raw_spin_unlock+0x15/0x30 ? ext4_discard_preallocations+0x15a/0x410 ? ext4_journal_check_start+0xe/0x90 ?
    __ext4_journal_start_sb+0x2f/0x110 ext4_truncate+0x1b5/0x460 ? __ext4_journal_start_sb+0x2f/0x110     ext4_evict_inode+0x2b4/0x6f0 evict+0xd0/0x1d0 ext4_enable_quotas+0x11f/0x1f0     ext4_orphan_cleanup+0x3de/0x430 ? proc_create_seq_private+0x43/0x50 ext4_fill_super+0x295f/0x3ae0 ?     snprintf+0x39/0x40 ? sget_fc+0x19c/0x330 ? ext4_reconfigure+0x850/0x850 get_tree_bdev+0x16d/0x260     vfs_get_tree+0x25/0xb0 path_mount+0x431/0xa70 __x64_sys_mount+0xe2/0x120 do_syscall_64+0x5b/0x80 ?     do_user_addr_fault+0x1e2/0x670 ? exc_page_fault+0x70/0x170 entry_SYSCALL_64_after_hwframe+0x46/0xb0 RIP:
    0033:0x7fdf4e512ace Fix it by making sure that the block range is properly validated before used every     time it changes in ext4_free_blocks() or ext4_mb_clear_bb(). (CVE-2022-50021)

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

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

    ext4: block range must be validated before use in ext4_mb_clear_bb()

    Block range to free is validated in ext4_free_blocks() using     ext4_inode_block_valid() and then it's passed to ext4_mb_clear_bb().
    However in some situations on bigalloc file system the range might be     adjusted after the validation in ext4_free_blocks() which can lead to     troubles on corrupted file systems such as one found by syzkaller that     resulted in the following BUG

    kernel BUG at fs/ext4/ext4.h:3319!     PREEMPT SMP NOPTI     CPU: 28 PID: 4243 Comm: repro Kdump: loaded Not tainted 5.19.0-rc6+ #1     Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1.fc35 04/01/2014     RIP: 0010:ext4_free_blocks+0x95e/0xa90     Call Trace:
     <TASK>      ? lock_timer_base+0x61/0x80      ? __es_remove_extent+0x5a/0x760      ? __mod_timer+0x256/0x380      ? ext4_ind_truncate_ensure_credits+0x90/0x220      ext4_clear_blocks+0x107/0x1b0      ext4_free_data+0x15b/0x170      ext4_ind_truncate+0x214/0x2c0      ? _raw_spin_unlock+0x15/0x30      ? ext4_discard_preallocations+0x15a/0x410      ? ext4_journal_check_start+0xe/0x90      ? __ext4_journal_start_sb+0x2f/0x110      ext4_truncate+0x1b5/0x460      ? __ext4_journal_start_sb+0x2f/0x110      ext4_evict_inode+0x2b4/0x6f0      evict+0xd0/0x1d0      ext4_enable_quotas+0x11f/0x1f0      ext4_orphan_cleanup+0x3de/0x430      ? proc_create_seq_private+0x43/0x50      ext4_fill_super+0x295f/0x3ae0      ? snprintf+0x39/0x40      ? sget_fc+0x19c/0x330      ? ext4_reconfigure+0x850/0x850      get_tree_bdev+0x16d/0x260      vfs_get_tree+0x25/0xb0      path_mount+0x431/0xa70
     __x64_sys_mount+0xe2/0x120      do_syscall_64+0x5b/0x80      ? do_user_addr_fault+0x1e2/0x670      ? exc_page_fault+0x70/0x170      entry_SYSCALL_64_after_hwframe+0x46/0xb0     RIP: 0033:0x7fdf4e512ace

    Fix it by making sure that the block range is properly validated before     used every time it changes in ext4_free_blocks() or ext4_mb_clear_bb().

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

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

    ext4: block range must be validated before use in ext4_mb_clear_bb()

    Block range to free is validated in ext4_free_blocks() using     ext4_inode_block_valid() and then it's passed to ext4_mb_clear_bb().
    However in some situations on bigalloc file system the range might be     adjusted after the validation in ext4_free_blocks() which can lead to     troubles on corrupted file systems such as one found by syzkaller that     resulted in the following BUG

    kernel BUG at fs/ext4/ext4.h:3319!     PREEMPT SMP NOPTI     CPU: 28 PID: 4243 Comm: repro Kdump: loaded Not tainted 5.19.0-rc6+ #1     Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1.fc35 04/01/2014     RIP: 0010:ext4_free_blocks+0x95e/0xa90     Call Trace:
     <TASK>      ? lock_timer_base+0x61/0x80      ? __es_remove_extent+0x5a/0x760      ? __mod_timer+0x256/0x380      ? ext4_ind_truncate_ensure_credits+0x90/0x220      ext4_clear_blocks+0x107/0x1b0      ext4_free_data+0x15b/0x170      ext4_ind_truncate+0x214/0x2c0      ? _raw_spin_unlock+0x15/0x30      ? ext4_discard_preallocations+0x15a/0x410      ? ext4_journal_check_start+0xe/0x90      ? __ext4_journal_start_sb+0x2f/0x110      ext4_truncate+0x1b5/0x460      ? __ext4_journal_start_sb+0x2f/0x110      ext4_evict_inode+0x2b4/0x6f0      evict+0xd0/0x1d0      ext4_enable_quotas+0x11f/0x1f0      ext4_orphan_cleanup+0x3de/0x430      ? proc_create_seq_private+0x43/0x50      ext4_fill_super+0x295f/0x3ae0      ? snprintf+0x39/0x40      ? sget_fc+0x19c/0x330      ? ext4_reconfigure+0x850/0x850      get_tree_bdev+0x16d/0x260      vfs_get_tree+0x25/0xb0      path_mount+0x431/0xa70
     __x64_sys_mount+0xe2/0x120      do_syscall_64+0x5b/0x80      ? do_user_addr_fault+0x1e2/0x670      ? exc_page_fault+0x70/0x170      entry_SYSCALL_64_after_hwframe+0x46/0xb0     RIP: 0033:0x7fdf4e512ace

    Fix it by making sure that the block range is properly validated before     used every time it changes in ext4_free_blocks() or ext4_mb_clear_bb().

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.

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

    KVM: VMX: Do _all_ initialization before exposing /dev/kvm to userspace(CVE-2022-49932)

    drivers:md:fix a potential use-after-free bug(CVE-2022-50022)

    ceph: don't leak snap_rwsem in handle_cap_grant(CVE-2022-50059)

    posix-cpu-timers: Cleanup CPU timers before freeing them during exec(CVE-2022-50095)

    scsi: qla2xxx: Fix crash due to stale SRB access around I/O timeouts(CVE-2022-50098)

    sched/core: Do not requeue task on CPU excluded from cpus_mask(CVE-2022-50100)

    sched, cpuset: Fix dl_cpu_busy() panic due to empty cs-cpus_allowed(CVE-2022-50103)

    An issue was discovered in drivers/tty/n_gsm.c in the Linux kernel 6.2. There is a sleeping function     called from an invalid context in gsmld_write, which will block the kernel. Note: This has been disputed     by 3rd parties as not a valid vulnerability.(CVE-2023-31082)

    scsi: qla2xxx: Perform lockless command completion in abort path(CVE-2023-53041)

    drm/nouveau: prime: fix ttm_bo_delayed_delete oops(CVE-2025-37765)

    dmaengine: idxd: fix memory leak in error handling path of idxd_alloc(CVE-2025-38015)

    padata: do not leak refcount in reorder_work(CVE-2025-38031)

    nvmet-tcp: don't restore null sk_state_change(CVE-2025-38035)

    rseq: Fix segfault on registration when rseq_cs is non-zero(CVE-2025-38067)

    libnvdimm/labels: Fix divide error in nd_label_data_init()(CVE-2025-38072)

    HID: usbhid: Eliminate recurrent out-of-bounds bug in usbhid_parse()(CVE-2025-38103)

    net: openvswitch: Fix the dead loop of MPLS parse(CVE-2025-38146)

    calipso: Don't call calipso functions for AF_INET sk.(CVE-2025-38147)

    tipc: fix null-ptr-deref when acquiring remote ip of ethernet bearer(CVE-2025-38184)

    net: clear the dst when changing skb protocol(CVE-2025-38192)

    ipc: fix to protect IPCS lookups using RCU(CVE-2025-38212)

    fbdev: Fix do_register_framebuffer to prevent null-ptr-deref in fb_videomode_to_var(CVE-2025-38215)

    sched/rt: Fix race in push_rt_task(CVE-2025-38234)

    nvme-tcp: sanitize request list handling(CVE-2025-38264)

    net: tipc: fix refcount warning in tipc_aead_encrypt(CVE-2025-38273)

    fbdev: core: fbcvt: avoid division by 0 in fb_cvt_hperiod()(CVE-2025-38312)

    arm64/ptrace: Fix stack-out-of-bounds read in regs_get_kernel_stack_nth()(CVE-2025-38320)

    virtio-net: ensure the received length does not exceed allocated size(CVE-2025-38375)

    NFSv4/pNFS: Fix a race to wake on NFS_LAYOUT_DRAIN(CVE-2025-38393)

    perf: Fix sample vs do_exit()(CVE-2025-38424)

    net/sched: Abort __tc_modify_qdisc if parent class does not exist(CVE-2025-38457)

    tipc: Fix use-after-free in tipc_conn_close().(CVE-2025-38464)

    netlink: Fix wraparounds of sk-sk_rmem_alloc.(CVE-2025-38465)

    perf: Revert to requiring CAP_SYS_ADMIN for uprobes(CVE-2025-38466)

    do_change_type(): refuse to operate on unmounted/not ours mounts(CVE-2025-38498)

    tracing: Add down_write(trace_event_sem) when adding trace event(CVE-2025-38539)

    perf/core: Prevent VMA split of buffer mappings(CVE-2025-38563)

    perf/core: Exit early on perf_mmap() fail(CVE-2025-38565)

    pptp: ensure minimal skb length in pptp_xmit()(CVE-2025-38574)

    pinmux: fix race causing mux_owner NULL with active mux_usecount(CVE-2025-38632)

    i2c: qup: jump out of the loop in case of timeout(CVE-2025-38671)

    ipv6: fix panic when forwarding a pkt with no in6 dev(CVE-2022-49048)

    netfilter: conntrack: revisit gc autotuning(CVE-2022-49110)

    bpf, sockmap: Fix memleak in sk_psock_queue_msg(CVE-2022-49207)

    block: fix rq-qos breakage from skipping rq_qos_done_bio()(CVE-2022-49266)

    tcp: add accessors to read/set tp-snd_cwnd(CVE-2022-49325)

    ip_gre: test csum_start instead of transport header(CVE-2022-49340)

    netfilter: nf_tables: double hook unregistration in netns path(CVE-2022-49558)

    tcp: Fix data-races around sysctl_tcp_recovery.(CVE-2022-49574)

    igmp: Fix data-races around sysctl_igmp_llm_reports.(CVE-2022-49590)

    tcp: Fix a data-race around sysctl_tcp_probe_interval.(CVE-2022-49593)

    ALSA: usb-audio: Drop snd_BUG_ON() from snd_usbmidi_output_open()(CVE-2022-49772)

    macvlan: enforce a consistent minimal mtu(CVE-2022-49776)

    x86/sgx: Add overflow check in sgx_validate_offset_length()(CVE-2022-49785)

    mmc: sdhci-pci: Fix possible memory leak caused by missing pci_dev_put()(CVE-2022-49787)

    tracing: Fix memory leak in tracing_read_pipe()(CVE-2022-49801)

    netdevsim: Fix memory leak of nsim_dev-fa_cookie(CVE-2022-49803)

    bridge: switchdev: Fix memory leaks when changing VLAN protocol(CVE-2022-49812)

    net: ena: Fix error handling in ena_init()(CVE-2022-49813)

    sctp: clear out_curr if all frag chunks of current msg are pruned(CVE-2022-49838)

    ipv6: addrlabel: fix infoleak when sending struct ifaddrlblmsg to network(CVE-2022-49865)

    net: gso: fix panic on frag_list with mixed head alloc types(CVE-2022-49872)

    bpf, sockmap: Fix the sk-sk_forward_alloc warning of sk_stream_kill_queues(CVE-2022-49877)

    ipv6: fix WARNING in ip6_route_net_exit_late()(CVE-2022-49903)

    net, neigh: Fix null-ptr-deref in neigh_table_clear()(CVE-2022-49904)

    net: mdio: fix undefined behavior in bit shift for __mdiobus_register(CVE-2022-49907)

    ipvs: fix WARNING in ip_vs_app_net_cleanup()(CVE-2022-49917)

    ipvs: fix WARNING in __ip_vs_cleanup_batch()(CVE-2022-49918)

    netfilter: nf_tables: release flow rule object from commit path(CVE-2022-49919)

    tty: n_gsm: add sanity check for gsm-receive in gsm_receive_buf()(CVE-2022-49940)

    vt: Clear selection before changing the font(CVE-2022-49948)

    bpf: Do mark_chain_precision for ARG_CONST_ALLOC_SIZE_OR_ZERO(CVE-2022-49961)

    arm64: cacheinfo: Fix incorrect assignment of signed error value to unsigned fw_level(CVE-2022-49964)

    bpf: Fix a data-race around bpf_jit_limit.(CVE-2022-49967)

    ftrace: Fix NULL pointer dereference in is_ftrace_trampoline when ftrace is dead(CVE-2022-49977)

    net: fix refcount bug in sk_psock_get (2)(CVE-2022-49979)

    media: pvrusb2: fix memory leak in pvr_probe(CVE-2022-49982)

    bpf: Don't use tnum_range on array range checking for poke descriptors(CVE-2022-49985)

    ice: xsk: prohibit usage of non-balanced queue id(CVE-2022-50003)

    kprobes: don't call disarm_kprobe() for disabled kprobes(CVE-2022-50008)

    ext4: avoid resizing to a partial cluster size(CVE-2022-50020)

    x86/fpu: KVM: Set the base guest FPU uABI size to sizeof(struct kvm_xsave).(CVE-2022-49557)

    A cross-privilege Spectre v2 vulnerability allows attackers to bypass all deployed mitigations, including     the recent Fine(IBT), and to leak arbitrary Linux kernel memory on Intel systems.(CVE-2024-2201)

    perf/x86/amd/uncore: Fix memory leak for events array(CVE-2022-49784)

    perf/x86/amd: Fix crash due to race between amd_pmu_enable_all, perf NMI and throttling(CVE-2022-49781)

    perf/x86/amd/core: Always clear status for idx(CVE-2023-53073)

    drm/drv: Fix potential memory leak in drm_dev_init().(CVE-2022-49830)

    drm/shmem-helper: Remove another errant put in error path(CVE-2023-53084)

    perf/core: Fix perf_output_begin parameter is incorrectly invoked in perf_event_bpf_output(CVE-2023-53065)

    arm64: bpf: Only mitigate cBPF programs loaded by unprivileged users(CVE-2025-37963)

    arm64: bpf: Add BHB mitigation to the epilogue for cBPF programs(CVE-2025-37948)

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

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

    media: dw2102: Fix null-ptr-deref in dw2102_i2c_transfer().(CVE-2023-53146)

    usb: ucsi: Fix NULL pointer deref in ucsi_connector_change().(CVE-2023-53049)

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

    drm     ouveau: Fix WARN_ON in nouveau_fence_context_kill().(CVE-2025-37930)

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

    bnxt_en: Fix out-of-bound memcpy() during ethtool -w(CVE-2025-37911)

    capabilities: fix undefined behavior in bit shift for CAP_TO_MASK(CVE-2022-49870)

    HID: intel-ish-hid: ipc: Fix potential use-after-free in work function(CVE-2023-53039)

    IB/hfi1: Correctly move list in sc_disable().(CVE-2022-49931)

    tpm: do not start chip while suspended(CVE-2025-23149)

    bpf: check changes_pkt_data property for extension programs(CVE-2024-58100)

    ext4: block range must be validated before use in ext4_mb_clear_bb()(CVE-2022-50021)

    iavf: Fix adminq error handling(CVE-2022-50055)

    virtio_net: fix memory leak inside XPD_TX with mergeable(CVE-2022-50065)

    net: atlantic: fix aq_vec index out of range error(CVE-2022-50066)

    BPF: Fix potential bad pointer dereference in bpf_sys_bpf()(CVE-2022-50069)

    net: tap: NULL pointer derefence in dev_parse_header_protocol when skb-dev is null(CVE-2022-50073)

    apparmor: Fix memleak in aa_simple_write_to_buffer()(CVE-2022-50074)

    resolved: apparmor: fix reference count leak in aa_pivotroot() (CVE-2022-50077)

    ext4: fix warning in ext4_iomap_begin as race between bmap and write(CVE-2022-50082)

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

    block: don't allow the same type rq_qos add more than once(CVE-2022-50086)

    jbd2: fix assertion 'jh-b_frozen_data == NULL' failure when journal aborted(CVE-2022-50126)

    RDMA/srpt: Fix a use-after-free(CVE-2022-50129)

    RDMA/hfi1: fix potential memory leak in setup_base_ctxt()(CVE-2022-50134)

    RDMA/qedr: Fix potential memory leak in __qedr_alloc_mr()(CVE-2022-50138)

    bpf: fix potential 32-bit overflow when accessing ARRAY map element(CVE-2022-50167)

    virtio-gpu: fix a missing check to avoid NULL dereference(CVE-2022-50181)

    selinux: Add boundary check in put_entry()(CVE-2022-50200)

    PM: hibernate: defer device probing when resuming from hibernation(CVE-2022-50202)

    arm64: fix oops in concurrently setting insn_emulation sysctls(CVE-2022-50206)

    netfilter: nf_tables: do not allow SET_ID to refer to another table(CVE-2022-50213)

    scsi: sg: Allow waiting for commands to complete on removed device(CVE-2022-50215)

    bpf: Fix KASAN use-after-free Read in compute_effective_progs(CVE-2022-50219)

    usbnet: Fix linkwatch use-after-free on disconnect(CVE-2022-50220)

    tty: vt: initialize unicode screen buffer(CVE-2022-50222)

    KVM: SVM: Don't BUG if userspace injects an interrupt with GIF=0(CVE-2022-50228)

    arm64: set UXN on swapper page tables(CVE-2022-50230)

    crypto: arm64/poly1305 - fix a read out-of-bound(CVE-2022-50231)

    arm64: set UXN on swapper page tables(CVE-2022-50232)

    netfilter: nf_tables: don't fail inserts if duplicate has expired(CVE-2023-52925)

    netfilter: allow exp not to be removed in nf_ct_find_expectation(CVE-2023-52927)

    dm crypt: add cond_resched() to dmcrypt_write()(CVE-2023-53051)

    erspan: do not use skb_mac_header() in ndo_start_xmit()(CVE-2023-53053)

    net/mlx5: E-Switch, Fix an Oops in error handling code(CVE-2023-53058)

    net: usb: smsc95xx: Limit packet length to skb-len(CVE-2023-53062)

    qed/qed_sriov: guard against NULL derefs from qed_iov_get_vf_info(CVE-2023-53066)

    net: usb: lan78xx: Limit packet length to skb-len(CVE-2023-53068)

    net/mlx5: Fix steering rules cleanup(CVE-2023-53079)

    xsk: Add missing overflow check in xdp_umem_reg(CVE-2023-53080)

    ice: xsk: disable txq irq before flushing hw(CVE-2023-53102)

    bonding: restore bond's IFF_SLAVE flag if a non-eth dev enslave fails(CVE-2023-53103)

    net: tunnels: annotate lockless accesses to dev-needed_headroom(CVE-2023-53109)

    i40e: Fix kernel crash during reboot when adapter is in recovery mode(CVE-2023-53114)

    tcp: tcp_make_synack() can be called from process context(CVE-2023-53121)

    net: usb: smsc75xx: Limit packet length to skb-len(CVE-2023-53125)

    SUNRPC: Fix a server shutdown leak(CVE-2023-53131)

    bpf, sockmap: Fix an infinite loop error when len is 0 in tcp_bpf_recvmsg_parser()(CVE-2023-53133)

    bpf: consider that tail calls invalidate packet pointers(CVE-2024-58237)

    net: avoid race between device unregistration and ethnl ops(CVE-2025-21701)

    ata: libata-sff: Ensure that we cannot write outside the allocated buffer(CVE-2025-21738)

    block: mark GFP_NOIO around sysfs -store()(CVE-2025-21817)

    netfilter: nf_tables: reject mismatching sum of field_len with set key length(CVE-2025-21826)

    netfilter: socket: Lookup orig tuple for IPv6 SNAT(CVE-2025-22021)

    net: fix geneve_opt length integer overflow(CVE-2025-22055)

    net: decrease cached dst counters in dst_release(CVE-2025-22057)

    rtnetlink: Allocate vfinfo size for VF GUIDs when supported(CVE-2025-22075)

    RDMA/mlx5: Fix mlx5_poll_one() cur_qp update flow(CVE-2025-22086)

    net: fix NULL pointer dereference in l3mdev_l3_rcv(CVE-2025-22103)

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

    net: ppp: Add bound checking for skb data on ppp_sync_txmung Ensure we have enough data in linear buffer     from skb before accessing initial bytes.(CVE-2025-37749)

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

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

    cxgb4: fix memory leak in cxgb4_init_ethtool_filters() error path(CVE-2025-37788)

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

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

    codel: remove sch-q.qlen check before qdisc_tree_reduce_backlog()(CVE-2025-37798)

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

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

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

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

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

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

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

    xsk: Fix race condition in AF_XDP generic RX path(CVE-2025-37920)

    sch_htb: make htb_qlen_notify() idempotent(CVE-2025-37932)

    bpf: Scrub packet on bpf_redirect_peer(CVE-2025-37959)

    ipvs: fix uninit-value for saddr in do_output_route4(CVE-2025-37961)

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

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

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

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

    sch_hfsc: Fix qlen accounting bug when using peek in hfsc_enqueue()(CVE-2025-38000)

    net_sched: hfsc: Address reentrant enqueue adding class to eltree twice(CVE-2025-38001)

    dmaengine: idxd: Refactor remove call with idxd_cleanup() helper(CVE-2025-38014)

    serial: mctrl_gpio: split disable_ms into sync and no_sync APIs(CVE-2025-38040)

    media: cx231xx: set device_caps for 417(CVE-2025-38044)

    net/tipc: fix slab-use-after-free Read in tipc_aead_encrypt_done(CVE-2025-38052)

    net: pktgen: fix access outside of user given buffer in pktgen_thread_write()(CVE-2025-38061)

    dm: fix unconditional IO throttle caused by REQ_PREFLUSH(CVE-2025-38063)

    dm cache: prevent BUG_ON by blocking retries on failed device resumes(CVE-2025-38066)

    crypto: lzo - Fix compression buffer overrun(CVE-2025-38068)

    vhost-scsi: protect vq-log_used with vq-mutex(CVE-2025-38074)

    scsi: target: iscsi: Fix timeout on deleted connection(CVE-2025-38075)

    net_sched: prio: fix a race in prio_tune()(CVE-2025-38083)

    mm/hugetlb: unshare page tables during VMA split, not before(CVE-2025-38084)

    net: ch9200: fix uninitialised access during mii_nway_restart(CVE-2025-38086)

    x86/iopl: Cure TIF_IO_BITMAP inconsistencies(CVE-2025-38100)

    VMCI: fix race between vmci_host_setup_notify and vmci_ctx_unset_notify(CVE-2025-38102)

    net_sched: red: fix a race in __red_change()(CVE-2025-38108)

    net/mdiobus: Fix potential out-of-bounds read/write access(CVE-2025-38111)

    net: Fix TOCTOU issue in sk_is_readable()(CVE-2025-38112)

    net_sched: sch_sfq: fix a potential crash on gso_skb handling(CVE-2025-38115)

    netfilter: nf_set_pipapo_avx2: fix initial map fill(CVE-2025-38120)

    net: fix udp gso skb_segment after pull from frag_list(CVE-2025-38124)

    ice: fix Tx scheduler error handling in XDP callback(CVE-2025-38127)

    page_pool: Fix use-after-free in page_pool_recycle_in_ring(CVE-2025-38129)

    bpf, sockmap: Avoid using sk_socket after free when sending(CVE-2025-38154)

    netfilter: nft_set_pipapo: prevent overflow in lookup table allocation(CVE-2025-38162)

    bpf, sockmap: Fix panic when calling skb_linearize(CVE-2025-38165)

    bpf: fix ktls panic with sockmap(CVE-2025-38166)

    RDMA/iwcm: Fix use-after-free of work objects after cm_id destruction(CVE-2025-38211)

    fbdev: Fix fb_set_var to prevent null-ptr-deref in fb_videomode_to_var(CVE-2025-38214)

    ext4: inline: fix len overflow in ext4_prepare_inline_data(CVE-2025-38222)

    media: cxusb: no longer judge rbuf when the write fails(CVE-2025-38229)

    bpf: Avoid __bpf_prog_ret0_warn when jit fails(CVE-2025-38280)

    bpf: Fix WARN() in get_bpf_raw_tp_regs(CVE-2025-38285)

    EDAC/skx_common: Fix general protection fault(CVE-2025-38298)

    mpls: Use rcu_dereference_rtnl() in mpls_route_input_rcu().(CVE-2025-38324)

    jbd2: fix data-race and null-ptr-deref in jbd2_journal_dirty_metadata()(CVE-2025-38337)

    ACPICA: fix acpi operand cache leak in dswstate.c(CVE-2025-38345)

    ftrace: Fix UAF when lookup kallsym after ftrace disabled(CVE-2025-38346)

    posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del()(CVE-2025-38352)

    ACPICA: Refuse to evaluate a method if arguments are missing(CVE-2025-38386)

    usb: typec: altmodes/displayport: do not index invalid pin_assignments(CVE-2025-38391)

    fs: export anon_inode_make_secure_inode() and fix secretmem LSM bypass(CVE-2025-38396)

    scsi: target: Fix NULL pointer dereference in core_scsi3_decode_spec_i_port()(CVE-2025-38399)

    drm/gem: Acquire references on GEM handles for framebuffers(CVE-2025-38449)

    HID: core: ensure the allocated report buffer can contain the reserved report ID(CVE-2025-38495)

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.

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

    ipv6: fix panic when forwarding a pkt with no in6 dev(CVE-2022-49048)

    netfilter: conntrack: revisit gc autotuning(CVE-2022-49110)

    bpf, sockmap: Fix memleak in sk_psock_queue_msg(CVE-2022-49207)

    block: fix rq-qos breakage from skipping rq_qos_done_bio()(CVE-2022-49266)

    tcp: add accessors to read/set tp-snd_cwnd(CVE-2022-49325)

    ip_gre: test csum_start instead of transport header(CVE-2022-49340)

    netfilter: nf_tables: double hook unregistration in netns path(CVE-2022-49558)

    tcp: Fix data-races around sysctl_tcp_recovery.(CVE-2022-49574)

    igmp: Fix data-races around sysctl_igmp_llm_reports.(CVE-2022-49590)

    tcp: Fix a data-race around sysctl_tcp_probe_interval.(CVE-2022-49593)

    ALSA: usb-audio: Drop snd_BUG_ON() from snd_usbmidi_output_open()(CVE-2022-49772)

    macvlan: enforce a consistent minimal mtu(CVE-2022-49776)

    x86/sgx: Add overflow check in sgx_validate_offset_length()(CVE-2022-49785)

    mmc: sdhci-pci: Fix possible memory leak caused by missing pci_dev_put()(CVE-2022-49787)

    tracing: Fix memory leak in tracing_read_pipe()(CVE-2022-49801)

    netdevsim: Fix memory leak of nsim_dev-fa_cookie(CVE-2022-49803)

    bridge: switchdev: Fix memory leaks when changing VLAN protocol(CVE-2022-49812)

    net: ena: Fix error handling in ena_init()(CVE-2022-49813)

    sctp: clear out_curr if all frag chunks of current msg are pruned(CVE-2022-49838)

    ipv6: addrlabel: fix infoleak when sending struct ifaddrlblmsg to network(CVE-2022-49865)

    net: gso: fix panic on frag_list with mixed head alloc types(CVE-2022-49872)

    bpf, sockmap: Fix the sk-sk_forward_alloc warning of sk_stream_kill_queues(CVE-2022-49877)

    ipv6: fix WARNING in ip6_route_net_exit_late()(CVE-2022-49903)

    net, neigh: Fix null-ptr-deref in neigh_table_clear()(CVE-2022-49904)

    net: mdio: fix undefined behavior in bit shift for __mdiobus_register(CVE-2022-49907)

    ipvs: fix WARNING in ip_vs_app_net_cleanup()(CVE-2022-49917)

    ipvs: fix WARNING in __ip_vs_cleanup_batch()(CVE-2022-49918)

    netfilter: nf_tables: release flow rule object from commit path(CVE-2022-49919)

    tty: n_gsm: add sanity check for gsm-receive in gsm_receive_buf()(CVE-2022-49940)

    vt: Clear selection before changing the font(CVE-2022-49948)

    bpf: Do mark_chain_precision for ARG_CONST_ALLOC_SIZE_OR_ZERO(CVE-2022-49961)

    arm64: cacheinfo: Fix incorrect assignment of signed error value to unsigned fw_level(CVE-2022-49964)

    bpf: Fix a data-race around bpf_jit_limit.(CVE-2022-49967)

    ftrace: Fix NULL pointer dereference in is_ftrace_trampoline when ftrace is dead(CVE-2022-49977)

    net: fix refcount bug in sk_psock_get (2)(CVE-2022-49979)

    media: pvrusb2: fix memory leak in pvr_probe(CVE-2022-49982)

    bpf: Don't use tnum_range on array range checking for poke descriptors(CVE-2022-49985)

    ice: xsk: prohibit usage of non-balanced queue id(CVE-2022-50003)

    kprobes: don't call disarm_kprobe() for disabled kprobes(CVE-2022-50008)

    ext4: avoid resizing to a partial cluster size(CVE-2022-50020)

    ext4: block range must be validated before use in ext4_mb_clear_bb()(CVE-2022-50021)

    iavf: Fix adminq error handling(CVE-2022-50055)

    virtio_net: fix memory leak inside XPD_TX with mergeable(CVE-2022-50065)

    net: atlantic: fix aq_vec index out of range error(CVE-2022-50066)

    BPF: Fix potential bad pointer dereference in bpf_sys_bpf()(CVE-2022-50069)

    net: tap: NULL pointer derefence in dev_parse_header_protocol when skb-dev is null(CVE-2022-50073)

    apparmor: Fix memleak in aa_simple_write_to_buffer()(CVE-2022-50074)

    resolved: apparmor: fix reference count leak in aa_pivotroot() (CVE-2022-50077)

    ext4: fix warning in ext4_iomap_begin as race between bmap and write(CVE-2022-50082)

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

    block: don't allow the same type rq_qos add more than once(CVE-2022-50086)

    jbd2: fix assertion 'jh-b_frozen_data == NULL' failure when journal aborted(CVE-2022-50126)

    RDMA/srpt: Fix a use-after-free(CVE-2022-50129)

    RDMA/hfi1: fix potential memory leak in setup_base_ctxt()(CVE-2022-50134)

    RDMA/qedr: Fix potential memory leak in __qedr_alloc_mr()(CVE-2022-50138)

    bpf: fix potential 32-bit overflow when accessing ARRAY map element(CVE-2022-50167)

    virtio-gpu: fix a missing check to avoid NULL dereference(CVE-2022-50181)

    selinux: Add boundary check in put_entry()(CVE-2022-50200)

    PM: hibernate: defer device probing when resuming from hibernation(CVE-2022-50202)

    arm64: fix oops in concurrently setting insn_emulation sysctls(CVE-2022-50206)

    netfilter: nf_tables: do not allow SET_ID to refer to another table(CVE-2022-50213)

    scsi: sg: Allow waiting for commands to complete on removed device(CVE-2022-50215)

    bpf: Fix KASAN use-after-free Read in compute_effective_progs(CVE-2022-50219)

    usbnet: Fix linkwatch use-after-free on disconnect(CVE-2022-50220)

    tty: vt: initialize unicode screen buffer(CVE-2022-50222)

    KVM: SVM: Don't BUG if userspace injects an interrupt with GIF=0(CVE-2022-50228)

    arm64: set UXN on swapper page tables(CVE-2022-50230)

    crypto: arm64/poly1305 - fix a read out-of-bound(CVE-2022-50231)

    arm64: set UXN on swapper page tables(CVE-2022-50232)

    netfilter: nf_tables: don't fail inserts if duplicate has expired(CVE-2023-52925)

    netfilter: allow exp not to be removed in nf_ct_find_expectation(CVE-2023-52927)

    dm crypt: add cond_resched() to dmcrypt_write()(CVE-2023-53051)

    erspan: do not use skb_mac_header() in ndo_start_xmit()(CVE-2023-53053)

    net/mlx5: E-Switch, Fix an Oops in error handling code(CVE-2023-53058)

    net: usb: smsc95xx: Limit packet length to skb-len(CVE-2023-53062)

    qed/qed_sriov: guard against NULL derefs from qed_iov_get_vf_info(CVE-2023-53066)

    net: usb: lan78xx: Limit packet length to skb-len(CVE-2023-53068)

    net/mlx5: Fix steering rules cleanup(CVE-2023-53079)

    xsk: Add missing overflow check in xdp_umem_reg(CVE-2023-53080)

    ice: xsk: disable txq irq before flushing hw(CVE-2023-53102)

    bonding: restore bond's IFF_SLAVE flag if a non-eth dev enslave fails(CVE-2023-53103)

    net: tunnels: annotate lockless accesses to dev-needed_headroom(CVE-2023-53109)

    i40e: Fix kernel crash during reboot when adapter is in recovery mode(CVE-2023-53114)

    tcp: tcp_make_synack() can be called from process context(CVE-2023-53121)

    net: usb: smsc75xx: Limit packet length to skb-len(CVE-2023-53125)

    SUNRPC: Fix a server shutdown leak(CVE-2023-53131)

    bpf, sockmap: Fix an infinite loop error when len is 0 in tcp_bpf_recvmsg_parser()(CVE-2023-53133)

    bpf: consider that tail calls invalidate packet pointers(CVE-2024-58237)

    net: avoid race between device unregistration and ethnl ops(CVE-2025-21701)

    ata: libata-sff: Ensure that we cannot write outside the allocated buffer(CVE-2025-21738)

    block: mark GFP_NOIO around sysfs -store()(CVE-2025-21817)

    netfilter: nf_tables: reject mismatching sum of field_len with set key length(CVE-2025-21826)

    netfilter: socket: Lookup orig tuple for IPv6 SNAT(CVE-2025-22021)

    net: fix geneve_opt length integer overflow(CVE-2025-22055)

    net: decrease cached dst counters in dst_release(CVE-2025-22057)

    rtnetlink: Allocate vfinfo size for VF GUIDs when supported(CVE-2025-22075)

    RDMA/mlx5: Fix mlx5_poll_one() cur_qp update flow(CVE-2025-22086)

    net: fix NULL pointer dereference in l3mdev_l3_rcv(CVE-2025-22103)

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

    net: ppp: Add bound checking for skb data on ppp_sync_txmung Ensure we have enough data in linear buffer     from skb before accessing initial bytes.(CVE-2025-37749)

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

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

    cxgb4: fix memory leak in cxgb4_init_ethtool_filters() error path(CVE-2025-37788)

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

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

    codel: remove sch-q.qlen check before qdisc_tree_reduce_backlog()(CVE-2025-37798)

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

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

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

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

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

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

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

    xsk: Fix race condition in AF_XDP generic RX path(CVE-2025-37920)

    sch_htb: make htb_qlen_notify() idempotent(CVE-2025-37932)

    bpf: Scrub packet on bpf_redirect_peer(CVE-2025-37959)

    ipvs: fix uninit-value for saddr in do_output_route4(CVE-2025-37961)

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

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

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

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

    sch_hfsc: Fix qlen accounting bug when using peek in hfsc_enqueue()(CVE-2025-38000)

    net_sched: hfsc: Address reentrant enqueue adding class to eltree twice(CVE-2025-38001)

    dmaengine: idxd: Refactor remove call with idxd_cleanup() helper(CVE-2025-38014)

    serial: mctrl_gpio: split disable_ms into sync and no_sync APIs(CVE-2025-38040)

    media: cx231xx: set device_caps for 417(CVE-2025-38044)

    net/tipc: fix slab-use-after-free Read in tipc_aead_encrypt_done(CVE-2025-38052)

    net: pktgen: fix access outside of user given buffer in pktgen_thread_write()(CVE-2025-38061)

    dm: fix unconditional IO throttle caused by REQ_PREFLUSH(CVE-2025-38063)

    dm cache: prevent BUG_ON by blocking retries on failed device resumes(CVE-2025-38066)

    crypto: lzo - Fix compression buffer overrun(CVE-2025-38068)

    vhost-scsi: protect vq-log_used with vq-mutex(CVE-2025-38074)

    scsi: target: iscsi: Fix timeout on deleted connection(CVE-2025-38075)

    net_sched: prio: fix a race in prio_tune()(CVE-2025-38083)

    mm/hugetlb: unshare page tables during VMA split, not before(CVE-2025-38084)

    net: ch9200: fix uninitialised access during mii_nway_restart(CVE-2025-38086)

    x86/iopl: Cure TIF_IO_BITMAP inconsistencies(CVE-2025-38100)

    VMCI: fix race between vmci_host_setup_notify and vmci_ctx_unset_notify(CVE-2025-38102)

    net_sched: red: fix a race in __red_change()(CVE-2025-38108)

    net/mdiobus: Fix potential out-of-bounds read/write access(CVE-2025-38111)

    net: Fix TOCTOU issue in sk_is_readable()(CVE-2025-38112)

    net_sched: sch_sfq: fix a potential crash on gso_skb handling(CVE-2025-38115)

    netfilter: nf_set_pipapo_avx2: fix initial map fill(CVE-2025-38120)

    net: fix udp gso skb_segment after pull from frag_list(CVE-2025-38124)

    ice: fix Tx scheduler error handling in XDP callback(CVE-2025-38127)

    page_pool: Fix use-after-free in page_pool_recycle_in_ring(CVE-2025-38129)

    bpf, sockmap: Avoid using sk_socket after free when sending(CVE-2025-38154)

    netfilter: nft_set_pipapo: prevent overflow in lookup table allocation(CVE-2025-38162)

    bpf, sockmap: Fix panic when calling skb_linearize(CVE-2025-38165)

    bpf: fix ktls panic with sockmap(CVE-2025-38166)

    RDMA/iwcm: Fix use-after-free of work objects after cm_id destruction(CVE-2025-38211)

    fbdev: Fix fb_set_var to prevent null-ptr-deref in fb_videomode_to_var(CVE-2025-38214)

    ext4: inline: fix len overflow in ext4_prepare_inline_data(CVE-2025-38222)

    media: cxusb: no longer judge rbuf when the write fails(CVE-2025-38229)

    bpf: Avoid __bpf_prog_ret0_warn when jit fails(CVE-2025-38280)

    bpf: Fix WARN() in get_bpf_raw_tp_regs(CVE-2025-38285)

    EDAC/skx_common: Fix general protection fault(CVE-2025-38298)

    mpls: Use rcu_dereference_rtnl() in mpls_route_input_rcu().(CVE-2025-38324)

    jbd2: fix data-race and null-ptr-deref in jbd2_journal_dirty_metadata()(CVE-2025-38337)

    ACPICA: fix acpi operand cache leak in dswstate.c(CVE-2025-38345)

    ftrace: Fix UAF when lookup kallsym after ftrace disabled(CVE-2025-38346)

    posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del()(CVE-2025-38352)

    ACPICA: Refuse to evaluate a method if arguments are missing(CVE-2025-38386)

    usb: typec: altmodes/displayport: do not index invalid pin_assignments(CVE-2025-38391)

    fs: export anon_inode_make_secure_inode() and fix secretmem LSM bypass(CVE-2025-38396)

    scsi: target: Fix NULL pointer dereference in core_scsi3_decode_spec_i_port()(CVE-2025-38399)

    drm/gem: Acquire references on GEM handles for framebuffers(CVE-2025-38449)

    HID: core: ensure the allocated report buffer can contain the reserved report ID(CVE-2025-38495)

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 Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - ext4: block range must be validated before use in ext4_mb_clear_bb() Block range to free is validated in     ext4_free_blocks() using ext4_inode_block_valid() and then it's passed to ext4_mb_clear_bb(). However in     some situations on bigalloc file system the range might be adjusted after the validation in     ext4_free_blocks() which can lead to troubles on corrupted file systems such as one found by syzkaller     that resulted in the following BUG kernel BUG at fs/ext4/ext4.h:3319! PREEMPT SMP NOPTI CPU: 28 PID: 4243     Comm: repro Kdump: loaded Not tainted 5.19.0-rc6+ #1 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009),     BIOS 1.15.0-1.fc35 04/01/2014 RIP: 0010:ext4_free_blocks+0x95e/0xa90 Call Trace: <TASK> ?     lock_timer_base+0x61/0x80 ? __es_remove_extent+0x5a/0x760 ? __mod_timer+0x256/0x380 ?     ext4_ind_truncate_ensure_credits+0x90/0x220 ext4_clear_blocks+0x107/0x1b0 ext4_free_data+0x15b/0x170     ext4_ind_truncate+0x214/0x2c0 ? _raw_spin_unlock+0x15/0x30 ? ext4_discard_preallocations+0x15a/0x410 ?     ext4_journal_check_start+0xe/0x90 ? __ext4_journal_start_sb+0x2f/0x110 ext4_truncate+0x1b5/0x460 ?
    __ext4_journal_start_sb+0x2f/0x110 ext4_evict_inode+0x2b4/0x6f0 evict+0xd0/0x1d0     ext4_enable_quotas+0x11f/0x1f0 ext4_orphan_cleanup+0x3de/0x430 ? proc_create_seq_private+0x43/0x50     ext4_fill_super+0x295f/0x3ae0 ? snprintf+0x39/0x40 ? sget_fc+0x19c/0x330 ? ext4_reconfigure+0x850/0x850     get_tree_bdev+0x16d/0x260 vfs_get_tree+0x25/0xb0 path_mount+0x431/0xa70 __x64_sys_mount+0xe2/0x120     do_syscall_64+0x5b/0x80 ? do_user_addr_fault+0x1e2/0x670 ? exc_page_fault+0x70/0x170     entry_SYSCALL_64_after_hwframe+0x46/0xb0 RIP: 0033:0x7fdf4e512ace Fix it by making sure that the block     range is properly validated before used every time it changes in ext4_free_blocks() or ext4_mb_clear_bb().
    (CVE-2022-50021)

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

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

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


    The following security bugs were fixed:

    - CVE-2021-47557: net/sched: sch_ets: do not peek at classes beyond 'nbands' (bsc#1207361 bsc#1225468).
    - CVE-2021-47595: net/sched: sch_ets: do not remove idle classes from the round-robin list (bsc#1207361     bsc#1226552).
    - CVE-2023-52924: netfilter: nf_tables: do not skip expired elements during walk (bsc#1236821).
    - CVE-2023-52925: netfilter: nf_tables: do not fail inserts if duplicate has expired (bsc#1236822).
    - CVE-2024-26808: netfilter: nft_chain_filter: handle NETDEV_UNREGISTER for inet/ingress basechain     (bsc#1222634).
    - CVE-2024-26924: scsi: lpfc: Release hbalock before calling lpfc_worker_wake_up() (bsc#1225820).
    - CVE-2024-27397: kabi: place tstamp needed for nftables set in a hole (bsc#1224095).
    - CVE-2024-36978: net: sched: sch_multiq: fix possible OOB write in multiq_tune() (bsc#1226514).
    - CVE-2024-46800: sch/netem: fix use after free in netem_dequeue (bsc#1230827).
    - CVE-2024-53057: net/sched: stop qdisc_tree_reduce_backlog on TC_H_ROOT (bsc#1233551).
    - CVE-2024-53125: bpf: sync_linked_regs() must preserve subreg_def (bsc#1234156).
    - CVE-2024-53141: netfilter: ipset: add missing range check in bitmap_ip_uadt (bsc#1234381).
    - CVE-2024-56770: sch/netem: fix use after free in netem_dequeue (bsc#1235637).
    - CVE-2024-57947: netfilter: nf_set_pipapo: fix initial map fill (bsc#1236333).
    - CVE-2025-21700: net: sched: Disallow replacing of child qdisc from one parent to another (bsc#1237159).
    - CVE-2025-21702: pfifo_tail_enqueue: Drop new packet when sch->limit == 0 (bsc#1237312).
    - CVE-2025-21703: netem: Update sch->q.qlen before qdisc_tree_reduce_backlog() (bsc#1237313).
    - CVE-2025-21756: vsock: Orphan socket after transport release (bsc#1238876).
    - CVE-2025-23141: KVM: x86: Acquire SRCU in KVM_GET_MP_STATE to protect guest memory accesses     (bsc#1242782).
    - CVE-2025-37752: net_sched: sch_sfq: move the limit validation (bsc#1242504).
    - CVE-2025-37797: net_sched: hfsc: Fix a UAF vulnerability in class handling (bsc#1242417).
    - CVE-2025-37823: net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too (bsc#1242924).
    - CVE-2025-37890: net_sched: hfsc: Fix a UAF vulnerability in class with netem as child qdisc     (bsc#1243330).
    - CVE-2025-37997: netfilter: ipset: fix region locking in hash types (bsc#1243832).
    - CVE-2025-38000: sch_hfsc: Fix qlen accounting bug when using peek in hfsc_enqueue() (bsc#1244277).
    - CVE-2025-38001: net_sched: hfsc: Address reentrant enqueue adding class to eltree twice (bsc#1244234).
    - CVE-2025-38014: dmaengine: idxd: Refactor remove call with idxd_cleanup() helper (bsc#1244732).
    - CVE-2025-38083: net_sched: prio: fix a race in prio_tune() (bsc#1245183).


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:02264-1 advisory.

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


    The following security bugs were fixed:

    - CVE-2021-47557: net/sched: sch_ets: do not peek at classes beyond 'nbands' (bsc#1207361 bsc#1225468).
    - CVE-2021-47595: net/sched: sch_ets: do not remove idle classes from the round-robin list (bsc#1207361     bsc#1226552).
    - CVE-2023-52924: netfilter: nf_tables: do not skip expired elements during walk (bsc#1236821).
    - CVE-2023-52925: netfilter: nf_tables: do not fail inserts if duplicate has expired (bsc#1236822).
    - CVE-2024-26808: netfilter: nft_chain_filter: handle NETDEV_UNREGISTER for inet/ingress basechain     (bsc#1222634).
    - CVE-2024-26924: scsi: lpfc: Release hbalock before calling lpfc_worker_wake_up() (bsc#1225820).
    - CVE-2024-27397: kabi: place tstamp needed for nftables set in a hole (bsc#1224095).
    - CVE-2024-36978: net: sched: sch_multiq: fix possible OOB write in multiq_tune() (bsc#1226514).
    - CVE-2024-46800: sch/netem: fix use after free in netem_dequeue (bsc#1230827).
    - CVE-2024-53125: bpf: sync_linked_regs() must preserve subreg_def (bsc#1234156).
    - CVE-2024-53141: netfilter: ipset: add missing range check in bitmap_ip_uadt (bsc#1234381).
    - CVE-2024-53197: ALSA: usb-audio: Fix potential out-of-bound accesses for Extigy and Mbox devices     (bsc#1235464).
    - CVE-2024-56770: sch/netem: fix use after free in netem_dequeue (bsc#1235637).
    - CVE-2025-21700: net: sched: Disallow replacing of child qdisc from one parent to another (bsc#1237159).
    - CVE-2025-21702: pfifo_tail_enqueue: Drop new packet when sch->limit == 0 (bsc#1237312).
    - CVE-2025-21703: netem: Update sch->q.qlen before qdisc_tree_reduce_backlog() (bsc#1237313).
    - CVE-2025-21756: vsock: Orphan socket after transport release (bsc#1238876).
    - CVE-2025-23141: KVM: x86: Acquire SRCU in KVM_GET_MP_STATE to protect guest memory accesses     (bsc#1242782).
    - CVE-2025-37752: net_sched: sch_sfq: move the limit validation (bsc#1242504).
    - CVE-2025-37823: net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too (bsc#1242924).
    - CVE-2025-37890: net_sched: hfsc: Fix a UAF vulnerability in class with netem as child qdisc     (bsc#1243330).
    - CVE-2025-37997: netfilter: ipset: fix region locking in hash types (bsc#1243832).
    - CVE-2025-38000: sch_hfsc: Fix qlen accounting bug when using peek in hfsc_enqueue() (bsc#1244277).
    - CVE-2025-38001: net_sched: hfsc: Address reentrant enqueue adding class to eltree twice (bsc#1244234).
    - CVE-2025-38014: dmaengine: idxd: Refactor remove call with idxd_cleanup() helper (bsc#1244732).
    - CVE-2025-38060: bpf: abort verification if env->cur_state->loop_entry != NULL (bsc#1245155).
    - CVE-2025-38083: net_sched: prio: fix a race in prio_tune() (bsc#1245183).


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 version of kernel installed on the remote host is prior to 5.10.176-157.645. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.10-2024-059 advisory.

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

    ext4: block range must be validated before use in ext4_mb_clear_bb() (CVE-2022-50021)

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

    block, bfq: fix possible uaf for 'bfqq->bic' (CVE-2022-50488)

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

    seccomp: Move copy_seccomp() to no failure path. (CVE-2022-50661)

    An issue was discovered in arch/x86/kvm/vmx/nested.c in the Linux kernel before 6.2.8. nVMX on x86_64     lacks consistency checks for CR0 and CR4. (CVE-2023-30456)

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

    ftrace: Fix invalid address access in lookup_rec() when index is 0 (CVE-2023-53075)

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

    drm/shmem-helper: Remove another errant put in error path (CVE-2023-53084)

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

    drm/i915/active: Fix misuse of non-idle barriers as fence trackers (CVE-2023-53087)

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

    ext4: fix task hung in ext4_xattr_delete_inode (CVE-2023-53089)

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

    interconnect: fix mem leak when freeing nodes (CVE-2023-53096)

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

    ext4: fix WARNING in ext4_update_inline_data (CVE-2023-53100)

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

    ext4: zero i_disksize when initializing the bootloader inode (CVE-2023-53101)

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

    net: tunnels: annotate lockless accesses to dev->needed_headroom (CVE-2023-53109)

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

    i40e: Fix kernel crash during reboot when adapter is in recovery mode (CVE-2023-53114)

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

    nvmet: avoid potential UAF in nvmet_req_complete() (CVE-2023-53116)

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

    fs: prevent out-of-bounds array speculation when closing a file descriptor (CVE-2023-53117)

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

    tcp: tcp_make_synack() can be called from process context (CVE-2023-53121)

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

    scsi: mpt3sas: Fix NULL pointer access in mpt3sas_transport_port_add() (CVE-2023-53124)

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

    net: usb: smsc75xx: Limit packet length to skb->len (CVE-2023-53125)

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

    SUNRPC: Fix a server shutdown leak (CVE-2023-53131)

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

    bnxt_en: Avoid order-5 memory allocation for TPA data (CVE-2023-53134)

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

    ext4: Fix possible corruption when moving a directory (CVE-2023-53137)

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

    scsi: core: Remove the /proc/scsi/${proc_name} directory earlier (CVE-2023-53140)

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

    ila: do not generate empty messages in ila_xlat_nl_cmd_get_mapping() (CVE-2023-53141)

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

    ext4: fix another off-by-one fsmap error on 1k block filesystems (CVE-2023-53143)

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

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

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

    KVM: VMX: Fix crash due to uninitialized current_vmcs (CVE-2023-53756)

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

    iommu/amd: Add a length limitation for the ivrs_acpihid command-line parameter (CVE-2023-54057)

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

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

    ext4: block range must be validated before use in ext4_mb_clear_bb() (CVE-2022-50021)

    A use-after-free vulnerability in the Linux Kernel Performance Events system can be exploited to achieve     local privilege escalation.

    The perf_group_detach function did not check the event's siblings' attach_state before calling     add_event_to_groups(), but remove_on_exec made it possible to call list_del_event() on before detaching     from their group, making it possible to use a dangling pointer causing a use-after-free vulnerability.

    We recommend upgrading past commit fd0815f632c24878e325821943edccc7fde947a2. (CVE-2023-2235)

    An issue was discovered in arch/x86/kvm/vmx/nested.c in the Linux kernel before 6.2.8. nVMX on x86_64     lacks consistency checks for CR0 and CR4. (CVE-2023-30456)

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

    ftrace: Fix invalid address access in lookup_rec() when index is 0 (CVE-2023-53075)

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

    drm/shmem-helper: Remove another errant put in error path (CVE-2023-53084)

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

    drm/i915/active: Fix misuse of non-idle barriers as fence trackers (CVE-2023-53087)

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

    ext4: fix task hung in ext4_xattr_delete_inode (CVE-2023-53089)

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

    ext4: update s_journal_inum if it changes after journal replay (CVE-2023-53091)

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

    interconnect: fix mem leak when freeing nodes (CVE-2023-53096)

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

    ext4: fix WARNING in ext4_update_inline_data (CVE-2023-53100)

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

    ext4: zero i_disksize when initializing the bootloader inode (CVE-2023-53101)

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

    bonding: restore bond's IFF_SLAVE flag if a non-eth dev enslave fails (CVE-2023-53103)

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

    net: tunnels: annotate lockless accesses to dev->needed_headroom (CVE-2023-53109)

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

    loop: Fix use-after-free issues (CVE-2023-53111)

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

    fs: prevent out-of-bounds array speculation when closing a file descriptor (CVE-2023-53117)

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

    tcp: tcp_make_synack() can be called from process context (CVE-2023-53121)

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

    PCI: s390: Fix use-after-free of PCI resources with per-function hotplug (CVE-2023-53123)

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

    SUNRPC: Fix a server shutdown leak (CVE-2023-53131)

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

    bpf, sockmap: Fix an infinite loop error when len is 0 in tcp_bpf_recvmsg_parser() (CVE-2023-53133)

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

    af_unix: fix struct pid leaks in OOB support (CVE-2023-53136)

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

    ext4: Fix possible corruption when moving a directory (CVE-2023-53137)

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

    scsi: core: Remove the /proc/scsi/${proc_name} directory earlier (CVE-2023-53140)

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

    ila: do not generate empty messages in ila_xlat_nl_cmd_get_mapping() (CVE-2023-53141)

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

    ext4: fix another off-by-one fsmap error on 1k block filesystems (CVE-2023-53143)

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

    x86/resctrl: Clear staged_config[] before and after it is used (CVE-2023-53169)

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

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

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

    KVM: VMX: Fix crash due to uninitialized current_vmcs (CVE-2023-53756)

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

    iommu/amd: Add a length limitation for the ivrs_acpihid command-line parameter (CVE-2023-54057)

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	Type	Severity
360215	CentOS Linux 8.5 [TuxCare] Security Update: bpftool / kernel / kernel-core / kernel-cross-headers / etc Multiple Vulnerabilities (CENTOS8.5:CLSA-2026:1782146775)	Nessus	CentOS Local Security Checks	Local	high
353232	CentOS Linux 7 [TuxCare] Security Update: bpftool / kernel / kernel-debug / kernel-debug-devel / kernel-devel / etc Multiple Vulnerabilities (CENTOS7:CLSA-2026:1782148320)	Nessus	CentOS Local Security Checks	Local	high
352893	CentOS Linux 8 [TuxCare] Security Update: bpftool / kernel / kernel-core / kernel-cross-headers / etc Multiple Vulnerabilities (CENTOS-STREAM8:CLSA-2026:1783790425)	Nessus	CentOS Local Security Checks	Local	critical
352525	CentOS Linux 8.4 [TuxCare] Security Update: bpftool / kernel / kernel-core / kernel-cross-headers / etc Multiple Vulnerabilities (CENTOS8.4:CLSA-2026:1783414634)	Nessus	CentOS Local Security Checks	Local	high
281295	Unity Linux 20.1060a / 20.1070a Security Update: kernel (UTSA-2025-993068)	Nessus	Unity Linux Local Security Checks	Local	high
280528	Unity Linux 20.1060e / 20.1070e Security Update: kernel (UTSA-2025-992567)	Nessus	Unity Linux Local Security Checks	Local	high
279319	EulerOS Virtualization 2.13.0 : kernel (EulerOS-SA-2025-2581)	Nessus	Huawei Local Security Checks	Local	high
279287	EulerOS Virtualization 2.13.1 : kernel (EulerOS-SA-2025-2546)	Nessus	Huawei Local Security Checks	Local	high
271309	EulerOS 2.0 SP13 : kernel (EulerOS-SA-2025-2264)	Nessus	Huawei Local Security Checks	Local	high
271298	EulerOS 2.0 SP13 : kernel (EulerOS-SA-2025-2296)	Nessus	Huawei Local Security Checks	Local	high
244444	Linux Distros Unpatched Vulnerability : CVE-2022-50021	Nessus	Misc.	Local	high
242951	SUSE SLES15: cluster-md-kmp-default / dlm-kmp-default / gfs2-kmp-default / etc (SUSE-SU-2025:02537-1)	Nessus	SuSE Local Security Checks	Local	high
241963	SUSE SLES15 : Security update for the Linux Kernel (SUSE-SU-2025:02264-1)	Nessus	SuSE Local Security Checks	Local	high
200362	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.10-2024-059 (ALASKERNEL-5.10-2024-059)	Nessus	Amazon Linux Local Security Checks	Local	high
176754	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.15-2023-019 (ALASKERNEL-5.15-2023-019)	Nessus	Amazon Linux Local Security Checks	Local	high
151965	Photon OS 4.0: Linux PHSA-2021-4.0-0065	Nessus	PhotonOS Local Security Checks	Local	high

Detections

Analytics

CVE-2022-50021

high

Tenable Plugins

high

high

critical

high

high

high

high

high

high

high

high

high

high

high

high

high