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

  - In the Linux kernel, the following vulnerability has been resolved: ASoC: soc-pcm: don't use soc_pcm_ret()     on .prepare callback commit 1f5664351410 (ASoC: lower no backend DAIs enabled for ... Port log     severity) ignores -EINVAL error message on common soc_pcm_ret(). It is used from many functions, ignoring
    -EINVAL is over-kill. The reason why -EINVAL was ignored was it really should only be used upon invalid     parameters coming from userspace and in that case we don't want to log an error since we do not want to     give userspace a way to do a denial-of-service attack on the syslog / diskspace. So don't use     soc_pcm_ret() on .prepare callback is better idea. (CVE-2024-58077)

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

The remote MiracleLinux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the AXSA:2025-11493:94 advisory.

    * kernel: can: isotp: fix potential CAN frame reception race in isotp_rcv() (CVE-2022-48830)
      * kernel: soc: qcom: cmd-db: Map shared memory as WC, not WB (CVE-2024-46689)
      * kernel: Squashfs: sanity check symbolic link size (CVE-2024-46744)
      * kernel: vfs: fix race between evice_inodes() and find_inode()&iput() (CVE-2024-47679)
      * kernel: x86/tdx: Fix in-kernel MMIO check (CVE-2024-47727)
      * kernel: rxrpc: Fix a race between socket set up and I/O thread creation (CVE-2024-49864)
      * kernel: io_uring: check if we need to reschedule during overflow flush (CVE-2024-50060)
      * kernel: can: m_can: pci: add missing m_can_class_free_dev() in probe/remove methods (CVE-2022-49024)
      * kernel: posix-clock: Fix missing timespec64 check in pc_clock_settime() (CVE-2024-50195)
      * kernel: rxrpc: Fix missing locking causing hanging calls (CVE-2024-50294)
      * kernel: io_uring/rw: fix missing NOWAIT check for O_DIRECT start write (CVE-2024-53052)
      * kernel: afs: Fix lock recursion (CVE-2024-53090)
      * kernel: virtio/vsock: Fix accept_queue memory leak (CVE-2024-53119)
      * kernel: KVM: VMX: Bury Intel PT virtualization (guest/host mode) behind CONFIG_BROKEN (CVE-2024-53135)
      * kernel: xen: Xen hypercall page unsafe against speculative attacks (Xen Security Advisory 466)     (CVE-2024-53241)
      * kernel: RDMA/rxe: Fix the qp flush warnings in req (CVE-2024-53229)
      * kernel: block: fix uaf for flush rq while iterating tags (CVE-2024-53170)
      * kernel: nfsd: release svc_expkey/svc_export with rcu_work (CVE-2024-53216)
      * kernel: net: af_can: do not leave a dangling sk pointer in can_create() (CVE-2024-56603)
      * kernel: blk-cgroup: Fix UAF in blkcg_unpin_online() (CVE-2024-56672)
      * kernel: acpi: nfit: vmalloc-out-of-bounds Read in acpi_nfit_ctl (CVE-2024-56662)
      * kernel: bpf: Fix UAF via mismatching bpf_prog/attachment RCU flavors (CVE-2024-56675)
      * kernel: can: j1939: j1939_session_new(): fix skb reference counting (CVE-2024-56645)
      * kernel: crypto: pcrypt - Call crypto layer directly when padata_do_parallel() return -EBUSY     (CVE-2024-56690)
      * kernel: io_uring: check if iowq is killed before queuing (CVE-2024-56709)
      * kernel: rtc: check if __rtc_read_time was successful in rtc_timer_do_work() (CVE-2024-56739)
      * kernel: bpf: put bpf_link's program when link is safe to be deallocated (CVE-2024-56786)
      * kernel: igb: Fix potential invalid memory access in igb_init_module() (CVE-2024-52332)
      * kernel: ipvs: fix UB due to uninitialized stack access in ip_vs_protocol_init() (CVE-2024-53680)
      * kernel: netfilter: conntrack: clamp maximum hashtable size to INT_MAX (CVE-2025-21648)
      * kernel: sched: sch_cake: add bounds checks to host bulk flow fairness counts (CVE-2025-21647)
      * kernel: block, bfq: fix waker_bfqq UAF after bfq_split_bfqq() (CVE-2025-21631)
      * kernel: zram: fix potential UAF of zram table (CVE-2025-21671)
      * kernel: afs: Fix merge preference rule failure condition (CVE-2025-21672)
      * kernel: mm: zswap: properly synchronize freeing resources during CPU hotunplug (CVE-2025-21693)
      * kernel: cachestat: fix page cache statistics permission checking (CVE-2025-21691)
      * kernel: mm: clear uffd-wp PTE/PMD state on mremap() (CVE-2025-21696)
      * kernel: pfifo_tail_enqueue: Drop new packet when sch->limit == 0 (CVE-2025-21702)
      * kernel: usbnet: fix memory leak in error case (CVE-2022-49657)
      * kernel: powerpc/xics: fix refcount leak in icp_opal_init() (CVE-2022-49432)
      * kernel: net: tun: unlink NAPI from device on destruction (CVE-2022-49672)
      * kernel: powerpc/papr_scm: don't requests stats with '0' sized stats buffer (CVE-2022-49353)
      * kernel: powerpc/xive: Fix refcount leak in xive_spapr_init (CVE-2022-49437)
      * kernel: ima: Fix potential memory leak in ima_init_crypto() (CVE-2022-49627)
      * kernel: linux/dim: Fix divide by 0 in RDMA DIM (CVE-2022-49670)
      * kernel: can: isotp: sanitize CAN ID checks in isotp_bind() (CVE-2022-49269)
      * kernel: ima: Fix a potential integer overflow in ima_appraise_measurement (CVE-2022-49643)
      * kernel: powerpc/xive/spapr: correct bitmap allocation size (CVE-2022-49623)
      * kernel: efi: Do not import certificates from UEFI Secure Boot for T2 Macs (CVE-2022-49357)
      * kernel: list: fix a data-race around ep->rdllist (CVE-2022-49443)
      * kernel: tracing/histograms: Fix memory leak problem (CVE-2022-49648)
      * kernel: Input: synaptics - fix crash when enabling pass-through port (CVE-2025-21746)
      * kernel: NFSD: fix hang in nfsd4_shutdown_callback (CVE-2025-21795)
      * kernel: bpf: Send signals asynchronously if !preemptible (CVE-2025-21728)
      * kernel: NFS: Fix potential buffer overflowin nfs_sysfs_link_rpc_client() (CVE-2024-54456)
      * kernel: Bluetooth: btrtl: check for NULL in btrtl_setup_realtek() (CVE-2024-57987)
      * kernel: wifi: brcmsmac: add gain range check to wlc_phy_iqcal_gainparams_nphy() (CVE-2024-58014)
      * kernel: Bluetooth: btbcm: Fix NULL deref in btbcm_get_board_name() (CVE-2024-57988)
      * kernel: RDMA/mlx5: Fix implicit ODP use after free (CVE-2025-21714)
      * kernel: drm/xe/tracing: Fix a potential TP_printk UAF (CVE-2024-49570)
      * kernel: HID: hid-thrustmaster: Fix warning in thrustmaster_probe by adding endpoint check     (CVE-2024-57993)
      * kernel: wifi: rtw89: fix race between cancel_hw_scan and hw_scan completion (CVE-2025-21729)
      * kernel: wifi: mt76: mt7925: fix NULL deref check in mt7925_change_vif_links (CVE-2024-57989)
      * kernel: wifi: ath12k: Fix for out-of bound access error (CVE-2024-58015)
      * kernel: OPP: add index check to assert to avoid buffer overflow in _read_freq() (CVE-2024-57998)
      * kernel: wifi: ath12k: fix read pointer after free in ath12k_mac_assign_vif_to_vdev() (CVE-2024-57995)
      * kernel: nfsd: clear acl_access/acl_default after releasing them (CVE-2025-21796)
      * kernel: scsi: ufs: core: Fix use-after free in init error and remove paths (CVE-2025-21739)
      * kernel: workqueue: Put the pwq after detaching the rescuer from the pool (CVE-2025-21786)
      * kernel: ata: libata-sff: Ensure that we cannot write outside the allocated buffer (CVE-2025-21738)
      * kernel: HID: core: Fix assumption that Resolution Multipliers must be in Logical Collections     (CVE-2024-57986)
      * kernel: padata: avoid UAF for reorder_work (CVE-2025-21726)
      * kernel: vrf: use RCU protection in l3mdev_l3_out() (CVE-2025-21791)
      * kernel: team: better TEAM_OPTION_TYPE_STRING validation (CVE-2025-21787)
      * kernel: usb: xhci: Fix NULL pointer dereference on certain command aborts (CVE-2024-57981)
      * kernel: vxlan: check vxlan_vnigroup_init() return value (CVE-2025-21790)
      * kernel: wifi: mt76: mt7925: fix off by one in mt7925_load_clc() (CVE-2024-57990)
      * kernel: ipv6: use RCU protection in ip6_default_advmss() (CVE-2025-21765)
      * kernel: ASoC: SOF: Intel: hda-dai: Ensure DAI widget is valid during params (CVE-2024-58012)
      * kernel: blk-cgroup: Fix class @block_class's subsystem refcount leakage (CVE-2025-21745)
      * kernel: net: let net.core.dev_weight always be non-zero (CVE-2025-21806)
      * kernel: wifi: rtlwifi: remove unused check_buddy_priv (CVE-2024-58072)
      * kernel: OPP: fix dev_pm_opp_find_bw_*() when bandwidth table not initialized (CVE-2024-58068)
      * kernel: wifi: iwlwifi: mvm: avoid NULL pointer dereference (CVE-2024-58062)
      * kernel: idpf: convert workqueues to unbound (CVE-2024-58057)
      * kernel: wifi: mac80211: don't flush non-uploaded STAs (CVE-2025-21828)
      * kernel: KVM: Explicitly verify target vCPU is online in kvm_get_vcpu() (CVE-2024-58083)
      * kernel: netfilter: nf_tables: reject mismatching sum of field_len with set key length (CVE-2025-21826)
      * kernel: ASoC: soc-pcm: don't use soc_pcm_ret() on .prepare callback (CVE-2024-58077)
      * kernel: crypto: tegra - do not transfer req when tegra init fails (CVE-2024-58075)
      * kernel: RDMA/rxe: Fix the warning __rxe_cleanup+0x12c/0x170 [rdma_rxe] (CVE-2025-21829)
      * kernel: KVM: x86: Load DR6 with guest value only before entering .vcpu_run() loop (CVE-2025-21839)
      * kernel: io_uring/uring_cmd: unconditionally copy SQEs at prep time (CVE-2025-21837)
      * kernel: information leak via transient execution vulnerability in some AMD processors (CVE-2024-36350)
      * kernel: transient execution vulnerability in some AMD processors (CVE-2024-36357)
      * kernel: bpf: Fix softlockup in arena_map_free on 64k page kernel (CVE-2025-21851)
      * kernel: ibmvnic: Don't reference skb after sending to VIOS (CVE-2025-21855)
      * kernel: smb: client: Add check for next_buffer in receive_encrypted_standard() (CVE-2025-21844)
      * kernel: bpf: avoid holding freeze_mutex during mmap operation (CVE-2025-21853)
      * kernel: ASoC: SOF: stream-ipc: Check for cstream nullity in sof_ipc_msg_data() (CVE-2025-21847)
      * kernel: tcp: drop secpath at the same time as we currently drop dst (CVE-2025-21864)
      * kernel: bpf: Fix deadlock when freeing cgroup storage (CVE-2024-58088)
      * kernel: acct: perform last write from workqueue (CVE-2025-21846)
      * kernel: mm/migrate_device: don't add folio to be freed to LRU in migrate_device_finalize()     (CVE-2025-21861)
      * kernel: io_uring: prevent opcode speculation (CVE-2025-21863)
      * kernel: nfp: bpf: Add check for nfp_app_ctrl_msg_alloc() (CVE-2025-21848)
      * kernel: netfilter: nft_tunnel: fix geneve_opt type confusion addition (CVE-2025-22056)
      * kernel: can: j1939: j1939_send_one(): fix missing CAN header initialization (CVE-2022-49845)
      * kernel: usb: typec: ucsi: displayport: Fix NULL pointer access (CVE-2025-37994)
      * kernel: wifi: ath12k: fix uaf in ath12k_core_init() (CVE-2025-38116)
      * kernel: fs: export anon_inode_make_secure_inode() and fix secretmem LSM bypass (CVE-2025-38396)

Tenable has extracted the preceding description block directly from the MiracleLinux 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	名称	产品	系列	发布时间	最近更新时间	严重程度
242830	NewStart CGSL MAIN 7.02 : kernel Multiple Vulnerabilities (NS-SA-2025-0118)	Nessus	NewStart CGSL Local Security Checks	2025/7/25	2026/1/6	high
232264	Linux Distros Unpatched Vulnerability : CVE-2024-58077	Nessus	Misc.	2025/3/6	2026/10/8	medium
282807	MiracleLinux 9 : kernel-5.14.0-611.5.1.el9_7 (AXSA:2025-11493:94)	Nessus	Miracle Linux Local Security Checks	2026/1/13	2026/2/16	high

检测

插件搜索

high

medium

high