リモートの Oracle Linux 9 ホストに、ELSA-2025-20480アドバイザリに記載されている複数の脆弱性の影響を受けるパッケージがインストールされています。

    - sunrpcsvc auth処理中にSVC_GARBAGEをauthエラーとして処理Jeff Layton[Orabug: 38178286] {CVE-2025-38089}
    - Zen34クライアントを追加Borislav PetkovAMD[Orabug: 38023239] {CVE-2024-36350} {CVE-2024-36357}
    - x86/processMONITORの前のバッファクリアを移動Kim Phillips[Orabug: 38023239] {CVE-2024-36350} {CVE-2024-36357}
    - 通常のカウンターを追加Borislav PetkovAMD[Orabug:38023239] {CVE-2024-36350} {CVE-2024-36357}
    - KVMSVMTSA CPUIDビットをゲストにアドバタイズBorislav PetkovAMD[Orabug:38023239] {CVE-2024-36350} {CVE-2024-36357}
    - x86/bugs一時的なスケジューラ攻撃の緩和策を追加しますBorislav PetkovAMD[Orabug: 38023239] {CVE-2024-36350} {CVE-2024-36357}
    - x86/bugsMDS 機器の名前をより一般的なものに変更しますBorislav PetkovAMD[Orabug: 38023239] {CVE-2024-36350} {CVE-2024-36357}
    - blockfolio を bio に追加するのを修正Ming Lei[Orabug: 37844657] {CVE-2025-22122}
    - f2fs初期化されていないcursegへのアクセスを回避するための修正Chao Yu[Orabug: 37844644] {CVE-2025-22123}
    - gpiovirtuser領域外書き込みの可能性を修正Markus Burri[Orabug: 38095181] {CVE-2025-38082}
    - net_schedhfsceltree にクラスを追加するリエントラントエンキューに対処しますPedro Tammela 氏[Orabug
    38049363] {CVE-2025-38001}
    - smbclientcifs_fill_direntのメモリ解放後使用Use After Freeを修正Zhaolong Wang[Orabug: 38094970] {CVE-2025-38051}
    - platform/x86dell-wmi-sysmancurrent_password_store()のバッファオーバーフローを回避Vladimir Moskovkin[Orabug: 38095141] {CVE-2025-38077}
    - ALSApcmPCM OSS レイヤーにおけるバッファアクセスの競合を修正Takashi Iwai[Orabug: 38095145] {CVE-2025-38078}
    - can: bcmprocfsコンテンツに対して欠如しているrcu読み取り保護を追加Oliver Hartkopp[Orabug: 38049369] {CVE-2025-38003}
    - can: bcmbcm_op runtime 更新のロックを追加しますOliver Hartkopp 氏[Orabug: 38049374] {CVE-2025-38004}
    - padatareorder_work で refcount を漏洩しませんDominik Grzegorzek 氏[Orabug: 38094842] {CVE-2025-38031}
    - cryptoalgif_hash - hash_acceptの二重解放を修正Ivan Plavdin[Orabug:38095153] {CVE-2025-38079}
    - net/tipctipc_aad_encrypt_doneのslab-use-after-freeを修正Wang Liang[Orabug: 38094978] {CVE-2025-38052}
    - sch_hfschfsc_enqueue()のピークを使用するときqlenのアカウンティングバグを修正Cong Wang[Orabug: 38049357] {CVE-2025-38000}
    - idpfidpf_features_checkのnull-ptr-derefを修正Pavan Kumar Linga[Orabug: 38094982] {CVE-2025-38053}
    - ptpocpサマリー出力関数のsignal/freqカウントを制限Sgi MaimonOrabug: 38094984 {CVE-2025-38054}
    - perf/x86/intelsample_freqでPEBS-via-PTのセグメンテーション違反を修正Adrian Hunter[Orabug: 38094988] {CVE-2025-38055}
    - ASoCSOFIntelhdaモジュールをリロードするときのUAFを修正Tavian Barnes[Orabug: 38094991] {CVE-2025-38056}
    - espintcpskb の漏洩を修正Sabrina Dubroca 氏[Orabug: 38094993] {CVE-2025-38057}
    - __legitimize_mnt()MNT_SYNC_UMOUNTのチェックはmount_lockの下にある必要がありますAl Viro[Orabug: 38095000] {CVE-2025-38058}
    - x86/KconfigCFI_AUTO_DEFAULT を !RUST または Rust >= に依存させます 1.88 Pawel Anikiel[Orabug: 38094847] {CVE-2025-38033}
    - btrfs有効な csum ツリーがない場合、NULL ポインターデリファレンスを回避しますQu Wenruo[Orabug: 38095010] {CVE-2025-38059}
    - btrfsbtrfs__prelim_ref の prelim_ref 引数の順序を修正します Goldwyn Rodrigues 氏 [Orabug
    38094856] {CVE-2025-38034}
    - nvmet-tcpnull sk_state_change を復元しませんAlistair Francisco 氏[Orabug: 38094863] {CVE-2025-38035}
    - vxlanFDBデータの競合に注釈を付けるIdo Schimmel[Orabug:38094879] {CVE-2025-38037}
    - cpufreqamd-pstateset_boostの不要なdriver_lockを削除Dhananjay Ugwekar[Orabug: 38094888] {CVE-2025-38038}
    - drm/amd/displayblock_sequence配列サイズを増やしますJoshua Aberback[Orabug: 38095164] {CVE-2025-38080}
    - bpfcopy_verifier_state()は「loop_entry」フィールドをコピーする必要がありますEduard Zingerman[Orabug: 38095018] {CVE-2025-38060}
    - シリアルmctrl_gpiosync および no_sync API に disable_ms を分割Alexis Lothore 氏[Orabug: 38094901] {CVE-2025-38040}
    - netpktgenpktgen_thread_write() でユーザーが与えられたバッファ外のアクセスを修正Peter Seiderer 氏[Orabug
    38095024] {CVE-2025-38061}
    - genirq/msiiommu_cookie の代わりに msi_desc に IOMMU IOVA を直接保存しますJason Gunthorpe 氏 [Orabug
    38095031] {CVE-2025-38062}
    - dmREQ_PREFLUSH によって引き起こされる無条件の IO スロットルを修正しますJinliang Zheng 氏[Orabug: 38095038] {CVE-2025-38063}
    - firmwarearm_ffaffaデバイスにdma_maskを設定Viresh Kumar[Orabug: 38094925] {CVE-2025-38043}
    - mediacx231xx417用にdevice_capsを設定Hans Verkuil[Orabug: 38094934] {CVE-2025-38044}
    - Orangefsファイルサイズを切り捨てませんMatthew Wilcox[Orabug: 38095056] {CVE-2025-38065}
    - dm cache失敗したデバイスの再開で再試行をブロックすることで、BUG_ON を回避しますMing-Hung Tsai 氏 [Orabug
    38095063] {CVE-2025-38066}
    - cryptolzo - 圧縮バッファオーバーランを修正Herbert Xu[Orabug:38095079] {CVE-2025-38068}
    - PCIendpointpci-epf-testカーネルを oops させる二重解放を修正しますChristian Bruel 氏[Orabug
    38095087] {CVE-2025-38069}
    - wifiiwlwifiデバッグアクション順序を修正Johannes Berg[Orabug: 38094942] {CVE-2025-38045}
    - x86/mmmemblock_phys_alloc_range()からの戻り値をチェックPhilip Redkin[Orabug: 38095101] {CVE-2025-38071}
    - libnvdimm/labelsnd_label_data_init()の除算エラーを修正Robert Richter[Orabug: 38095109] {CVE-2025-38072}
    - spi-rockchip登録の領域外アクセスを修正Luis de Arquer[Orabug: 38095173] {CVE-2025-38081}
    - x86/fredFREDを有効にしてS4を再開する際のシステムハングを修正Xin Li[Orabug: 38094951] {CVE-2025-38047}
    - ブロックset_blocksizeと読み込みパスの間の競合を修正Darrick J. Wong[Orabug: 38095117] {CVE-2025-38073}
    - virtio_ringevent_triggered を KCSAN の競合としてタグ付けすることで、データ競合を修正しますZhongqiu Han 氏 [Orabug
    38094958] {CVE-2025-38048}
    - scsitargetiscsi削除された接続のタイムアウトを修正Dmitry Bogdanov[Orabug: 38095134] {CVE-2025-38075}
    - usbtypecucsidisplayportデッドロックを修正Andrei Kuchnski[Orabug: 37977018] {CVE-2025-37967}
    - BluetoothbtnxpuartFWリリース中のカーネルパニックを修正Neeraj Sanjay Kale[Orabug:37844459] {CVE-2025-22102}
    - iiolightopt3001同時フラグアクセスによるデッドロックを修正Luca Ceresoli[Orabug: 37977026] {CVE-2025-37968}
    - mm/page_alloc受け入れられないメモリ処理の競合状態を修正Kirill A. Shutemov[Orabug: 38094767] {CVE-2025-38008}
    - dmaengineidxdidxd_cleanup() ヘルパーで削除の呼び出しをリファクタリングしますShangai Xue[Orabug: 38094790] {CVE-2025-38014}
    - dmaengineidxdidxd_allocのエラー処理パスにあるメモリリークを修正しますShangai Xue[Orabug: 38094793] {CVE-2025-38015}
    - dmaengineti k3-udma欠落しているロックを追加Ronald Wahl[Orabug: 38094756] {CVE-2025-38005}
    - wifimt76ドライバー削除でnapiを無効化Fedor Pchelkin[Orabug: 38094770] {CVE-2025-38009}
    - phy: tegra: xusbUTMI パッドの電源の状態追跡用のビットマスクを使用しますWayne Chang[Orabug: 38094777] {CVE-2025-38010}
    - drm/amdgpucsa unmap use uninterruptibleロックPhilip Yang[Orabug: 38094779] {CVE-2025-38011}
    - HIDbpfデバイスが破損した場合はディスパッチを中止Rongrong[Orabug: 38094796] {CVE-2025-38016}
    - sched_extbpf_iter_scx_dsq_new()は常にイテレータを初期化する必要がありますTejun Heo[Orabug: 38094786] {CVE-2025-38012}
    - net/tlsalloc_page が失敗した場合のカーネルパニックを修正Pengtao He 氏[Orabug: 38094802] {CVE-2025-38018}
    - mlxswspectrum_routerGRE net デバイスを削除する際の use-after-free を修正しますIdo Schimmel 氏[Orabug
    38094804] {CVE-2025-38019}
    - wifimac80211構造体 cfg80211_scan_request の割り当て後に n_channels を設定しますKees Cook 氏 [Orabug
    38094788] {CVE-2025-38013}
    -registermax20086無効なメモリアクセスを修正Cosmintanislav[Orabug:38094833] {CVE-2025-38027}
    - net/mlx5eアップリンクリ件名プロファイルの MACsec オフロードを無効にしますCarolina Jubran 氏[Orabug: 38094808] {CVE-2025-38020}
    - net_sched->change()中にgso_skbリストもフラッシュCong Wang[Orabug: 37998128] {CVE-2025-37992}
    - RDMA/core「KASAN: ib_register_device の slab-use-after-free」問題を修正しますZhu Yanjun 氏 [Orabug
    38094813] {CVE-2025-38022}
    - nfsロック解除パスでnfs_get_lock_contextの失敗を処理Li Lingfeng[Orabug: 38094818] {CVE-2025-38023}
    - HIDuclogicuclogic_input_configured() に NULL チェックを追加Henry Martin 氏[Orabug: 38094764] {CVE-2025-38007}
    - RDMA/rxerxe_queue_cleanupバグのslab-use-after-freeを修正Zhu Yanjun[Orabug: 38094827] {CVE-2025-38024}
    - arm64bpf権限のないユーザーによって読み込まれたcBPFプログラムのみを軽減James Morse[Orabug: 37977004] {CVE-2025-37963}
    - arm64bpfBHB緩和策をcBPFプログラムのエピローグに追加しますJames Morse[Orabug:37976926] {CVE-2025-37948}
    - usbtypecucsidisplayportNULLポインターアクセスを修正Andrei Kuchnski[Orabug: 38015126] {CVE-2025-37994}
    - modulekobject_put()がモジュールタイプkobjectsに対して安全であることを保証しますDmitry Antipov[Orabug: 38015131] {CVE-2025-37995}
    - memblockmemblock_double_array() で使用する前に割り当てられたメモリを受け入れますTom Lendacky 氏 [Orabug
    37976994] {CVE-2025-37960}
    - xenbuskrefを使用してreqの有効期間を追跡Jason Andryyuk[Orabug:37976934] {CVE-2025-37949}
    - smbclientリースブレークとのopen_cached_dirでの競合を回避Paul Aurich[Orabug: 37976959] {CVE-2025-37954}
    - drm/amd/displaydmlヘルパーの無効なコンテキストエラーを修正Roman Li[Orabug: 37977185] {CVE-2025-37965}
    - drm/v3dリセットがスキップされた場合、ジョブを保留リストに追加Maira Canal[Orabug: 37976942] {CVE-2025-37951}
    - iioimust_lsm6dsxst_lsm6dsx_read_tagged_fifo での潜在的なロックアップを修正しますSilvano Seva 氏[Orabug
    37977031] {CVE-2025-37969}
    - iioimust_lsm6dsxst_lsm6dsx_read_fifoの潜在的なロックアップを修正Silvano Seva[Orabug: 37977037] {CVE-2025-37970}
    - KVMSVMSHUTDOWN 傍受で SMM モードを強制的に放置しますMikhail Lobanov 氏[Orabug: 37976977] {CVE-2025-37957}
    - mm/huge_memory無効なpmd移行エントリのデリファレンスを修正Gavin Guo[Orabug: 37976982] {CVE-2025-37958}
    - x86/mmTLBフラッシュが不注意でスキップされる可能性のあるウィンドウを排除Dave HansenOrabug: 37977013{CVE-2025-37964}
    - stagingbcm2835-camerav4l2_devのdevを初期化Dave Stevenson[Orabug:37977042] {CVE-2025-37971}
    - 入力mtk-pmic-keys - 潜在的なNULLポインターデリファレンスを修正Gary Bisson[Orabug:37977044] {CVE-2025-37972}
    - bpfbpf_redirect_peerでパケットをスクラブPaul Chaignon[Orabug:37976990] {CVE-2025-37959}
    - netfilteripsetハッシュ型のリージョンロックを修正しますJozsef Kadlecsik[Orabug: 38015141] {CVE-2025-37997}
    - ipvsdo_output_route4におけるsaddrのuninit-valueを修正Julian Anastasov[Orabug:37976996] {CVE-2025-37961}
    - canm_canm_can_class_allocate_dev()デバイスプローブのスピンロックを初期化しますAntonios Salios 氏 [Orabug
    38015123] {CVE-2025-37993}
    - virtio-netvirtnet_xsk_pool_enable()のエラーでxsk_buffsを解放Jakub Kicinski[Orabug: 37976969] {CVE-2025-37955}
    - sch_htbhtb_deactivate()を冪等にしますCong Wang[Orabug:37977176] {CVE-2025-37953}
    - ksmbdparse_lease_state()のメモリリークを修正しますZhaolong Wang[Orabug: 37977180] {CVE-2025-37962}
    - openvswitchoutput_userspace() における安全でない属性解析を修正Eelco Chaudron 氏[Orabug: 38015148] {CVE-2025-37998}
    - ksmbd__close_file_table_idsのUAFを修正Sean Heelan[Orabug: 37976951] {CVE-2025-37952}
    - ksmbd*posを検証することで領域外ストリーム書き込みを防止Norbert Szetei[Orabug: 37976923] {CVE-2025-37947}
    - ksmbd空の文字列での名前変更を防ぎますNamjae Jeon[Orabug: 37976972] {CVE-2025-37956}
    - s390/pciPF に子 VF がある場合の disable_slot() での pci_dev_put() の重複を修正しますNiklas Schnelle 氏[Orabug
    37976920] {CVE-2025-37946}
    - wificfg80211マルチリンク要素のデフラグ中の領域外アクセスを修正Veerendranath Jakkam[Orabug: 37977046] {CVE-2025-37973}
    - s390/pcizpci_create_device()のエラーリターンの欠落しているチェックを修正Niklas Schnelle[Orabug:37977050] {CVE-2025-37974}
    - fs/erofs/fileiobio_add_folio() の後に erofs_onlinefolio_split() を呼び出しますMax Kellermann 氏 [Orabug
    38015155] {CVE-2025-37999}
    - mlxbf-bootctlsecure_boot_fuse_state_show() で sysfs_emit_at() を使用しますDavid Thompson 氏[Orabug
    37964051,38037120] {CVE-2025-37866}

Tenable は、前述の記述ブロックを Oracle Linux セキュリティアドバイザリから直接抽出しています。

Nessus はこれらの問題をテストしておらず、代わりにアプリケーションが自己報告するバージョン番号にのみ依存していることに注意してください。

The remote AlmaLinux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the ALSA-2025:7423 advisory.

    * kernel: io_uring/sqpoll: zero sqd->thread on tctx errors (CVE-2025-21633)
      * kernel: soc: qcom: socinfo: Avoid out of bounds read of serial number (CVE-2024-58007)
      * kernel: tpm: Change to kvalloc() in eventlog/acpi.c (CVE-2024-58005)
      * kernel: rtc: pcf85063: fix potential OOB write in PCF85063 NVMEM read (CVE-2024-58069)
      * kernel: nvme-tcp: fix potential memory corruption in nvme_tcp_recv_pdu() (CVE-2025-21927)
      * kernel: iscsi_ibft: Fix UBSAN shift-out-of-bounds warning in ibft_attr_show_nic() (CVE-2025-21993)

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

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

The remote CentOS Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the kernel-5.14.0-578.el9 build changelog.

  - In the Linux kernel, the following vulnerability has been resolved: soc: qcom: socinfo: Avoid out of     bounds read of serial number On MSM8916 devices, the serial number exposed in sysfs is constant and does     not change across individual devices. It's always: db410c:/sys/devices/soc0$ cat serial_number 2644893864     The firmware used on MSM8916 exposes SOCINFO_VERSION(0, 8), which does not have support for the serial_num     field in the socinfo struct. There is an existing check to avoid exposing the serial number in that case,     but it's not correct: When checking the item_size returned by SMEM, we need to make sure the *end* of the     serial_num is within bounds, instead of comparing with the *start* offset. The serial_number currently     exposed on MSM8916 devices is just an out of bounds read of whatever comes after the socinfo struct in     SMEM. Fix this by changing offsetof() to offsetofend(), so that the size of the field is also taken into     account. (CVE-2024-58007)

  - In the Linux kernel, the following vulnerability has been resolved: padata: avoid UAF for reorder_work     Although the previous patch can avoid ps and ps UAF for _do_serial, it can not avoid potential UAF issue     for reorder_work. This issue can happen just as below: crypto_request crypto_request crypto_del_alg     padata_do_serial ... padata_reorder // processes all remaining // requests then breaks while (1) { if     (!padata) break; ... } padata_do_serial // new request added list_add // sees the new request     queue_work(reorder_work) padata_reorder queue_work_on(squeue->work) ... <kworker context>     padata_serial_worker // completes new request, // no more outstanding // requests crypto_del_alg // free     pd <kworker context> invoke_padata_reorder // UAF of pd To avoid UAF for 'reorder_work', get 'pd' ref     before put 'reorder_work' into the 'serial_wq' and put 'pd' ref until the 'serial_wq' finish.
    (CVE-2025-21726)

  - In the Linux kernel, the following vulnerability has been resolved: nfsd: clear acl_access/acl_default     after releasing them If getting acl_default fails, acl_access and acl_default will be released     simultaneously. However, acl_access will still retain a pointer pointing to the released posix_acl, which     will trigger a WARNING in nfs3svc_release_getacl like this: ------------[ cut here ]------------     refcount_t: underflow; use-after-free. WARNING: CPU: 26 PID: 3199 at lib/refcount.c:28     refcount_warn_saturate+0xb5/0x170 Modules linked in: CPU: 26 UID: 0 PID: 3199 Comm: nfsd Not tainted     6.12.0-rc6-00079-g04ae226af01f-dirty #8 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS     1.16.1-2.fc37 04/01/2014 RIP: 0010:refcount_warn_saturate+0xb5/0x170 Code: cc cc 0f b6 1d b3 20 a5 03 80     fb 01 0f 87 65 48 d8 00 83 e3 01 75 e4 48 c7 c7 c0 3b 9b 85 c6 05 97 20 a5 03 01 e8 fb 3e 30 ff <0f> 0b eb     cd 0f b6 1d 8a3 RSP: 0018:ffffc90008637cd8 EFLAGS: 00010282 RAX: 0000000000000000 RBX: 0000000000000000     RCX: ffffffff83904fde RDX: dffffc0000000000 RSI: 0000000000000008 RDI: ffff88871ed36380 RBP:
    ffff888158beeb40 R08: 0000000000000001 R09: fffff520010c6f56 R10: ffffc90008637ab7 R11: 0000000000000001     R12: 0000000000000001 R13: ffff888140e77400 R14: ffff888140e77408 R15: ffffffff858b42c0 FS:
    0000000000000000(0000) GS:ffff88871ed00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0:
    0000000080050033 CR2: 0000562384d32158 CR3: 000000055cc6a000 CR4: 00000000000006f0 DR0: 0000000000000000     DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7:
    0000000000000400 Call Trace: <TASK> ? refcount_warn_saturate+0xb5/0x170 ? __warn+0xa5/0x140 ?     refcount_warn_saturate+0xb5/0x170 ? report_bug+0x1b1/0x1e0 ? handle_bug+0x53/0xa0 ?     exc_invalid_op+0x17/0x40 ? asm_exc_invalid_op+0x1a/0x20 ? tick_nohz_tick_stopped+0x1e/0x40 ?     refcount_warn_saturate+0xb5/0x170 ? refcount_warn_saturate+0xb5/0x170 nfs3svc_release_getacl+0xc9/0xe0     svc_process_common+0x5db/0xb60 ? __pfx_svc_process_common+0x10/0x10 ? __rcu_read_unlock+0x69/0xa0 ?
    __pfx_nfsd_dispatch+0x10/0x10 ? svc_xprt_received+0xa1/0x120 ? xdr_init_decode+0x11d/0x190     svc_process+0x2a7/0x330 svc_handle_xprt+0x69d/0x940 svc_recv+0x180/0x2d0 nfsd+0x168/0x200 ?
    __pfx_nfsd+0x10/0x10 kthread+0x1a2/0x1e0 ? kthread+0xf4/0x1e0 ? __pfx_kthread+0x10/0x10     ret_from_fork+0x34/0x60 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> Kernel panic - not     syncing: kernel: panic_on_warn set ... Clear acl_access/acl_default after posix_acl_release is called to     prevent UAF from being triggered. (CVE-2025-21796)

  - In the Linux kernel, the following vulnerability has been resolved: tcp: drop secpath at the same time as     we currently drop dst Xiumei reported hitting the WARN in xfrm6_tunnel_net_exit while running tests that     boil down to: - create a pair of netns - run a basic TCP test over ipcomp6 - delete the pair of netns The     xfrm_state found on spi_byaddr was not deleted at the time we delete the netns, because we still have a     reference on it. This lingering reference comes from a secpath (which holds a ref on the xfrm_state),     which is still attached to an skb. This skb is not leaked, it ends up on sk_receive_queue and then gets     defer-free'd by skb_attempt_defer_free. The problem happens when we defer freeing an skb (push it on one     CPU's defer_list), and don't flush that list before the netns is deleted. In that case, we still have a     reference on the xfrm_state that we don't expect at this point. We already drop the skb's dst in the TCP     receive path when it's no longer needed, so let's also drop the secpath. At this point, tcp_filter has     already called into the LSM hooks that may require the secpath, so it should not be needed anymore.
    However, in some of those places, the MPTCP extension has just been attached to the skb, so we cannot     simply drop all extensions. (CVE-2025-21864)

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

The remote Ubuntu 18.04 LTS / 20.04 LTS host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-7516-1 advisory.

    Several security issues were discovered in the Linux kernel. An attacker could possibly use these to     compromise the system. This update corrects flaws in the following subsystems:

    - ARM64 architecture;

    - PowerPC architecture;

    - Block layer subsystem;

    - Drivers core;

    - Network block device driver;

    - Character device driver;

    - GPU drivers;

    - HID subsystem;

    - InfiniBand drivers;

    - Media drivers;

    - Network drivers;

    - PPS (Pulse Per Second) driver;

    - PTP clock framework;

    - RapidIO drivers;

    - Real Time Clock drivers;

    - SCSI subsystem;

    - SLIMbus drivers;

    - QCOM SoC drivers;

    - Trusted Execution Environment drivers;

    - USB DSL drivers;

    - USB Device Class drivers;

    - USB core drivers;

    - USB Gadget drivers;

    - USB Host Controller drivers;

    - Renesas USBHS Controller drivers;

    - File systems infrastructure;

    - BTRFS file system;

    - NILFS2 file system;

    - UBI file system;

    - KVM subsystem;

    - L3 Master device support module;

    - Process Accounting mechanism;

    - printk logging mechanism;

    - Scheduler infrastructure;

    - Tracing infrastructure;

    - Memory management;

    - 802.1Q VLAN protocol;

    - B.A.T.M.A.N. meshing protocol;

    - Bluetooth subsystem;

    - Networking core;

    - IPv4 networking;

    - IPv6 networking;

    - Logical Link layer;

    - NFC subsystem;

    - Open vSwitch;

    - Rose network layer;

    - Network traffic control;

    - Wireless networking;

    - Tomoyo security module; (CVE-2025-21866, CVE-2025-21846, CVE-2025-21971, CVE-2025-21909, CVE-2024-58083,     CVE-2025-21811, CVE-2025-21776, CVE-2024-58051, CVE-2025-21917, CVE-2025-21935, CVE-2025-21785,     CVE-2021-47191, CVE-2025-21765, CVE-2025-21704, CVE-2025-21647, CVE-2024-58069, CVE-2025-21877,     CVE-2025-21948, CVE-2024-58007, CVE-2024-58001, CVE-2025-21871, CVE-2024-58055, CVE-2025-21848,     CVE-2025-21925, CVE-2024-58058, CVE-2025-21814, CVE-2025-21905, CVE-2025-21898, CVE-2025-21926,     CVE-2025-21760, CVE-2024-57973, CVE-2025-21806, CVE-2024-58071, CVE-2025-21761, CVE-2025-21762,     CVE-2024-57986, CVE-2025-21708, CVE-2025-21744, CVE-2024-26996, CVE-2024-50055, CVE-2024-58020,     CVE-2025-21858, CVE-2025-21715, CVE-2025-21904, CVE-2025-21920, CVE-2024-56599, CVE-2025-21781,     CVE-2025-21764, CVE-2025-21865, CVE-2025-21772, CVE-2024-58072, CVE-2025-21928, CVE-2025-21859,     CVE-2025-21721, CVE-2025-21719, CVE-2025-21914, CVE-2025-21753, CVE-2024-58009, CVE-2024-57981,     CVE-2024-58063, CVE-2024-58052, CVE-2025-21722, CVE-2024-57977, CVE-2025-21736, CVE-2025-21922,     CVE-2024-26982, CVE-2025-21718, CVE-2025-21916, CVE-2025-21749, CVE-2025-21787, CVE-2024-58085,     CVE-2024-58010, CVE-2024-57979, CVE-2024-57980, CVE-2025-21782, CVE-2025-21791, CVE-2025-21728,     CVE-2023-52741, CVE-2025-21934, CVE-2024-58002, CVE-2025-21735, CVE-2025-21910, CVE-2025-21823,     CVE-2024-58090, CVE-2025-21862, CVE-2025-21731, CVE-2025-21835, CVE-2024-58017, CVE-2024-58014,     CVE-2025-21763)

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

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

The remote Ubuntu 20.04 LTS / 22.04 LTS host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-7510-1 advisory.

    Several security issues were discovered in the Linux kernel. An attacker could possibly use these to     compromise the system. This update corrects flaws in the following subsystems:

    - ARM64 architecture;

    - PowerPC architecture;

    - x86 architecture;

    - Block layer subsystem;

    - Network block device driver;

    - Bus devices;

    - Character device driver;

    - TPM device driver;

    - Clock framework and drivers;

    - GPIO subsystem;

    - GPU drivers;

    - HID subsystem;

    - I2C subsystem;

    - InfiniBand drivers;

    - Media drivers;

    - NVIDIA Tegra memory controller driver;

    - Network drivers;

    - PCI subsystem;

    - PPS (Pulse Per Second) driver;

    - PTP clock framework;

    - RapidIO drivers;

    - Real Time Clock drivers;

    - SLIMbus drivers;

    - QCOM SoC drivers;

    - Trusted Execution Environment drivers;

    - TTY drivers;

    - USB DSL drivers;

    - USB Device Class drivers;

    - USB core drivers;

    - USB Gadget drivers;

    - USB Host Controller drivers;

    - Renesas USBHS Controller drivers;

    - ACRN Hypervisor Service Module driver;

    - File systems infrastructure;

    - BTRFS file system;

    - F2FS file system;

    - Network file system (NFS) server daemon;

    - NILFS2 file system;

    - Overlay file system;

    - SMB network file system;

    - UBI file system;

    - KVM subsystem;

    - L3 Master device support module;

    - Process Accounting mechanism;

    - Padata parallel execution mechanism;

    - printk logging mechanism;

    - Scheduler infrastructure;

    - Timer subsystem;

    - Tracing infrastructure;

    - Memory management;

    - 802.1Q VLAN protocol;

    - B.A.T.M.A.N. meshing protocol;

    - Networking core;

    - IPv4 networking;

    - IPv6 networking;

    - Logical Link layer;

    - Multipath TCP;

    - Netfilter;

    - NFC subsystem;

    - Open vSwitch;

    - Rose network layer;

    - Network traffic control;

    - Wireless networking;

    - Landlock security;

    - Linux Security Modules (LSM) Framework;

    - Tomoyo security module; (CVE-2025-21731, CVE-2025-21926, CVE-2025-21830, CVE-2024-58010, CVE-2025-21745,     CVE-2025-21871, CVE-2024-57980, CVE-2025-21916, CVE-2025-21735, CVE-2025-21763, CVE-2025-21799,     CVE-2025-21811, CVE-2025-21814, CVE-2024-58083, CVE-2025-21922, CVE-2025-21802, CVE-2024-58034,     CVE-2025-21758, CVE-2024-58069, CVE-2025-21905, CVE-2024-57986, CVE-2025-21718, CVE-2024-58020,     CVE-2025-21858, CVE-2025-21749, CVE-2025-21928, CVE-2024-58085, CVE-2025-21795, CVE-2025-21744,     CVE-2025-21776, CVE-2025-21804, CVE-2024-57973, CVE-2025-21848, CVE-2025-21844, CVE-2024-56721,     CVE-2024-58079, CVE-2025-21781, CVE-2025-21866, CVE-2024-58052, CVE-2024-58017, CVE-2024-58071,     CVE-2025-21791, CVE-2024-26982, CVE-2025-21787, CVE-2024-58090, CVE-2025-21951, CVE-2025-21846,     CVE-2025-21722, CVE-2024-58001, CVE-2025-21715, CVE-2025-21919, CVE-2025-21904, CVE-2024-57977,     CVE-2025-21785, CVE-2025-21950, CVE-2025-21924, CVE-2024-57979, CVE-2025-21711, CVE-2024-47726,     CVE-2024-58002, CVE-2025-21914, CVE-2024-58086, CVE-2024-58005, CVE-2025-21835, CVE-2024-58051,     CVE-2025-21761, CVE-2025-21760, CVE-2025-21767, CVE-2025-21766, CVE-2025-21726, CVE-2025-21865,     CVE-2024-58014, CVE-2025-21878, CVE-2025-21934, CVE-2024-58007, CVE-2025-21898, CVE-2025-21806,     CVE-2024-58058, CVE-2025-21779, CVE-2024-58063, CVE-2025-21708, CVE-2025-21684, CVE-2024-57834,     CVE-2025-21971, CVE-2025-21762, CVE-2025-21728, CVE-2024-58076, CVE-2025-21704, CVE-2025-21719,     CVE-2025-21948, CVE-2025-21707, CVE-2025-21917, CVE-2025-21782, CVE-2025-21943, CVE-2025-21765,     CVE-2025-21721, CVE-2024-58016, CVE-2025-21859, CVE-2025-21909, CVE-2025-21748, CVE-2025-21912,     CVE-2025-21736, CVE-2025-21862, CVE-2024-57978, CVE-2025-21826, CVE-2025-21920, CVE-2025-21772,     CVE-2025-21877, CVE-2025-21935, CVE-2024-56599, CVE-2025-21820, CVE-2025-21764, CVE-2025-21796,     CVE-2025-21887, CVE-2025-21753, CVE-2025-21910, CVE-2024-57981, CVE-2025-21727, CVE-2025-21875,     CVE-2024-58072, CVE-2024-58055, CVE-2025-21925, CVE-2025-21823, CVE-2025-21647)

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

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

The remote Ubuntu 22.04 LTS host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-7653-1 advisory.

    It was discovered that the CIFS network file system implementation in the Linux kernel did not properly     verify the target namespace when handling upcalls. An attacker could use this to expose sensitive     information. (CVE-2025-2312)

    Several security issues were discovered in the Linux kernel. An attacker could possibly use these to     compromise the system. This update corrects flaws in the following subsystems:

    - PowerPC architecture;

    - S390 architecture;

    - Block layer subsystem;

    - Serial ATA and Parallel ATA drivers;

    - Drivers core;

    - Network block device driver;

    - Character device driver;

    - TPM device driver;

    - Clock framework and drivers;

    - FireWire subsystem;

    - GPIO subsystem;

    - GPU drivers;

    - HID subsystem;

    - I3C subsystem;

    - InfiniBand drivers;

    - IOMMU subsystem;

    - IRQ chip drivers;

    - Media drivers;

    - NVIDIA Tegra memory controller driver;

    - Fastrpc Driver;

    - Network drivers;

    - Mellanox network drivers;

    - Operating Performance Points (OPP) driver;

    - PCI subsystem;

    - x86 platform drivers;

    - i.MX PM domains;

    - PPS (Pulse Per Second) driver;

    - PTP clock framework;

    - Remote Processor subsystem;

    - Real Time Clock drivers;

    - SCSI subsystem;

    - QCOM SoC drivers;

    - Media staging drivers;

    - TTY drivers;

    - UFS subsystem;

    - USB Gadget drivers;

    - USB Host Controller drivers;

    - USB Serial drivers;

    - AFS file system;

    - File systems infrastructure;

    - BTRFS file system;

    - F2FS file system;

    - GFS2 file system;

    - NILFS2 file system;

    - File system notification infrastructure;

    - Overlay file system;

    - Proc file system;

    - SMB network file system;

    - UBI file system;

    - Timer subsystem;

    - KVM subsystem;

    - Networking core;

    - ptr_ring data structure definitions;

    - Networking subsytem;

    - Amateur Radio drivers;

    - XFRM subsystem;

    - Tracing infrastructure;

    - BPF subsystem;

    - Kernel CPU control infrastructure;

    - Padata parallel execution mechanism;

    - printk logging mechanism;

    - Memory management;

    - Bluetooth subsystem;

    - DCCP (Datagram Congestion Control Protocol);

    - IPv4 networking;

    - IPv6 networking;

    - MAC80211 subsystem;

    - IEEE 802.15.4 subsystem;

    - Multipath TCP;

    - Netfilter;

    - NFC subsystem;

    - Open vSwitch;

    - Rose network layer;

    - RxRPC session sockets;

    - Network traffic control;

    - VMware vSockets driver;

    - Landlock security;

    - Linux Security Modules (LSM) Framework;

    - Tomoyo security module;

    - SoC audio core drivers; (CVE-2025-21830, CVE-2025-21678, CVE-2025-21815, CVE-2024-57974, CVE-2025-21725,     CVE-2025-21718, CVE-2025-21748, CVE-2025-21732, CVE-2024-57953, CVE-2025-21727, CVE-2025-21816,     CVE-2025-21719, CVE-2024-53124, CVE-2024-58019, CVE-2025-38001, CVE-2025-21720, CVE-2025-21734,     CVE-2025-21672, CVE-2025-21692, CVE-2024-58076, CVE-2025-21694, CVE-2024-58061, CVE-2025-21714,     CVE-2025-21689, CVE-2024-49887, CVE-2024-57949, CVE-2025-38177, CVE-2025-21683, CVE-2025-21669,     CVE-2025-21722, CVE-2024-57980, CVE-2025-38000, CVE-2025-37932, CVE-2024-58034, CVE-2024-58081,     CVE-2025-21733, CVE-2025-21682, CVE-2024-57924, CVE-2025-21743, CVE-2024-57975, CVE-2025-37798,     CVE-2024-58058, CVE-2025-21809, CVE-2025-21676, CVE-2024-57993, CVE-2025-21699, CVE-2024-58016,     CVE-2025-21832, CVE-2025-21804, CVE-2024-58011, CVE-2024-58007, CVE-2025-21826, CVE-2024-58055,     CVE-2025-21668, CVE-2025-21715, CVE-2024-58078, CVE-2025-21829, CVE-2025-21811, CVE-2025-21814,     CVE-2024-58053, CVE-2025-21726, CVE-2025-21943, CVE-2025-37750, CVE-2025-21673, CVE-2024-57984,     CVE-2025-37997, CVE-2025-21684, CVE-2025-21750, CVE-2024-58013, CVE-2025-21799, CVE-2024-58083,     CVE-2025-21798, CVE-2025-21731, CVE-2025-21708, CVE-2024-57986, CVE-2025-21744, CVE-2024-58014,     CVE-2025-21721, CVE-2024-58063, CVE-2024-57979, CVE-2024-58005, CVE-2025-21728, CVE-2025-21681,     CVE-2025-21806, CVE-2024-57982, CVE-2024-58002, CVE-2024-58082, CVE-2025-21812, CVE-2025-21745,     CVE-2024-58017, CVE-2025-21665, CVE-2025-21828, CVE-2025-37890, CVE-2024-57952, CVE-2024-57997,     CVE-2025-21825, CVE-2025-21716, CVE-2024-57948, CVE-2025-21710, CVE-2025-21674, CVE-2025-21675,     CVE-2024-50157, CVE-2025-21738, CVE-2025-22088, CVE-2024-58071, CVE-2024-58085, CVE-2025-21723,     CVE-2025-21690, CVE-2025-21670, CVE-2025-21741, CVE-2024-57999, CVE-2025-21691, CVE-2024-58068,     CVE-2024-58057, CVE-2024-57994, CVE-2024-58072, CVE-2025-21742, CVE-2024-58006, CVE-2024-58077,     CVE-2024-58003, CVE-2025-21753, CVE-2024-57981, CVE-2024-57973, CVE-2024-58001, CVE-2025-21666,     CVE-2025-21810, CVE-2025-21808, CVE-2024-57996, CVE-2024-58054, CVE-2024-57998, CVE-2025-21707,     CVE-2025-21736, CVE-2025-21820, CVE-2025-21739, CVE-2024-57951, CVE-2025-21667, CVE-2024-58070,     CVE-2025-21801, CVE-2024-58051, CVE-2024-58079, CVE-2025-21754, CVE-2024-58069, CVE-2025-37974,     CVE-2025-21802, CVE-2025-21749, CVE-2024-57990, CVE-2024-58080, CVE-2025-21705, CVE-2025-21697,     CVE-2024-58052, CVE-2025-21711, CVE-2024-58056, CVE-2025-21724, CVE-2024-58018, CVE-2025-21735,     CVE-2024-58010, CVE-2025-21680)

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

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

The remote Ubuntu 24.04 LTS host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-7651-1 advisory.

    Several security issues were discovered in the Linux kernel. An attacker could possibly use these to     compromise the system. This update corrects flaws in the following subsystems:

    - PowerPC architecture;

    - S390 architecture;

    - Block layer subsystem;

    - Serial ATA and Parallel ATA drivers;

    - Drivers core;

    - Network block device driver;

    - Character device driver;

    - TPM device driver;

    - Clock framework and drivers;

    - FireWire subsystem;

    - GPU drivers;

    - HID subsystem;

    - I3C subsystem;

    - InfiniBand drivers;

    - IOMMU subsystem;

    - Media drivers;

    - NVIDIA Tegra memory controller driver;

    - Fastrpc Driver;

    - Network drivers;

    - Operating Performance Points (OPP) driver;

    - PCI subsystem;

    - x86 platform drivers;

    - PPS (Pulse Per Second) driver;

    - PTP clock framework;

    - Remote Processor subsystem;

    - Real Time Clock drivers;

    - SCSI subsystem;

    - QCOM SoC drivers;

    - Media staging drivers;

    - TTY drivers;

    - UFS subsystem;

    - USB Gadget drivers;

    - USB Host Controller drivers;

    - File systems infrastructure;

    - BTRFS file system;

    - F2FS file system;

    - NILFS2 file system;

    - SMB network file system;

    - UBI file system;

    - Timer subsystem;

    - KVM subsystem;

    - Networking core;

    - ptr_ring data structure definitions;

    - Networking subsytem;

    - Amateur Radio drivers;

    - XFRM subsystem;

    - Tracing infrastructure;

    - BPF subsystem;

    - Padata parallel execution mechanism;

    - printk logging mechanism;

    - Memory management;

    - Bluetooth subsystem;

    - IPv4 networking;

    - IPv6 networking;

    - MAC80211 subsystem;

    - Multipath TCP;

    - Netfilter;

    - NFC subsystem;

    - Rose network layer;

    - RxRPC session sockets;

    - Network traffic control;

    - Landlock security;

    - Linux Security Modules (LSM) Framework;

    - Tomoyo security module;

    - SoC audio core drivers; (CVE-2024-57980, CVE-2024-58061, CVE-2025-21742, CVE-2025-21820, CVE-2024-57993,     CVE-2024-58071, CVE-2024-58017, CVE-2024-58019, CVE-2025-21745, CVE-2024-58016, CVE-2024-58011,     CVE-2024-58054, CVE-2025-21731, CVE-2024-58058, CVE-2024-58082, CVE-2025-21722, CVE-2024-58063,     CVE-2024-58014, CVE-2025-21735, CVE-2025-21828, CVE-2025-21804, CVE-2024-58018, CVE-2025-21814,     CVE-2024-58005, CVE-2024-58078, CVE-2025-21832, CVE-2025-21725, CVE-2025-21732, CVE-2025-21718,     CVE-2024-58069, CVE-2024-58052, CVE-2024-57973, CVE-2025-21825, CVE-2024-58056, CVE-2024-58080,     CVE-2025-21810, CVE-2024-57953, CVE-2025-37974, CVE-2024-57979, CVE-2025-21708, CVE-2024-57974,     CVE-2025-21753, CVE-2025-21736, CVE-2025-21728, CVE-2025-21743, CVE-2025-21815, CVE-2025-21802,     CVE-2025-21739, CVE-2024-57986, CVE-2024-57982, CVE-2025-21749, CVE-2025-21806, CVE-2025-21754,     CVE-2025-21738, CVE-2025-21716, CVE-2025-21705, CVE-2024-57998, CVE-2024-58006, CVE-2024-58068,     CVE-2025-21748, CVE-2024-58077, CVE-2025-21723, CVE-2024-58013, CVE-2025-21719, CVE-2024-58002,     CVE-2025-21750, CVE-2024-58053, CVE-2024-58070, CVE-2025-21809, CVE-2024-57975, CVE-2025-21816,     CVE-2025-21798, CVE-2024-58051, CVE-2024-58083, CVE-2025-21808, CVE-2025-21799, CVE-2024-57996,     CVE-2024-58085, CVE-2025-21744, CVE-2024-57994, CVE-2024-58055, CVE-2024-58076, CVE-2025-21710,     CVE-2025-21707, CVE-2024-58072, CVE-2025-21726, CVE-2025-21811, CVE-2025-37750, CVE-2024-58001,     CVE-2025-21714, CVE-2025-21711, CVE-2025-21830, CVE-2024-58007, CVE-2025-21812, CVE-2025-21734,     CVE-2024-58034, CVE-2024-58081, CVE-2024-58079, CVE-2024-58003, CVE-2025-21721, CVE-2024-49887,     CVE-2024-57984, CVE-2025-21715, CVE-2025-21801, CVE-2024-57997, CVE-2025-21741, CVE-2025-21727,     CVE-2024-58057, CVE-2025-21724, CVE-2024-57990, CVE-2024-57981, CVE-2024-57999, CVE-2025-21733,     CVE-2025-21829, CVE-2024-58010, CVE-2025-21720, CVE-2025-21826)

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

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

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

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

    The following security bugs were fixed:

    - CVE-2023-52927: netfilter: allow exp not to be removed in nf_ct_find_expectation (bsc#1239644).
    - CVE-2024-35910: tcp: properly terminate timers for kernel sockets (bsc#1224489).
    - CVE-2024-41005: netpoll: Fix race condition in netpoll_owner_active (bsc#1227858).
    - CVE-2024-46782: ila: call nf_unregister_net_hooks() sooner (bsc#1230769).
    - CVE-2024-47408: net/smc: check smcd_v2_ext_offset when receiving proposal msg (bsc#1235711).
    - CVE-2024-47794: kABI: bpf: Prevent tailcall infinite loop caused by freplace kABI workaround     (bsc#1235712).
    - CVE-2024-49571: net/smc: check iparea_offset and ipv6_prefixes_cnt when receiving proposal msg     (bsc#1235733).
    - CVE-2024-49940: kABI fix for l2tp: prevent possible tunnel refcount underflow (bsc#1232812).
    - CVE-2024-50056: usb: gadget: uvc: Fix ERR_PTR dereference in uvc_v4l2.c (bsc#1232389).
    - CVE-2024-50140: net: sched: use RCU read-side critical section in taprio_dump() (bsc#1233060).
    - CVE-2024-53057: net/sched: stop qdisc_tree_reduce_backlog on TC_H_ROOT (bsc#1233551).
    - CVE-2024-53140: netlink: terminate outstanding dump on socket close (bsc#1234222).
    - CVE-2024-53680: ipvs: fix UB due to uninitialized stack access in ip_vs_protocol_init() (bsc#1235715).
    - CVE-2024-54683: netfilter: IDLETIMER: Fix for possible ABBA deadlock (bsc#1235729).
    - CVE-2024-56638: kABI fix for 'netfilter: nft_inner: incorrect percpu area handling under softirq'     (bsc#1235524).
    - CVE-2024-56640: net/smc: fix LGR and link use-after-free issue (bsc#1235436).
    - CVE-2024-56702: bpf: Add tracepoints with null-able arguments (bsc#1235501).
    - CVE-2024-56703: ipv6: Fix soft lockups in fib6_select_path under high next hop churn (bsc#1235455).
    - CVE-2024-56718: net/smc: protect link down work from execute after lgr freed (bsc#1235589).
    - CVE-2024-56719: net: stmmac: fix TSO DMA API usage causing oops (bsc#1235591).
    - CVE-2024-56751: ipv6: release nexthop on device removal (bsc#1234936).
    - CVE-2024-56758: btrfs: check folio mapping after unlock in relocate_one_folio() (bsc#1235621).
    - CVE-2024-56770: net/sched: netem: account for backlog updates from child qdisc (bsc#1235637).
    - CVE-2024-57900: ila: serialize calls to nf_register_net_hooks() (bsc#1235973).
    - CVE-2024-57947: netfilter: nf_set_pipapo: fix initial map fill (bsc#1236333).
    - CVE-2024-57974: udp: Deal with race between UDP socket address change and rehash (bsc#1238532).
    - CVE-2024-57996: net_sched: sch_sfq: do not allow 1 packet limit (bsc#1239076).
    - CVE-2024-58012: ASoC: SOF: Intel: hda-dai: Ensure DAI widget is valid during params (bsc#1239104).
    - CVE-2024-58019: nvkm/gsp: correctly advance the read pointer of GSP message queue (bsc#1238997).
    - CVE-2024-58083: KVM: Explicitly verify target vCPU is online in kvm_get_vcpu() (bsc#1239036).
    - CVE-2025-21635: rds: sysctl: rds_tcp_{rcv,snd}buf: avoid using current->nsproxy (bsc#1236111).
    - CVE-2025-21659: netdev: prevent accessing NAPI instances from another namespace (bsc#1236206).
    - CVE-2025-21693: mm: zswap: properly synchronize freeing resources during CPU hotunplug (bsc#1237029).
    - CVE-2025-21701: net: avoid race between device unregistration and ethnl ops (bsc#1237164).
    - CVE-2025-21703: netem: Update sch->q.qlen before qdisc_tree_reduce_backlog() (bsc#1237313).
    - CVE-2025-21706: mptcp: pm: only set fullmesh for subflow endp (bsc#1238528).
    - CVE-2025-21739: kABI: ufshcd: add ufshcd_dealloc_host back (bsc#1238506).
    - CVE-2025-21753: btrfs: fix use-after-free when attempting to join an aborted transaction (bsc#1237875).
    - CVE-2025-21759: ipv6: mcast: extend RCU protection in igmp6_send() (bsc#1238738).
    - CVE-2025-21760: ndisc: extend RCU protection in ndisc_send_skb() (bsc#1238763).
    - CVE-2025-21761: openvswitch: use RCU protection in ovs_vport_cmd_fill_info() (bsc#1238775).
    - CVE-2025-21762: arp: use RCU protection in arp_xmit() (bsc#1238780).
    - CVE-2025-21763: neighbour: use RCU protection in __neigh_notify() (bsc#1237897).
    - CVE-2025-21765: ipv6: use RCU protection in ip6_default_advmss() (bsc#1237906).
    - CVE-2025-21766: ipv4: use RCU protection in __ip_rt_update_pmtu() (bsc#1238754).
    - CVE-2025-21791: vrf: use RCU protection in l3mdev_l3_out() (bsc#1238512).
    - CVE-2025-21825: selftests/bpf: Add test case for the freeing of bpf_timer (bsc#1238971).
    - CVE-2025-21844: smb: client: Add check for next_buffer in receive_encrypted_standard() (bsc#1239512).
    - CVE-2025-21848: nfp: bpf: Add check for nfp_app_ctrl_msg_alloc() (bsc#1239479).
    - CVE-2025-21856: s390/ism: add release function for struct device (bsc#1239486).
    - CVE-2025-21857: net/sched: cls_api: fix error handling causing NULL dereference (bsc#1239478).
    - CVE-2025-21861: mm/migrate_device: do not add folio to be freed to LRU in migrate_device_finalize()     (bsc#1239483).
    - CVE-2025-21862: drop_monitor: fix incorrect initialization order (bsc#1239474).
    - CVE-2025-21864: kABI fix for tcp: drop secpath at the same time as we currently drop (bsc#1239482).
    - CVE-2025-21865: gtp: Suppress list corruption splat in gtp_net_exit_batch_rtnl() (bsc#1239481).
    - CVE-2025-21870: ASoC: SOF: ipc4-topology: Harden loops for looking up ALH copiers (bsc#1240191).
    - CVE-2025-21871: tee: optee: Fix supplicant wait loop (bsc#1240183).
    - CVE-2025-21883: ice: Fix deinitializing VF in error path (bsc#1240189).
    - CVE-2025-21890: idpf: fix checksums set in idpf_rx_rsc() (bsc#1240173).
    - CVE-2025-21891: ipvlan: ensure network headers are in skb linear part (bsc#1240186).


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

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

The remote Debian 11 host has packages installed that are affected by multiple vulnerabilities as referenced in the dla-4178 advisory.

    -------------------------------------------------------------------------     Debian LTS Advisory DLA-4178-1                debian-lts@lists.debian.org     https://www.debian.org/lts/security/                        Ben Hutchings     May 25, 2025                                  https://wiki.debian.org/LTS
    -------------------------------------------------------------------------

    Package        : linux     Version        : 5.10.237-1     CVE ID         : CVE-2021-47247 CVE-2021-47489 CVE-2022-48893 CVE-2022-49046                      CVE-2022-49190 CVE-2022-49219 CVE-2022-49309 CVE-2022-49546                      CVE-2022-49728 CVE-2023-52572 CVE-2023-52621 CVE-2023-52752                      CVE-2023-52757 CVE-2023-53034 CVE-2024-26686 CVE-2024-26928                      CVE-2024-26982 CVE-2024-35867 CVE-2024-35943 CVE-2024-36908                      CVE-2024-38611 CVE-2024-39494 CVE-2024-41073 CVE-2024-42322                      CVE-2024-44938 CVE-2024-46753 CVE-2024-46812 CVE-2024-46816                      CVE-2024-46821 CVE-2024-47726 CVE-2024-47730 CVE-2024-49960                      CVE-2024-50047 CVE-2024-50154 CVE-2024-50280 CVE-2024-53144                      CVE-2024-54458 CVE-2024-56599 CVE-2024-56608 CVE-2024-56658                      CVE-2024-56664 CVE-2024-57834 CVE-2024-57973 CVE-2024-57977                      CVE-2024-57979 CVE-2024-57980 CVE-2024-57981 CVE-2024-57986                      CVE-2024-58001 CVE-2024-58002 CVE-2024-58005 CVE-2024-58007                      CVE-2024-58010 CVE-2024-58014 CVE-2024-58016 CVE-2024-58017                      CVE-2024-58020 CVE-2024-58051 CVE-2024-58052 CVE-2024-58055                      CVE-2024-58058 CVE-2024-58063 CVE-2024-58069 CVE-2024-58071                      CVE-2024-58072 CVE-2024-58083 CVE-2024-58085 CVE-2024-58090                      CVE-2025-21647 CVE-2025-21700 CVE-2025-21702 CVE-2025-21704                      CVE-2025-21708 CVE-2025-21711 CVE-2025-21715 CVE-2025-21718                      CVE-2025-21719 CVE-2025-21721 CVE-2025-21722 CVE-2025-21726                      CVE-2025-21727 CVE-2025-21728 CVE-2025-21731 CVE-2025-21735                      CVE-2025-21736 CVE-2025-21744 CVE-2025-21745 CVE-2025-21749                      CVE-2025-21753 CVE-2025-21756 CVE-2025-21760 CVE-2025-21761                      CVE-2025-21762 CVE-2025-21763 CVE-2025-21764 CVE-2025-21765                      CVE-2025-21767 CVE-2025-21772 CVE-2025-21776 CVE-2025-21779                      CVE-2025-21781 CVE-2025-21782 CVE-2025-21785 CVE-2025-21787                      CVE-2025-21791 CVE-2025-21795 CVE-2025-21796 CVE-2025-21799                      CVE-2025-21802 CVE-2025-21804 CVE-2025-21806 CVE-2025-21811                      CVE-2025-21814 CVE-2025-21823 CVE-2025-21826 CVE-2025-21835                      CVE-2025-21844 CVE-2025-21846 CVE-2025-21848 CVE-2025-21853                      CVE-2025-21858 CVE-2025-21859 CVE-2025-21862 CVE-2025-21871                      CVE-2025-21872 CVE-2025-21875 CVE-2025-21877 CVE-2025-21878                      CVE-2025-21898 CVE-2025-21904 CVE-2025-21905 CVE-2025-21909                      CVE-2025-21910 CVE-2025-21914 CVE-2025-21916 CVE-2025-21917                      CVE-2025-21920 CVE-2025-21922 CVE-2025-21925 CVE-2025-21926                      CVE-2025-21928 CVE-2025-21934 CVE-2025-21935 CVE-2025-21941                      CVE-2025-21943 CVE-2025-21948 CVE-2025-21956 CVE-2025-21957                      CVE-2025-21959 CVE-2025-21968 CVE-2025-21971 CVE-2025-21975                      CVE-2025-21981 CVE-2025-21991 CVE-2025-21992 CVE-2025-21993                      CVE-2025-21996 CVE-2025-21999 CVE-2025-22004 CVE-2025-22005                      CVE-2025-22007 CVE-2025-22008 CVE-2025-22010 CVE-2025-22014                      CVE-2025-22018 CVE-2025-22020 CVE-2025-22021 CVE-2025-22025                      CVE-2025-22027 CVE-2025-22035 CVE-2025-22044 CVE-2025-22045                      CVE-2025-22054 CVE-2025-22055 CVE-2025-22056 CVE-2025-22063                      CVE-2025-22075 CVE-2025-22079 CVE-2025-22086 CVE-2025-23136                      CVE-2025-23138 CVE-2025-23140 CVE-2025-23142 CVE-2025-23144                      CVE-2025-23145 CVE-2025-23146 CVE-2025-23147 CVE-2025-23148                      CVE-2025-23150 CVE-2025-23156 CVE-2025-23157 CVE-2025-23158                      CVE-2025-23159 CVE-2025-23163 CVE-2025-37738 CVE-2025-37739                      CVE-2025-37740 CVE-2025-37741 CVE-2025-37749 CVE-2025-37756                      CVE-2025-37757 CVE-2025-37765 CVE-2025-37766 CVE-2025-37768                      CVE-2025-37770 CVE-2025-37773 CVE-2025-37780 CVE-2025-37781                      CVE-2025-37782 CVE-2025-37785 CVE-2025-37788 CVE-2025-37789                      CVE-2025-37792 CVE-2025-37794 CVE-2025-37796 CVE-2025-37797                      CVE-2025-37803 CVE-2025-37808 CVE-2025-37810 CVE-2025-37812                      CVE-2025-37817 CVE-2025-37823 CVE-2025-37824 CVE-2025-37829                      CVE-2025-37836 CVE-2025-37838 CVE-2025-37839 CVE-2025-37840                      CVE-2025-37841 CVE-2025-37844 CVE-2025-37850 CVE-2025-37851                      CVE-2025-37857 CVE-2025-37858 CVE-2025-37859 CVE-2025-37862                      CVE-2025-37867 CVE-2025-37871 CVE-2025-37881 CVE-2025-37885                      CVE-2025-38637 CVE-2025-39728 CVE-2025-39735

    Several vulnerabilities have been discovered in the Linux kernel that     may lead to a privilege escalation, denial of service or information     leaks.

    For Debian 11 bullseye, these problems have been fixed in version     5.10.237-1.  This additionally includes many more bug fixes from     stable updates 5.10.235-5.10.237.

    We recommend that you upgrade your linux packages.

    For the detailed security status of linux please refer to     its security tracker page at:
    https://security-tracker.debian.org/tracker/linux

    Further information about Debian LTS security advisories, how to apply     these updates to your system and frequently asked questions can be     found at: https://wiki.debian.org/LTS     Attachment:
    signature.asc     Description: PGP signature

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

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

The remote NewStart CGSL host, running version MAIN 7.02, has kernel packages installed that are affected by multiple vulnerabilities:

  - In the Linux kernel, the following vulnerability has been resolved: smack: tcp: ipv4, fix incorrect     labeling Currently, Smack mirrors the label of incoming tcp/ipv4 connections: when a label 'foo' connects     to a label 'bar' with tcp/ipv4, 'foo' always gets 'foo' in returned ipv4 packets. So, 1) returned packets     are incorrectly labeled ('foo' instead of 'bar') 2) 'bar' can write to 'foo' without being authorized to     write. Here is a scenario how to see this: * Take two machines, let's call them C and S, with active Smack     in the default state (no settings, no rules, no labeled hosts, only builtin labels) * At S, add Smack rule     'foo bar w' (labels 'foo' and 'bar' are instantiated at S at this moment) * At S, at label 'bar', launch a     program that listens for incoming tcp/ipv4 connections * From C, at label 'foo', connect to the listener     at S. (label 'foo' is instantiated at C at this moment) Connection succeedes and works. * Send some data     in both directions. * Collect network traffic of this connection. All packets in both directions are     labeled with the CIPSO of the label 'foo'. Hence, label 'bar' writes to 'foo' without being authorized,     and even without ever being known at C. If anybody cares: exactly the same happens with DCCP. This     behavior 1st manifested in release 2.6.29.4 (see Fixes below) and it looks unintentional. At least, no     explanation was provided. I changed returned packes label into the 'bar', to bring it into line with the     Smack documentation claims. (CVE-2024-47659)

  - In the Linux kernel, the following vulnerability has been resolved: HID: logitech-hidpp: Fix kernel crash     on receiver USB disconnect hidpp_connect_event() has *four* time-of-check vs time-of-use (TOCTOU) races     when it races with itself. hidpp_connect_event() primarily runs from a workqueue but it also runs on     probe() and if a device-connected packet is received by the hw when the thread running     hidpp_connect_event() from probe() is waiting on the hw, then a second thread running     hidpp_connect_event() will be started from the workqueue. This opens the following races (note the below     code is simplified): 1. Retrieving + printing the protocol (harmless race): if (!hidpp->protocol_major) {     hidpp_root_get_protocol_version() hidpp->protocol_major = response.rap.params[0]; } We can actually see     this race hit in the dmesg in the abrt output attached to rhbz#2227968: [ 3064.624215] logitech-hidpp-     device 0003:046D:4071.0049: HID++ 4.5 device connected. [ 3064.658184] logitech-hidpp-device     0003:046D:4071.0049: HID++ 4.5 device connected. Testing with extra logging added has shown that after     this the 2 threads take turn grabbing the hw access mutex (send_mutex) so they ping-pong through all the     other TOCTOU cases managing to hit all of them: 2. Updating the name to the HIDPP name (harmless race): if     (hidpp->name == hdev->name) { ... hidpp->name = new_name; } 3. Initializing the power_supply class for the     battery (problematic!): hidpp_initialize_battery() { if (hidpp->battery.ps) return 0; probe_battery(); /*     Blocks, threads take turns executing this */ hidpp->battery.desc.properties = devm_kmemdup(dev,     hidpp_battery_props, cnt, GFP_KERNEL); hidpp->battery.ps =     devm_power_supply_register(&hidpp->hid_dev->dev, &hidpp->battery.desc, cfg); } 4. Creating delayed     input_device (potentially problematic): if (hidpp->delayed_input) return; hidpp->delayed_input =     hidpp_allocate_input(hdev); The really big problem here is 3. Hitting the race leads to the following     sequence: hidpp->battery.desc.properties = devm_kmemdup(dev, hidpp_battery_props, cnt, GFP_KERNEL);
    hidpp->battery.ps = devm_power_supply_register(&hidpp->hid_dev->dev, &hidpp->battery.desc, cfg); ...
    hidpp->battery.desc.properties = devm_kmemdup(dev, hidpp_battery_props, cnt, GFP_KERNEL);
    hidpp->battery.ps = devm_power_supply_register(&hidpp->hid_dev->dev, &hidpp->battery.desc, cfg); So now we     have registered 2 power supplies for the same battery, which looks a bit weird from userspace's pov but     this is not even the really big problem. Notice how: 1. This is all devm-maganaged 2. The     hidpp->battery.desc struct is shared between the 2 power supplies 3. hidpp->battery.desc.properties points     to the result from the second devm_kmemdup() This causes a use after free scenario on USB disconnect of     the receiver: 1. The last registered power supply class device gets unregistered 2. The memory from the     last devm_kmemdup() call gets freed, hidpp->battery.desc.properties now points to freed memory 3. The     first registered power supply class device gets unregistered, this involves sending a remove uevent to     userspace which invokes power_supply_uevent() to fill the uevent data 4. power_supply_uevent() uses     hidpp->battery.desc.properties which now points to freed memory leading to backtraces like this one: Sep     22 20:01:35 eric kernel: BUG: unable to handle page fault for address: ffffb2140e017f08 ... Sep 22     20:01:35 eric kernel: Workqueue: usb_hub_wq hub_event Sep 22 20:01:35 eric kernel: RIP:
    0010:power_supply_uevent+0xee/0x1d0 ... Sep 22 20:01:35 eric kernel: ? asm_exc_page_fault+0x26/0x30 Sep 22     20:01:35 eric kernel: ? power_supply_uevent+0xee/0x1d0 Sep 22 20:01:35 eric kernel: ?     power_supply_uevent+0x10d/0x1d0 Sep 22 20:01:35 eric kernel: dev_uevent+0x10f/0x2d0 Sep 22 20:01:35 eric     kernel: kobject_uevent_env+0x291/0x680 Sep 22 20:01:35 eric kernel: ---truncated--- (CVE-2023-52478)

  - In the Linux kernel, the following vulnerability has been resolved: clk: sunxi-ng: h6: Reparent CPUX     during PLL CPUX rate change While PLL CPUX clock rate change when CPU is running from it works in vast     majority of cases, now and then it causes instability. This leads to system crashes and other undefined     behaviour. After a lot of testing (30+ hours) while also doing a lot of frequency switches, we can't     observe any instability issues anymore when doing reparenting to stable clock like 24 MHz oscillator.
    (CVE-2023-52882)

  - In the Linux kernel, the following vulnerability has been resolved: net: can: j1939: enhanced error     handling for tightly received RTS messages in xtp_rx_rts_session_new This patch enhances error handling in     scenarios with RTS (Request to Send) messages arriving closely. It replaces the less informative     WARN_ON_ONCE backtraces with a new error handling method. This provides clearer error messages and allows     for the early termination of problematic sessions. Previously, sessions were only released at the end of     j1939_xtp_rx_rts(). Potentially this could be reproduced with something like: testj1939 -r vcan0:0x80 &     while true; do # send first RTS cansend vcan0 18EC8090#1014000303002301; # send second RTS cansend vcan0     18EC8090#1014000303002301; # send abort cansend vcan0 18EC8090#ff00000000002301; done (CVE-2023-52887)

  - In the Linux kernel, the following vulnerability has been resolved: media: mediatek: vcodec: Only free     buffer VA that is not NULL In the MediaTek vcodec driver, while mtk_vcodec_mem_free() is mostly called     only when the buffer to free exists, there are some instances that didn't do the check and triggered     warnings in practice. We believe those checks were forgotten unintentionally. Add the checks back to fix     the warnings. (CVE-2023-52888)

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	Published	Updated	Severity
240769	SUSE SLES15 セキュリティ更新 : kernel (SUSE-SU-2025:01919-1)	Nessus	SuSE Local Security Checks	6/27/2025	9/24/2025	medium
242347	Oracle Linux 9 : Unbreakable Enterprise カーネル (ELSA-2025-20480)	Nessus	Oracle Linux Local Security Checks	7/18/2025	7/19/2025	medium
237234	AlmaLinux 9 : kernel (ALSA-2025:7423)	Nessus	Alma Linux Local Security Checks	5/26/2025	9/23/2025	high
234322	CentOS 9 : kernel-5.14.0-578.el9	Nessus	CentOS Local Security Checks	4/14/2025	4/14/2025	high
236878	Ubuntu 18.04 LTS / 20.04 LTS : Linux kernel vulnerabilities (USN-7516-1)	Nessus	Ubuntu Local Security Checks	5/16/2025	5/16/2025	high
236880	Ubuntu 20.04 LTS / 22.04 LTS : Linux kernel vulnerabilities (USN-7510-1)	Nessus	Ubuntu Local Security Checks	5/16/2025	5/16/2025	high
242344	Ubuntu 22.04 LTS : Linux kernel (HWE) vulnerabilities (USN-7653-1)	Nessus	Ubuntu Local Security Checks	7/18/2025	7/18/2025	high
242282	Ubuntu 24.04 LTS : Linux kernel vulnerabilities (USN-7651-1)	Nessus	Ubuntu Local Security Checks	7/17/2025	7/17/2025	high
234057	SUSE SLES15 / openSUSE 15 Security Update : kernel (SUSE-SU-2025:1177-1)	Nessus	SuSE Local Security Checks	4/9/2025	4/9/2025	high
237255	Debian dla-4178 : ata-modules-5.10.0-34-armmp-di - security update	Nessus	Debian Local Security Checks	5/26/2025	9/24/2025	high
242830	NewStart CGSL MAIN 7.02 : kernel Multiple Vulnerabilities (NS-SA-2025-0118)	Nessus	NewStart CGSL Local Security Checks	7/25/2025	9/24/2025	high

Detections

Analytics

Plugins Search

medium

medium

high

high

high

high

high

high

high

high

high