In the Linux kernel, the following vulnerability has been resolved: rcu-tasks: Fix race in schedule and flush work While booting secondary CPUs, cpus_read_[lock/unlock] is not keeping online cpumask stable. The transient online mask results in below calltrace. [ 0.324121] CPU1: Booted secondary processor 0x0000000001 [0x410fd083] [ 0.346652] Detected PIPT I-cache on CPU2 [ 0.347212] CPU2: Booted secondary processor 0x0000000002 [0x410fd083] [ 0.377255] Detected PIPT I-cache on CPU3 [ 0.377823] CPU3: Booted secondary processor 0x0000000003 [0x410fd083] [ 0.379040] ------------[ cut here ]------------ [ 0.383662] WARNING: CPU: 0 PID: 10 at kernel/workqueue.c:3084 __flush_work+0x12c/0x138 [ 0.384850] Modules linked in: [ 0.385403] CPU: 0 PID: 10 Comm: rcu_tasks_rude_ Not tainted 5.17.0-rc3-v8+ #13 [ 0.386473] Hardware name: Raspberry Pi 4 Model B Rev 1.4 (DT) [ 0.387289] pstate: 20000005 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 0.388308] pc : __flush_work+0x12c/0x138 [ 0.388970] lr : __flush_work+0x80/0x138 [ 0.389620] sp : ffffffc00aaf3c60 [ 0.390139] x29: ffffffc00aaf3d20 x28: ffffffc009c16af0 x27: ffffff80f761df48 [ 0.391316] x26: 0000000000000004 x25: 0000000000000003 x24: 0000000000000100 [ 0.392493] x23: ffffffffffffffff x22: ffffffc009c16b10 x21: ffffffc009c16b28 [ 0.393668] x20: ffffffc009e53861 x19: ffffff80f77fbf40 x18: 00000000d744fcc9 [ 0.394842] x17: 000000000000000b x16: 00000000000001c2 x15: ffffffc009e57550 [ 0.396016] x14: 0000000000000000 x13: ffffffffffffffff x12: 0000000100000000 [ 0.397190] x11: 0000000000000462 x10: ffffff8040258008 x9 : 0000000100000000 [ 0.398364] x8 : 0000000000000000 x7 : ffffffc0093c8bf4 x6 : 0000000000000000 [ 0.399538] x5 : 0000000000000000 x4 : ffffffc00a976e40 x3 : ffffffc00810444c [ 0.400711] x2 : 0000000000000004 x1 : 0000000000000000 x0 : 0000000000000000 [ 0.401886] Call trace: [ 0.402309] __flush_work+0x12c/0x138 [ 0.402941] schedule_on_each_cpu+0x228/0x278 [ 0.403693] rcu_tasks_rude_wait_gp+0x130/0x144 [ 0.404502] rcu_tasks_kthread+0x220/0x254 [ 0.405264] kthread+0x174/0x1ac [ 0.405837] ret_from_fork+0x10/0x20 [ 0.406456] irq event stamp: 102 [ 0.406966] hardirqs last enabled at (101): [<ffffffc0093c8468>] _raw_spin_unlock_irq+0x78/0xb4 [ 0.408304] hardirqs last disabled at (102): [<ffffffc0093b8270>] el1_dbg+0x24/0x5c [ 0.409410] softirqs last enabled at (54): [<ffffffc0081b80c8>] local_bh_enable+0xc/0x2c [ 0.410645] softirqs last disabled at (50): [<ffffffc0081b809c>] local_bh_disable+0xc/0x2c [ 0.411890] ---[ end trace 0000000000000000 ]--- [ 0.413000] smp: Brought up 1 node, 4 CPUs [ 0.413762] SMP: Total of 4 processors activated. [ 0.414566] CPU features: detected: 32-bit EL0 Support [ 0.415414] CPU features: detected: 32-bit EL1 Support [ 0.416278] CPU features: detected: CRC32 instructions [ 0.447021] Callback from call_rcu_tasks_rude() invoked. [ 0.506693] Callback from call_rcu_tasks() invoked. This commit therefore fixes this issue by applying a single-CPU optimization to the RCU Tasks Rude grace-period process. The key point here is that the purpose of this RCU flavor is to force a schedule on each online CPU since some past event. But the rcu_tasks_rude_wait_gp() function runs in the context of the RCU Tasks Rude's grace-period kthread, so there must already have been a context switch on the current CPU since the call to either synchronize_rcu_tasks_rude() or call_rcu_tasks_rude(). So if there is only a single CPU online, RCU Tasks Rude's grace-period kthread does not need to anything at all. It turns out that the rcu_tasks_rude_wait_gp() function's call to schedule_on_each_cpu() causes problems during early boot. During that time, there is only one online CPU, namely the boot CPU. Therefore, applying this single-CPU optimization fixes early-boot instances of this problem.

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

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

    rcu-tasks: Fix race in schedule and flush work

    While booting secondary CPUs, cpus_read_[lock/unlock] is not keeping     online cpumask stable. The transient online mask results in below     calltrace.

    [    0.324121] CPU1: Booted secondary processor 0x0000000001 [0x410fd083]     [    0.346652] Detected PIPT I-cache on CPU2     [    0.347212] CPU2: Booted secondary processor 0x0000000002 [0x410fd083]     [    0.377255] Detected PIPT I-cache on CPU3     [    0.377823] CPU3: Booted secondary processor 0x0000000003 [0x410fd083]     [    0.379040] ------------[ cut here ]------------     [    0.383662] WARNING: CPU: 0 PID: 10 at kernel/workqueue.c:3084 __flush_work+0x12c/0x138     [    0.384850] Modules linked in:
    [    0.385403] CPU: 0 PID: 10 Comm: rcu_tasks_rude_ Not tainted 5.17.0-rc3-v8+ #13     [    0.386473] Hardware name: Raspberry Pi 4 Model B Rev 1.4 (DT)     [    0.387289] pstate: 20000005 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)     [    0.388308] pc : __flush_work+0x12c/0x138     [    0.388970] lr : __flush_work+0x80/0x138     [    0.389620] sp : ffffffc00aaf3c60     [    0.390139] x29: ffffffc00aaf3d20 x28: ffffffc009c16af0 x27: ffffff80f761df48     [    0.391316] x26: 0000000000000004 x25: 0000000000000003 x24: 0000000000000100     [    0.392493] x23: ffffffffffffffff x22: ffffffc009c16b10 x21: ffffffc009c16b28     [    0.393668] x20: ffffffc009e53861 x19: ffffff80f77fbf40 x18: 00000000d744fcc9     [    0.394842] x17: 000000000000000b x16: 00000000000001c2 x15: ffffffc009e57550     [    0.396016] x14: 0000000000000000 x13: ffffffffffffffff x12: 0000000100000000     [    0.397190] x11: 0000000000000462 x10: ffffff8040258008 x9 : 0000000100000000     [    0.398364] x8 : 0000000000000000 x7 : ffffffc0093c8bf4 x6 : 0000000000000000     [    0.399538] x5 : 0000000000000000 x4 : ffffffc00a976e40 x3 : ffffffc00810444c     [    0.400711] x2 : 0000000000000004 x1 : 0000000000000000 x0 : 0000000000000000     [    0.401886] Call trace:
    [    0.402309]  __flush_work+0x12c/0x138     [    0.402941]  schedule_on_each_cpu+0x228/0x278     [    0.403693]  rcu_tasks_rude_wait_gp+0x130/0x144     [    0.404502]  rcu_tasks_kthread+0x220/0x254     [    0.405264]  kthread+0x174/0x1ac     [    0.405837]  ret_from_fork+0x10/0x20     [    0.406456] irq event stamp: 102     [    0.406966] hardirqs last  enabled at (101): [<ffffffc0093c8468>] _raw_spin_unlock_irq+0x78/0xb4     [    0.408304] hardirqs last disabled at (102): [<ffffffc0093b8270>] el1_dbg+0x24/0x5c     [    0.409410] softirqs last  enabled at (54): [<ffffffc0081b80c8>] local_bh_enable+0xc/0x2c     [    0.410645] softirqs last disabled at (50): [<ffffffc0081b809c>] local_bh_disable+0xc/0x2c     [    0.411890] ---[ end trace 0000000000000000 ]---     [    0.413000] smp: Brought up 1 node, 4 CPUs     [    0.413762] SMP: Total of 4 processors activated.
    [    0.414566] CPU features: detected: 32-bit EL0 Support     [    0.415414] CPU features: detected: 32-bit EL1 Support     [    0.416278] CPU features: detected: CRC32 instructions     [    0.447021] Callback from call_rcu_tasks_rude() invoked.
    [    0.506693] Callback from call_rcu_tasks() invoked.

    This commit therefore fixes this issue by applying a single-CPU     optimization to the RCU Tasks Rude grace-period process.  The key point     here is that the purpose of this RCU flavor is to force a schedule on     each online CPU since some past event.  But the rcu_tasks_rude_wait_gp()     function runs in the context of the RCU Tasks Rude's grace-period kthread,     so there must already have been a context switch on the current CPU since     the call to either synchronize_rcu_tasks_rude() or call_rcu_tasks_rude().
    So if there is only a single CPU online, RCU Tasks Rude's grace-period     kthread does not need to anything at all.

    It turns out that the rcu_tasks_rude_wait_gp() function's call to     schedule_on_each_cpu() causes problems during early boot.  During that     time, there is only one online CPU, namely the boot CPU.  Therefore,     applying this single-CPU optimization fixes early-boot instances of     this problem.

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

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

    rcu-tasks: Fix race in schedule and flush work

    While booting secondary CPUs, cpus_read_[lock/unlock] is not keeping     online cpumask stable. The transient online mask results in below     calltrace.

    [    0.324121] CPU1: Booted secondary processor 0x0000000001 [0x410fd083]     [    0.346652] Detected PIPT I-cache on CPU2     [    0.347212] CPU2: Booted secondary processor 0x0000000002 [0x410fd083]     [    0.377255] Detected PIPT I-cache on CPU3     [    0.377823] CPU3: Booted secondary processor 0x0000000003 [0x410fd083]     [    0.379040] ------------[ cut here ]------------     [    0.383662] WARNING: CPU: 0 PID: 10 at kernel/workqueue.c:3084 __flush_work+0x12c/0x138     [    0.384850] Modules linked in:
    [    0.385403] CPU: 0 PID: 10 Comm: rcu_tasks_rude_ Not tainted 5.17.0-rc3-v8+ #13     [    0.386473] Hardware name: Raspberry Pi 4 Model B Rev 1.4 (DT)     [    0.387289] pstate: 20000005 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)     [    0.388308] pc : __flush_work+0x12c/0x138     [    0.388970] lr : __flush_work+0x80/0x138     [    0.389620] sp : ffffffc00aaf3c60     [    0.390139] x29: ffffffc00aaf3d20 x28: ffffffc009c16af0 x27: ffffff80f761df48     [    0.391316] x26: 0000000000000004 x25: 0000000000000003 x24: 0000000000000100     [    0.392493] x23: ffffffffffffffff x22: ffffffc009c16b10 x21: ffffffc009c16b28     [    0.393668] x20: ffffffc009e53861 x19: ffffff80f77fbf40 x18: 00000000d744fcc9     [    0.394842] x17: 000000000000000b x16: 00000000000001c2 x15: ffffffc009e57550     [    0.396016] x14: 0000000000000000 x13: ffffffffffffffff x12: 0000000100000000     [    0.397190] x11: 0000000000000462 x10: ffffff8040258008 x9 : 0000000100000000     [    0.398364] x8 : 0000000000000000 x7 : ffffffc0093c8bf4 x6 : 0000000000000000     [    0.399538] x5 : 0000000000000000 x4 : ffffffc00a976e40 x3 : ffffffc00810444c     [    0.400711] x2 : 0000000000000004 x1 : 0000000000000000 x0 : 0000000000000000     [    0.401886] Call trace:
    [    0.402309]  __flush_work+0x12c/0x138     [    0.402941]  schedule_on_each_cpu+0x228/0x278     [    0.403693]  rcu_tasks_rude_wait_gp+0x130/0x144     [    0.404502]  rcu_tasks_kthread+0x220/0x254     [    0.405264]  kthread+0x174/0x1ac     [    0.405837]  ret_from_fork+0x10/0x20     [    0.406456] irq event stamp: 102     [    0.406966] hardirqs last  enabled at (101): [<ffffffc0093c8468>] _raw_spin_unlock_irq+0x78/0xb4     [    0.408304] hardirqs last disabled at (102): [<ffffffc0093b8270>] el1_dbg+0x24/0x5c     [    0.409410] softirqs last  enabled at (54): [<ffffffc0081b80c8>] local_bh_enable+0xc/0x2c     [    0.410645] softirqs last disabled at (50): [<ffffffc0081b809c>] local_bh_disable+0xc/0x2c     [    0.411890] ---[ end trace 0000000000000000 ]---     [    0.413000] smp: Brought up 1 node, 4 CPUs     [    0.413762] SMP: Total of 4 processors activated.
    [    0.414566] CPU features: detected: 32-bit EL0 Support     [    0.415414] CPU features: detected: 32-bit EL1 Support     [    0.416278] CPU features: detected: CRC32 instructions     [    0.447021] Callback from call_rcu_tasks_rude() invoked.
    [    0.506693] Callback from call_rcu_tasks() invoked.

    This commit therefore fixes this issue by applying a single-CPU     optimization to the RCU Tasks Rude grace-period process.  The key point     here is that the purpose of this RCU flavor is to force a schedule on     each online CPU since some past event.  But the rcu_tasks_rude_wait_gp()     function runs in the context of the RCU Tasks Rude's grace-period kthread,     so there must already have been a context switch on the current CPU since     the call to either synchronize_rcu_tasks_rude() or call_rcu_tasks_rude().
    So if there is only a single CPU online, RCU Tasks Rude's grace-period     kthread does not need to anything at all.

    It turns out that the rcu_tasks_rude_wait_gp() function's call to     schedule_on_each_cpu() causes problems during early boot.  During that     time, there is only one online CPU, namely the boot CPU.  Therefore,     applying this single-CPU optimization fixes early-boot instances of     this problem.

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 installation on the remote host is affected by the following vulnerabilities :

    usbnet: gl620a: fix endpoint checking in genelink_bind().(CVE-2025-21877)

    ASoC: soc-compress: prevent the potentially use of null pointer(CVE-2021-47650)

    net: gso: fix ownership in __udp_gso_segment(CVE-2025-21926)

    exec: Force single empty string when argv is empty(CVE-2022-49264)

    IB/rdmavt: add lock to call to rvt_error_qp to prevent a race condition(CVE-2022-49089)

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

    erspan: do not assume transport header is always set(CVE-2022-49691)

    tipc: check attribute length for bearer name(CVE-2022-49374)

    qede: confirm skb is allocated before using(CVE-2022-49084)

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

    ice: fix memory leak in aRFS after reset(CVE-2025-21981)

    arm64: compat: Do not treat syscall number as ESR_ELx for a bad syscall(CVE-2022-49520)

    NFSD: prevent underflow in nfssvc_decode_writeargs().(CVE-2022-49280)

    tcp: fix tcp_mtup_probe_success vs wrong snd_cwnd(CVE-2022-49330)

    net: sched: Disallow replacing of child qdisc from one parent to another(CVE-2025-21702)

    net: ipv4: fix route with nexthop object delete warning(CVE-2022-49092)

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

    firewire: fix memory leak for payload of request subaction to IEC 61883-1 FCP region(CVE-2023-52989)

    netfilter: nf_tables: don't skip expired elements during walk(CVE-2023-52924)

    net: openvswitch: fix leak of nested actions(CVE-2022-49086)

    drm/nouveau: prime: fix refcount underflow(CVE-2024-43867)

    net_sched: Prevent creation of classes with TC_H_ROOT(CVE-2025-21971)

    netfilter: nf_tables: memleak flow rule from commit path(CVE-2022-49358)

    rcu-tasks: Fix race in schedule and flush work(CVE-2022-49540)

    netfilter: use get_random_u32 instead of prandom(CVE-2022-49698)

    fbdev: hyperv_fb: Allow graceful removal of framebuffer(CVE-2025-21976)

    nvme-pci: add missing condition check for existence of mapped data(CVE-2024-42276)

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

    ipv6: mcast: add RCU protection to mld_newpack().(CVE-2025-21758)

    ftrace: Clean up hash direct_functions on register failures(CVE-2022-49402)

    clocksource: hyper-v: unexport __init-annotated hv_init_clocksource().(CVE-2022-49726)

    usb: cdc-acm: Check control transfer buffer size before access(CVE-2025-21704)

    PCI: Avoid putting some root ports into D3 on TUXEDO Sirius Gen1(CVE-2025-21831)

    ixgbe: Add locking to prevent panic when setting sriov_numvfs to zero(CVE-2022-49584)

    gpio: Restrict usage of GPIO chip irq members before initialization(CVE-2022-49072)

    i40e: Fix call trace in setup_tx_descriptors(CVE-2022-49725)

    RDMA/hfi1: Fix potential integer multiplication overflow errors(CVE-2022-49404)

    ice: Fix memory corruption in VF driver(CVE-2022-49722)

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

    ACPI: CPPC: Avoid out of bounds access when parsing _CPC data(CVE-2022-49145)

    KVM: SVM: fix panic on out-of-bounds guest IRQ(CVE-2022-49154)

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

    net: fix NULL pointer in skb_segment_list(CVE-2023-52991)

    dlm: fix plock invalid read(CVE-2022-49407)

    netfilter: nf_conncount: Fully initialize struct nf_conncount_tuple in insert_tree().(CVE-2025-21959)

    tee: optee: Fix supplicant wait loop(CVE-2025-21871)

    dm raid: fix accesses beyond end of raid member array(CVE-2022-49674)

    ipv4: use RCU protection in __ip_rt_update_pmtu().(CVE-2025-21766)

    dm array: fix releasing a faulty array block twice in dm_array_cursor_end(CVE-2024-57929)

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

    net: phy: dp83822: Fix null pointer access on DP83825/DP83826 devices(CVE-2023-52984)

    net: xfrm: unexport __init-annotated xfrm4_protocol_init().(CVE-2022-49345)

    tunnels: do not assume mac header is set in skb_tunnel_check_pmtu().(CVE-2022-49663)

    cpufreq: governor: Use kobject release() method to free dbs_data(CVE-2022-49513)

    brcmfmac: pcie: Release firmwares in the brcmf_pcie_setup error path(CVE-2022-49263)

    HID: core: Fix assumption that Resolution Multipliers must be in Logical Collections(CVE-2024-57986)

    ovl: fix UAF in ovl_dentry_update_reval by moving dput() in ovl_link_up(CVE-2025-21887)

    xsk: Fix race at socket teardown(CVE-2022-49215)

    acct: perform last write from workqueue(CVE-2025-21846)

    nvme-pci: fix a NULL pointer dereference in nvme_alloc_admin_tags(CVE-2022-49492)

    drop_monitor: fix incorrect initialization order(CVE-2025-21862)

    udp: Fix a data-race around sysctl_udp_l3mdev_accept.(CVE-2022-49577)

    ip: Fix data-races around sysctl_ip_prot_sock.(CVE-2022-49578)

    ipv4: Fix data-races around sysctl_fib_multipath_hash_policy.(CVE-2022-49579)

    ipv4: Fix a data-race around sysctl_fib_multipath_use_neigh.(CVE-2022-49580)

    tcp: Fix data-races around sysctl_tcp_fastopen_blackhole_timeout.(CVE-2022-49585)

    drm/drm_vma_manager: Add drm_vma_node_allow_once().(CVE-2023-53001)

    x86/microcode/AMD: Fix out-of-bounds on systems with CPU-less NUMA nodes(CVE-2025-21991)

    ipv6: Fix signed integer overflow in __ip6_append_data(CVE-2022-49728)

    ipv6: Fix memleak of nhc_pcpu_rth_output in fib_check_nh_v6_gw().(CVE-2025-22005)

    exec: don't WARN for racy path_noexec check(CVE-2024-50010)

    iscsi_ibft: Fix UBSAN shift-out-of-bounds warning in ibft_attr_show_nic().(CVE-2025-21993)

    RDMA/hns: Fix soft lockup during bt pages loop(CVE-2025-22010)

    tracing: Fix use-after-free in print_graph_function_flags during tracer switching(CVE-2025-22035)

    regulator: check that dummy regulator has been probed before using it(CVE-2025-22008)

    smb: client: Add check for next_buffer in receive_encrypted_standard().(CVE-2025-21844)

    vlan: enforce underlying device type(CVE-2025-21920)

    tcp: Fix data-races around sysctl_tcp_mtu_probing.(CVE-2022-49598)

    mm/swapfile: add cond_resched() in get_swap_pages().(CVE-2023-52932)

    proc: fix UAF in proc_get_inode().(CVE-2025-21999)

    driver core: Fix wait_for_device_probe()  deferred_probe_timeout interaction(CVE-2022-49379)

    NFSD: prevent integer overflow on 32 bit systems(CVE-2022-49279)

    x86/kexec: fix memory leak of elf header buffer(CVE-2022-49546)

    PM: core: keep irq flags in device_pm_check_callbacks().(CVE-2022-49175)

    KVM: SVM: Use kzalloc for sev ioctl interfaces to prevent kernel data leak(CVE-2022-49556)

    tracing: Fix bad hist from corrupting named_triggers list(CVE-2025-21899)

    drivers/base/node.c: fix compaction sysfs file leak(CVE-2022-49442)

    hwpoison, memory_hotplug: lock folio before unmap hwpoisoned folio(CVE-2025-21931)

    s390/cpum_sf: Handle CPU hotplug remove during sampling(CVE-2024-57849)

    bpf, sockmap: Fix double uncharge the mem of sk_msg(CVE-2022-49205)

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

    firmware: dmi-sysfs: Fix memory leak in dmi_sysfs_register_handle(CVE-2022-49370)

    driver core: fix deadlock in __device_attach(CVE-2022-49371)

    RDMA/bnxt_re: Fix the page details for the srq created by kernel consumers(CVE-2025-21885)

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

    net: let net.core.dev_weight always be non-zero(CVE-2025-21806)

    irqchip/gic-v3: Fix GICR_CTLR.RWP polling(CVE-2022-49074)

    x86/speculation: Fill RSB on vmexit for IBRS(CVE-2022-49611)

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

    arm64: asm-bug: Add .align 2 to the end of __BUG_ENTRY(CVE-2024-39488)

    udp: Deal with race between UDP socket address change and rehash(CVE-2024-57974)

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

    ppp: Fix KMSAN uninit-value warning with bpf(CVE-2025-21922)

    KVM: x86: Use __try_cmpxchg_user() to update guest PTE A/D bits(CVE-2022-49562)

    NFS: Avoid writeback threads getting stuck in mempool_alloc().(CVE-2022-49097)

    virtio_net: fix xdp_rxq_info bug after suspend/resume(CVE-2022-49687)

    LSM: general protection fault in legacy_parse_param(CVE-2022-49180)

    net/mlx5: handle errors in mlx5_chains_create_table().(CVE-2025-21975)

    net: mdio: unexport __init-annotated mdio_bus_init().(CVE-2022-49350)

    be2net: Fix buffer overflow in be_get_module_eeprom(CVE-2022-49581)

    l2tp: close all race conditions in l2tp_tunnel_register().(CVE-2023-53020)

    ipvlan: ensure network headers are in skb linear part(CVE-2025-21891)

    serial: 8250: Fix PM usage_count for console handover(CVE-2022-49613)

    scsi: iscsi_tcp: Fix UAF during logout when accessing the shost ipaddress(CVE-2023-52975)

    NFSD: Fix the behavior of READ near OFFSET_MAX(CVE-2022-48827)

    af_netlink: Fix shift out of bounds in group mask calculation(CVE-2022-49197)

    dm thin: make get_first_thin use rcu-safe list first function(CVE-2025-21664)

    netfilter: conntrack: re-fetch conntrack after insertion(CVE-2022-49561)

    mm: memcg: fix NULL pointer in mem_cgroup_track_foreign_dirty_slowpath().(CVE-2023-52939)

    tick/nohz: unexport __init-annotated tick_nohz_full_setup().(CVE-2022-49675)

    ipv6: use RCU protection in ip6_default_advmss().(CVE-2025-21765)

    virtio_console: eliminate anonymous module_init  module_exit(CVE-2022-49100)

    net: tun: unlink NAPI from device on destruction(CVE-2022-49672)

    Drivers: hv: vmbus: Fix potential crash on module unload(CVE-2022-49098)

    net/tls: fix slab-out-of-bounds bug in decrypt_internal(CVE-2022-49094)

    keys: Fix UAF in key_put().(CVE-2025-21893)

    bpf, sockmap: Check for any of tcp_bpf_prots when cloning a listener(CVE-2023-52986)

    RDMA/hfi1: Prevent panic when SDMA is disabled(CVE-2022-49429)

    xhci: Handle TD clearing for multiple streams case(CVE-2024-40927)

    ipmr: do not call mr_mfc_uses_dev() for unres entries(CVE-2025-21719)

    scsi: hisi_sas: Add cond_resched() for no forced preemption model(CVE-2024-56589)

    veth: Ensure eth header is in skb's linear part(CVE-2022-49066)

    tracing: Fix potential double free in create_var_ref().(CVE-2022-49410)

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

    scsi: iscsi_tcp: Fix UAF during login when accessing the shost ipaddress(CVE-2023-52974)

    net_sched: sch_sfq: don't allow 1 packet limit(CVE-2024-57996)

    vc_screen: move load of struct vc_data pointer in vcs_read() to avoid UAF(CVE-2023-52973)

    dm mirror log: round up region bitmap size to BITS_PER_LONG(CVE-2022-49710)

    x86/xen: don't do PV iret hypercall through hypercall page(CVE-2024-53241)

    bpf, sockmap: Fix more uncharged while msg has more_data(CVE-2022-49204)

    mm/khugepaged: fix -anon_vma race(CVE-2023-52935)

    dm integrity: fix memory corruption when tag_size is less than digest size(CVE-2022-49044)

    scsi: lpfc: Fix resource leak in lpfc_sli4_send_seq_to_ulp().(CVE-2022-49521)

    bpf: Fix request_sock leak in sk lookup helpers(CVE-2022-49697)

    mm/migrate_device: don't add folio to be freed to LRU in migrate_device_finalize().(CVE-2025-21861)

    efi: Don't map the entire mokvar table to determine its size(CVE-2025-21872)

    net: asix: add proper error handling of usb read errors(CVE-2022-49226)

    HID: intel-ish-hid: Fix use-after-free issue in ishtp_hid_remove().(CVE-2025-21928)

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

    bpf: Skip invalid kfunc call in backtrack_insn(CVE-2023-52928)

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

    igb: Fix potential invalid memory access in igb_init_module().(CVE-2024-52332)

    ftrace: Avoid potential division by zero in function_stat_show().(CVE-2025-21898)

    efi: fix potential NULL deref in efi_mem_reserve_persistent(CVE-2023-52976)

    uprobes: Reject the shared zeropage in uprobe_write_opcode().(CVE-2025-21881)

    bnxt: Do not read past the end of test names(CVE-2023-53010)

    trace_events_hist: add check for return value of 'create_hist_field'(CVE-2023-53005)

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

    Squashfs: fix handling and sanity checking of xattr_ids count(CVE-2023-52933)

    tcp: Fix a data-race around sysctl_tcp_probe_threshold.(CVE-2022-49595)

    tcp: Fix data-races around sysctl_tcp_min_snd_mss.(CVE-2022-49596)

    tcp: Fix data-races around sysctl_tcp_base_mss.(CVE-2022-49597)

    tcp: Fix data-races around sysctl_tcp_l3mdev_accept.(CVE-2022-49599)

    hrtimers: Force migrate away hrtimers queued after CPUHP_AP_HRTIMERS_DYING(CVE-2025-21816)

    RDMA/hfi1: Prevent use of lock before it is initialized(CVE-2022-49433)

    cifs: fix potential memory leaks in session setup(CVE-2023-53008)

    ovl: Use 'buf' flexible array for memcpy() destination(CVE-2022-49743)

    openvswitch: fix lockup on tx to unregistering netdev with carrier(CVE-2025-21681)

    net: hns3: add vlan list lock to protect vlan list(CVE-2022-49182)

    driver: base: fix UAF when driver_attach failed(CVE-2022-49385)

    ubi: ubi_create_volume: Fix use-after-free when volume creation failed(CVE-2022-49388)

    rtc: pcf85063: fix potential OOB write in PCF85063 NVMEM read(CVE-2024-58069)

    lz4: fix LZ4_decompress_safe_partial read out of bound(CVE-2022-49078)

    um: Fix out-of-bounds read in LDT setup(CVE-2022-49395)

    KVM: Explicitly verify target vCPU is online in kvm_get_vcpu().(CVE-2024-58083)

    ipv6: mcast: extend RCU protection in igmp6_send().(CVE-2025-21759)

    vsock: Keep the binding until socket destruction(CVE-2025-21756)

    pps: Fix a use-after-free(CVE-2024-57979)

    padata: fix UAF in padata_reorder(CVE-2025-21727)

    netfilter: nf_tables: avoid skb access on nf_stolen(CVE-2022-49622)

    srcu: Tighten cleanup_srcu_struct() GP checks(CVE-2022-49651)

    openvswitch: use RCU protection in ovs_vport_cmd_fill_info().(CVE-2025-21761)

    cgroup: Use separate src/dst nodes when preloading css_sets for migration(CVE-2022-49647)

    ice: arfs: fix use-after-free when freeing @rx_cpu_rmap(CVE-2022-49063)

    macsec: fix UAF bug for real_dev(CVE-2022-49390)

    ndisc: extend RCU protection in ndisc_send_skb().(CVE-2025-21760)

    nfsd: release svc_expkey(CVE-2024-53216)

    nfsd: make sure exp active before svc_export_show(CVE-2024-56558)

    net: sched: Disallow replacing of child qdisc from one parent to another(CVE-2025-21700)

    neighbour: use RCU protection in __neigh_notify().(CVE-2025-21763)

    nfsd: clear acl_access/acl_default after releasing them(CVE-2025-21796)

    ndisc: use RCU protection in ndisc_alloc_skb().(CVE-2025-21764)

    arp: use RCU protection in arp_xmit().(CVE-2025-21762)

    iommu/arm-smmu-v3: check return value after calling platform_get_resource().(CVE-2022-49319)

    memcg: fix soft lockup in the OOM process(CVE-2024-57977)

    rdma/cxgb4: Prevent potential integer overflow on 32bit(CVE-2024-57973)

    scsi: hisi_sas: Free irq vectors in order for v3 HW(CVE-2022-49118)

    drm/plane: Move range check for format_count earlier(CVE-2021-47659)

    USB: hub: Ignore non-compliant devices with too many configs or interfaces(CVE-2025-21776)

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

    linux/dim: Fix divide by 0 in RDMA DIM(CVE-2022-49670)

    HID: multitouch: Add NULL check in mt_input_configured(CVE-2024-58020)

    nfp: bpf: Add check for nfp_app_ctrl_msg_alloc().(CVE-2025-21848)

    KVM: x86: Reject Hyper-V's SEND_IPI hypercalls if local APIC isn't in-kernel(CVE-2025-21779)

    usb: xhci: Fix NULL pointer dereference on certain command aborts(CVE-2024-57981)

    ceph: fix memory leak in ceph_readdir when note_last_dentry returns error(CVE-2022-49107)

    NFSv4.2: fix reference count leaks in _nfs42_proc_copy_notify().(CVE-2022-49103)

    io_uring: fix memory leak of uid in files registration(CVE-2022-49144)

    hwrng: cavium - fix NULL but dereferenced coccicheck error(CVE-2022-49177)

    mlxsw: spectrum: Guard against invalid local ports(CVE-2022-49134)

    iommu/arm-smmu: fix possible null-ptr-deref in arm_smmu_device_probe().(CVE-2022-49323)

    drm/virtio: fix NULL pointer dereference in virtio_gpu_conn_get_modes(CVE-2022-49532)

    scsi: qla2xxx: Suppress a kernel complaint in qla_create_qpair().(CVE-2022-49155)

    NFSv4: Don't hold the layoutget locks across multiple RPC calls(CVE-2022-49316)

    kernel/resource: fix kfree() of bootmem memory again(CVE-2022-49190)

    vrf: use RCU protection in l3mdev_l3_out().(CVE-2025-21791)

    tcp: Fix a data-race around sysctl_tcp_ecn_fallback.(CVE-2022-49630)

    i2c: dev: check return value when calling dev_set_name().(CVE-2022-49046)

    list: fix a data-race around ep-rdllist(CVE-2022-49443)

    perf/core: Fix data race between perf_event_set_output() and perf_mmap_close()(CVE-2022-49607)

    drm/amd/display: Fix memory leak(CVE-2022-49135)

    media: uvcvideo: Fix double free in error path(CVE-2024-57980)

    io_uring: prevent opcode speculation(CVE-2025-21863)

    geneve: Fix use-after-free in geneve_find_dev().(CVE-2025-21858)

    arm64: cacheinfo: Avoid out-of-bounds write to cacheinfo array(CVE-2025-21785)

    scsi: lpfc: Fix SCSI I/O completion and abort handler deadlock(CVE-2022-49536)

    KVM: VMX: Prevent RSB underflow before vmenter(CVE-2022-49610)

    tpm: Change to kvalloc() in eventlog/acpi.c(CVE-2024-58005)

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.

  - rcu-tasks: Fix race in schedule and flush work While booting secondary CPUs, cpus_read_[lock/unlock] is     not keeping online cpumask stable. The transient online mask results in below calltrace. [ 0.324121] CPU1:
    Booted secondary processor 0x0000000001 [0x410fd083] [ 0.346652] Detected PIPT I-cache on CPU2 [ 0.347212]     CPU2: Booted secondary processor 0x0000000002 [0x410fd083] [ 0.377255] Detected PIPT I-cache on CPU3 [     0.377823] CPU3: Booted secondary processor 0x0000000003 [0x410fd083] [ 0.379040] ------------[ cut here     ]------------ [ 0.383662] WARNING: CPU: 0 PID: 10 at kernel/workqueue.c:3084 __flush_work+0x12c/0x138 [     0.384850] Modules linked in: [ 0.385403] CPU: 0 PID: 10 Comm: rcu_tasks_rude_ Not tainted 5.17.0-rc3-v8+     #13 [ 0.386473] Hardware name: Raspberry Pi 4 Model B Rev 1.4 (DT) [ 0.387289] pstate: 20000005 (nzCv daif
    -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 0.388308] pc : __flush_work+0x12c/0x138 [ 0.388970] lr :
    __flush_work+0x80/0x138 [ 0.389620] sp : ffffffc00aaf3c60 [ 0.390139] x29: ffffffc00aaf3d20 x28:
    ffffffc009c16af0 x27: ffffff80f761df48 [ 0.391316] x26: 0000000000000004 x25: 0000000000000003 x24:
    0000000000000100 [ 0.392493] x23: ffffffffffffffff x22: ffffffc009c16b10 x21: ffffffc009c16b28 [ 0.393668]     x20: ffffffc009e53861 x19: ffffff80f77fbf40 x18: 00000000d744fcc9 [ 0.394842] x17: 000000000000000b x16:
    00000000000001c2 x15: ffffffc009e57550 [ 0.396016] x14: 0000000000000000 x13: ffffffffffffffff x12:
    0000000100000000 [ 0.397190] x11: 0000000000000462 x10: ffffff8040258008 x9 : 0000000100000000 [ 0.398364]     x8 : 0000000000000000 x7 : ffffffc0093c8bf4 x6 : 0000000000000000 [ 0.399538] x5 : 0000000000000000 x4 :
    ffffffc00a976e40 x3 : ffffffc00810444c [ 0.400711] x2 : 0000000000000004 x1 : 0000000000000000 x0 :
    0000000000000000 [ 0.401886] Call trace: [ 0.402309] __flush_work+0x12c/0x138 [ 0.402941]     schedule_on_each_cpu+0x228/0x278 [ 0.403693] rcu_tasks_rude_wait_gp+0x130/0x144 [ 0.404502]     rcu_tasks_kthread+0x220/0x254 [ 0.405264] kthread+0x174/0x1ac [ 0.405837] ret_from_fork+0x10/0x20 [     0.406456] irq event stamp: 102 [ 0.406966] hardirqs last enabled at (101): [<ffffffc0093c8468>]
    _raw_spin_unlock_irq+0x78/0xb4 [ 0.408304] hardirqs last disabled at (102): [<ffffffc0093b8270>]     el1_dbg+0x24/0x5c [ 0.409410] softirqs last enabled at (54): [<ffffffc0081b80c8>] local_bh_enable+0xc/0x2c     [ 0.410645] softirqs last disabled at (50): [<ffffffc0081b809c>] local_bh_disable+0xc/0x2c [ 0.411890]
    ---[ end trace 0000000000000000 ]--- [ 0.413000] smp: Brought up 1 node, 4 CPUs [ 0.413762] SMP: Total of     4 processors activated. [ 0.414566] CPU features: detected: 32-bit EL0 Support [ 0.415414] CPU features:
    detected: 32-bit EL1 Support [ 0.416278] CPU features: detected: CRC32 instructions [ 0.447021] Callback     from call_rcu_tasks_rude() invoked. [ 0.506693] Callback from call_rcu_tasks() invoked. This commit     therefore fixes this issue by applying a single-CPU optimization to the RCU Tasks Rude grace-period     process. The key point here is that the purpose of this RCU flavor is to force a schedule on each online     CPU since some past event. But the rcu_tasks_rude_wait_gp() function runs in the context of the RCU Tasks     Rude's grace-period kthread, so there must already have been a context switch on the current CPU since the     call to either synchronize_rcu_tasks_rude() or call_rcu_tasks_rude(). So if there is only a single CPU     online, RCU Tasks Rude's grace-period kthread does not need to anything at all. It turns out that the     rcu_tasks_rude_wait_gp() function's call to schedule_on_each_cpu() causes problems during early boot.
    During that time, there is only one online CPU, namely the boot CPU. Therefore, applying this single-CPU     optimization fixes early-boot instances of this problem. (CVE-2022-49540)

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

The version of kernel installed on the remote host is prior to 5.15.50-23.125. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.15-2022-002 advisory.

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

    drm/plane: Move range check for format_count earlier (CVE-2021-47659)

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

    fs/ntfs3: Fix some memory leaks in an error handling path of 'log_replay()' (CVE-2021-47660)

    A use-after-free flaw was found in fs/ext4/namei.c:dx_insert_block() in the Linux kernel's filesystem sub-     component. This flaw allows a local attacker with a user privilege to cause a denial of service.
    (CVE-2022-1184)

    With shadow paging enabled, the INVPCID instruction results in a call to kvm_mmu_invpcid_gva. If INVPCID     is executed with CR0.PG=0, the invlpg callback is not set and the result is a NULL pointer dereference.
    (CVE-2022-1789)

    A NULL pointer dereference flaw was found in the Linux kernel's KVM module, which can lead to a denial of     service in the x86_emulate_insn in arch/x86/kvm/emulate.c. This flaw occurs while executing an illegal     instruction in guest in the Intel CPU. (CVE-2022-1852)

    A use-after-free vulnerability was found in the Linux kernel's Netfilter subsystem in     net/netfilter/nf_tables_api.c. This flaw allows a local attacker with user access to cause a privilege     escalation issue. (CVE-2022-1966)

    A use-after-free flaw was found in the Linux kernel in log_replay in fs/ntfs3/fslog.c in the NTFS journal.
    This flaw allows a local attacker to crash the system and leads to a kernel information leak problem.
    (CVE-2022-1973)

    A vulnerability was found in the Linux kernel's nft_set_desc_concat_parse() function .This flaw allows an     attacker to trigger a buffer overflow via nft_set_desc_concat_parse() , causing a denial of service and     possibly to run code. (CVE-2022-2078)

    A flaw was found in hw. Incomplete cleanup of multi-core shared buffers for some Intel(r) Processors may     allow an authenticated user to enable information disclosure via local access. (CVE-2022-21123)

    A flaw was found in hw. Incomplete cleanup of microarchitectural fill buffers on some Intel(r) Processors     may allow an authenticated user to enable information disclosure via local access. (CVE-2022-21125)

    A flaw was found in hw. Incomplete cleanup in specific special register write operations for some     Intel Processors may allow an authenticated user to enable information disclosure via local access.
    (CVE-2022-21166)

    net/netfilter/nf_tables_api.c in the Linux kernel through 5.18.1 allows a local user (able to create     user/net namespaces) to escalate privileges to root because an incorrect NFT_STATEFUL_EXPR check leads to     a use-after-free. (CVE-2022-32250)

    An issue was discovered in the Linux kernel through 5.18.3 on powerpc 32-bit platforms. There is a buffer     overflow in ptrace PEEKUSER and POKEUSER (aka PEEKUSR and POKEUSR) when accessing floating point     registers. (CVE-2022-32981)

    rpmsg_virtio_add_ctrl_dev in drivers/rpmsg/virtio_rpmsg_bus.c in the Linux kernel before 5.18.4 has a     double free. (CVE-2022-34494)

    rpmsg_probe in drivers/rpmsg/virtio_rpmsg_bus.c in the Linux kernel before 5.18.4 has a double free.
    (CVE-2022-34495)

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

    nbd: call genl_unregister_family() first in nbd_cleanup() (CVE-2022-49295)

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

    nbd: fix io hung while disconnecting device (CVE-2022-49297)

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

    nbd: fix race between nbd_alloc_config() and module removal (CVE-2022-49300)

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

    NFSv4: Don't hold the layoutget locks across multiple RPC calls (CVE-2022-49316)

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

    iommu/arm-smmu-v3: check return value after calling platform_get_resource() (CVE-2022-49319)

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

    tracing: Fix sleeping function called from invalid context on RT kernel (CVE-2022-49322)

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

    iommu/arm-smmu: fix possible null-ptr-deref in arm_smmu_device_probe() (CVE-2022-49323)

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

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

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

    bcache: avoid journal no-space deadlock by reserving 1 journal bucket (CVE-2022-49327)

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

    tcp: fix tcp_mtup_probe_success vs wrong snd_cwnd (CVE-2022-49330)

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

    net: ipv6: unexport __init-annotated seg6_hmac_init() (CVE-2022-49339)

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

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

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

    bpf, arm64: Clear prog->jited_len along prog->jited (CVE-2022-49341)

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

    ext4: avoid cycles in directory h-tree (CVE-2022-49343)

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

    af_unix: Fix a data-race in unix_dgram_peer_wake_me(). (CVE-2022-49344)

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

    net: xfrm: unexport __init-annotated xfrm4_protocol_init() (CVE-2022-49345)

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

    ext4: fix bug_on in ext4_writepages (CVE-2022-49347)

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

    ext4: filter out EXT4_FC_REPLAY from on-disk superblock field s_state (CVE-2022-49348)

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

    ext4: fix use-after-free in ext4_rename_dir_prepare (CVE-2022-49349)

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

    net: mdio: unexport __init-annotated mdio_bus_init() (CVE-2022-49350)

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

    ext4: fix warning in ext4_handle_inode_extension (CVE-2022-49352)

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

    netfilter: nf_tables: memleak flow rule from commit path (CVE-2022-49358)

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

    firmware: dmi-sysfs: Fix memory leak in dmi_sysfs_register_handle (CVE-2022-49370)

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

    driver core: fix deadlock in __device_attach (CVE-2022-49371)

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

    tcp: tcp_rtx_synack() can be called from process context (CVE-2022-49372)

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

    tipc: check attribute length for bearer name (CVE-2022-49374)

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

    scsi: sd: Fix potential NULL pointer dereference (CVE-2022-49376)

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

    blk-mq: don't touch ->tagset in blk_mq_get_sq_hctx (CVE-2022-49377)

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

    driver core: Fix wait_for_device_probe() & deferred_probe_timeout interaction (CVE-2022-49379)

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

    md: fix double free of io_acct_set bioset (CVE-2022-49384)

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

    driver: base: fix UAF when driver_attach failed (CVE-2022-49385)

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

    usb: usbip: fix a refcount leak in stub_probe() (CVE-2022-49389)

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

    md: Don't set mddev private to NULL in raid0 pers->free (CVE-2022-49400)

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

    ftrace: Clean up hash direct_functions on register failures (CVE-2022-49402)

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

    dlm: fix plock invalid read (CVE-2022-49407)

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

    ext4: fix bug_on in __es_tree_search (CVE-2022-49409)

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

    tracing: Fix potential double free in create_var_ref() (CVE-2022-49410)

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

    bfq: Make sure bfqg for which we are queueing requests is online (CVE-2022-49411)

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

    bfq: Avoid merging queues with different parents (CVE-2022-49412)

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

    bfq: Update cgroup information before merging bio (CVE-2022-49413)

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

    ext4: fix race condition between ext4_write and ext4_convert_inline_data (CVE-2022-49414)

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

    iommu/arm-smmu-v3-sva: Fix mm use-after-free (CVE-2022-49426)

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

    PCI: Avoid pci_dev_lock() AB/BA deadlock with sriov_numvfs_store() (CVE-2022-49434)

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

    tty: fix deadlock caused by calling printk() under tty_port->lock (CVE-2022-49441)

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

    drivers/base/node.c: fix compaction sysfs file leak (CVE-2022-49442)

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

    list: fix a data-race around ep->rdllist (CVE-2022-49443)

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

    nvdimm: Fix firmware activation deadlock scenarios (CVE-2022-49446)

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

    rxrpc: Fix listen() setting the bar too high for the prealloc rings (CVE-2022-49450)

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

    thermal/core: Fix memory leak in __thermal_cooling_device_register() (CVE-2022-49468)

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

    nvme-pci: fix a NULL pointer dereference in nvme_alloc_admin_tags (CVE-2022-49492)

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

    net: remove two BUG() from skb_checksum_help() (CVE-2022-49497)

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

    HID: elan: Fix potential double free in elan_input_configured (CVE-2022-49508)

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

    arm64: compat: Do not treat syscall number as ESR_ELx for a bad syscall (CVE-2022-49520)

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

    md/bitmap: don't set sb values if can't pass sanity check (CVE-2022-49526)

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

    rcu-tasks: Fix race in schedule and flush work (CVE-2022-49540)

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

    cifs: fix potential double free during failed mount (CVE-2022-49541)

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

    x86/kexec: fix memory leak of elf header buffer (CVE-2022-49546)

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

    bpf: Fix potential array overflow in bpf_trampoline_get_progs() (CVE-2022-49548)

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

    x86/MCE/AMD: Fix memory leak when threshold_create_bank() fails (CVE-2022-49549)

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

    fs/ntfs3: validate BOOT sectors_per_clusters (CVE-2022-49553)

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

    zsmalloc: fix races between asynchronous zspage free and page migration (CVE-2022-49554)

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

    KVM: SVM: Use kzalloc for sev ioctl interfaces to prevent kernel data leak (CVE-2022-49556)

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

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

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

    KVM: x86: Drop WARNs that assert a triple fault never escapes from L2 (CVE-2022-49559)

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

    exfat: check if cluster num is valid (CVE-2022-49560)

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

    netfilter: conntrack: re-fetch conntrack after insertion (CVE-2022-49561)

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

    zonefs: fix zonefs_iomap_begin() for reads (CVE-2022-49706)

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

    ext4: add reserved GDT blocks check (CVE-2022-49707)

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

    ext4: fix bug_on ext4_mb_use_inode_pa (CVE-2022-49708)

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

    cfi: Fix __cfi_slowpath_diag RCU usage with cpuidle (CVE-2022-49709)

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

    dm mirror log: round up region bitmap size to BITS_PER_LONG (CVE-2022-49710)

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

    irqchip/gic-v3: Fix refcount leak in gic_populate_ppi_partitions (CVE-2022-49715)

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

    irqchip/gic-v3: Fix error handling in gic_populate_ppi_partitions (CVE-2022-49716)

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

    block: Fix handling of offline queues in blk_mq_alloc_request_hctx() (CVE-2022-49720)

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

    arm64: ftrace: consistently handle PLTs. (CVE-2022-49721)

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

    drm/i915/reset: Fix error_state_read ptr + offset use (CVE-2022-49723)

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

    clocksource: hyper-v: unexport __init-annotated hv_init_clocksource() (CVE-2022-49726)

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

    ata: libata-core: fix NULL pointer deref in ata_host_alloc_pinfo() (CVE-2022-49731)

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

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

The version of kernel installed on the remote host is prior to 5.10.126-117.518. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.10-2022-015 advisory.

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

    drm/plane: Move range check for format_count earlier (CVE-2021-47659)

    Due to the small table perturb size, a memory leak flaw was found in the Linux kernel's TCP source port     generation algorithm in the net/ipv4/tcp.c function. This flaw allows an attacker to leak information and     may cause a denial of service. (CVE-2022-1012)

    A use-after-free flaw was found in fs/ext4/namei.c:dx_insert_block() in the Linux kernel's filesystem sub-     component. This flaw allows a local attacker with a user privilege to cause a denial of service.
    (CVE-2022-1184)

    With shadow paging enabled, the INVPCID instruction results in a call to kvm_mmu_invpcid_gva. If INVPCID     is executed with CR0.PG=0, the invlpg callback is not set and the result is a NULL pointer dereference.
    (CVE-2022-1789)

    A NULL pointer dereference flaw was found in the Linux kernel's KVM module, which can lead to a denial of     service in the x86_emulate_insn in arch/x86/kvm/emulate.c. This flaw occurs while executing an illegal     instruction in guest in the Intel CPU. (CVE-2022-1852)

    A use-after-free vulnerability was found in the Linux kernel's Netfilter subsystem in     net/netfilter/nf_tables_api.c. This flaw allows a local attacker with user access to cause a privilege     escalation issue. (CVE-2022-1966)

    A vulnerability was found in the Linux kernel's nft_set_desc_concat_parse() function .This flaw allows an     attacker to trigger a buffer overflow via nft_set_desc_concat_parse() , causing a denial of service and     possibly to run code. (CVE-2022-2078)

    A flaw was found in hw. Incomplete cleanup of multi-core shared buffers for some Intel(r) Processors may     allow an authenticated user to enable information disclosure via local access. (CVE-2022-21123)

    A flaw was found in hw. Incomplete cleanup of microarchitectural fill buffers on some Intel(r) Processors     may allow an authenticated user to enable information disclosure via local access. (CVE-2022-21125)

    A flaw was found in hw. Incomplete cleanup in specific special register write operations for some     Intel Processors may allow an authenticated user to enable information disclosure via local access.
    (CVE-2022-21166)

    KGDB and KDB allow read and write access to kernel memory, and thus should be restricted during lockdown.
    An attacker with access to a serial port could trigger the debugger so it is important that the debugger     respect the lockdown mode when/if it is triggered. CVSS 3.1 Base Score 6.5 (Confidentiality, Integrity and     Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H). (CVE-2022-21499)

    net/netfilter/nf_tables_api.c in the Linux kernel through 5.18.1 allows a local user (able to create     user/net namespaces) to escalate privileges to root because an incorrect NFT_STATEFUL_EXPR check leads to     a use-after-free. (CVE-2022-32250)

    The Linux kernel before 5.17.9 allows TCP servers to identify clients by observing what source ports are     used. (CVE-2022-32296)

    An issue was discovered in the Linux kernel through 5.18.3 on powerpc 32-bit platforms. There is a buffer     overflow in ptrace PEEKUSER and POKEUSER (aka PEEKUSR and POKEUSR) when accessing floating point     registers. (CVE-2022-32981)

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

    drm/radeon: fix a possible null pointer dereference (CVE-2022-48710)

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

    nbd: call genl_unregister_family() first in nbd_cleanup() (CVE-2022-49295)

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

    nbd: fix io hung while disconnecting device (CVE-2022-49297)

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

    nbd: fix race between nbd_alloc_config() and module removal (CVE-2022-49300)

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

    tty: synclink_gt: Fix null-pointer-dereference in slgt_clean() (CVE-2022-49307)

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

    extcon: Modify extcon device to be created after driver data is set (CVE-2022-49308)

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

    NFSv4: Don't hold the layoutget locks across multiple RPC calls (CVE-2022-49316)

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

    iommu/arm-smmu-v3: check return value after calling platform_get_resource() (CVE-2022-49319)

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

    xprtrdma: treat all calls not a bcall when bc_serv is NULL (CVE-2022-49321)

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

    tracing: Fix sleeping function called from invalid context on RT kernel (CVE-2022-49322)

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

    iommu/arm-smmu: fix possible null-ptr-deref in arm_smmu_device_probe() (CVE-2022-49323)

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

    bcache: avoid journal no-space deadlock by reserving 1 journal bucket (CVE-2022-49327)

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

    tcp: fix tcp_mtup_probe_success vs wrong snd_cwnd (CVE-2022-49330)

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

    net: ipv6: unexport __init-annotated seg6_hmac_init() (CVE-2022-49339)

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

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

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

    bpf, arm64: Clear prog->jited_len along prog->jited (CVE-2022-49341)

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

    ext4: avoid cycles in directory h-tree (CVE-2022-49343)

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

    af_unix: Fix a data-race in unix_dgram_peer_wake_me(). (CVE-2022-49344)

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

    net: xfrm: unexport __init-annotated xfrm4_protocol_init() (CVE-2022-49345)

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

    ext4: fix bug_on in ext4_writepages (CVE-2022-49347)

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

    ext4: filter out EXT4_FC_REPLAY from on-disk superblock field s_state (CVE-2022-49348)

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

    ext4: fix use-after-free in ext4_rename_dir_prepare (CVE-2022-49349)

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

    net: mdio: unexport __init-annotated mdio_bus_init() (CVE-2022-49350)

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

    ext4: fix warning in ext4_handle_inode_extension (CVE-2022-49352)

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

    netfilter: nf_tables: memleak flow rule from commit path (CVE-2022-49358)

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

    firmware: dmi-sysfs: Fix memory leak in dmi_sysfs_register_handle (CVE-2022-49370)

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

    driver core: fix deadlock in __device_attach (CVE-2022-49371)

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

    tcp: tcp_rtx_synack() can be called from process context (CVE-2022-49372)

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

    tipc: check attribute length for bearer name (CVE-2022-49374)

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

    scsi: sd: Fix potential NULL pointer dereference (CVE-2022-49376)

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

    driver core: Fix wait_for_device_probe() & deferred_probe_timeout interaction (CVE-2022-49379)

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

    driver: base: fix UAF when driver_attach failed (CVE-2022-49385)

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

    ubi: ubi_create_volume: Fix use-after-free when volume creation failed (CVE-2022-49388)

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

    usb: usbip: fix a refcount leak in stub_probe() (CVE-2022-49389)

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

    ftrace: Clean up hash direct_functions on register failures (CVE-2022-49402)

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

    dlm: fix plock invalid read (CVE-2022-49407)

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

    ext4: fix bug_on in __es_tree_search (CVE-2022-49409)

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

    tracing: Fix potential double free in create_var_ref() (CVE-2022-49410)

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

    bfq: Make sure bfqg for which we are queueing requests is online (CVE-2022-49411)

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

    bfq: Update cgroup information before merging bio (CVE-2022-49413)

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

    PCI: Avoid pci_dev_lock() AB/BA deadlock with sriov_numvfs_store() (CVE-2022-49434)

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

    tty: fix deadlock caused by calling printk() under tty_port->lock (CVE-2022-49441)

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

    drivers/base/node.c: fix compaction sysfs file leak (CVE-2022-49442)

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

    nvdimm: Fix firmware activation deadlock scenarios (CVE-2022-49446)

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

    rxrpc: Fix listen() setting the bar too high for the prealloc rings (CVE-2022-49450)

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

    thermal/core: Fix memory leak in __thermal_cooling_device_register() (CVE-2022-49468)

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

    net: phy: micrel: Allow probing without .driver_data (CVE-2022-49472)

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

    nvme-pci: fix a NULL pointer dereference in nvme_alloc_admin_tags (CVE-2022-49492)

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

    net: remove two BUG() from skb_checksum_help() (CVE-2022-49497)

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

    ALSA: pcm: Check for null pointer of pointer substream before dereferencing it (CVE-2022-49498)

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

    HID: elan: Fix potential double free in elan_input_configured (CVE-2022-49508)

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

    arm64: compat: Do not treat syscall number as ESR_ELx for a bad syscall (CVE-2022-49520)

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

    scsi: lpfc: Fix resource leak in lpfc_sli4_send_seq_to_ulp() (CVE-2022-49521)

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

    md/bitmap: don't set sb values if can't pass sanity check (CVE-2022-49526)

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

    drm/virtio: fix NULL pointer dereference in virtio_gpu_conn_get_modes (CVE-2022-49532)

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

    rcu-tasks: Fix race in schedule and flush work (CVE-2022-49540)

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

    bpf: Fix potential array overflow in bpf_trampoline_get_progs() (CVE-2022-49548)

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

    x86/MCE/AMD: Fix memory leak when threshold_create_bank() fails (CVE-2022-49549)

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

    zsmalloc: fix races between asynchronous zspage free and page migration (CVE-2022-49554)

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

    KVM: SVM: Use kzalloc for sev ioctl interfaces to prevent kernel data leak (CVE-2022-49556)

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

    exfat: check if cluster num is valid (CVE-2022-49560)

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

    netfilter: conntrack: re-fetch conntrack after insertion (CVE-2022-49561)

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

    zonefs: fix zonefs_iomap_begin() for reads (CVE-2022-49706)

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

    ext4: add reserved GDT blocks check (CVE-2022-49707)

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

    ext4: fix bug_on ext4_mb_use_inode_pa (CVE-2022-49708)

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

    dm mirror log: round up region bitmap size to BITS_PER_LONG (CVE-2022-49710)

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

    irqchip/gic-v3: Fix refcount leak in gic_populate_ppi_partitions (CVE-2022-49715)

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

    irqchip/gic-v3: Fix error handling in gic_populate_ppi_partitions (CVE-2022-49716)

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

    block: Fix handling of offline queues in blk_mq_alloc_request_hctx() (CVE-2022-49720)

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

    arm64: ftrace: consistently handle PLTs. (CVE-2022-49721)

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

    drm/i915/reset: Fix error_state_read ptr + offset use (CVE-2022-49723)

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

    i40e: Fix call trace in setup_tx_descriptors (CVE-2022-49725)

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

    clocksource: hyper-v: unexport __init-annotated hv_init_clocksource() (CVE-2022-49726)

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

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

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

    ata: libata-core: fix NULL pointer deref in ata_host_alloc_pinfo() (CVE-2022-49731)

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

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

ID	Name	Product	Family	Severity
273414	Unity Linux 20.1070a Security Update: kernel (UTSA-2025-989050)	Nessus	Unity Linux Local Security Checks	medium
272874	Unity Linux 20.1070e Security Update: kernel (UTSA-2025-989654)	Nessus	Unity Linux Local Security Checks	medium
265114	EulerOS Virtualization 2.13.1 : kernel (EulerOS-SA-2025-2168)	Nessus	Huawei Local Security Checks	high
265107	EulerOS Virtualization 2.13.0 : kernel (EulerOS-SA-2025-2169)	Nessus	Huawei Local Security Checks	high
241018	EulerOS 2.0 SP13 : kernel (EulerOS-SA-2025-1704)	Nessus	Huawei Local Security Checks	high
241015	EulerOS 2.0 SP13 : kernel (EulerOS-SA-2025-1689)	Nessus	Huawei Local Security Checks	high
226649	Linux Distros Unpatched Vulnerability : CVE-2022-49540	Nessus	Misc.	medium
163372	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.15-2022-002 (ALASKERNEL-5.15-2022-002)	Nessus	Amazon Linux Local Security Checks	high
163313	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.10-2022-015 (ALASKERNEL-5.10-2022-015)	Nessus	Amazon Linux Local Security Checks	high

Detections

Analytics

CVE-2022-49540

medium

Tenable Plugins

medium

medium

high

high

high

high

medium

high

high