In the Linux kernel, the following vulnerability has been resolved: bpf, verifier: Fix memory leak in array reallocation for stack state If an error (NULL) is returned by krealloc(), callers of realloc_array() were setting their allocation pointers to NULL, but on error krealloc() does not touch the original allocation. This would result in a memory resource leak. Instead, free the old allocation on the error handling path. The memory leak information is as follows as also reported by Zhengchao: unreferenced object 0xffff888019801800 (size 256): comm "bpf_repo", pid 6490, jiffies 4294959200 (age 17.170s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [<00000000b211474b>] __kmalloc_node_track_caller+0x45/0xc0 [<0000000086712a0b>] krealloc+0x83/0xd0 [<00000000139aab02>] realloc_array+0x82/0xe2 [<00000000b1ca41d1>] grow_stack_state+0xfb/0x186 [<00000000cd6f36d2>] check_mem_access.cold+0x141/0x1341 [<0000000081780455>] do_check_common+0x5358/0xb350 [<0000000015f6b091>] bpf_check.cold+0xc3/0x29d [<000000002973c690>] bpf_prog_load+0x13db/0x2240 [<00000000028d1644>] __sys_bpf+0x1605/0x4ce0 [<00000000053f29bd>] __x64_sys_bpf+0x75/0xb0 [<0000000056fedaf5>] do_syscall_64+0x35/0x80 [<000000002bd58261>] entry_SYSCALL_64_after_hwframe+0x63/0xcd

The AlmaLinux 9.2 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.2:CLSA-2026:1780516677 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: can: isotp: fix potential CAN frame     reception race in isotp_rcv() When receiving a CAN frame the current code logic does not consider     concurrently receiving processes which do not show up in real world usage. Ziyang Xuan writes: The     following syz problem is one of the scenarios. so->rx.len is changed by isotp_rcv_ff() during     isotp_rcv_cf(), so->rx.len equals 0 before alloc_skb() and equals 4096 after alloc_skb(). That will     trigger skb_over_panic() in skb_put(). ======================================================= CPU: 1 PID:
    19 Comm: ksoftirqd/1 Not tainted 5.16.0-rc8-syzkaller #0 RIP: 0010:skb_panic+0x16c/0x16e     net/core/skbuff.c:113 Call Trace: <TASK> skb_over_panic net/core/skbuff.c:118 [inline]     skb_put.cold+0x24/0x24 net/core/skbuff.c:1990 isotp_rcv_cf net/can/isotp.c:570 [inline]     isotp_rcv+0xa38/0x1e30 net/can/isotp.c:668 deliver net/can/af_can.c:574 [inline]     can_rcv_filter+0x445/0x8d0 net/can/af_can.c:635 can_receive+0x31d/0x580 net/can/af_can.c:665     can_rcv+0x120/0x1c0 net/can/af_can.c:696 __netif_receive_skb_one_core+0x114/0x180 net/core/dev.c:5465
    __netif_receive_skb+0x24/0x1b0 net/core/dev.c:5579 Therefore we make sure the state changes and data     structures stay consistent at CAN frame reception time by adding a spin_lock in isotp_rcv(). This fixes     the issue reported by syzkaller but does not affect real world operation. (CVE-2022-48830)

  - In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: sdata can be NULL     during AMPDU start ieee80211_tx_ba_session_handle_start() may get NULL for sdata when a deauthentication     is ongoing. Here a trace triggering the race with the hostapd test multi_ap_fronthaul_on_ap: (gdb) list
    *drv_ampdu_action+0x46 0x8b16 is in drv_ampdu_action (net/mac80211/driver-ops.c:396). 391 int ret =
    -EOPNOTSUPP; 392 393 might_sleep(); 394 395 sdata = get_bss_sdata(sdata); 396 if     (!check_sdata_in_driver(sdata)) 397 return -EIO; 398 399 trace_drv_ampdu_action(local, sdata, params); 400     wlan0: moving STA 02:00:00:00:03:00 to state 3 wlan0: associated wlan0: deauthenticating from     02:00:00:00:03:00 by local choice (Reason: 3=DEAUTH_LEAVING) wlan3.sta1: Open BA session requested for     02:00:00:00:00:00 tid 0 wlan3.sta1: dropped frame to 02:00:00:00:00:00 (unauthorized port) wlan0: moving     STA 02:00:00:00:03:00 to state 2 wlan0: moving STA 02:00:00:00:03:00 to state 1 wlan0: Removed STA     02:00:00:00:03:00 wlan0: Destroyed STA 02:00:00:00:03:00 BUG: unable to handle page fault for address:
    fffffffffffffb48 PGD 11814067 P4D 11814067 PUD 11816067 PMD 0 Oops: 0000 [#1] PREEMPT SMP PTI CPU: 2 PID:
    133397 Comm: kworker/u16:1 Tainted: G W 6.1.0-rc8-wt+ #59 Hardware name: QEMU Standard PC (Q35 + ICH9,     2009), BIOS 1.16.0-20220807_005459-localhost 04/01/2014 Workqueue: phy3 ieee80211_ba_session_work     [mac80211] RIP: 0010:drv_ampdu_action+0x46/0x280 [mac80211] Code: 53 48 89 f3 be 89 01 00 00 e8 d6 43 bf     ef e8 21 46 81 f0 83 bb a0 1b 00 00 04 75 0e 48 8b 9b 28 0d 00 00 48 81 eb 10 0e 00 00 <8b> 93 58 09 00 00     f6 c2 20 0f 84 3b 01 00 00 8b 05 dd 1c 0f 00 85 RSP: 0018:ffffc900025ebd20 EFLAGS: 00010287 RAX:
    0000000000000000 RBX: fffffffffffff1f0 RCX: ffff888102228240 RDX: 0000000080000000 RSI: ffffffff918c5de0     RDI: ffff888102228b40 RBP: ffffc900025ebd40 R08: 0000000000000001 R09: 0000000000000001 R10:
    0000000000000001 R11: 0000000000000000 R12: ffff888118c18ec0 R13: 0000000000000000 R14: ffffc900025ebd60     R15: ffff888018b7efb8 FS: 0000000000000000(0000) GS:ffff88817a600000(0000) knlGS:0000000000000000 CS: 0010     DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: fffffffffffffb48 CR3: 0000000105228006 CR4: 0000000000170ee0     Call Trace: <TASK> ieee80211_tx_ba_session_handle_start+0xd0/0x190 [mac80211]     ieee80211_ba_session_work+0xff/0x2e0 [mac80211] process_one_work+0x29f/0x620 worker_thread+0x4d/0x3d0 ?     process_one_work+0x620/0x620 kthread+0xfb/0x120 ? kthread_complete_and_exit+0x20/0x20     ret_from_fork+0x22/0x30 </TASK> (CVE-2022-48875)

  - In the Linux kernel, the following vulnerability has been resolved: udf: Fix preallocation discarding at     indirect extent boundary When preallocation extent is the first one in the extent block, the code would     corrupt extent tree header instead. Fix the problem and use udf_delete_aext() for deleting extent to avoid     some code duplication. (CVE-2022-48946)

  - In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Fix crash when replugging     CSR fake controllers It seems fake CSR 5.0 clones can cause the suspend notifier to be registered twice     causing the following kernel panic: [ 71.986122] Call Trace: [ 71.986124] <TASK> [ 71.986125]     blocking_notifier_chain_register+0x33/0x60 [ 71.986130] hci_register_dev+0x316/0x3d0 [bluetooth     99b5497ea3d09708fa1366c1dc03288bf3cca8da] [ 71.986154] btusb_probe+0x979/0xd85 [btusb     e1e0605a4f4c01984a4b9c8ac58c3666ae287477] [ 71.986159] ? __pm_runtime_set_status+0x1a9/0x300 [ 71.986162]     ? ktime_get_mono_fast_ns+0x3e/0x90 [ 71.986167] usb_probe_interface+0xe3/0x2b0 [ 71.986171]     really_probe+0xdb/0x380 [ 71.986174] ? pm_runtime_barrier+0x54/0x90 [ 71.986177]
    __driver_probe_device+0x78/0x170 [ 71.986180] driver_probe_device+0x1f/0x90 [ 71.986183]
    __device_attach_driver+0x89/0x110 [ 71.986186] ? driver_allows_async_probing+0x70/0x70 [ 71.986189]     bus_for_each_drv+0x8c/0xe0 [ 71.986192] __device_attach+0xb2/0x1e0 [ 71.986195] bus_probe_device+0x92/0xb0     [ 71.986198] device_add+0x422/0x9a0 [ 71.986201] ? sysfs_merge_group+0xd4/0x110 [ 71.986205]     usb_set_configuration+0x57a/0x820 [ 71.986208] usb_generic_driver_probe+0x4f/0x70 [ 71.986211]     usb_probe_device+0x3a/0x110 [ 71.986213] really_probe+0xdb/0x380 [ 71.986216] ?     pm_runtime_barrier+0x54/0x90 [ 71.986219] __driver_probe_device+0x78/0x170 [ 71.986221]     driver_probe_device+0x1f/0x90 [ 71.986224] __device_attach_driver+0x89/0x110 [ 71.986227] ?     driver_allows_async_probing+0x70/0x70 [ 71.986230] bus_for_each_drv+0x8c/0xe0 [ 71.986232]
    __device_attach+0xb2/0x1e0 [ 71.986235] bus_probe_device+0x92/0xb0 [ 71.986237] device_add+0x422/0x9a0 [     71.986239] ? _dev_info+0x7d/0x98 [ 71.986242] ? blake2s_update+0x4c/0xc0 [ 71.986246]     usb_new_device.cold+0x148/0x36d [ 71.986250] hub_event+0xa8a/0x1910 [ 71.986255]     process_one_work+0x1c4/0x380 [ 71.986259] worker_thread+0x51/0x390 [ 71.986262] ?     rescuer_thread+0x3b0/0x3b0 [ 71.986264] kthread+0xdb/0x110 [ 71.986266] ?     kthread_complete_and_exit+0x20/0x20 [ 71.986268] ret_from_fork+0x1f/0x30 [ 71.986273] </TASK> [ 71.986274]
    ---[ end trace 0000000000000000 ]--- [ 71.986284] btusb: probe of 2-1.6:1.0 failed with error -17     (CVE-2022-48982)

  - In the Linux kernel, the following vulnerability has been resolved: can: m_can: pci: add missing     m_can_class_free_dev() in probe/remove methods In m_can_pci_remove() and error handling path of     m_can_pci_probe(), m_can_class_free_dev() should be called to free resource allocated by     m_can_class_allocate_dev(), otherwise there will be memleak. (CVE-2022-49024)

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 :

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

    igb: revert rtnl_lock() that causes deadlock(CVE-2023-53060)

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

    net_sched: sch_sfq: move the limit validation(CVE-2025-37752)

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

    net: annotate races around sk-sk_bound_dev_if(CVE-2022-49420)

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

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

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

    udp: Fix memory accounting leak.(CVE-2025-22058)

    netem: Update sch-q.qlen before qdisc_tree_reduce_backlog().(CVE-2025-21703)

    net: fix memory leak in tcp_conn_request().(CVE-2024-57841)

    xfrm: state: fix out-of-bounds read during lookup(CVE-2024-57982)

    Insufficient control flow management for the Intel(R) 82599 Ethernet Controllers and Adapters may allow an     authenticated user to potentially enable denial of service via local access.(CVE-2021-33061)

    udf: Fix a slab-out-of-bounds write bug in udf_find_entry().(CVE-2022-49846)

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

    ata: libata-transport: fix error handling in ata_tport_add().(CVE-2022-49825)

    ata: libata-transport: fix double ata_host_put() in ata_tport_add().(CVE-2022-49826)

    bpf: track changes_pkt_data property for global functions(CVE-2024-58098)

    pinctrl: devicetree: fix null pointer dereferencing in pinctrl_dt_to_map(CVE-2022-49832)

    scsi: core: Fix a procfs host directory removal regression(CVE-2023-53118)

    bpf, verifier: Fix memory leak in array reallocation for stack state(CVE-2022-49878)

    kprobes: Skip clearing aggrprobe's post_handler in kprobe-on-ftrace case(CVE-2022-49779)

    i2c: piix4: Fix adapter not be removed in piix4_remove().(CVE-2022-49900)

    bpf: Fix kmemleak warning for percpu hashmap(CVE-2025-37807)

    drm: Fix potential null-ptr-deref in drm_vblank_destroy_worker().(CVE-2022-49827)

    RDMA/core: Fix null-ptr-deref in ib_core_cleanup().(CVE-2022-49925)

    net: tun: Fix memory leaks of napi_get_frags(CVE-2022-49871)

    net: sched: Fix use after free in red_enqueue().(CVE-2022-49921)

    bnxt_en: Fix possible crash in bnxt_hwrm_set_coal().(CVE-2022-49869)

    tipc: fix the msg-req tlv len check in tipc_nl_compat_name_table_dump_header(CVE-2022-49862)

    bpf, test_run: Fix alignment problem in bpf_prog_test_run_skb().(CVE-2022-49840)

    net: macvlan: fix memory leaks of macvlan_common_newlink(CVE-2022-49853)

    HID: hyperv: fix possible memory leak in mousevsc_probe().(CVE-2022-49874)

    bpftool: Fix NULL pointer dereference when pin {PROG, MAP, LINK} without FILE(CVE-2022-49875)

    ftrace: Fix null pointer dereference in ftrace_add_mod().(CVE-2022-49802)

    tracing: Do not let histogram values have some modifiers(CVE-2023-53093)

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

    iavf: Fix handling of dummy receive descriptors(CVE-2022-49583)

    ftrace: Fix use-after-free for dynamic ftrace_ops(CVE-2022-49892)

    fscrypt: stop using keyrings subsystem for fscrypt_master_key(CVE-2022-49899)

    bpf: Fix wrong reg type conversion in release_reference().(CVE-2022-49873)

    capabilities: fix potential memleak on error path from vfs_getxattr_alloc().(CVE-2022-49890)

    nfs4: Fix kmemleak when allocate slot failed(CVE-2022-49927)

    scsi: scsi_transport_sas: Fix error handling in sas_phy_add().(CVE-2022-49839)

    ACPI: APEI: Fix integer overflow in ghes_estatus_pool_init().(CVE-2022-49885)

    blk-mq: Fix kmemleak in blk_mq_init_allocated_queue(CVE-2022-49901)

    bpf: Fix memory leaks in __check_func_call(CVE-2022-49837)

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

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

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

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

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

    ata: libata-transport: fix error handling in ata_tdev_add().(CVE-2022-49823)

    ext4: fix BUG_ON() when directory entry has invalid rec_len(CVE-2022-49879)

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

    scsi: target: tcm_loop: Fix possible name leak in tcm_loop_setup_hba_bus().(CVE-2022-49780)

    ext4: fix warning in 'ext4_da_release_space'(CVE-2022-49880)

    ring-buffer: Check for NULL cpu_buffer in ring_buffer_wake_waiters().(CVE-2022-49889)

    netlabel: Fix NULL pointer exception caused by CALIPSO on IPv4 sockets.(CVE-2025-22063)

    clk: samsung: Fix UBSAN panic in samsung_clk_init().(CVE-2025-39728)

    x86/mm/pat: Fix VM_PAT handling when fork() fails in copy_page_range().(CVE-2025-22090)

    misc/vmw_vmci: fix an infoleak in vmci_host_do_receive_datagram().(CVE-2022-49788)

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

    tracing: Fix wild-memory-access in register_synth_event().(CVE-2022-49799)

    hrtimers: Handle CPU state correctly on hotplug(CVE-2024-57951)

    block, bfq: fix uaf for bfqq in bic_set_bfqq().(CVE-2023-52983)

    tcp: Fix data-races around sysctl_tcp_max_reordering.(CVE-2022-49571)

    tcp: Fix data-races around sysctl_tcp_slow_start_after_idle.(CVE-2022-49572)

    tcp: Fix a data-race around sysctl_tcp_early_retrans.(CVE-2022-49573)

    kthread: unpark only parked kthread(CVE-2024-50019)

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

    net: openvswitch: fix flow memory leak in ovs_flow_cmd_new(CVE-2023-52977)

    efi: Do not import certificates from UEFI Secure Boot for T2 Macs(CVE-2022-49357)

    Bluetooth: fix dangling sco_conn and use-after-free in sco_sock_timeout(CVE-2022-49474)

    mmc: core: use sysfs_emit() instead of sprintf().(CVE-2022-49267)

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

    tcp: Fix data-races around sysctl_tcp_fastopen.(CVE-2022-49586)

    tcp: Fix a data-race around sysctl_tcp_thin_linear_timeouts.(CVE-2022-49575)

    ipv6: Fix signed integer overflow in l2tp_ip6_sendmsg(CVE-2022-49727)

    tcp: Fix a data-race around sysctl_tcp_notsent_lowat.(CVE-2022-49587)

    dlm: prevent NPD when writing a positive value to event_done(CVE-2025-23131)

    thermal: int340x: Add NULL check for adev(CVE-2025-23136)

    nfsd: don't ignore the return code of svc_proc_register().(CVE-2025-22026)

    ext4: fix out-of-bound read in ext4_xattr_inode_dec_ref_all().(CVE-2025-22121)

    ext4: avoid journaling sb update on error if journal is destroying(CVE-2025-22113)

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.

  - In the Linux kernel, the following vulnerability has been resolved: bpf, verifier: Fix memory leak in     array reallocation for stack state If an error (NULL) is returned by krealloc(), callers of     realloc_array() were setting their allocation pointers to NULL, but on error krealloc() does not touch the     original allocation. This would result in a memory resource leak. Instead, free the old allocation on the     error handling path. The memory leak information is as follows as also reported by Zhengchao: unreferenced     object 0xffff888019801800 (size 256): comm bpf_repo, pid 6490, jiffies 4294959200 (age 17.170s) hex dump     (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00     00 00 00 00 00 00 00 00 ................ backtrace: [<00000000b211474b>]
    __kmalloc_node_track_caller+0x45/0xc0 [<0000000086712a0b>] krealloc+0x83/0xd0 [<00000000139aab02>]     realloc_array+0x82/0xe2 [<00000000b1ca41d1>] grow_stack_state+0xfb/0x186 [<00000000cd6f36d2>]     check_mem_access.cold+0x141/0x1341 [<0000000081780455>] do_check_common+0x5358/0xb350 [<0000000015f6b091>]     bpf_check.cold+0xc3/0x29d [<000000002973c690>] bpf_prog_load+0x13db/0x2240 [<00000000028d1644>]
    __sys_bpf+0x1605/0x4ce0 [<00000000053f29bd>] __x64_sys_bpf+0x75/0xb0 [<0000000056fedaf5>]     do_syscall_64+0x35/0x80 [<000000002bd58261>] entry_SYSCALL_64_after_hwframe+0x63/0xcd (CVE-2022-49878)

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

The remote Redhat Enterprise Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2023:6583 advisory.

    The kernel packages contain the Linux kernel, the core of any Linux operating system.

    Security Fix(es):

    * kernel: net/sched: cls_u32 component reference counter leak if tcf_change_indev() fails (CVE-2023-3609)

    * kernel: net/sched: Use-after-free vulnerabilities in the net/sched classifiers: cls_fw, cls_u32 and     cls_route (CVE-2023-4128, CVE-2023-4206, CVE-2023-4207, CVE-2023-4208)

    * kernel: eBPF: insufficient stack type checks in dynptr (CVE-2023-39191)

    * Kernel: race when faulting a device private page in memory manager (CVE-2022-3523)

    * kernel: use-after-free in l1oip timer handlers (CVE-2022-3565)

    * kernel: Rate limit overflow messages in r8152 in intr_callback (CVE-2022-3594)

    * kernel: vmwgfx: use-after-free in vmw_cmd_res_check (CVE-2022-38457)

    * kernel: vmwgfx: use-after-free in vmw_execbuf_tie_context (CVE-2022-40133)

    * hw: Intel: Gather Data Sampling (GDS) side channel vulnerability (CVE-2022-40982)

    * kernel: Information leak in l2cap_parse_conf_req in net/bluetooth/l2cap_core.c (CVE-2022-42895)

    * kernel: x86/mm: Randomize per-cpu entry area (CVE-2023-0597)

    * kernel: HID: check empty report_list in hid_validate_values() (CVE-2023-1073)

    * kernel: sctp: fail if no bound addresses can be used for a given scope (CVE-2023-1074)

    * kernel: hid: Use After Free in asus_remove() (CVE-2023-1079)

    * kernel: hash collisions in the IPv6 connection lookup table (CVE-2023-1206)

    * kernel: ovl: fix use after free in struct ovl_aio_req (CVE-2023-1252)

    * Kernel: use-after-free in nfsd4_ssc_setup_dul in fs/nfsd/nfs4proc.c (CVE-2023-1652)

    * kernel: Use after free bug in btsdio_remove due to race condition (CVE-2023-1989)

    * kernel: fbcon: shift-out-of-bounds in fbcon_set_font() (CVE-2023-3161)

    * kernel: out-of-bounds access in relay_file_read (CVE-2023-3268)

    * kernel: xfrm: NULL pointer dereference in xfrm_update_ae_params() (CVE-2023-3772)

    * kernel: xfrm: out-of-bounds read of XFRMA_MTIMER_THRESH nlattr (CVE-2023-3773)

    * kernel: KVM: SEV-ES / SEV-SNP VMGEXIT double fetch vulnerability (CVE-2023-4155)

    * kernel: exFAT: stack overflow in exfat_get_uniname_from_ext_entry (CVE-2023-4273)

    * kernel: mpls: double free on sysctl allocation failure (CVE-2023-26545)

    * kernel: KVM: nVMX: missing consistency checks for CR0 and CR4 (CVE-2023-30456)

    * kernel: net: qcom/emac: race condition leading to use-after-free in emac_remove() (CVE-2023-33203)

    * kernel: vmwgfx: race condition leading to information disclosure vulnerability (CVE-2023-33951)

    * kernel: vmwgfx: double free within the handling of vmw_buffer_object objects (CVE-2023-33952)

    * kernel: r592: race condition leading to use-after-free in r592_remove() (CVE-2023-35825)

    * kernel: net/tls: tls_is_tx_ready() checked list_entry (CVE-2023-1075)

    * kernel: tap: tap_open(): correctly initialize socket uid (CVE-2023-1076)

    * kernel: missing mmap_lock in file_files_note that could possibly lead to a use after free in the     coredump code (CVE-2023-1249)

    * kernel: use-after-free bug in remove function xgene_hwmon_remove (CVE-2023-1855)

    * kernel: Use after free bug in r592_remove (CVE-2023-3141)

    * kernel: gfs2: NULL pointer dereference in gfs2_evict_inode() (CVE-2023-3212)

    * kernel: NULL pointer dereference due to missing kalloc() return value check in     shtp_cl_get_dma_send_buf() (CVE-2023-3358)

    * kernel: tap: tap_open(): correctly initialize socket uid next fix of i_uid to current_fsuid     (CVE-2023-4194)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

    Additional Changes:

    For detailed information on changes in this release, see the Red Hat Enterprise Linux 9.3 Release Notes     linked from the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux 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.79-51.138. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.15-2022-011 advisory.

    A vulnerability classified as problematic has been found in Linux Kernel. This affects the function     fib_nh_match of the file net/ipv4/fib_semantics.c of the component IPv4 Handler. The manipulation leads to     out-of-bounds read. It is possible to initiate the attack remotely. It is recommended to apply a patch to     fix this issue. The identifier VDB-210357 was assigned to this vulnerability. (CVE-2022-3435)

    A vulnerability was found in Linux Kernel. It has been declared as problematic. Affected by this     vulnerability is the function ipv6_renew_options of the component IPv6 Handler. The manipulation leads to     memory leak. The attack can be launched remotely. It is recommended to apply a patch to fix this issue.
    The identifier VDB-211021 was assigned to this vulnerability. (CVE-2022-3524)

    A vulnerability, which was classified as problematic, has been found in Linux Kernel. This issue affects     the function unix_sock_destructor/unix_release_sock of the file net/unix/af_unix.c of the component BPF.
    The manipulation leads to memory leak. It is recommended to apply a patch to fix this issue. The     associated identifier of this vulnerability is VDB-211043. (CVE-2022-3543)

    A vulnerability classified as critical was found in Linux Kernel. Affected by this vulnerability is the     function l2cap_reassemble_sdu of the file net/bluetooth/l2cap_core.c of the component Bluetooth. The     manipulation leads to use after free. It is recommended to apply a patch to fix this issue. The associated     identifier of this vulnerability is VDB-211087. (CVE-2022-3564)

    A vulnerability has been found in Linux Kernel and classified as problematic. This vulnerability affects     the function l2cap_recv_acldata of the file net/bluetooth/l2cap_core.c of the component Bluetooth. The     manipulation leads to memory leak. It is recommended to apply a patch to fix this issue. VDB-211918 is the     identifier assigned to this vulnerability. (CVE-2022-3619)

    A vulnerability was found in Linux Kernel. It has been declared as problematic. Affected by this     vulnerability is the function follow_page_pte of the file mm/gup.c of the component BPF. The manipulation     leads to race condition. The attack can be launched remotely. It is recommended to apply a patch to fix     this issue. The identifier VDB-211921 was assigned to this vulnerability. (CVE-2022-3623)

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

    btrfs: zoned: initialize device's zone info for seeding (CVE-2022-49831)

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

    udf: Fix a slab-out-of-bounds write bug in udf_find_entry() (CVE-2022-49846)

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

    btrfs: fix match incorrectly in dev_args_match_device (CVE-2022-49849)

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

    net: macvlan: fix memory leaks of macvlan_common_newlink (CVE-2022-49853)

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

    can: af_can: fix NULL pointer dereference in can_rx_register() (CVE-2022-49863)

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

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

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

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

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

    net: tun: Fix memory leaks of napi_get_frags (CVE-2022-49871)

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

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

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

    bpf: Fix wrong reg type conversion in release_reference() (CVE-2022-49873)

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

    HID: hyperv: fix possible memory leak in mousevsc_probe() (CVE-2022-49874)

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

    bpftool: Fix NULL pointer dereference when pin {PROG, MAP, LINK} without FILE (CVE-2022-49875)

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

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

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

    bpf, verifier: Fix memory leak in array reallocation for stack state (CVE-2022-49878)

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

    ext4: fix BUG_ON() when directory entry has invalid rec_len (CVE-2022-49879)

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

    ext4: fix warning in 'ext4_da_release_space' (CVE-2022-49880)

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

    ACPI: APEI: Fix integer overflow in ghes_estatus_pool_init() (CVE-2022-49885)

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

    arm64: entry: avoid kprobe recursion (CVE-2022-49888)

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

    ring-buffer: Check for NULL cpu_buffer in ring_buffer_wake_waiters() (CVE-2022-49889)

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

    capabilities: fix potential memleak on error path from vfs_getxattr_alloc() (CVE-2022-49890)

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

    ftrace: Fix use-after-free for dynamic ftrace_ops (CVE-2022-49892)

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

    btrfs: fix tree mod log mishandling of reallocated nodes (CVE-2022-49898)

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

    fscrypt: stop using keyrings subsystem for fscrypt_master_key (CVE-2022-49899)

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

    block: Fix possible memory leak for rq_wb on add_disk failure (CVE-2022-49902)

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

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

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

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

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

    net/smc: Fix possible leaked pernet namespace in smc_init() (CVE-2022-49905)

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

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

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

    netfilter: ipset: enforce documented limit to prevent allocating huge memory (CVE-2022-49911)

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

    btrfs: fix ulist leaks in error paths of qgroup self tests (CVE-2022-49912)

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

    btrfs: fix inode list leak during backref walking at find_parent_nodes() (CVE-2022-49913)

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

    btrfs: fix inode list leak during backref walking at resolve_indirect_refs() (CVE-2022-49914)

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

    mISDN: fix possible memory leak in mISDN_register_device() (CVE-2022-49915)

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

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

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

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

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

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

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

    netfilter: nf_tables: netlink notifier might race to release objects (CVE-2022-49920)

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

    net: sched: Fix use after free in red_enqueue() (CVE-2022-49921)

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

    RDMA/core: Fix null-ptr-deref in ib_core_cleanup() (CVE-2022-49925)

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

    nfs4: Fix kmemleak when allocate slot failed (CVE-2022-49927)

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

    SUNRPC: Fix null-ptr-deref when xps sysfs alloc failed (CVE-2022-49928)

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

    kcm: annotate data-races around kcm->rx_wait (CVE-2022-50265)

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

    mm,hugetlb: take hugetlb_lock before decrementing h->resv_huge_pages (CVE-2022-50285)

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

    kcm: annotate data-races around kcm->rx_psock (CVE-2022-50291)

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

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

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

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

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

    cifs: Fix xid leak in cifs_create() (CVE-2022-50351)

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

    net: sched: sfb: fix null pointer access issue when sfb_init() fails (CVE-2022-50356)

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

    mm: /proc/pid/smaps_rollup: fix no vma's null-deref (CVE-2022-50380)

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

    kernfs: fix use-after-free in __kernfs_remove (CVE-2022-50432)

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

    net: sched: cake: fix null pointer access issue when cake_init() fails (CVE-2022-50452)

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

    cifs: Fix xid leak in cifs_flock() (CVE-2022-50460)

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

    fs/binfmt_elf: Fix memory leak in load_elf_binary() (CVE-2022-50466)

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

    xhci: Remove device endpoints from bandwidth list when freeing the device (CVE-2022-50470)

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

    iommu/vt-d: Clean up si_domain in the init_dmars() error path (CVE-2022-50482)

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

    cifs: Fix xid leak in cifs_copy_file_range() (CVE-2022-50643)

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

    ethtool: eeprom: fix null-deref on genl_info in dump (CVE-2022-50651)

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

    selinux: enable use of both GFP_KERNEL and GFP_ATOMIC in convert_context() (CVE-2022-50699)

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

    net: fix UAF issue in nfqnl_nf_hook_drop() when ops_init() failed (CVE-2022-50780)

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

    ipv6: ensure sane device mtu in tunnels (CVE-2022-50816)

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

    net: hsr: avoid possible NULL deref in skb_clone() (CVE-2022-50817)

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

    cifs: Fix xid leak in cifs_ses_add_channel() (CVE-2022-50856)

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

    tcp: fix a signed-integer-overflow bug in tcp_add_backlog() (CVE-2022-50865)

    A use-after-free flaw was found in qdisc_graft in net/sched/sch_api.c in the Linux Kernel due to a race     problem. This flaw leads to a denial of service issue. (CVE-2023-0590)

    An out-of-bounds memory access flaw was found in the Linux kernel's TUN/TAP device driver functionality in     how a user generates a malicious (too big) networking packet when napi frags is enabled. This flaw allows     a local user to crash or potentially escalate their privileges on the system. (CVE-2023-3812)

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

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

ID	Name	Product	Family	Type	Severity
351689	AlmaLinux 9.2 [TuxCare] Security Update: bpftool / kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2026:1780516677)	Nessus	Alma Linux Local Security Checks	Local	high
265114	EulerOS Virtualization 2.13.1 : kernel (EulerOS-SA-2025-2168)	Nessus	Huawei Local Security Checks	Local	high
265107	EulerOS Virtualization 2.13.0 : kernel (EulerOS-SA-2025-2169)	Nessus	Huawei Local Security Checks	Local	high
249320	EulerOS 2.0 SP13 : kernel (EulerOS-SA-2025-1979)	Nessus	Huawei Local Security Checks	Local	high
249192	EulerOS 2.0 SP13 : kernel (EulerOS-SA-2025-1993)	Nessus	Huawei Local Security Checks	Local	high
245116	Linux Distros Unpatched Vulnerability : CVE-2022-49878	Nessus	Misc.	Local	medium
194262	RHEL 9 : kernel (RHSA-2023:6583)	Nessus	Red Hat Local Security Checks	Local	high
168507	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.15-2022-011 (ALASKERNEL-5.15-2022-011)	Nessus	Amazon Linux Local Security Checks	Local	high

Detections

Analytics

CVE-2022-49878

medium

Tenable Plugins

high

high

high

high

high

medium

high

high