In the Linux kernel, the following vulnerability has been resolved: OPP: Fix race between OPP addition and lookup A race exists between dev_pm_opp_add_dynamic() and dev_pm_opp_find_freq_exact(): CPU0 (add) CPU1 (lookup) ------------------------------- ------------------------------ _opp_add() mutex_lock() list_add(&new_opp->node, head) mutex_unlock() _opp_table_find_key() mutex_lock() dev_pm_opp_get(opp) kref_get() mutex_unlock() kref_init(&new_opp->kref) dev_pm_opp_put() kref_put_mutex() The newly added OPP is inserted into the list before its kref is initialized. A concurrent lookup can find this OPP and increment its reference count while it is still uninitialized, leading to refcount corruption and a potential premature free. Fix this by initializing ->kref and ->opp_table before making the OPP visible via list_add(). This ensures any concurrent lookup observes a fully initialized object. [ Viresh: Updated commit log ]

The Rocky Linux 9.6 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.6:CLSA-2026:1793100968 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: udf: Avoid double brelse() in     udf_rename() syzbot reported a warning like below [1]: VFS: brelse: Trying to free free buffer WARNING:
    CPU: 2 PID: 7301 at fs/buffer.c:1145 __brelse+0x67/0xa0 ... Call Trace: <TASK>     invalidate_bh_lru+0x99/0x150 smp_call_function_many_cond+0xe2a/0x10c0 ?     generic_remap_file_range_prep+0x50/0x50 ? __brelse+0xa0/0xa0 ? __mutex_lock+0x21c/0x12d0 ?     smp_call_on_cpu+0x250/0x250 ? rcu_read_lock_sched_held+0xb/0x60 ? lock_release+0x587/0x810 ?
    __brelse+0xa0/0xa0 ? generic_remap_file_range_prep+0x50/0x50 on_each_cpu_cond_mask+0x3c/0x80     blkdev_flush_mapping+0x13a/0x2f0 blkdev_put_whole+0xd3/0xf0 blkdev_put+0x222/0x760     deactivate_locked_super+0x96/0x160 deactivate_super+0xda/0x100 cleanup_mnt+0x222/0x3d0     task_work_run+0x149/0x240 ? task_work_cancel+0x30/0x30 do_exit+0xb29/0x2a40 ?     reacquire_held_locks+0x4a0/0x4a0 ? do_raw_spin_lock+0x12a/0x2b0 ? mm_update_next_owner+0x7c0/0x7c0 ?     rwlock_bug.part.0+0x90/0x90 ? zap_other_threads+0x234/0x2d0 do_group_exit+0xd0/0x2a0
    __x64_sys_exit_group+0x3a/0x50 do_syscall_64+0x34/0xb0 entry_SYSCALL_64_after_hwframe+0x63/0xcd The cause     of the issue is that brelse() is called on both ofibh.sbh and ofibh.ebh by udf_find_entry() when it     returns NULL. However, brelse() is called by udf_rename(), too. So, b_count on buffer_head becomes     unbalanced. This patch fixes the issue by not calling brelse() by udf_rename() when udf_find_entry()     returns NULL. (CVE-2022-50755)

  - In the Linux kernel, the following vulnerability has been resolved: soc: qcom: qmi_encdec: Restrict string     length in decode The QMI TLV value for strings in a lot of qmi element info structures account for null     terminated strings with MAX_LEN + 1. If a string is actually MAX_LEN + 1 length, this will cause an out of     bounds access when the NULL character is appended in decoding. (CVE-2023-53729)

  - In the Linux kernel, the following vulnerability has been resolved: can: isotp: check CAN address family     in isotp_bind() Add missing check to block non-AF_CAN binds. Syzbot created some code which matched the     right sockaddr struct size but used AF_XDP (0x2C) instead of AF_CAN (0x1D) in the address family field:
    bind$xdp(r2, &(0x7f0000000540)={0x2c, 0x0, r4, 0x0, r2}, 0x10) ^^^^ This has no funtional impact but the     userspace should be notified about the wrong address family field content. (CVE-2023-54105)

  - In the Linux kernel, the following vulnerability has been resolved: usb: rndis_host: Secure rndis_query     check against int overflow Variables off and len typed as uint32 in rndis_query function are controlled by     incoming RNDIS response message thus their value may be manipulated. Setting off to a unexpectetly large     value will cause the sum with len and 8 to overflow and pass the implemented validation step. Consequently     the response pointer will be referring to a location past the expected buffer boundaries allowing     information leakage e.g. via RNDIS_OID_802_3_PERMANENT_ADDRESS OID. (CVE-2023-54110)

  - In the Linux kernel, the following vulnerability has been resolved: mtd: spi-nor: Fix shift-out-of-bounds     in spi_nor_set_erase_type spi_nor_set_erase_type() was used either to set or to mask out an erase type.
    When we used it to mask out an erase type a shift-out-of-bounds was hit: UBSAN: shift-out-of-bounds in     drivers/mtd/spi-nor/core.c:2237:24 shift exponent 4294967295 is too large for 32-bit type 'int' The     setting of the size_{shift, mask} and of the opcode are unnecessary when the erase size is zero, as     throughout the code just the erase size is considered to determine whether an erase type is supported or     not. Setting the opcode to 0xFF was wrong too as nobody guarantees that 0xFF is an unused opcode. Thus     when masking out an erase type, just set the erase size to zero. This will fix the shift-out-of-bounds.
    [ta: refine changes, new commit message, fix compilation error] (CVE-2023-54295)

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

The AlmaLinux 9.6 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.6:CLSA-2026:1793100968 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: udf: Avoid double brelse() in     udf_rename() syzbot reported a warning like below [1]: VFS: brelse: Trying to free free buffer WARNING:
    CPU: 2 PID: 7301 at fs/buffer.c:1145 __brelse+0x67/0xa0 ... Call Trace: <TASK>     invalidate_bh_lru+0x99/0x150 smp_call_function_many_cond+0xe2a/0x10c0 ?     generic_remap_file_range_prep+0x50/0x50 ? __brelse+0xa0/0xa0 ? __mutex_lock+0x21c/0x12d0 ?     smp_call_on_cpu+0x250/0x250 ? rcu_read_lock_sched_held+0xb/0x60 ? lock_release+0x587/0x810 ?
    __brelse+0xa0/0xa0 ? generic_remap_file_range_prep+0x50/0x50 on_each_cpu_cond_mask+0x3c/0x80     blkdev_flush_mapping+0x13a/0x2f0 blkdev_put_whole+0xd3/0xf0 blkdev_put+0x222/0x760     deactivate_locked_super+0x96/0x160 deactivate_super+0xda/0x100 cleanup_mnt+0x222/0x3d0     task_work_run+0x149/0x240 ? task_work_cancel+0x30/0x30 do_exit+0xb29/0x2a40 ?     reacquire_held_locks+0x4a0/0x4a0 ? do_raw_spin_lock+0x12a/0x2b0 ? mm_update_next_owner+0x7c0/0x7c0 ?     rwlock_bug.part.0+0x90/0x90 ? zap_other_threads+0x234/0x2d0 do_group_exit+0xd0/0x2a0
    __x64_sys_exit_group+0x3a/0x50 do_syscall_64+0x34/0xb0 entry_SYSCALL_64_after_hwframe+0x63/0xcd The cause     of the issue is that brelse() is called on both ofibh.sbh and ofibh.ebh by udf_find_entry() when it     returns NULL. However, brelse() is called by udf_rename(), too. So, b_count on buffer_head becomes     unbalanced. This patch fixes the issue by not calling brelse() by udf_rename() when udf_find_entry()     returns NULL. (CVE-2022-50755)

  - In the Linux kernel, the following vulnerability has been resolved: soc: qcom: qmi_encdec: Restrict string     length in decode The QMI TLV value for strings in a lot of qmi element info structures account for null     terminated strings with MAX_LEN + 1. If a string is actually MAX_LEN + 1 length, this will cause an out of     bounds access when the NULL character is appended in decoding. (CVE-2023-53729)

  - In the Linux kernel, the following vulnerability has been resolved: can: isotp: check CAN address family     in isotp_bind() Add missing check to block non-AF_CAN binds. Syzbot created some code which matched the     right sockaddr struct size but used AF_XDP (0x2C) instead of AF_CAN (0x1D) in the address family field:
    bind$xdp(r2, &(0x7f0000000540)={0x2c, 0x0, r4, 0x0, r2}, 0x10) ^^^^ This has no funtional impact but the     userspace should be notified about the wrong address family field content. (CVE-2023-54105)

  - In the Linux kernel, the following vulnerability has been resolved: usb: rndis_host: Secure rndis_query     check against int overflow Variables off and len typed as uint32 in rndis_query function are controlled by     incoming RNDIS response message thus their value may be manipulated. Setting off to a unexpectetly large     value will cause the sum with len and 8 to overflow and pass the implemented validation step. Consequently     the response pointer will be referring to a location past the expected buffer boundaries allowing     information leakage e.g. via RNDIS_OID_802_3_PERMANENT_ADDRESS OID. (CVE-2023-54110)

  - In the Linux kernel, the following vulnerability has been resolved: mtd: spi-nor: Fix shift-out-of-bounds     in spi_nor_set_erase_type spi_nor_set_erase_type() was used either to set or to mask out an erase type.
    When we used it to mask out an erase type a shift-out-of-bounds was hit: UBSAN: shift-out-of-bounds in     drivers/mtd/spi-nor/core.c:2237:24 shift exponent 4294967295 is too large for 32-bit type 'int' The     setting of the size_{shift, mask} and of the opcode are unnecessary when the erase size is zero, as     throughout the code just the erase size is considered to determine whether an erase type is supported or     not. Setting the opcode to 0xFF was wrong too as nobody guarantees that 0xFF is an unused opcode. Thus     when masking out an erase type, just set the erase size to zero. This will fix the shift-out-of-bounds.
    [ta: refine changes, new commit message, fix compilation error] (CVE-2023-54295)

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

The version of kernel installed on the remote host is prior to 5.10.268-266.1092. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.10-2026-132 advisory.

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

    drm/virtio: use uninterruptible resv lock for plane updates (CVE-2026-64098)

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

    bpf: Reject BPF_MAP_TYPE_INODE_STORAGE creation if BPF LSM is uninitialized

    When CONFIG_BPF_LSM=y is set, BPF inode storage maps(BPF_MAP_TYPE_INODE_STORAGE) are compiled into the     kernel. However,if the BPF LSM is not explicitly enabled at boot time (e.g. omittedfrom the lsm= boot     parameter), lsm_prepare() is never executed forthe BPF LSM.

    Consequently, the BPF inode security blob offset(bpf_lsm_blob_sizes.lbs_inode) is never initialized and     remains atits default compiled size of 8 bytes instead of being updated to avalid offset past the reserved     struct rcu_head (typically 16 bytesor more).

    When a privileged user creates and updates a BPF_MAP_TYPE_INODE_STORAGEmap, bpf_inode() evaluates     inode->i_security + 8. This erroneouslyaliases the struct rcu_head.func callback pointer at the     beginningof the inode->i_security blob. During subsequent map element cleanupor inode destruction, writing     NULL to owner_storage clears the queuedRCU callback pointer. When rcu_do_batch() later executes the     queuedcallback, it attempts an instruction fetch at address 0x0, triggeringan immediate kernel panic.

    Fix this by introducing a global bpf_lsm_initialized boolean flagmarked with __ro_after_init. Set this     flag to true inside bpf_lsm_init()when the LSM framework successfully registers the BPF LSM. Gate     mapallocation in inode_storage_map_alloc() on this flag, returning-EOPNOTSUPP if the BPF LSM is in turn     uninitialized.

    This fail-fast approach prevents userspace from allocating inodestorage maps when the supporting BPF LSM     infrastructure is absent,avoiding zombie map states. (CVE-2026-64192)

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

    i2c: core: fix adapter deregistration race (CVE-2026-64279)

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

    libceph: fix two unsafe bare decodes in decode_lockers() (CVE-2026-68082)

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

    audit: fix recursive locking deadlock in audit_dupe_exe() (CVE-2026-68096)

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

    super: fix emergency thaw deadlock on frozen block devices (CVE-2026-68132)

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

    net: gro: fix double aggregation of flush-marked skbs (CVE-2026-68136)

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

    ftrace: Add global mutex to serialize trace_parser access (CVE-2026-68146)

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

    libceph: bound pg_{temp,upmap,upmap_items} length to CEPH_PG_MAX_SIZE (CVE-2026-68159)

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

    sctp: avoid auth_enable sysctl UAF during netns teardown (CVE-2026-68162)

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

    drm/virtio: bound EDID block reads to the response buffer (CVE-2026-68255)

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

    drm/dp/mst: fix OOB reads on 2-byte fields in sideband reply parsers (CVE-2026-68277)

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

    drm/dp/mst: fix buffer overflows in sideband chunk accumulation (CVE-2026-68278)

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

    drm/dp/mst: fix OOB reads in remote DPCD/I2C sideband reply parsers (CVE-2026-68279)

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

    mmc: vub300: fix use-after-free on probe failure (CVE-2026-72073)

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

    scsi: target: Bound PR-OUT TransportID parsing to the received buffer (CVE-2026-72084)

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

    scsi: lpfc: Fix memory leak in lpfc_sli4_driver_resource_setup() (CVE-2026-72087)

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

    dm-verity: make error counter atomic (CVE-2026-72096)

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

    dm-integrity: don't increment hash_offset twice (CVE-2026-72099)

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

    jbd2: fix integer underflow in jbd2_journal_initialize_fast_commit() (CVE-2026-72225)

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

    selinux: avoid sk_socket dereference in selinux_sctp_bind_connect() (CVE-2026-72242)

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

    netfilter: nft_set_pipapo: don't leak bad clone into future transaction (CVE-2026-72252)

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

    netfilter: nf_conntrack_sip: validate skb_dst() before accessing it (CVE-2026-72253)

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

    netfilter: nf_queue: pin bridge device while NFQUEUE holds fake dst (CVE-2026-72255)

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

    KVM: arm64: vgic: Handle race between interrupt affinity change and LPI disabling (CVE-2026-72288)

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

    tipc: restrict socket queue dumps in enqueue tracepoints (CVE-2026-72299)

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

    mlxsw: fix refcount leak in mlxsw_sp_port_lag_join() (CVE-2026-72308)

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

    sctp: add INIT verification after cookie unpacking (CVE-2026-72398)

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

    sctp: fix err_chunk memory leaks in INIT handling (CVE-2026-72413)

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

    netfilter: nft_compat: ebtables emulation must reject non-bridge targets (CVE-2026-72416)

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

    xprtrdma: Repost Receive buffers for malformed replies (CVE-2026-72464)

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

    RDMA/rxe: Fix TOCTOU heap overflow in get_srq_wqe (CVE-2026-74378)

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

    OPP: Fix race between OPP addition and lookup (CVE-2026-74405)

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

    scsi: scsi_debug: Fix REPORT ZONES alloc_len underflow OOB write (CVE-2026-74470)

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

    net: pktgen: fix proc entry use-after-free (CVE-2026-74479)

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

    binfmt_misc: restore write access when removing an entry (CVE-2026-74487)

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

    netfilter: nf_tables: make nft_object rhltable per table (CVE-2026-74565)

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

    packet: use consistent hard_header_len in non-ring send paths (CVE-2026-74582)

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

    sched/psi: Shut down rtpoll_timer in psi_cgroup_free() (CVE-2026-74594)

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

    ring-buffer: Use current_context for safe per-CPU buffer swap (CVE-2026-74601)

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

    net/sched: act_gact, act_police: range check the fallback control action (CVE-2026-74620)

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

    mm/huge_memory: fix huge_zero_pfn race (CVE-2026-74632)

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

    perf/core: Fix group leader use-after-free after sibling detach (CVE-2026-74637)

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

    ipv4: Fix fib_nlmsg_size() for RTA_VIA nexthops (CVE-2026-74657)

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

    inet: frags: publish queues before arming timer (CVE-2026-74662)

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

    net/sched: reject overly deep qdisc hierarchies (CVE-2026-74663)

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

    packet: synchronize pressure clearing with ring reconfiguration (CVE-2026-74666)

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

    packet: use consistent hard_header_len in TX_RING send path (CVE-2026-74668)

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

    net: tap: set skb->dev before parsing virtio net header in tap_get_user_xdp() (CVE-2026-74684)

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

    net/sched: cls_api: Always acquire rtnl_lock when destroying locked classifiers (CVE-2026-74700)

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

    netfilter: flowtable: publish GC-visible tuple last (CVE-2026-74746)

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

    netfilter: ipset: fix refcount race between list:set GC and swap (CVE-2026-74748)

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

    ceph: fix hanging __ceph_get_caps() with stale mds_wanted (CVE-2026-80527)

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

    ceph: avoid fs reclaim while using current->journal_info (CVE-2026-80528)

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

    xfs: fix ilock leak on error in xfs_dq_get_next_id (CVE-2026-80534)

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

    xfs: bounds-check buffer log item's dirty bitmap (CVE-2026-80536)

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

    libceph: fix OOB read in decode_watchers() via missing bounds check (CVE-2026-80557)

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

    libceph: Avoid using invalid osd indices from primary_temp (CVE-2026-80558)

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

    libceph: fix multiple unsafe decodes in decode_locker() (CVE-2026-80561)

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

    mptcp: options: reset DSS fields in case of unexpected size (CVE-2026-80586)

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

    inet: frags: strip GSO state from fragments before reassembly (CVE-2026-80590)

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

    serial: amba-pl011: synchronize DMA teardown (CVE-2026-80737)

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

    af_packet: Don't send zero-byte data in tpacket_snd(). (CVE-2026-80742)

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

    netfilter: nf_tables_offload: suppress WARN_ON_ONCE for ENOMEM in abort path (CVE-2026-80744)

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

    selinux: do not cancel a policy conversion that never started (CVE-2026-80756)

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

    selinux: reject a class permission count below its inherited common (CVE-2026-80757)

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

    HID: hyperv: validate initial device info bounds (CVE-2026-80765)

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

    HID: core: fix OOB read of field->usage in hid_set_field() (CVE-2026-80781)

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

    ipv6: fix use-after-free in ip6_finish_output2() (CVE-2026-80792)

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

    ipv4: reject undersized MTUs in ip_do_fragment() (CVE-2026-80793)

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

    xfs: validate attr entry pointer before field access (CVE-2026-80805)

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

    ext4: stop retrying saturated xattr cache entries (CVE-2026-80808)

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

    rndis_host: add overflow check in rndis_rx_fixup() (CVE-2026-80814)

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

    net: packet: fix wrong transport_header when sending VLAN-tagged frame (CVE-2026-80906)

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

    selinux: require every boolean value to be defined (CVE-2026-80913)

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

    HID: core: fix number/pointer type confusion on long items (CVE-2026-80918)

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

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

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

    It was discovered that some Arm processors could complete a broadcast translation lookaside buffer (TLB)     invalidation before memory writes made through the invalidated translation were globally observed. A local     attacker could possibly use this to write to memory after permission to do so had been revoked, bypassing     memory protections or escalating privileges. (CVE-2025-10263)

    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;

    - User-space API (UAPI);

    - Kernel build system;

    - ARM32 architecture;

    - PowerPC architecture;

    - RISC-V architecture;

    - S390 architecture;

    - User-Mode Linux (UML);

    - x86 architecture;

    - Cryptographic API;

    - Intel NPU Driver;

    - Compute Acceleration Framework;

    - ACPI drivers;

    - Drivers core;

    - DRBD Distributed Replicated Block Device drivers;

    - Rados block device (RBD) driver;

    - Ublk userspace block driver;

    - Compressed RAM block device driver;

    - Bluetooth drivers;

    - Hardware crypto device drivers;

    - CXL (Compute Express Link) drivers;

    - Arm Firmware Framework for ARMv8-A(FFA);

    - EFI core;

    - FPGA Framework;

    - GPU drivers;

    - HID subsystem;

    - Hardware monitoring drivers;

    - I2C subsystem;

    - I3C subsystem;

    - InfiniBand drivers;

    - Input Device core drivers;

    - Input Device (Mouse) drivers;

    - IOMMU subsystem;

    - Multiple devices driver;

    - Media drivers;

    - Fastrpc Driver;

    - Network drivers;

    - Mellanox network drivers;

    - Microsoft Azure Network Adapter (MANA) driver;

    - MediaTek network drivers;

    - NVME drivers;

    - Operating Performance Points (OPP) driver;

    - PCI subsystem;

    - PTP clock framework;

    - RPMSG subsystem;

    - SCSI subsystem;

    - SoundWire subsystem;

    - SPI subsystem;

    - Greybus lights staging drivers;

    - Media staging drivers;

    - NVIDIA Tegra embedded controller (NVEC) staging driver;

    - Realtek RTL8723BS SDIO drivers;

    - TCM subsystem;

    - Trusted Execution Environment drivers;

    - Thunderbolt and USB4 drivers;

    - TTY drivers;

    - USB Gadget drivers;

    - USB Dual Role (OTG-ready) Controller drivers;

    - USB Serial drivers;

    - vDPA drivers;

    - VFIO drivers;

    - Virtio Host (VHOST) subsystem;

    - Virtio drivers;

    - Xen hypervisor drivers;

    - 9P distributed file system;

    - AFS file system;

    - File systems infrastructure;

    - BTRFS file system;

    - Ceph distributed file system;

    - exFAT file system;

    - F2FS file system;

    - GFS2 file system;

    - HFS file system;

    - HFS+ file system;

    - JFS file system;

    - Network file systems library;

    - Network file system (NFS) client;

    - Network file system (NFS) server daemon;

    - NTFS3 file system;

    - OCFS2 file system;

    - OrangeFS file system;

    - SMB network file system;

    - BPF subsystem;

    - File system encryption (fscrypt);

    - Software nodes and device properties;

    - IPv4 networking;

    - KVM subsystem;

    - Mellanox drivers;

    - Memory management;

    - Networking core;

    - Netfilter;

    - Socket messages infrastructure;

    - MediaTek SoC drivers;

    - Sun RPC protocol;

    - Network traffic control;

    - IPv6 networking;

    - Amateur Radio drivers;

    - Bluetooth subsystem;

    - IP tunnels definitions;

    - KCM (Kernel Connection Multiplexor) sockets driver;

    - MultiProtocol Label Switching driver;

    - TCP network protocol;

    - XFRM subsystem;

    - Tracing infrastructure;

    - io_uring subsystem;

    - Control group (cgroup);

    - Perf events;

    - IRQ subsystem;

    - Locking primitives;

    - KProbes tracing;

    - 9P file system network protocol;

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

    - Ethernet bridge;

    - CAN network layer;

    - Ceph Core library;

    - Handshake API;

    - HSR network protocol;

    - IFE protocol;

    - L2TP protocol;

    - MAC80211 subsystem;

    - IEEE 802.15.4 subsystem;

    - Multipath TCP;

    - NFC subsystem;

    - Open vSwitch;

    - Phonet protocol;

    - RDS protocol;

    - RxRPC session sockets;

    - SCTP protocol;

    - SMC sockets;

    - TIPC protocol;

    - TLS protocol;

    - Unix domain sockets;

    - VMware vSockets driver;

    - Wireless networking;

    - X.25 network layer;

    - eXpress Data Path;

    - Rust bindings mechanism;

    - AppArmor security module;

    - Key management;

    - Linux Security Modules (LSM) Framework;

    - SELinux security module;

    - ALSA framework;

    - AudioScience HPI driver;

    - Intel ASoC drivers;

    - USB sound devices; (CVE-2024-14040, CVE-2024-35948, CVE-2024-41008, CVE-2024-43872, CVE-2024-44932,     CVE-2024-44964, CVE-2024-49932, CVE-2024-49940, CVE-2024-50106, CVE-2024-50217, CVE-2024-52560,     CVE-2024-53098, CVE-2024-56552, CVE-2024-56591, CVE-2024-57857, CVE-2024-58089, CVE-2024-58094,     CVE-2024-58098, CVE-2024-58100, CVE-2024-58241, CVE-2025-21687, CVE-2025-21693, CVE-2025-21984,     CVE-2025-21985, CVE-2025-22104, CVE-2025-22108, CVE-2025-22109, CVE-2025-23132, CVE-2025-37776,     CVE-2025-37876, CVE-2025-37906, CVE-2025-38064, CVE-2025-38069, CVE-2025-38187, CVE-2025-38204,     CVE-2025-38206, CVE-2025-38242, CVE-2025-38498, CVE-2025-38563, CVE-2025-38565, CVE-2025-38636,     CVE-2025-38717, CVE-2025-39677, CVE-2025-39789, CVE-2025-39859, CVE-2025-39862, CVE-2025-39896,     CVE-2025-39933, CVE-2025-39958, CVE-2025-39990, CVE-2025-40025, CVE-2025-40040, CVE-2025-40054,     CVE-2025-40064, CVE-2025-40074, CVE-2025-40075, CVE-2025-40139, CVE-2025-40158, CVE-2025-40168,     CVE-2025-40170, CVE-2025-40203, CVE-2025-40274, CVE-2025-40344, CVE-2025-40354, CVE-2025-68174,     CVE-2025-68304, CVE-2025-68360, CVE-2025-68745, CVE-2025-68822, CVE-2025-71073, CVE-2025-71074,     CVE-2025-71202, CVE-2025-71289, CVE-2026-23208, CVE-2026-23239, CVE-2026-23240, CVE-2026-23327,     CVE-2026-23393, CVE-2026-23469, CVE-2026-31420, CVE-2026-31479, CVE-2026-31486, CVE-2026-31493,     CVE-2026-31560, CVE-2026-31568, CVE-2026-31630, CVE-2026-31663, CVE-2026-31771, CVE-2026-43009,     CVE-2026-43029, CVE-2026-43042, CVE-2026-43048, CVE-2026-43101, CVE-2026-43116, CVE-2026-43126,     CVE-2026-43172, CVE-2026-43213, CVE-2026-43263, CVE-2026-43303, CVE-2026-43352, CVE-2026-43353,     CVE-2026-43464, CVE-2026-45850, CVE-2026-45894, CVE-2026-45932, CVE-2026-45944, CVE-2026-46054,     CVE-2026-46130, CVE-2026-46158, CVE-2026-46170, CVE-2026-46175, CVE-2026-46181, CVE-2026-46203,     CVE-2026-46275, CVE-2026-46315, CVE-2026-46320, CVE-2026-46324, CVE-2026-46330, CVE-2026-52908,     CVE-2026-52909, CVE-2026-52910, CVE-2026-52912, CVE-2026-52915, CVE-2026-52916, CVE-2026-52918,     CVE-2026-52919, CVE-2026-52921, CVE-2026-52922, CVE-2026-52926, CVE-2026-52934, CVE-2026-52941,     CVE-2026-52956, CVE-2026-52988, CVE-2026-52991, CVE-2026-53000, CVE-2026-53005, CVE-2026-53009,     CVE-2026-53024, CVE-2026-53025, CVE-2026-53053, CVE-2026-53070, CVE-2026-53078, CVE-2026-53089,     CVE-2026-53090, CVE-2026-53091, CVE-2026-53109, CVE-2026-53118, CVE-2026-53120, CVE-2026-53129,     CVE-2026-53131, CVE-2026-53132, CVE-2026-53133, CVE-2026-53148, CVE-2026-53159, CVE-2026-53182,     CVE-2026-53183, CVE-2026-53185, CVE-2026-53186, CVE-2026-53196, CVE-2026-53198, CVE-2026-53216,     CVE-2026-53217, CVE-2026-53221, CVE-2026-53230, CVE-2026-53232, CVE-2026-53239, CVE-2026-53250,     CVE-2026-53254, CVE-2026-53256, CVE-2026-53262, CVE-2026-53264, CVE-2026-53266, CVE-2026-53269,     CVE-2026-53270, CVE-2026-53273, CVE-2026-53275, CVE-2026-53281, CVE-2026-53284, CVE-2026-53354,     CVE-2026-53355, CVE-2026-53357, CVE-2026-53358, CVE-2026-53361, CVE-2026-53368, CVE-2026-53384,     CVE-2026-53398, CVE-2026-53399, CVE-2026-63795, CVE-2026-63796, CVE-2026-63797, CVE-2026-63800,     CVE-2026-63801, CVE-2026-63804, CVE-2026-63807, CVE-2026-63808, CVE-2026-63815, CVE-2026-63818,     CVE-2026-63825, CVE-2026-63828, CVE-2026-63829, CVE-2026-63830, CVE-2026-63831, CVE-2026-63853,     CVE-2026-63858, CVE-2026-63886, CVE-2026-63887, CVE-2026-63888, CVE-2026-63893, CVE-2026-63906,     CVE-2026-63912, CVE-2026-63914, CVE-2026-63915, CVE-2026-63916, CVE-2026-63917, CVE-2026-63919,     CVE-2026-63921, CVE-2026-63922, CVE-2026-63924, CVE-2026-63926, CVE-2026-63940, CVE-2026-63944,     CVE-2026-63945, CVE-2026-63946, CVE-2026-63947, CVE-2026-63948, CVE-2026-63952, CVE-2026-63974,     CVE-2026-63975, CVE-2026-63976, CVE-2026-63978, CVE-2026-63979, CVE-2026-63980, CVE-2026-63984,     CVE-2026-63992, CVE-2026-63993, CVE-2026-63994, CVE-2026-64000, CVE-2026-64007, CVE-2026-64010,     CVE-2026-64011, CVE-2026-64015, CVE-2026-64018, CVE-2026-64025, CVE-2026-64029, CVE-2026-64032,     CVE-2026-64033, CVE-2026-64034, CVE-2026-64039, CVE-2026-64046, CVE-2026-64047, CVE-2026-64048,     CVE-2026-64051, CVE-2026-64055, CVE-2026-64056, CVE-2026-64064, CVE-2026-64073, CVE-2026-64076,     CVE-2026-64077, CVE-2026-64082, CVE-2026-64083, CVE-2026-64084, CVE-2026-64085, CVE-2026-64086,     CVE-2026-64087, CVE-2026-64088, CVE-2026-64089, CVE-2026-64091, CVE-2026-64092, CVE-2026-64093,     CVE-2026-64096, CVE-2026-64097, CVE-2026-64098, CVE-2026-64099, CVE-2026-64102, CVE-2026-64103,     CVE-2026-64106, CVE-2026-64108, CVE-2026-64109, CVE-2026-64111, CVE-2026-64112, CVE-2026-64113,     CVE-2026-64114, CVE-2026-64115, CVE-2026-64116, CVE-2026-64117, CVE-2026-64118, CVE-2026-64121,     CVE-2026-64125, CVE-2026-64126, CVE-2026-64127, CVE-2026-64128, CVE-2026-64133, CVE-2026-64134,     CVE-2026-64135, CVE-2026-64136, CVE-2026-64137, CVE-2026-64138, CVE-2026-64144, CVE-2026-64147,     CVE-2026-64148, CVE-2026-64153, CVE-2026-64155, CVE-2026-64160, CVE-2026-64163, CVE-2026-64165,     CVE-2026-64166, CVE-2026-64168, CVE-2026-64170, CVE-2026-64173, CVE-2026-64174, CVE-2026-64177,     CVE-2026-64178, CVE-2026-64179, CVE-2026-64180, CVE-2026-64182, CVE-2026-64183, CVE-2026-64184,     CVE-2026-64185, CVE-2026-64191, CVE-2026-64206, CVE-2026-64214, CVE-2026-64217, CVE-2026-64218,     CVE-2026-64219, CVE-2026-64220, CVE-2026-64221, CVE-2026-64225, CVE-2026-64231, CVE-2026-64237,     CVE-2026-64247, CVE-2026-64249, CVE-2026-64268, CVE-2026-64269, CVE-2026-64280, CVE-2026-64303,     CVE-2026-64313, CVE-2026-64315, CVE-2026-64319, CVE-2026-64320, CVE-2026-64355, CVE-2026-64361,     CVE-2026-64364, CVE-2026-64382, CVE-2026-64383, CVE-2026-64384, CVE-2026-64385, CVE-2026-64386,     CVE-2026-64387, CVE-2026-64390, CVE-2026-64391, CVE-2026-64392, CVE-2026-64393, CVE-2026-64394,     CVE-2026-64396, CVE-2026-64397, CVE-2026-64399, CVE-2026-64400, CVE-2026-64408, CVE-2026-64438,     CVE-2026-64441, CVE-2026-64445, CVE-2026-64450, CVE-2026-64475, CVE-2026-64510, CVE-2026-64518,     CVE-2026-64523, CVE-2026-64529, CVE-2026-64530, CVE-2026-64534, CVE-2026-64535, CVE-2026-64541,     CVE-2026-64548, CVE-2026-64551, CVE-2026-64552, CVE-2026-64554, CVE-2026-64555, CVE-2026-64557,     CVE-2026-64561, CVE-2026-64562, CVE-2026-64564, CVE-2026-64586, CVE-2026-64597, CVE-2026-64598,     CVE-2026-68082, CVE-2026-68083, CVE-2026-68117, CVE-2026-68123, CVE-2026-68124, CVE-2026-68127,     CVE-2026-68136, CVE-2026-68137, CVE-2026-68138, CVE-2026-68144, CVE-2026-68147, CVE-2026-68152,     CVE-2026-68154, CVE-2026-68156, CVE-2026-68158, CVE-2026-68159, CVE-2026-68160, CVE-2026-68161,     CVE-2026-68162, CVE-2026-68198, CVE-2026-68206, CVE-2026-68209, CVE-2026-68210, CVE-2026-68213,     CVE-2026-68228, CVE-2026-68229, CVE-2026-68300, CVE-2026-68302, CVE-2026-68343, CVE-2026-68381,     CVE-2026-68388, CVE-2026-68426, CVE-2026-68431, CVE-2026-68457, CVE-2026-68461, CVE-2026-68470,     CVE-2026-68476, CVE-2026-68477, CVE-2026-72014, CVE-2026-72020, CVE-2026-72033, CVE-2026-72041,     CVE-2026-72065, CVE-2026-72069, CVE-2026-72071, CVE-2026-72083, CVE-2026-72084, CVE-2026-72085,     CVE-2026-72098, CVE-2026-72111, CVE-2026-72124, CVE-2026-72125, CVE-2026-72126, CVE-2026-72129,     CVE-2026-72130, CVE-2026-72191, CVE-2026-72192, CVE-2026-72194, CVE-2026-72200, CVE-2026-72217,     CVE-2026-72221, CVE-2026-72222, CVE-2026-72226, CVE-2026-72234, CVE-2026-72251, CVE-2026-72255,     CVE-2026-72288, CVE-2026-72289, CVE-2026-72296, CVE-2026-72299, CVE-2026-72317, CVE-2026-72318,     CVE-2026-72319, CVE-2026-72320, CVE-2026-72322, CVE-2026-72323, CVE-2026-72329, CVE-2026-72339,     CVE-2026-72348, CVE-2026-72351, CVE-2026-72380, CVE-2026-72383, CVE-2026-72398, CVE-2026-72399,     CVE-2026-72421, CVE-2026-72422, CVE-2026-72434, CVE-2026-72436, CVE-2026-72451, CVE-2026-72454,     CVE-2026-72466, CVE-2026-72472, CVE-2026-72473, CVE-2026-72487, CVE-2026-72488, CVE-2026-72489,     CVE-2026-72491, CVE-2026-72494, CVE-2026-72495, CVE-2026-72496, CVE-2026-72499, CVE-2026-74255,     CVE-2026-74264, CVE-2026-74267, CVE-2026-74268, CVE-2026-74269, CVE-2026-74279, CVE-2026-74280,     CVE-2026-74287, CVE-2026-74302, CVE-2026-74305, CVE-2026-74310, CVE-2026-74345, CVE-2026-74350,     CVE-2026-74376, CVE-2026-74384, CVE-2026-74394, CVE-2026-74398, CVE-2026-74401, CVE-2026-74405,     CVE-2026-74406, CVE-2026-74407, CVE-2026-74408, CVE-2026-74410, CVE-2026-74411, CVE-2026-74417,     CVE-2026-74427, CVE-2026-74436, CVE-2026-74439, CVE-2026-74440, CVE-2026-74473, CVE-2026-74474,     CVE-2026-74475, CVE-2026-74476, CVE-2026-74478, CVE-2026-74480, CVE-2026-74493, CVE-2026-74495,     CVE-2026-74521, CVE-2026-74538, CVE-2026-74541, CVE-2026-74556, CVE-2026-74569)

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

  - OPP: Fix race between OPP addition and lookup A race exists between dev_pm_opp_add_dynamic() and     dev_pm_opp_find_freq_exact(): CPU0 (add) CPU1 (lookup) -------------------------------
    ------------------------------ _opp_add() mutex_lock() list_add(&new_opp->node, head) mutex_unlock()
    _opp_table_find_key() mutex_lock() dev_pm_opp_get(opp) kref_get() mutex_unlock() kref_init(&new_opp->kref)     dev_pm_opp_put() kref_put_mutex() The newly added OPP is inserted into the list before its kref is     initialized. A concurrent lookup can find this OPP and increment its reference count while it is still     uninitialized, leading to refcount corruption and a potential premature free. Fix this by initializing
    ->kref and ->opp_table before making the OPP visible via list_add(). This ensures any concurrent lookup     observes a fully initialized object. [ Viresh: Updated commit log ] (CVE-2026-74405)

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

ID	Name	Product	Family	Type	Severity
377578	Ubuntu 24.04 LTS / 26.04 LTS : Linux kernel (NVIDIA) vulnerabilities (USN-9003-1)	Nessus	Ubuntu Local Security Checks	Local	medium
373068	Rocky Linux 9.6 [TuxCare] Security Update: kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1793100968)	Nessus	Rocky Linux Local Security Checks	Local	high
373062	AlmaLinux 9.6 [TuxCare] Security Update: kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1793100968)	Nessus	Alma Linux Local Security Checks	Local	high
365768	Ubuntu 26.04 LTS : Linux kernel (Azure) vulnerabilities (USN-8888-1)	Nessus	Ubuntu Local Security Checks	Local	medium
365767	Ubuntu 26.04 LTS : Linux kernel vulnerabilities (USN-8887-1)	Nessus	Ubuntu Local Security Checks	Local	medium
365463	Ubuntu 26.04 LTS : Linux kernel (OEM) vulnerabilities (USN-8889-1)	Nessus	Ubuntu Local Security Checks	Local	medium
351061	Amazon Linux 2 : kernel (ALASKERNEL-5.10-2026-132)	Nessus	Amazon Linux Local Security Checks	Local	medium
348386	Ubuntu 24.04 LTS / Pro Realtime 24.04 LTS : Linux kernel (NVIDIA Tegra) vulnerabilities (USN-8781-1)	Nessus	Ubuntu Local Security Checks	Local	high
341880	Amazon Linux 2023 : bpftool6.18, kernel6.18, kernel6.18-devel (ALAS2023-2026-2071)	Nessus	Amazon Linux Local Security Checks	Local	high
335638	Linux Distros Unpatched Vulnerability : CVE-2026-74405	Nessus	Misc.	Local	high

Detections

Analytics

CVE-2026-74405

high

Tenable Plugins

medium

high

high

medium

medium

medium

medium

high

high

high