Linux/Unix ホストには、ベンダーが提供するパッチが利用できない脆弱性の影響を受ける複数のパッケージがインストールされています。

  - wifibrcmfmacof_property_read_string_index() の戻り値をチェックします 6.10 から 6.11 の間ののある時点で、ドライバーが MacBookPro14、3 でクラッシュし始めました。プロパティが存在せず、「tmp」が初期化されないため、ランダムなポインターを devm_kstrdup() に渡します。発生しているクラッシュは次のようになります BUG
    アドレスのページ障害を処理できない00007f033c669379 PFカーネルモードPFのスーパーバイザー読み取りアクセス
    error_code(0x0001) - permissions violation PGD 8000000101341067 P4D 8000000101341067 PUD 101340067 PMD 1013bb067 PTE 800000010aee9025 Oops: Oops: 0001 [#1] SMP PTI CPU: 4 UID: 0 PID: 827 Comm: (udev-worker) Not tainted 6.11.8- gentoo #1 ハードウェア名Apple Inc. MacBookPro14,3/Mac-551B86E5744E2388、BIOS 529.140.2.0.0 06/23/2024 RIP: 0010:strlen+0x4/0x30 コード: f7 75 ec 31 c0 c3 cc cc cc 48 89 f8 c3 cc cc cc 0f 1f 40 00 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa <80> 3f 00 74 14 48 89 f8 48 83 c0 01 80 38 00 75 f9 f7 48 007564 cc RSP:0018:ffffb4aac0683ad8 EFGS:00010202 RAX:00000000ffffffea RBX:00007f033c669379 RCX:000000000000000000000001 RDX:0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    00007f033c669379 RBP: 00000000ffffffea R08: 0000000000000000 R09: 00000000c0ba916a R10: ffffffffffffffff R11: ffffffffb61ea260 R12: ffff91f7815b50c8 R13: 0000000000000cc0 R14: ffff91fafefffe30 R15:
    ffffb4aac0683b30 FS: 00007f033ccbe8c0(0000) GS:ffff91faeed00000(0000) knlGS:000000000000000 CS: 0010 DS: 0010 DS
    0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f033c669379 CR3: 0000000107b1e004 CR4: 00000000003706f0 DR0:
     <TASK> 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 __die+0x23/0x70 ? page_fault_oops+0x149/0x4c0 ? raw_spin_rq_lock_nested+0xe/0x20 ? sched_balance_newidle+0x22b/0x3c0 ? update_load_avg+0x78/0x770 ? exc_page_fault+0x6f/0x150 ? asm_exc_page_fault+0x26/0x30 ? __pfx_pci_conf1_write+0x10/0x10 ? strlen+0x4/0x30 devm_kstrdup+0x25/0x70 brcmf_of_probe+0x273/0x350 [brcmfmac]CVE-2025-21750

Nessus は、ベンダーによって報告されたパッケージの存在に依存していることに注意してください。

リモートの SUSE Linux SLED15 / SLED_SAP15 / SLES15 / SLES_SAP15 / openSUSE 15 ホストには、SUSE-SU-2025:1180-1 のアドバイザリに記載された複数の脆弱性の影響を受けるパッケージがインストールされています。

    SUSE Linux Enterprise 15 SP6 カーネルが更新され、さまざまなセキュリティバグ修正が行われています。

    次のセキュリティバグを修正しました。


    - CVE-2023-52927: netfilter: nf_ct_find_expectation で exp が削除されないようにする (bsc#1239644)。
    - CVE-2024-35910: tcp: カーネルソケットのタイマーを適切に終了させる (bsc#1224489)。
    - CVE-2024-41005: netpoll: netpoll_owner_active 内の競合状態の修正 (bsc#1227858)。
    - CVE-2024-46782: ila: nf_unregister_net_hooks() をより早く呼び出す (bsc#1230769)。
    - CVE-2024-47408: net/smc: 提案メッセージを受信する際に smcd_v2_ext_offset をチェック (bsc#1235711)。
    - CVE-2024-47794: kABI: bpf: freplace kABI の回避策によって引き起こされる tailcall の無限ループを防ぐ (bsc#1235712)。
    - CVE-2024-49571: net/smc: 提案メッセージを受信する際に iparea_offset および ipv6_prefixes_cnt をチェック (bsc#1235733)。
    - CVE-2024-49940: kABI の L2TP 修正: トンネルの参照カウントのアンダーフローを防ぐ (bsc#1232812)。
    - CVE-2024-50056: usb: gadget: uvc: uvc_v4l2.c の ERR_PTR 逆参照を修正 (bsc#1232389)。
    - CVE-2024-50140: net: sched: taprio_dump() の RCU 読み取り側の重要セクションを使用 (bsc#1233060)。
    - CVE-2024-53057: net/sched: TC_H_ROOT の qdisc_tree_reduce_backlog を停止します (bsc#1233551)。
    - CVE-2024-53140: netlink: ソケットクローズでの未処理のダンプを終了する (bsc#1234222)。
    - CVE-2024-53680: ipvs: ip_vs_protocol_init() の初期化されていないスタックアクセスによる UB を修正 (bsc#1235715)。
    - CVE-2024-54683: netfilter: IDLETIMER: 潜在的な ABBA デッドロックの修正 (bsc#1235729)。
    - CVE-2024-56638: kABI の「netfilter: nft_inner: softirq での不適切な percpu エリア処理」(bsc#1235524)。
    - CVE-2024-56640: net/smc: LGR および use-after-free 問題のリンクの修正 (bsc#1235436)。
    - CVE-2024-56702: bpf: null 許容の引数を持つトレースポイントを追加 (bsc#1235501)。
    - CVE-2024-56703: ipv6: next hop churn が高い場合の fib6_select_path のソフトロックアップを修正 (bsc#1235455)。
    - CVE-2024-56718: net/smc: lgr が解放された後の実行からリンクダウンワークを保護 (bsc#1235589)。
    - CVE-2024-56719: net: stmmac: oops を引き起こす TSO DMA API の使用を修正 (bsc#1235591)。
    - CVE-2024-56751: ipv6: デバイス取り外し時に nexthop をリリース (bsc#1234936)。
    - CVE-2024-56758: btrfs: relocate_one_folio() でのロック解除後に folio マッピングをチェック (bsc#1235621)。
    - CVE-2024-56770: net/sched: netem: 子 qdisc からのバックログ更新に対応 (bsc#1235637)。
    - CVE-2024-57900: ila: nf_register_net_hooks() への呼び出しをシリアル化 (bsc#1235973)。
    - CVE-2024-57947: netfilter: nf_set_pipapo: 初期マップの塗りつぶしを修正 (bsc#1236333)。
    - CVE-2024-57974: udp: UDP ソケットアドレスの変更と再ハッシュの間の競合に対処 (bsc#1238532)。
    - CVE-2024-57979: pps の変更に対する kABI の回避策 (bsc#1238521)。
    - CVE-2024-57996: net_sched: sch_sfq: 1 パケット制限を許可しません (bsc#1239076)。
    - CVE-2024-58012: ASoC: SOF: Intel: hda-dai: DAI ウィジェットが params 中に有効であることを確認 (bsc#1239104)。
    - CVE-2024-58019: nvkm/gsp: GSP メッセージキューの読み取りポインターを適切に進める (bsc#1238997)。
    - CVE-2024-58083: KVM: kvm_get_vcpu() で、ターゲット vCPU がオンラインであることを明示的に検証 (bsc#1239036)。
    - CVE-2025-21635: rds: sysctl: rds_tcp_{rcv,snd}buf: current->nsproxy の使用を回避 (bsc#1236111)。
    - CVE-2025-21659: netdev: 別の名前空間から NAPI インスタンスにアクセスすることを阻止 (bsc#1236206)。
    - CVE-2025-21693: mm: zswap: CPU のホットアンプラグ中に解放中のリソースを適切に同期 (bsc#1237029)。
    - CVE-2025-21701: net: デバイス登録解除と ethnl ops の間の競合を回避 (bsc#1237164)。
    - CVE-2025-21703: netem: qdisc_tree_reduce_backlog() の前に sch->q.qlen を更新 (bsc#1237313)。
    - CVE-2025-21706: mptcp: pm: サブフロー endp に対して fullmesh のみを設定 (bsc#1238528)。
    - CVE-2025-21733: tracing/osnoise: トレースポイントのリセットを修正します (bsc#1238494)。
    - CVE-2025-21739: kABI: ufshcd: ufshcd_dealloc_host バックを追加 (bsc#1238506)。
    - CVE-2025-21753: btrfs: 中止されたトランザクションに参加しようとするときのメモリ解放後使用 (use-after-free) を修正 (bsc#1237875)。
    - CVE-2025-21754: btrfs: トランザクション中止後に順序付けられたエクステントを分割する際のアサーション失敗を修正 (bsc#1238496)。
    - CVE-2025-21759: ipv6: mcast: igmp6_send() の RCU 保護を拡張 (bsc#1238738)。
    - CVE-2025-21760: ndisc: ndisc_send_skb() の RCU 保護を拡張 (bsc#1238763)。
    - CVE-2025-21761: openvswitch: ovs_vport_cmd_fill_info() で RCU 保護を使用 (bsc#1238775)。
    - CVE-2025-21762: arp: arp_xmit() で RCU 保護を使用 (bsc#1238780)。
    - CVE-2025-21763: neighbour: __neigh_notify() で RCU 保護を使用 (bsc#1237897)。
    - CVE-2025-21765: ipv6: ip6_default_advmss() で RCU 保護を使用 (bsc#1237906)。
    - CVE-2025-21766: ipv4: __ip_rt_update_pmtu() で RCU 保護を使用 (bsc#1238754)。
    - CVE-2025-21791: vrf: l3mdev_l3_out() で RCU 保護を使用 (bsc#1238512)。
    - CVE-2025-21825: selftests/bpf: bpfbpf_timer の解放のためのテストケースを追加 (bsc#1238971)。
    - CVE-2025-21844: smb: client: receive_encrypted_standard() の next_buffer にチェックを追加 (bsc#1239512)。
    - CVE-2025-21848: nfp: bpf: nfp_app_ctrl_msg_alloc() のチェックを追加 (bsc#1239479)。
    - CVE-2025-21856: s390/ism: 構造体デバイスに対してリリース関数を追加 (bsc#1239486)。
    - CVE-2025-21857: net/sched: cls_api: NULL 逆参照を引き起こすエラー処理を修正 (bsc#1239478)。
    - CVE-2025-21861: mm/migrate_device: migrate_device_finalize() の LRU に解放される folio を追加しない (bsc#1239483)。
    - CVE-2025-21862: drop_monitor: 誤った初期化順序を修正 (bsc#1239474)。
    - CVE-2025-21864: kABI の tcp の修正: 現在のドロップと同時に secpath をドロップ (bsc#1239482)。
    - CVE-2025-21865: gtp: gtp_net_exit_batch_rtnl() のリスト破損スプラットを抑制 (bsc#1239481)。
    - CVE-2025-21870: ASoC: SOF: ipc4-topology: ALH コピーを検索するためにループを強化 (bsc#1240191)。
    - CVE-2025-21871: tee: optee: supplicant 待機ループを修正 (bsc#1240183)。
    - CVE-2025-21883: ice: エラーパスでの VF の非初期化を修正 (bsc#1240189)。
    - CVE-2025-21890: idpf: idpf_rx_rsc() に設定されたチェックサムを修正 (bsc#1240173)。
    - CVE-2025-21891: ipvlan: ネットワークヘッダーが skb 線形部分にあることを確認 (bsc#1240186)。


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

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

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

    - sunrpcsvc auth処理中のSVC_GARBAGEをauthエラーとして処理Jeff Layton[Orabug: 38137447] {CVE-2025-38089}
    - Zen34クライアントを追加Borislav PetkovAMD[Orabug:38172252] {CVE-2024-36350} {CVE-2024-36357}
    - x86/processMONITORの前のバッファクリアを移動しますKim Phillips[Orabug: 38172252] {CVE-2024-36350} {CVE-2024-36357}
    - 通常のカウンターを追加Borislav PetkovAMD[Orabug:38172252] {CVE-2024-36350} {CVE-2024-36357}
    - KVMSVMTSA CPUIDビットをゲストにアドバタイズBorislav PetkovAMD[Orabug:38172252] {CVE-2024-36350} {CVE-2024-36357}
    - x86/bugs一時的なスケジューラ攻撃の緩和策を追加しますBorislav PetkovAMD[Orabug:38172252] {CVE-2024-36350} {CVE-2024-36357}

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

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

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

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.

ID	名前	製品	ファミリー	公開日	更新日	深刻度
230933	Linux Distros のパッチ未適用の脆弱性: CVE-2025-21750	Nessus	Misc.	2025/3/6	2025/11/11	medium
234120	SUSE SLED15 / SLES15 / openSUSE 15 セキュリティ更新 : kernel (SUSE-SU-2025:1180-1)	Nessus	SuSE Local Security Checks	2025/4/10	2025/4/10	high
252244	Oracle Linux 10/9Unbreakable Enterprise kernelELSA-2025-20530	Nessus	Oracle Linux Local Security Checks	2025/8/19	2025/8/19	medium
242282	Ubuntu 24.04 LTS : Linux kernel vulnerabilities (USN-7651-1)	Nessus	Ubuntu Local Security Checks	2025/7/17	2025/7/17	high
242344	Ubuntu 22.04 LTS : Linux kernel (HWE) vulnerabilities (USN-7653-1)	Nessus	Ubuntu Local Security Checks	2025/7/18	2025/7/18	high
242830	NewStart CGSL MAIN 7.02 : kernel Multiple Vulnerabilities (NS-SA-2025-0118)	Nessus	NewStart CGSL Local Security Checks	2025/7/25	2025/9/24	high
234057	SUSE SLES15 / openSUSE 15 Security Update : kernel (SUSE-SU-2025:1177-1)	Nessus	SuSE Local Security Checks	2025/4/9	2025/4/9	high

検出

プラグインの検索

medium

high

medium

high

high

high

high