In the Linux kernel, the following vulnerability has been resolved: clk: qcom: dispcc-sm6350: Add missing parent_map for a clock If a clk_rcg2 has a parent, it should also have parent_map defined, otherwise we'll get a NULL pointer dereference when calling clk_set_rate like the following: [ 3.388105] Call trace: [ 3.390664] qcom_find_src_index+0x3c/0x70 (P) [ 3.395301] qcom_find_src_index+0x1c/0x70 (L) [ 3.399934] _freq_tbl_determine_rate+0x48/0x100 [ 3.404753] clk_rcg2_determine_rate+0x1c/0x28 [ 3.409387] clk_core_determine_round_nolock+0x58/0xe4 [ 3.421414] clk_core_round_rate_nolock+0x48/0xfc [ 3.432974] clk_core_round_rate_nolock+0xd0/0xfc [ 3.444483] clk_core_set_rate_nolock+0x8c/0x300 [ 3.455886] clk_set_rate+0x38/0x14c Add the parent_map property for the clock where it's missing and also un-inline the parent_data as well to keep the matching parent_map and parent_data together.

An update of the linux package has been released.

The remote Ubuntu 22.04 LTS / 24.04 LTS host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-7737-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;

    - S390 architecture;

    - x86 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;

    - Input Device (Mouse) drivers;

    - IOMMU subsystem;

    - Multiple devices driver;

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

    - S/390 drivers;

    - SCSI subsystem;

    - QCOM SoC drivers;

    - SPI subsystem;

    - Media staging drivers;

    - Trusted Execution Environment drivers;

    - TTY drivers;

    - UFS subsystem;

    - USB Device Class drivers;

    - USB core drivers;

    - USB Gadget drivers;

    - USB Host Controller drivers;

    - Framebuffer layer;

    - File systems infrastructure;

    - BTRFS file system;

    - F2FS file system;

    - Network file system (NFS) client;

    - Network file system (NFS) server daemon;

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

    - L3 Master device support module;

    - TCP network protocol;

    - XFRM subsystem;

    - Tracing infrastructure;

    - io_uring subsystem;

    - Process Accounting mechanism;

    - BPF subsystem;

    - Padata parallel execution mechanism;

    - printk logging mechanism;

    - Workqueue subsystem;

    - Memory management;

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

    - Bluetooth subsystem;

    - IPv4 networking;

    - IPv6 networking;

    - MAC80211 subsystem;

    - Multipath TCP;

    - Netfilter;

    - NFC subsystem;

    - Open vSwitch;

    - Rose network layer;

    - RxRPC session sockets;

    - Network traffic control;

    - Landlock security;

    - Linux Security Modules (LSM) Framework;

    - Tomoyo security module;

    - SoC audio core drivers;

    - SOF drivers; (CVE-2025-37750, CVE-2025-21707, CVE-2025-21814, CVE-2025-21863, CVE-2025-21775,     CVE-2024-57997, CVE-2025-21749, CVE-2025-21739, CVE-2025-21829, CVE-2025-21731, CVE-2025-21704,     CVE-2024-57979, CVE-2025-21864, CVE-2024-57953, CVE-2025-21796, CVE-2025-21826, CVE-2024-57998,     CVE-2025-21784, CVE-2024-58072, CVE-2025-21859, CVE-2025-21790, CVE-2025-21762, CVE-2025-37797,     CVE-2024-57981, CVE-2024-58068, CVE-2025-21810, CVE-2024-58070, CVE-2025-21738, CVE-2024-58081,     CVE-2024-58010, CVE-2025-21832, CVE-2025-21839, CVE-2024-58061, CVE-2024-58069, CVE-2024-58055,     CVE-2024-57834, CVE-2025-21804, CVE-2025-21783, CVE-2025-21772, CVE-2024-57975, CVE-2024-57980,     CVE-2024-58082, CVE-2025-21741, CVE-2025-21733, CVE-2025-21750, CVE-2025-21728, CVE-2025-21716,     CVE-2025-21753, CVE-2025-21802, CVE-2024-57993, CVE-2025-21785, CVE-2024-57994, CVE-2025-21868,     CVE-2025-21812, CVE-2025-21760, CVE-2025-21782, CVE-2025-21763, CVE-2024-57999, CVE-2025-21823,     CVE-2024-57986, CVE-2024-58080, CVE-2025-21766, CVE-2025-21743, CVE-2025-21838, CVE-2025-21706,     CVE-2025-21820, CVE-2024-58003, CVE-2025-21809, CVE-2025-21867, CVE-2024-57982, CVE-2025-21759,     CVE-2024-57984, CVE-2025-21736, CVE-2024-58058, CVE-2025-21754, CVE-2024-49887, CVE-2025-21781,     CVE-2025-21795, CVE-2025-21746, CVE-2024-58019, CVE-2025-21780, CVE-2024-58083, CVE-2025-21734,     CVE-2025-21764, CVE-2025-21825, CVE-2024-54456, CVE-2024-58056, CVE-2025-21861, CVE-2024-57973,     CVE-2025-21735, CVE-2025-21705, CVE-2024-57990, CVE-2025-21836, CVE-2025-21816, CVE-2024-58088,     CVE-2024-58005, CVE-2025-21761, CVE-2025-21791, CVE-2025-21808, CVE-2025-21723, CVE-2025-21848,     CVE-2025-21870, CVE-2024-58076, CVE-2025-21854, CVE-2024-58093, CVE-2024-57977, CVE-2024-58034,     CVE-2024-58011, CVE-2024-58051, CVE-2025-21847, CVE-2025-21866, CVE-2024-58013, CVE-2025-21786,     CVE-2025-21856, CVE-2025-21765, CVE-2024-58057, CVE-2024-54458, CVE-2024-58002, CVE-2025-21715,     CVE-2025-21798, CVE-2025-21725, CVE-2025-21858, CVE-2025-21768, CVE-2025-21792, CVE-2024-58052,     CVE-2025-21721, CVE-2025-21773, CVE-2025-21835, CVE-2025-21853, CVE-2025-21869, CVE-2025-21722,     CVE-2025-21724, CVE-2024-58020, CVE-2025-21710, CVE-2024-58016, CVE-2025-21718, CVE-2025-21767,     CVE-2024-58079, CVE-2025-21779, CVE-2025-21857, CVE-2024-58017, CVE-2025-21719, CVE-2024-58001,     CVE-2025-21758, CVE-2024-58054, CVE-2024-58077, CVE-2025-21793, CVE-2024-58014, CVE-2025-21830,     CVE-2024-58071, CVE-2025-21748, CVE-2025-21806, CVE-2024-58006, CVE-2025-21844, CVE-2025-21745,     CVE-2024-58063, CVE-2024-58007, CVE-2025-21712, CVE-2024-58086, CVE-2025-21846, CVE-2025-21711,     CVE-2025-21787, CVE-2025-38083, CVE-2025-21742, CVE-2025-21732, CVE-2025-21714, CVE-2025-21744,     CVE-2025-21776, CVE-2024-52559, CVE-2025-21801, CVE-2025-21720, CVE-2025-21828, CVE-2024-57974,     CVE-2025-21821, CVE-2025-21811, CVE-2024-58053, CVE-2025-21855, CVE-2025-21726, CVE-2025-21862,     CVE-2025-21815, CVE-2024-58018, CVE-2025-21727, CVE-2025-21871, CVE-2024-58078, CVE-2024-58085,     CVE-2025-21799, CVE-2025-21708, CVE-2025-37974)

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 Oracle Linux 10 / 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the ELSA-2025-20530 advisory.

    - sunrpc: handle SVC_GARBAGE during svc auth processing as auth error (Jeff Layton)  [Orabug: 38137447]     {CVE-2025-38089}
    - Add Zen34 clients (Borislav Petkov (AMD))  [Orabug: 38172252]  {CVE-2024-36350} {CVE-2024-36357}
    - x86/process: Move the buffer clearing before MONITOR (Kim Phillips)  [Orabug: 38172252]     {CVE-2024-36350} {CVE-2024-36357}
    - Add normal counters (Borislav Petkov (AMD))  [Orabug: 38172252]  {CVE-2024-36350} {CVE-2024-36357}
    - KVM: SVM: Advertize TSA CPUID bits to guests (Borislav Petkov (AMD))  [Orabug: 38172252]     {CVE-2024-36350} {CVE-2024-36357}
    - x86/bugs: Add a Transient Scheduler Attacks mitigation (Borislav Petkov (AMD))  [Orabug: 38172252]     {CVE-2024-36350} {CVE-2024-36357}

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

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

The 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 Oracle Linux 10 / 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the ELSA-2025-20480 advisory.

    - sunrpc: handle SVC_GARBAGE during svc auth processing as auth error (Jeff Layton)  [Orabug: 38178286]     {CVE-2025-38089}
    - Add Zen34 clients (Borislav Petkov (AMD))  [Orabug: 38023239]  {CVE-2024-36350} {CVE-2024-36357}
    - x86/process: Move the buffer clearing before MONITOR (Kim Phillips)  [Orabug: 38023239]     {CVE-2024-36350} {CVE-2024-36357}
    - Add normal counters (Borislav Petkov (AMD))  [Orabug: 38023239]  {CVE-2024-36350} {CVE-2024-36357}
    - KVM: SVM: Advertize TSA CPUID bits to guests (Borislav Petkov (AMD))  [Orabug: 38023239]     {CVE-2024-36350} {CVE-2024-36357}
    - x86/bugs: Add a Transient Scheduler Attacks mitigation (Borislav Petkov (AMD))  [Orabug: 38023239]     {CVE-2024-36350} {CVE-2024-36357}
    - x86/bugs: Rename MDS machinery to something more generic (Borislav Petkov (AMD))  [Orabug: 38023239]     {CVE-2024-36350} {CVE-2024-36357}
    - block: fix adding folio to bio (Ming Lei) [Orabug: 37844657] {CVE-2025-22122}
    - f2fs: fix to avoid accessing uninitialized curseg (Chao Yu) [Orabug: 37844644] {CVE-2025-22123}
    - gpio: virtuser: fix potential out-of-bound write (Markus Burri) [Orabug: 38095181] {CVE-2025-38082}
    - net_sched: hfsc: Address reentrant enqueue adding class to eltree twice (Pedro Tammela) [Orabug:
    38049363] {CVE-2025-38001}
    - smb: client: Fix use-after-free in cifs_fill_dirent (Zhaolong Wang) [Orabug: 38094970] {CVE-2025-38051}
    - platform/x86: dell-wmi-sysman: Avoid buffer overflow in current_password_store() (Vladimir Moskovkin)     [Orabug: 38095141] {CVE-2025-38077}
    - ALSA: pcm: Fix race of buffer access at PCM OSS layer (Takashi Iwai) [Orabug: 38095145] {CVE-2025-38078}
    - can: bcm: add missing rcu read protection for procfs content (Oliver Hartkopp) [Orabug: 38049369]     {CVE-2025-38003}
    - can: bcm: add locking for bcm_op runtime updates (Oliver Hartkopp) [Orabug: 38049374] {CVE-2025-38004}
    - padata: do not leak refcount in reorder_work (Dominik Grzegorzek) [Orabug: 38094842] {CVE-2025-38031}
    - crypto: algif_hash - fix double free in hash_accept (Ivan Pravdin) [Orabug: 38095153] {CVE-2025-38079}
    - net/tipc: fix slab-use-after-free Read in tipc_aead_encrypt_done (Wang Liang) [Orabug: 38094978]     {CVE-2025-38052}
    - sch_hfsc: Fix qlen accounting bug when using peek in hfsc_enqueue() (Cong Wang) [Orabug: 38049357]     {CVE-2025-38000}
    - idpf: fix null-ptr-deref in idpf_features_check (Pavan Kumar Linga) [Orabug: 38094982] {CVE-2025-38053}
    - ptp: ocp: Limit signal/freq counts in summary output functions (Sagi Maimon) [Orabug: 38094984]     {CVE-2025-38054}
    - perf/x86/intel: Fix segfault with PEBS-via-PT with sample_freq (Adrian Hunter) [Orabug: 38094988]     {CVE-2025-38055}
    - ASoC: SOF: Intel: hda: Fix UAF when reloading module (Tavian Barnes) [Orabug: 38094991] {CVE-2025-38056}
    - espintcp: fix skb leaks (Sabrina Dubroca) [Orabug: 38094993] {CVE-2025-38057}
    - __legitimize_mnt(): check for MNT_SYNC_UMOUNT should be under mount_lock (Al Viro) [Orabug: 38095000]     {CVE-2025-38058}
    - x86/Kconfig: make CFI_AUTO_DEFAULT depend on !RUST or Rust >= 1.88 (Pawel Anikiel) [Orabug: 38094847]     {CVE-2025-38033}
    - btrfs: avoid NULL pointer dereference if no valid csum tree (Qu Wenruo) [Orabug: 38095010]     {CVE-2025-38059}
    - btrfs: correct the order of prelim_ref arguments in btrfs__prelim_ref (Goldwyn Rodrigues) [Orabug:
    38094856] {CVE-2025-38034}
    - nvmet-tcp: don't restore null sk_state_change (Alistair Francis) [Orabug: 38094863] {CVE-2025-38035}
    - vxlan: Annotate FDB data races (Ido Schimmel) [Orabug: 38094879] {CVE-2025-38037}
    - cpufreq: amd-pstate: Remove unnecessary driver_lock in set_boost (Dhananjay Ugwekar) [Orabug: 38094888]     {CVE-2025-38038}
    - drm/amd/display: Increase block_sequence array size (Joshua Aberback) [Orabug: 38095164]     {CVE-2025-38080}
    - bpf: copy_verifier_state() should copy 'loop_entry' field (Eduard Zingerman) [Orabug: 38095018]     {CVE-2025-38060}
    - serial: mctrl_gpio: split disable_ms into sync and no_sync APIs (Alexis Lothore) [Orabug: 38094901]     {CVE-2025-38040}
    - net: pktgen: fix access outside of user given buffer in pktgen_thread_write() (Peter Seiderer) [Orabug:
    38095024] {CVE-2025-38061}
    - genirq/msi: Store the IOMMU IOVA directly in msi_desc instead of iommu_cookie (Jason Gunthorpe) [Orabug:
    38095031] {CVE-2025-38062}
    - dm: fix unconditional IO throttle caused by REQ_PREFLUSH (Jinliang Zheng) [Orabug: 38095038]     {CVE-2025-38063}
    - firmware: arm_ffa: Set dma_mask for ffa devices (Viresh Kumar) [Orabug: 38094925] {CVE-2025-38043}
    - media: cx231xx: set device_caps for 417 (Hans Verkuil) [Orabug: 38094934] {CVE-2025-38044}
    - orangefs: Do not truncate file size (Matthew Wilcox) [Orabug: 38095056] {CVE-2025-38065}
    - dm cache: prevent BUG_ON by blocking retries on failed device resumes (Ming-Hung Tsai) [Orabug:
    38095063] {CVE-2025-38066}
    - crypto: lzo - Fix compression buffer overrun (Herbert Xu) [Orabug: 38095079] {CVE-2025-38068}
    - PCI: endpoint: pci-epf-test: Fix double free that causes kernel to oops (Christian Bruel) [Orabug:
    38095087] {CVE-2025-38069}
    - wifi: iwlwifi: fix debug actions order (Johannes Berg) [Orabug: 38094942] {CVE-2025-38045}
    - x86/mm: Check return value from memblock_phys_alloc_range() (Philip Redkin) [Orabug: 38095101]     {CVE-2025-38071}
    - libnvdimm/labels: Fix divide error in nd_label_data_init() (Robert Richter) [Orabug: 38095109]     {CVE-2025-38072}
    - spi-rockchip: Fix register out of bounds access (Luis de Arquer) [Orabug: 38095173] {CVE-2025-38081}
    - x86/fred: Fix system hang during S4 resume with FRED enabled (Xin Li) [Orabug: 38094951]     {CVE-2025-38047}
    - block: fix race between set_blocksize and read paths (Darrick J. Wong) [Orabug: 38095117]     {CVE-2025-38073}
    - virtio_ring: Fix data race by tagging event_triggered as racy for KCSAN (Zhongqiu Han) [Orabug:
    38094958] {CVE-2025-38048}
    - scsi: target: iscsi: Fix timeout on deleted connection (Dmitry Bogdanov) [Orabug: 38095134]     {CVE-2025-38075}
    - usb: typec: ucsi: displayport: Fix deadlock (Andrei Kuchynski) [Orabug: 37977018] {CVE-2025-37967}
    - Bluetooth: btnxpuart: Fix kernel panic during FW release (Neeraj Sanjay Kale) [Orabug: 37844459]     {CVE-2025-22102}
    - iio: light: opt3001: fix deadlock due to concurrent flag access (Luca Ceresoli) [Orabug: 37977026]     {CVE-2025-37968}
    - mm/page_alloc: fix race condition in unaccepted memory handling (Kirill A. Shutemov) [Orabug: 38094767]     {CVE-2025-38008}
    - dmaengine: idxd: Refactor remove call with idxd_cleanup() helper (Shuai Xue) [Orabug: 38094790]     {CVE-2025-38014}
    - dmaengine: idxd: fix memory leak in error handling path of idxd_alloc (Shuai Xue) [Orabug: 38094793]     {CVE-2025-38015}
    - dmaengine: ti: k3-udma: Add missing locking (Ronald Wahl) [Orabug: 38094756] {CVE-2025-38005}
    - wifi: mt76: disable napi on driver removal (Fedor Pchelkin) [Orabug: 38094770] {CVE-2025-38009}
    - phy: tegra: xusb: Use a bitmask for UTMI pad power state tracking (Wayne Chang) [Orabug: 38094777]     {CVE-2025-38010}
    - drm/amdgpu: csa unmap use uninterruptible lock (Philip Yang) [Orabug: 38094779] {CVE-2025-38011}
    - HID: bpf: abort dispatch if device destroyed (Rongrong) [Orabug: 38094796] {CVE-2025-38016}
    - sched_ext: bpf_iter_scx_dsq_new() should always initialize iterator (Tejun Heo) [Orabug: 38094786]     {CVE-2025-38012}
    - net/tls: fix kernel panic when alloc_page failed (Pengtao He) [Orabug: 38094802] {CVE-2025-38018}
    - mlxsw: spectrum_router: Fix use-after-free when deleting GRE net devices (Ido Schimmel) [Orabug:
    38094804] {CVE-2025-38019}
    - wifi: mac80211: Set n_channels after allocating struct cfg80211_scan_request (Kees Cook) [Orabug:
    38094788] {CVE-2025-38013}
    - regulator: max20086: fix invalid memory access (Cosmin Tanislav) [Orabug: 38094833] {CVE-2025-38027}
    - net/mlx5e: Disable MACsec offload for uplink representor profile (Carolina Jubran) [Orabug: 38094808]     {CVE-2025-38020}
    - net_sched: Flush gso_skb list too during ->change() (Cong Wang) [Orabug: 37998128] {CVE-2025-37992}
    - RDMA/core: Fix 'KASAN: slab-use-after-free Read in ib_register_device' problem (Zhu Yanjun) [Orabug:
    38094813] {CVE-2025-38022}
    - nfs: handle failure of nfs_get_lock_context in unlock path (Li Lingfeng) [Orabug: 38094818]     {CVE-2025-38023}
    - HID: uclogic: Add NULL check in uclogic_input_configured() (Henry Martin) [Orabug: 38094764]     {CVE-2025-38007}
    - RDMA/rxe: Fix slab-use-after-free Read in rxe_queue_cleanup bug (Zhu Yanjun) [Orabug: 38094827]     {CVE-2025-38024}
    - arm64: bpf: Only mitigate cBPF programs loaded by unprivileged users (James Morse) [Orabug: 37977004]     {CVE-2025-37963}
    - arm64: bpf: Add BHB mitigation to the epilogue for cBPF programs (James Morse) [Orabug: 37976926]     {CVE-2025-37948}
    - usb: typec: ucsi: displayport: Fix NULL pointer access (Andrei Kuchynski) [Orabug: 38015126]     {CVE-2025-37994}
    - module: ensure that kobject_put() is safe for module type kobjects (Dmitry Antipov) [Orabug: 38015131]     {CVE-2025-37995}
    - memblock: Accept allocated memory before use in memblock_double_array() (Tom Lendacky) [Orabug:
    37976994] {CVE-2025-37960}
    - xenbus: Use kref to track req lifetime (Jason Andryuk) [Orabug: 37976934] {CVE-2025-37949}
    - smb: client: Avoid race in open_cached_dir with lease breaks (Paul Aurich) [Orabug: 37976959]     {CVE-2025-37954}
    - drm/amd/display: Fix invalid context error in dml helper (Roman Li) [Orabug: 37977185] {CVE-2025-37965}
    - drm/v3d: Add job to pending list if the reset was skipped (Maira Canal) [Orabug: 37976942]     {CVE-2025-37951}
    - iio: imu: st_lsm6dsx: fix possible lockup in st_lsm6dsx_read_tagged_fifo (Silvano Seva) [Orabug:
    37977031] {CVE-2025-37969}
    - iio: imu: st_lsm6dsx: fix possible lockup in st_lsm6dsx_read_fifo (Silvano Seva) [Orabug: 37977037]     {CVE-2025-37970}
    - KVM: SVM: Forcibly leave SMM mode on SHUTDOWN interception (Mikhail Lobanov) [Orabug: 37976977]     {CVE-2025-37957}
    - mm/huge_memory: fix dereferencing invalid pmd migration entry (Gavin Guo) [Orabug: 37976982]     {CVE-2025-37958}
    - x86/mm: Eliminate window where TLB flushes may be inadvertently skipped (Dave Hansen) [Orabug: 37977013]     {CVE-2025-37964}
    - staging: bcm2835-camera: Initialise dev in v4l2_dev (Dave Stevenson) [Orabug: 37977042] {CVE-2025-37971}
    - Input: mtk-pmic-keys - fix possible null pointer dereference (Gary Bisson) [Orabug: 37977044]     {CVE-2025-37972}
    - bpf: Scrub packet on bpf_redirect_peer (Paul Chaignon) [Orabug: 37976990] {CVE-2025-37959}
    - netfilter: ipset: fix region locking in hash types (Jozsef Kadlecsik) [Orabug: 38015141]     {CVE-2025-37997}
    - ipvs: fix uninit-value for saddr in do_output_route4 (Julian Anastasov) [Orabug: 37976996]     {CVE-2025-37961}
    - can: m_can: m_can_class_allocate_dev(): initialize spin lock on device probe (Antonios Salios) [Orabug:
    38015123] {CVE-2025-37993}
    - virtio-net: free xsk_buffs on error in virtnet_xsk_pool_enable() (Jakub Kicinski) [Orabug: 37976969]     {CVE-2025-37955}
    - sch_htb: make htb_deactivate() idempotent (Cong Wang) [Orabug: 37977176] {CVE-2025-37953}
    - ksmbd: fix memory leak in parse_lease_state() (Zhaolong Wang) [Orabug: 37977180] {CVE-2025-37962}
    - openvswitch: Fix unsafe attribute parsing in output_userspace() (Eelco Chaudron) [Orabug: 38015148]     {CVE-2025-37998}
    - ksmbd: Fix UAF in __close_file_table_ids (Sean Heelan) [Orabug: 37976951] {CVE-2025-37952}
    - ksmbd: prevent out-of-bounds stream writes by validating *pos (Norbert Szetei) [Orabug: 37976923]     {CVE-2025-37947}
    - ksmbd: prevent rename with empty string (Namjae Jeon) [Orabug: 37976972] {CVE-2025-37956}
    - s390/pci: Fix duplicate pci_dev_put() in disable_slot() when PF has child VFs (Niklas Schnelle) [Orabug:
    37976920] {CVE-2025-37946}
    - wifi: cfg80211: fix out-of-bounds access during multi-link element defragmentation (Veerendranath     Jakkam) [Orabug: 37977046] {CVE-2025-37973}
    - s390/pci: Fix missing check for zpci_create_device() error return (Niklas Schnelle) [Orabug: 37977050]     {CVE-2025-37974}
    - fs/erofs/fileio: call erofs_onlinefolio_split() after bio_add_folio() (Max Kellermann) [Orabug:
    38015155] {CVE-2025-37999}
    - mlxbf-bootctl: use sysfs_emit_at() in secure_boot_fuse_state_show() (David Thompson) [Orabug:
    37964051,38037120] {CVE-2025-37866}

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

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

The 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 Pro 24.04 LTS Realtime Kernel host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-7652-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-58055, CVE-2024-58077, CVE-2024-58080, CVE-2024-58082, CVE-2025-21743,     CVE-2024-57953, CVE-2024-57994, CVE-2025-21806, CVE-2024-58007, CVE-2024-58002, CVE-2024-57974,     CVE-2024-57980, CVE-2025-21720, CVE-2024-57990, CVE-2025-21725, CVE-2024-58057, CVE-2024-58018,     CVE-2024-58011, CVE-2025-21814, CVE-2025-21799, CVE-2024-58017, CVE-2024-58014, CVE-2025-21731,     CVE-2024-58072, CVE-2024-58069, CVE-2024-58006, CVE-2024-57984, CVE-2025-21710, CVE-2024-58061,     CVE-2024-57997, CVE-2024-57975, CVE-2025-21724, CVE-2025-37974, CVE-2025-21808, CVE-2024-58056,     CVE-2025-21753, CVE-2024-58068, CVE-2025-21728, CVE-2025-21714, CVE-2024-58054, CVE-2025-21741,     CVE-2025-21736, CVE-2025-21715, CVE-2025-21802, CVE-2025-21739, CVE-2025-21727, CVE-2025-21749,     CVE-2024-58053, CVE-2024-58081, CVE-2025-21828, CVE-2025-21705, CVE-2024-58051, CVE-2024-57979,     CVE-2025-21754, CVE-2025-21734, CVE-2025-21829, CVE-2025-21735, CVE-2025-21826, CVE-2025-21738,     CVE-2024-58079, CVE-2025-21815, CVE-2025-21708, CVE-2024-57986, CVE-2024-58085, CVE-2025-21801,     CVE-2024-58071, CVE-2025-21810, CVE-2025-21726, CVE-2025-21744, CVE-2025-21830, CVE-2025-21748,     CVE-2024-58001, CVE-2024-58063, CVE-2024-57996, CVE-2025-21716, CVE-2024-58013, CVE-2024-58019,     CVE-2025-21811, CVE-2025-21711, CVE-2024-58076, CVE-2024-58070, CVE-2024-57982, CVE-2024-57998,     CVE-2025-21745, CVE-2025-21804, CVE-2024-57973, CVE-2024-58083, CVE-2025-21742, CVE-2025-37750,     CVE-2025-21733, CVE-2025-21750, CVE-2024-57981, CVE-2025-21718, CVE-2024-58058, CVE-2024-49887,     CVE-2024-58003, CVE-2024-57993, CVE-2024-57999, CVE-2024-58010, CVE-2025-21825, CVE-2025-21732,     CVE-2025-21719, CVE-2025-21721, CVE-2024-58034, CVE-2024-58005, CVE-2025-21707, CVE-2025-21809,     CVE-2024-58078, CVE-2025-21812, CVE-2024-58016, CVE-2025-21816, CVE-2024-58052, CVE-2025-21722,     CVE-2025-21832, CVE-2025-21723, CVE-2025-21820, CVE-2025-21798)

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 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: ksmbd: fix racy issue from session     lookup and expire Increment the session reference count within the lock for lookup to avoid racy issue     with session expire. (CVE-2024-58087)

  - In the Linux kernel, the following vulnerability has been resolved: nouveau: fix instmem race condition     around ptr stores Running a lot of VK CTS in parallel against nouveau, once every few hours you might see     something like this crash. BUG: kernel NULL pointer dereference, address: 0000000000000008 PGD     8000000114e6e067 P4D 8000000114e6e067 PUD 109046067 PMD 0 Oops: 0000 [#1] PREEMPT SMP PTI CPU: 7 PID:
    53891 Comm: deqp-vk Not tainted 6.8.0-rc6+ #27 Hardware name: Gigabyte Technology Co., Ltd. Z390 I AORUS     PRO WIFI/Z390 I AORUS PRO WIFI-CF, BIOS F8 11/05/2021 RIP: 0010:gp100_vmm_pgt_mem+0xe3/0x180 [nouveau]     Code: c7 48 01 c8 49 89 45 58 85 d2 0f 84 95 00 00 00 41 0f b7 46 12 49 8b 7e 08 89 da 42 8d 2c f8 48 8b     47 08 41 83 c7 01 48 89 ee <48> 8b 40 08 ff d0 0f 1f 00 49 8b 7e 08 48 89 d9 48 8d 75 04 48 c1 RSP:
    0000:ffffac20c5857838 EFLAGS: 00010202 RAX: 0000000000000000 RBX: 00000000004d8001 RCX: 0000000000000001     RDX: 00000000004d8001 RSI: 00000000000006d8 RDI: ffffa07afe332180 RBP: 00000000000006d8 R08:
    ffffac20c5857ad0 R09: 0000000000ffff10 R10: 0000000000000001 R11: ffffa07af27e2de0 R12: 000000000000001c     R13: ffffac20c5857ad0 R14: ffffa07a96fe9040 R15: 000000000000001c FS: 00007fe395eed7c0(0000)     GS:ffffa07e2c980000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2:
    0000000000000008 CR3: 000000011febe001 CR4: 00000000003706f0 DR0: 0000000000000000 DR1: 0000000000000000     DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: ... ?     gp100_vmm_pgt_mem+0xe3/0x180 [nouveau] ? gp100_vmm_pgt_mem+0x37/0x180 [nouveau] nvkm_vmm_iter+0x351/0xa20     [nouveau] ? __pfx_nvkm_vmm_ref_ptes+0x10/0x10 [nouveau] ? __pfx_gp100_vmm_pgt_mem+0x10/0x10 [nouveau] ?
    __pfx_gp100_vmm_pgt_mem+0x10/0x10 [nouveau] ? __lock_acquire+0x3ed/0x2170 ?
    __pfx_gp100_vmm_pgt_mem+0x10/0x10 [nouveau] nvkm_vmm_ptes_get_map+0xc2/0x100 [nouveau] ?
    __pfx_nvkm_vmm_ref_ptes+0x10/0x10 [nouveau] ? __pfx_gp100_vmm_pgt_mem+0x10/0x10 [nouveau]     nvkm_vmm_map_locked+0x224/0x3a0 [nouveau] Adding any sort of useful debug usually makes it go away, so I     hand wrote the function in a line, and debugged the asm. Every so often pt->memory->ptrs is NULL. This     ptrs ptr is set in the nv50_instobj_acquire called from nvkm_kmap. If Thread A and Thread B both get to     nv50_instobj_acquire around the same time, and Thread A hits the refcount_set line, and in lockstep thread     B succeeds at refcount_inc_not_zero, there is a chance the ptrs value won't have been stored since     refcount_set is unordered. Force a memory barrier here, I picked smp_mb, since we want it on all CPUs and     it's write followed by a read. v2: use paired smp_rmb/smp_wmb. (CVE-2024-26984)

  - In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Fix use-after-free bugs     caused by sco_sock_timeout When the sco connection is established and then, the sco socket is releasing,     timeout_work will be scheduled to judge whether the sco disconnection is timeout. The sock will be     deallocated later, but it is dereferenced again in sco_sock_timeout. As a result, the use-after-free bugs     will happen. The root cause is shown below: Cleanup Thread | Worker Thread sco_sock_release |     sco_sock_close | __sco_sock_close | sco_sock_set_timer | schedule_delayed_work | sco_sock_kill | (wait a     time) sock_put(sk) //FREE | sco_sock_timeout | sock_hold(sk) //USE The KASAN report triggered by POC is     shown below: [ 95.890016] ================================================================== [ 95.890496]     BUG: KASAN: slab-use-after-free in sco_sock_timeout+0x5e/0x1c0 [ 95.890755] Write of size 4 at addr     ffff88800c388080 by task kworker/0:0/7 ... [ 95.890755] Workqueue: events sco_sock_timeout [ 95.890755]     Call Trace: [ 95.890755] <TASK> [ 95.890755] dump_stack_lvl+0x45/0x110 [ 95.890755]     print_address_description+0x78/0x390 [ 95.890755] print_report+0x11b/0x250 [ 95.890755] ?
    __virt_addr_valid+0xbe/0xf0 [ 95.890755] ? sco_sock_timeout+0x5e/0x1c0 [ 95.890755]     kasan_report+0x139/0x170 [ 95.890755] ? update_load_avg+0xe5/0x9f0 [ 95.890755] ?     sco_sock_timeout+0x5e/0x1c0 [ 95.890755] kasan_check_range+0x2c3/0x2e0 [ 95.890755]     sco_sock_timeout+0x5e/0x1c0 [ 95.890755] process_one_work+0x561/0xc50 [ 95.890755]     worker_thread+0xab2/0x13c0 [ 95.890755] ? pr_cont_work+0x490/0x490 [ 95.890755] kthread+0x279/0x300 [     95.890755] ? pr_cont_work+0x490/0x490 [ 95.890755] ? kthread_blkcg+0xa0/0xa0 [ 95.890755]     ret_from_fork+0x34/0x60 [ 95.890755] ? kthread_blkcg+0xa0/0xa0 [ 95.890755] ret_from_fork_asm+0x11/0x20 [     95.890755] </TASK> [ 95.890755] [ 95.890755] Allocated by task 506: [ 95.890755]     kasan_save_track+0x3f/0x70 [ 95.890755] __kasan_kmalloc+0x86/0x90 [ 95.890755] __kmalloc+0x17f/0x360 [     95.890755] sk_prot_alloc+0xe1/0x1a0 [ 95.890755] sk_alloc+0x31/0x4e0 [ 95.890755] bt_sock_alloc+0x2b/0x2a0     [ 95.890755] sco_sock_create+0xad/0x320 [ 95.890755] bt_sock_create+0x145/0x320 [ 95.890755]
    __sock_create+0x2e1/0x650 [ 95.890755] __sys_socket+0xd0/0x280 [ 95.890755] __x64_sys_socket+0x75/0x80 [     95.890755] do_syscall_64+0xc4/0x1b0 [ 95.890755] entry_SYSCALL_64_after_hwframe+0x67/0x6f [ 95.890755] [     95.890755] Freed by task 506: [ 95.890755] kasan_save_track+0x3f/0x70 [ 95.890755]     kasan_save_free_info+0x40/0x50 [ 95.890755] poison_slab_object+0x118/0x180 [ 95.890755]
    __kasan_slab_free+0x12/0x30 [ 95.890755] kfree+0xb2/0x240 [ 95.890755] __sk_destruct+0x317/0x410 [     95.890755] sco_sock_release+0x232/0x280 [ 95.890755] sock_close+0xb2/0x210 [ 95.890755] __fput+0x37f/0x770     [ 95.890755] task_work_run+0x1ae/0x210 [ 95.890755] get_signal+0xe17/0xf70 [ 95.890755]     arch_do_signal_or_restart+0x3f/0x520 [ 95.890755] syscall_exit_to_user_mode+0x55/0x120 [ 95.890755]     do_syscall_64+0xd1/0x1b0 [ 95.890755] entry_SYSCALL_64_after_hwframe+0x67/0x6f [ 95.890755] [ 95.890755]     The buggy address belongs to the object at ffff88800c388000 [ 95.890755] which belongs to the cache     kmalloc-1k of size 1024 [ 95.890755] The buggy address is located 128 bytes inside of [ 95.890755] freed     1024-byte region [ffff88800c388000, ffff88800c388400) [ 95.890755] [ 95.890755] The buggy address belongs     to the physical page: [ 95.890755] page: refcount:1 mapcount:0 mapping:0000000000000000     index:0xffff88800c38a800 pfn:0xc388 [ 95.890755] head: order:3 entire_mapcount:0 nr_pages_mapped:0     pincount:0 [ 95.890755] ano ---truncated--- (CVE-2024-27398)

  - In the Linux kernel, the following vulnerability has been resolved: firewire: nosy: ensure user_length is     taken into account when fetching packet contents Ensure that packet_buffer_get respects the user_length     provided. If the length of the head packet exceeds the user_length, packet_buffer_get will now return 0 to     signify to the user that no data were read and a larger buffer size is required. Helps prevent user space     overflows. (CVE-2024-27401)

  - In the Linux kernel, the following vulnerability has been resolved: riscv: process: Fix kernel gp leakage     childregs represents the registers which are active for the new thread in user context. For a kernel     thread, childregs->gp is never used since the kernel gp is not touched by switch_to. For a user mode     helper, the gp value can be observed in user space after execve or possibly by other means. [From the     email thread] The /* Kernel thread */ comment is somewhat inaccurate in that it is also used for     user_mode_helper threads, which exec a user process, e.g. /sbin/init or when /proc/sys/kernel/core_pattern     is a pipe. Such threads do not have PF_KTHREAD set and are valid targets for ptrace etc. even before they     exec. childregs is the *user* context during syscall execution and it is observable from userspace in at     least five ways: 1. kernel_execve does not currently clear integer registers, so the starting register     state for PID 1 and other user processes started by the kernel has sp = user stack, gp = kernel
    __global_pointer$, all other integer registers zeroed by the memset in the patch comment. This is a bug in     its own right, but I'm unwilling to bet that it is the only way to exploit the issue addressed by this     patch. 2. ptrace(PTRACE_GETREGSET): you can PTRACE_ATTACH to a user_mode_helper thread before it execs,     but ptrace requires SIGSTOP to be delivered which can only happen at user/kernel boundaries. 3.
    /proc/*/task/*/syscall: this is perfectly happy to read pt_regs for user_mode_helpers before the exec     completes, but gp is not one of the registers it returns. 4. PERF_SAMPLE_REGS_USER: LOCKDOWN_PERF normally     prevents access to kernel addresses via PERF_SAMPLE_REGS_INTR, but due to this bug kernel addresses are     also exposed via PERF_SAMPLE_REGS_USER which is permitted under LOCKDOWN_PERF. I have not attempted to     write exploit code. 5. Much of the tracing infrastructure allows access to user registers. I have not     attempted to determine which forms of tracing allow access to user registers without already allowing     access to kernel registers. (CVE-2024-35871)

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 / 24.10 host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-7521-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;

    - Serial ATA and Parallel ATA drivers;

    - Drivers core;

    - Network block device driver;

    - Bluetooth drivers;

    - Character device driver;

    - TPM device driver;

    - Clock framework and drivers;

    - Hardware crypto device drivers;

    - FireWire subsystem;

    - EFI core;

    - Qualcomm firmware drivers;

    - GPIO subsystem;

    - GPU drivers;

    - HID subsystem;

    - I2C subsystem;

    - I3C subsystem;

    - InfiniBand drivers;

    - Input Device (Mouse) drivers;

    - IOMMU subsystem;

    - Multiple devices driver;

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

    - S/390 drivers;

    - SCSI subsystem;

    - QCOM SoC drivers;

    - SPI subsystem;

    - Media staging drivers;

    - Trusted Execution Environment drivers;

    - TTY drivers;

    - UFS subsystem;

    - USB Device Class drivers;

    - USB core drivers;

    - USB Gadget drivers;

    - USB Host Controller drivers;

    - Framebuffer layer;

    - File systems infrastructure;

    - BTRFS file system;

    - Ceph distributed file system;

    - Network file system (NFS) client;

    - Network file system (NFS) server daemon;

    - NILFS2 file system;

    - Overlay file system;

    - SMB network file system;

    - UBI file system;

    - BPF subsystem;

    - Timer subsystem;

    - KVM subsystem;

    - Networking core;

    - ptr_ring data structure definitions;

    - Networking subsytem;

    - Amateur Radio drivers;

    - L3 Master device support module;

    - TCP network protocol;

    - XFRM subsystem;

    - Tracing infrastructure;

    - io_uring subsystem;

    - Process Accounting mechanism;

    - Perf events;

    - Padata parallel execution mechanism;

    - printk logging mechanism;

    - Scheduler infrastructure;

    - Workqueue subsystem;

    - Memory management;

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

    - Bluetooth subsystem;

    - IPv4 networking;

    - IPv6 networking;

    - MAC80211 subsystem;

    - Multipath TCP;

    - Netfilter;

    - NFC subsystem;

    - Open vSwitch;

    - Rose network layer;

    - RxRPC session sockets;

    - Network traffic control;

    - Wireless networking;

    - Key management;

    - Landlock security;

    - Linux Security Modules (LSM) Framework;

    - Tomoyo security module;

    - SoC audio core drivers;

    - SOF drivers; (CVE-2025-21737, CVE-2025-21711, CVE-2025-21987, CVE-2025-21848, CVE-2024-49570,     CVE-2025-21762, CVE-2025-21738, CVE-2025-21712, CVE-2025-21719, CVE-2025-21870, CVE-2024-57984,     CVE-2025-21815, CVE-2025-21744, CVE-2024-58058, CVE-2024-58078, CVE-2024-57990, CVE-2024-54458,     CVE-2025-21899, CVE-2025-21814, CVE-2025-21746, CVE-2024-54456, CVE-2025-21739, CVE-2024-58057,     CVE-2025-21855, CVE-2025-21758, CVE-2024-58006, CVE-2024-58007, CVE-2025-21720, CVE-2024-58090,     CVE-2025-21852, CVE-2024-57982, CVE-2024-58013, CVE-2024-58082, CVE-2025-21825, CVE-2024-58072,     CVE-2024-57996, CVE-2025-21787, CVE-2025-21742, CVE-2025-21705, CVE-2025-21829, CVE-2024-58060,     CVE-2025-21811, CVE-2025-21900, CVE-2025-21853, CVE-2025-21809, CVE-2025-21938, CVE-2025-21728,     CVE-2025-21785, CVE-2025-21732, CVE-2025-21888, CVE-2025-21768, CVE-2025-21875, CVE-2025-21721,     CVE-2025-21766, CVE-2025-21892, CVE-2024-57953, CVE-2025-21772, CVE-2025-21735, CVE-2024-58017,     CVE-2024-58086, CVE-2024-58084, CVE-2025-21761, CVE-2024-58008, CVE-2024-57988, CVE-2025-21874,     CVE-2024-58011, CVE-2025-21706, CVE-2024-57999, CVE-2025-21858, CVE-2024-58061, CVE-2025-21727,     CVE-2025-21780, CVE-2024-58051, CVE-2025-21791, CVE-2025-21788, CVE-2025-21786, CVE-2024-58012,     CVE-2024-58010, CVE-2024-58001, CVE-2025-21844, CVE-2025-21708, CVE-2024-57834, CVE-2025-21873,     CVE-2025-21704, CVE-2025-21765, CVE-2025-21839, CVE-2025-21723, CVE-2024-57974, CVE-2025-21876,     CVE-2025-21782, CVE-2025-21866, CVE-2024-58076, CVE-2025-21724, CVE-2025-21895, CVE-2025-21770,     CVE-2025-21835, CVE-2024-58052, CVE-2025-21827, CVE-2024-58069, CVE-2025-21828, CVE-2025-21734,     CVE-2025-21781, CVE-2025-21971, CVE-2025-21775, CVE-2024-52559, CVE-2024-58020, CVE-2025-21713,     CVE-2024-58068, CVE-2024-58018, CVE-2025-21806, CVE-2025-21802, CVE-2025-21731, CVE-2025-21741,     CVE-2025-21847, CVE-2025-21767, CVE-2024-58003, CVE-2024-57993, CVE-2025-21725, CVE-2025-21796,     CVE-2025-21764, CVE-2025-21862, CVE-2025-21733, CVE-2024-58075, CVE-2025-21808, CVE-2024-58034,     CVE-2025-21707, CVE-2024-58080, CVE-2025-21784, CVE-2024-57994, CVE-2025-21890, CVE-2025-21754,     CVE-2024-58063, CVE-2025-21826, CVE-2025-21821, CVE-2024-58079, CVE-2024-58056, CVE-2025-21798,     CVE-2024-58077, CVE-2024-58019, CVE-2025-21748, CVE-2025-21759, CVE-2024-58004, CVE-2024-58081,     CVE-2024-57978, CVE-2025-21865, CVE-2024-58002, CVE-2025-21810, CVE-2025-21743, CVE-2024-57989,     CVE-2025-21718, CVE-2024-57987, CVE-2025-21877, CVE-2024-57973, CVE-2024-58070, CVE-2024-58071,     CVE-2025-21891, CVE-2024-58021, CVE-2024-58016, CVE-2024-58005, CVE-2025-21760, CVE-2025-21883,     CVE-2025-21878, CVE-2025-21881, CVE-2025-21838, CVE-2025-21783, CVE-2024-57986, CVE-2025-21793,     CVE-2025-21859, CVE-2025-21792, CVE-2025-21820, CVE-2025-21799, CVE-2025-21750, CVE-2025-21795,     CVE-2025-21854, CVE-2025-21836, CVE-2025-21726, CVE-2025-21846, CVE-2025-21864, CVE-2024-57977,     CVE-2025-21887, CVE-2025-21710, CVE-2025-21889, CVE-2025-21812, CVE-2025-21773, CVE-2024-57852,     CVE-2025-21856, CVE-2025-21871, CVE-2025-21763, CVE-2024-58064, CVE-2025-21804, CVE-2024-58055,     CVE-2025-21898, CVE-2025-21776, CVE-2025-21869, CVE-2025-21745, CVE-2025-21736, CVE-2025-21716,     CVE-2024-57981, CVE-2024-57979, CVE-2025-21715, CVE-2024-57998, CVE-2025-21790, CVE-2024-58085,     CVE-2025-21749, CVE-2024-58088, CVE-2025-21753, CVE-2025-21851, CVE-2024-58054, CVE-2025-21830,     CVE-2025-21832, CVE-2024-57980, CVE-2025-21885, CVE-2025-21863, CVE-2024-58053, CVE-2025-21823,     CVE-2025-21857, CVE-2024-58083, CVE-2024-58014, CVE-2025-21816, CVE-2025-21779, CVE-2025-21872,     CVE-2024-57997, CVE-2025-21867, CVE-2024-57985, CVE-2025-21831, CVE-2025-21801, CVE-2025-21868,     CVE-2025-21849)

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 SLED15 / SLED_SAP15 / SLES15 / SLES_SAP15 / openSUSE 15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2025:1180-1 advisory.

    The SUSE Linux Enterprise 15 SP6 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-57979: kABI workaround for pps changes (bsc#1238521).
    - 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-21733: tracing/osnoise: Fix resetting of tracepoints (bsc#1238494).
    - 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-21754: btrfs: fix assertion failure when splitting ordered extent after transaction abort     (bsc#1238496).
    - 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 SUSE Linux SLES15 / openSUSE 15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2025:1178-1 advisory.

    The SUSE Linux Enterprise 15 SP6 RT 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-57979: kABI workaround for pps changes (bsc#1238521).
    - 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-21733: tracing/osnoise: Fix resetting of tracepoints (bsc#1238494).
    - 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-21754: btrfs: fix assertion failure when splitting ordered extent after transaction abort     (bsc#1238496).
    - 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 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-4102 advisory.

    -------------------------------------------------------------------------     Debian LTS Advisory DLA-4102-1                debian-lts@lists.debian.org     https://www.debian.org/lts/security/                        Ben Hutchings     March 31, 2025                                https://wiki.debian.org/LTS
    -------------------------------------------------------------------------

    Package        : linux-6.1     Version        : 6.1.129-1~deb11u1     CVE ID         : CVE-2024-26596 CVE-2024-40945 CVE-2024-42069 CVE-2024-42122                      CVE-2024-45001 CVE-2024-47726 CVE-2024-49989 CVE-2024-50061                      CVE-2024-54458 CVE-2024-56549 CVE-2024-57834 CVE-2024-57973                      CVE-2024-57978 CVE-2024-57979 CVE-2024-57980 CVE-2024-57981                      CVE-2024-57986 CVE-2024-57993 CVE-2024-57996 CVE-2024-57997                      CVE-2024-57998 CVE-2024-58001 CVE-2024-58007 CVE-2024-58009                      CVE-2024-58010 CVE-2024-58011 CVE-2024-58013 CVE-2024-58014                      CVE-2024-58016 CVE-2024-58017 CVE-2024-58020 CVE-2024-58034                      CVE-2024-58051 CVE-2024-58052 CVE-2024-58054 CVE-2024-58055                      CVE-2024-58056 CVE-2024-58058 CVE-2024-58061 CVE-2024-58063                      CVE-2024-58068 CVE-2024-58069 CVE-2024-58071 CVE-2024-58072                      CVE-2024-58076 CVE-2024-58077 CVE-2024-58080 CVE-2024-58083                      CVE-2024-58085 CVE-2024-58086 CVE-2025-21684 CVE-2025-21700                      CVE-2025-21701 CVE-2025-21703 CVE-2025-21704 CVE-2025-21705                      CVE-2025-21706 CVE-2025-21707 CVE-2025-21708 CVE-2025-21711                      CVE-2025-21715 CVE-2025-21716 CVE-2025-21718 CVE-2025-21719                      CVE-2025-21722 CVE-2025-21724 CVE-2025-21725 CVE-2025-21726                      CVE-2025-21727 CVE-2025-21728 CVE-2025-21731 CVE-2025-21734                      CVE-2025-21735 CVE-2025-21736 CVE-2025-21738 CVE-2025-21744                      CVE-2025-21745 CVE-2025-21748 CVE-2025-21749 CVE-2025-21750                      CVE-2025-21753 CVE-2025-21758 CVE-2025-21760 CVE-2025-21761                      CVE-2025-21762 CVE-2025-21763 CVE-2025-21764 CVE-2025-21765                      CVE-2025-21766 CVE-2025-21767 CVE-2025-21772 CVE-2025-21775                      CVE-2025-21776 CVE-2025-21779 CVE-2025-21780 CVE-2025-21781                      CVE-2025-21782 CVE-2025-21785 CVE-2025-21787 CVE-2025-21790                      CVE-2025-21791 CVE-2025-21792 CVE-2025-21794 CVE-2025-21795                      CVE-2025-21796 CVE-2025-21799 CVE-2025-21802 CVE-2025-21804                      CVE-2025-21806 CVE-2025-21811 CVE-2025-21812 CVE-2025-21814                      CVE-2025-21819 CVE-2025-21820 CVE-2025-21821 CVE-2025-21823                      CVE-2025-21826 CVE-2025-21829 CVE-2025-21830 CVE-2025-21832                      CVE-2025-21835     Debian Bug     : 1071562 1087807 1088159 1091517 1091858 1093371 1095435                      1095745 1095764 1098250 1098354 1099138

    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     6.1.129-1~deb11u1.  This additionally includes many more bug fixes     from stable update 6.1.129, and a fix for a regression affecting some     Rockchip SoCs.

    We recommend that you upgrade your linux-6.1 packages.

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

    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 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: clk: qcom: dispcc-sm6350: Add missing     parent_map for a clock If a clk_rcg2 has a parent, it should also have parent_map defined, otherwise we'll     get a NULL pointer dereference when calling clk_set_rate like the following: [ 3.388105] Call trace: [     3.390664] qcom_find_src_index+0x3c/0x70 (P) [ 3.395301] qcom_find_src_index+0x1c/0x70 (L) [ 3.399934]
    _freq_tbl_determine_rate+0x48/0x100 [ 3.404753] clk_rcg2_determine_rate+0x1c/0x28 [ 3.409387]     clk_core_determine_round_nolock+0x58/0xe4 [ 3.421414] clk_core_round_rate_nolock+0x48/0xfc [ 3.432974]     clk_core_round_rate_nolock+0xd0/0xfc [ 3.444483] clk_core_set_rate_nolock+0x8c/0x300 [ 3.455886]     clk_set_rate+0x38/0x14c Add the parent_map property for the clock where it's missing and also un-inline     the parent_data as well to keep the matching parent_map and parent_data together. (CVE-2024-58080)

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

ID	Name	Product	Family	Type	Severity
332461	Photon OS 5.0: Linux PHSA-2025-5.0-91-0486	Nessus	PhotonOS Local Security Checks	Local	high
261430	Ubuntu 22.04 LTS / 24.04 LTS : Linux kernel (Azure) vulnerabilities (USN-7737-1)	Nessus	Ubuntu Local Security Checks	Local	high
252244	Oracle Linux 10 / 9 : Unbreakable Enterprise kernel (ELSA-2025-20530)	Nessus	Oracle Linux Local Security Checks	Local	medium
242830	NewStart CGSL MAIN 7.02 : kernel Multiple Vulnerabilities (NS-SA-2025-0118)	Nessus	NewStart CGSL Local Security Checks	Local	high
242347	Oracle Linux 10 / 9 : Unbreakable Enterprise kernel (ELSA-2025-20480)	Nessus	Oracle Linux Local Security Checks	Local	medium
242344	Ubuntu 22.04 LTS : Linux kernel (HWE) vulnerabilities (USN-7653-1)	Nessus	Ubuntu Local Security Checks	Local	high
242342	Ubuntu Pro 24.04 LTS Realtime Kernel : Linux kernel (Real-time) vulnerabilities (USN-7652-1)	Nessus	Ubuntu Local Security Checks	Local	high
242282	Ubuntu 24.04 LTS : Linux kernel vulnerabilities (USN-7651-1)	Nessus	Ubuntu Local Security Checks	Local	high
240769	SUSE SLES15 Security Update : kernel (SUSE-SU-2025:01919-1)	Nessus	SuSE Local Security Checks	Local	medium
238008	NewStart CGSL MAIN 7.02 : kernel Multiple Vulnerabilities (NS-SA-2025-0084)	Nessus	NewStart CGSL Local Security Checks	Local	high
236983	Ubuntu 24.04 LTS / 24.10 : Linux kernel vulnerabilities (USN-7521-1)	Nessus	Ubuntu Local Security Checks	Local	high
234120	SUSE SLED15 / SLES15 / openSUSE 15 Security Update : kernel (SUSE-SU-2025:1180-1)	Nessus	SuSE Local Security Checks	Local	high
234058	SUSE SLES15: cluster-md-kmp-rt / dlm-kmp-rt / gfs2-kmp-rt / kernel-devel-rt / etc (SUSE-SU-2025:1178-1)	Nessus	SuSE Local Security Checks	Local	high
234057	SUSE SLES15: cluster-md-kmp-azure / dlm-kmp-azure / gfs2-kmp-azure / etc (SUSE-SU-2025:1177-1)	Nessus	SuSE Local Security Checks	Local	high
233595	Debian dla-4102 : linux-config-6.1 - security update	Nessus	Debian Local Security Checks	Local	high
232764	Photon OS 5.0: Linux PHSA-2025-5.0-0486	Nessus	PhotonOS Local Security Checks	Local	high
232239	Linux Distros Unpatched Vulnerability : CVE-2024-58080	Nessus	Misc.	Local	medium

Detections

Analytics

CVE-2024-58080

medium

Tenable Plugins

high

high

medium

high

medium

high

high

high

medium

high

high

high

high

high

high

high

medium