The version of kernel installed on the remote Azure Linux 3.0 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the CVE-2024-41009 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: bpf: Fix overrunning reservations in     ringbuf The BPF ring buffer internally is implemented as a power-of-2 sized circular buffer, with two     logical and ever-increasing counters: consumer_pos is the consumer counter to show which logical position     the consumer consumed the data, and producer_pos which is the producer counter denoting the amount of data     reserved by all producers. Each time a record is reserved, the producer that owns the record will     successfully advance producer counter. In user space each time a record is read, the consumer of the data     advanced the consumer counter once it finished processing. Both counters are stored in separate pages so     that from user space, the producer counter is read-only and the consumer counter is read-write. One aspect     that simplifies and thus speeds up the implementation of both producers and consumers is how the data area     is mapped twice contiguously back-to-back in the virtual memory, allowing to not take any special measures     for samples that have to wrap around at the end of the circular buffer data area, because the next page     after the last data page would be first data page again, and thus the sample will still appear completely     contiguous in virtual memory. Each record has a struct bpf_ringbuf_hdr { u32 len; u32 pg_off; } header for     book-keeping the length and offset, and is inaccessible to the BPF program. Helpers like     bpf_ringbuf_reserve() return `(void *)hdr + BPF_RINGBUF_HDR_SZ` for the BPF program to use. Bing-Jhong and     Muhammad reported that it is however possible to make a second allocated memory chunk overlapping with the     first chunk and as a result, the BPF program is now able to edit first chunk's header. For example,     consider the creation of a BPF_MAP_TYPE_RINGBUF map with size of 0x4000. Next, the consumer_pos is     modified to 0x3000 /before/ a call to bpf_ringbuf_reserve() is made. This will allocate a chunk A, which     is in [0x0,0x3008], and the BPF program is able to edit [0x8,0x3008]. Now, lets allocate a chunk B with     size 0x3000. This will succeed because consumer_pos was edited ahead of time to pass the `new_prod_pos -     cons_pos > rb->mask` check. Chunk B will be in range [0x3008,0x6010], and the BPF program is able to edit     [0x3010,0x6010]. Due to the ring buffer memory layout mentioned earlier, the ranges [0x0,0x4000] and     [0x4000,0x8000] point to the same data pages. This means that chunk B at [0x4000,0x4008] is chunk A's     header. bpf_ringbuf_submit() / bpf_ringbuf_discard() use the header's pg_off to then locate the     bpf_ringbuf itself via bpf_ringbuf_restore_from_rec(). Once chunk B modified chunk A's header, then     bpf_ringbuf_commit() refers to the wrong page and could cause a crash. Fix it by calculating the oldest     pending_pos and check whether the range from the oldest outstanding record to the newest would span beyond     the ring buffer size. If that is the case, then reject the request. We've tested with the ring buffer     benchmark in BPF selftests (./benchs/run_bench_ringbufs.sh) before/after the fix and while it seems a bit     slower on some benchmarks, it is still not significantly enough to matter. (CVE-2024-41009)

Note that Nessus has not tested for this issue 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-2024:3195-1 advisory.

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

    The following security bugs were fixed:

    - CVE-2024-41062: Sync sock recv cb and release (bsc#1228576).
    - CVE-2023-52489: Fix race in accessing memory_section->usage (bsc#1221326).
    - CVE-2024-43821: Fix a possible null pointer dereference (bsc#1229315).
    - CVE-2024-43911: Fix NULL dereference at band check in starting tx ba session (bsc#1229827).
    - CVE-2024-42277: Avoid NULL deref in sprd_iommu_hw_en (bsc#1229409).
    - CVE-2024-43880: Put back removed metod in struct objagg_ops (bsc#1229481).
    - CVE-2024-43899: Fix null pointer deref in dcn20_resource.c (bsc#1229754).
    - CVE-2024-43882: Fixed ToCToU between perm check and set-uid/gid usage. (bsc#1229503)
    - CVE-2024-43866: Always drain health in shutdown callback (bsc#1229495).
    - CVE-2024-26812: Struct virqfd kABI workaround (bsc#1222808).
    - CVE-2024-27010: Fix mirred deadlock on device recursion (bsc#1223720).
    - CVE-2024-36881: Fix reset ptes when close() for wr-protected (bsc#1225718).
    - CVE-2024-42316: Fix div-by-zero in vmpressure_calc_level() (bsc#1229353).
    - CVE-2024-43855: Fix deadlock between mddev_suspend and flush bio (bsc#1229342).
    - CVE-2024-43864: Fix CT entry update leaks of modify header context (bsc#1229496).
    - CVE-2024-26631: Fix data-race in ipv6_mc_down / mld_ifc_work (bsc#1221630).
    - CVE-2024-42109: Unconditionally flush pending work before notifier (bsc#1228505).
    - CVE-2024-41084: Avoid null pointer dereference in region lookup (bsc#1228472).
    - CVE-2024-40905: Fix possible race in __fib6_drop_pcpu_from() (bsc#1227761)
    - CVE-2024-39489: Fix memleak in seg6_hmac_init_algo (bsc#1227623)
    - CVE-2024-36489: Fix missing memory barrier in tls_init (bsc#1226874)
    - CVE-2024-27079: Fix NULL domain on device release (bsc#1223742).
    - CVE-2024-41020: Fix fcntl/close race recovery compat path (bsc#1228427).
    - CVE-2024-35897: Discard table flag update with pending basechain deletion (bsc#1224510).
    - CVE-2024-27403: Restore const specifier in flow_offload_route_init() (bsc#1224415).
    - CVE-2024-27011: Fix memleak in map from abort path (bsc#1223803).
    - CVE-2024-26668: Reject configurations that cause integer overflow (bsc#1222335).
    - CVE-2024-26835: Set dormant flag on hook register failure (bsc#1222967).
    - CVE-2024-26808: Handle NETDEV_UNREGISTER for inet/ingress basechain (bsc#1222634).
    - CVE-2024-26809: Release elements in clone only from destroy path (bsc#1222633).
    - CVE-2023-52581: Fix memleak when more than 255 elements expired (bsc#1220877).
    - CVE-2024-43837: Fix updating attached freplace prog in prog_array map (bsc#1229297).
    - CVE-2024-35939: Fixed leak pages on dma_set_decrypted() failure (bsc#1224535).
    - CVE-2024-42291: Add a per-VF limit on number of FDIR filters (bsc#1229374).
    - CVE-2024-42268: Fix missing lock on sync reset reload (bsc#1229391).
    - CVE-2024-43834: Fix invalid wait context of page_pool_destroy() (bsc#1229314)
    - CVE-2024-27433: Fix an error handling path in clk_mt8135_apmixed_probe() (bsc#1224711).
    - CVE-2024-36286: Acquire rcu_read_lock() in instance_destroy_rcu() (bsc#1226801)
    - CVE-2024-26851: Add protection for bmp length out of range (bsc#1223074)
    - CVE-2024-40920: Fix suspicious rcu usage in br_mst_set_state (bsc#1227781).
    - CVE-2024-40921: Pass vlan group directly to br_mst_vlan_set_state (bsc#1227784).
    - CVE-2024-36979: Fix vlan use-after-free (bsc#1226604).
    - CVE-2024-26590: Fix inconsistent per-file compression format (bsc#1220252).
    - CVE-2023-52859: Fix use-after-free when register pmu fails (bsc#1225582).
    - CVE-2024-42270: Fix null-ptr-deref in iptable_nat_table_init() (bsc#1229404).
    - CVE-2024-42269: Fix potential null-ptr-deref in ip6table_nat_table_init() (bsc#1229402).
    - CVE-2024-42284: Return non-zero value from tipc_udp_addr2str() on error (bsc#1229382)
    - CVE-2024-42283: Initialize all fields in dumped nexthops (bsc#1229383)
    - CVE-2024-42312: Always initialize i_uid/i_gid (bsc#1229357)
    - CVE-2024-43854: Initialize integrity buffer to zero before writing it to media (bsc#1229345)
    - CVE-2024-42322: Properly dereference pe in ip_vs_add_service (bsc#1229347)
    - CVE-2024-42290: Handle runtime power management correctly (bsc#1229379).
    - CVE-2024-42318: Do not lose track of restrictions on cred_transfer (bsc#1229351).
    - CVE-2023-52889: Fix null pointer deref when receiving skb during sock creation (bsc#1229287).
    - CVE-2024-42295: Handle inconsistent state in nilfs_btnode_create_block() (bsc#1229370).
    - CVE-2024-43850: Fix refcount imbalance seen during bwmon_remove (bsc#1229316).
    - CVE-2024-43831: Handle invalid decoder vsi (bsc#1229309).
    - CVE-2024-43839: Adjust 'name' buf size of bna_tcb and bna_ccb structures (bsc#1229301).
    - CVE-2024-41007: Use signed arithmetic in tcp_rtx_probe0_timed_out() (bsc#1227863).
    - CVE-2024-42281: Fix a segment issue when downgrading gso_size (bsc#1229386).
    - CVE-2024-26669: Fix chain template offload (bsc#1222350).
    - CVE-2024-26677: Blacklist e7870cf13d20 (' Fix delayed ACKs to not set the reference serial number')     (bsc#1222387)
    - CVE-2024-41050: Cyclic allocation of msg_id to avoid reuse (bsc#1228499).
    - CVE-2024-41051: Wait for ondemand_object_worker to finish when dropping object (bsc#1228468).
    - CVE-2024-41074: Set object to close if ondemand_id < 0 in copen (bsc#1228643).
    - CVE-2024-41075: Add consistency check for copen/cread (bsc#1228646).
    - CVE-2024-41012: Remove locks reliably when fcntl/close race is detected (bsc#1228247).
    - CVE-2024-41080: Fix possible deadlock in io_register_iowq_max_workers() (bsc#1228616).
    - CVE-2024-42246: Remap EPERM in case of connection failure in xs_tcp_setup_socket (bsc#1228989).
    - CVE-2024-42159: Fix sanitise num_phys (bsc#1228754).
    - CVE-2024-42241: Disable PMD-sized page cache if needed (bsc#1228986).
    - CVE-2024-42245: Revert 'sched/fair: Make sure to try to detach at least one movable task' (bsc#1228978).
    - CVE-2024-26735: Fix possible use-after-free and null-ptr-deref (bsc#1222372).
    - CVE-2024-26837: Race between creation of new group memberships and generation of the list of MDB events     to replay (bsc#1222973).
    - CVE-2024-42155: Wipe copies of protected- and secure-keys (bsc#1228733).
    - CVE-2024-42156: Wipe copies of clear-key structures on failure (bsc#1228722).
    - CVE-2024-42157: Wipe sensitive data on failure (bsc#1228727).
    - CVE-2024-42158: Use kfree_sensitive() to fix Coccinelle warnings (bsc#1228720).
    - CVE-2024-38662: Cover verifier checks for mutating sockmap/sockhash (bsc#1226885).
    - CVE-2024-40938: Fix d_parent walk (bsc#1227840).
    - CVE-2024-42247: Avoid unaligned 64-bit memory accesses (bsc#1228988).
    - CVE-2024-41010: Fix too early release of tcx_entry (bsc#1228021).
    - CVE-2024-42106: Initialize pad field in struct inet_diag_req_v2 (bsc#1228493).
    - CVE-2024-42095: Fix Errata i2310 with RX FIFO level check (bsc#1228446).
    - CVE-2024-41068: Fix sclp_init() cleanup on failure (bsc#1228579).
    - CVE-2024-42138: Fix double memory deallocation in case of invalid INI file (bsc#1228500).
    - CVE-2024-42107: Do not process extts if PTP is disabled (bsc#1228494).
    - CVE-2024-42139: Fix improper extts handling (bsc#1228503).
    - CVE-2024-42110: Move ntb_netdev_rx_handler() to call netif_rx() from __netif_rx() (bsc#1228501).
    - CVE-2024-42113: Initialize num_q_vectors for MSI/INTx interrupts (bsc#1228568).
    - CVE-2024-42148: Fix multiple UBSAN array-index-out-of-bounds (bsc#1228487).
    - CVE-2024-42142: E-switch, Create ingress ACL when needed (bsc#1228491).
    - CVE-2024-42073: Fix memory corruptions on Spectrum-4 systems (bsc#1228457).
    - CVE-2024-42162: Account for stopped queues when reading NIC stats (bsc#1228706).
    - CVE-2024-42082: Remove WARN() from __xdp_reg_mem_model() (bsc#1228482).
    - CVE-2024-40978: Fix crash while reading debugfs attribute (bsc#1227929).
    - CVE-2024-41000: Prefer different overflow check (bsc#1227867).
    - CVE-2024-40995: Fix possible infinite loop in tcf_idr_check_alloc() (bsc#1227830).
    - CVE-2024-42161: Avoid uninitialized value in BPF_CORE_READ_BITFIELD (bsc#1228756).
    - CVE-2024-41069: Fix route memory corruption (bsc#1228644).
    - CVE-2024-39506: Adjust a NULL pointer handling path in lio_vf_rep_copy_packet (bsc#1227729).
    - CVE-2024-42145: Implement a limit on UMAD receive List (bsc#1228743).
    - CVE-2024-40994: Fix integer overflow in max_vclocks_store (bsc#1227829).
    - CVE-2024-42124: Make qedf_execute_tmf() non-preemptible (bsc#1228705).
    - CVE-2024-42096: Stop playing stack games in profile_pc() (bsc#1228633).
    - CVE-2024-42224: Correct check for empty list (bsc#1228723).
    - CVE-2024-41048: Skip zero length skb in sk_msg_recvmsg (bsc#1228565).
    - CVE-2024-40958: Make get_net_ns() handle zero refcount net (bsc#1227812).
    - CVE-2024-40939: Fix tainted pointer delete is case of region creation fail (bsc#1227799).
    - CVE-2024-36933: Use correct mac_offset to unwind gso skb in nsh_gso_segment() (bsc#1225832).
    - CVE-2024-36929: Reject skb_copy(_expand) for fraglist GSO skbs (bsc#1225814).
    - CVE-2024-41044: Reject claimed-as-LCP but actually malformed packets (bsc#1228530).
    - CVE-2024-41066: Add tx check to prevent skb leak (bsc#1228640).
    - CVE-2024-42093: Avoid explicit cpumask var allocation on stack (bsc#1228680).
    - CVE-2024-42122: Add NULL pointer check for kzalloc (bsc#1228591).
    - CVE-2024-41078: Fix quota root leak after quota disable failure (bsc#1228655).
    - CVE-2024-40989: Disassociate vcpus from redistributor region on teardown (bsc#1227823).
    - CVE-2024-41064: Avoid possible crash when edev->pdev changes (bsc#1228599).
    - CVE-2024-41036: Fix deadlock with the SPI chip variant (bsc#1228496).
    - CVE-2024-41040: Fix UAF when resolving a clash (bsc#1228518).
    - CVE-2024-35949: Make sure that WRITTEN is set on all metadata blocks (bsc#1224700).
    - CVE-2024-41081: Block BH in ila_output() (bsc#1228617).
    - CVE-2024-41076: Fix memory leak in nfs4_set_security_label (bsc#1228649).
    - CVE-2024-42079: Fix NULL pointer dereference in gfs2_log_flush (bsc#1228672).
    - CVE-2024-41057: Fix slab-use-after-free in cachefiles_withdraw_cookie() (bsc#1228462).
    - CVE-2024-41058: Fix slab-use-after-free in fscache_withdraw_volume() (bsc#1228459).
    - CVE-2024-41015: Add bounds checking to ocfs2_check_dir_entry() (bsc#1228409).
    - CVE-2024-40956: Fix possible Use-After-Free in irq_process_work_list (bsc#1227810).
    - CVE-2024-27437: Disable auto-enable of exclusive INTx IRQ (bsc#1222625).
    - CVE-2024-41032: Check if a hash-index is in cpu_possible_mask (bsc#1228460).
    - CVE-2024-40957: Fix parameter passing when calling NF_HOOK() in End.DX4 and End.DX6 behaviors     (bsc#1227811).
    - CVE-2024-41041: Set SOCK_RCU_FREE earlier in udp_lib_get_port() (bsc#1228520).
    - CVE-2024-40954: Do not leave a dangling sk pointer, when socket creation fails (bsc#1227808)
    - CVE-2024-42070: Fully validate NFT_DATA_VALUE on store to data registers (bsc#1228470).
    - CVE-2024-41070: Prevent UAF in kvm_spapr_tce_attach_iommu_group() (bsc#1228581).
    - CVE-2024-40959: Check ip6_dst_idev() return value in xfrm6_get_saddr() (bsc#1227884).
    - CVE-2024-41009: Fix overrunning reservations in ringbuf (bsc#1228020).
    - CVE-2024-40909: Fix a potential use-after-free in bpf_link_free() (bsc#1227798).
    - CVE-2024-27024: Fix WARNING in rds_conn_connect_if_down (bsc#1223777).


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 Ubuntu 22.04 LTS host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-7021-5 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:

    - GPU drivers;

    - BTRFS file system;

    - F2FS file system;

    - GFS2 file system;

    - BPF subsystem;

    - Netfilter;

    - RxRPC session sockets;

    - Integrity Measurement Architecture(IMA) framework; (CVE-2024-27012, CVE-2024-38570, CVE-2024-42228,     CVE-2024-41009, CVE-2024-39494, CVE-2024-42160, CVE-2024-39496, CVE-2024-26677)

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 Redhat Enterprise Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2024:10773 advisory.

    The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with     extremely high determinism requirements.

    Security Fix(es):

    * kernel: x86/mm: Randomize per-cpu entry area (CVE-2023-0597)

    * kernel: TCP-spoofed ghost ACKs and leak leak initial sequence number (CVE-2023-52881,RHV-2024-1001)

    * kernel: pstore/ram: Fix crash when setting number of cpus to an odd number (CVE-2023-52619)

    * kernel: nouveau: fix instmem race condition around ptr stores (CVE-2024-26984)

    * kernel: Bluetooth: l2cap: fix null-ptr-deref in l2cap_chan_timeout (CVE-2024-27399)

    * kernel: spi: Fix null dereference on suspend (CVE-2023-52749)

    * kernel: scsi: mpi3mr: Avoid memcpy field-spanning write WARNING (CVE-2024-36920)

    * kernel: tcp: Fix shift-out-of-bounds in dctcp_update_alpha(). (CVE-2024-37356)

    * kernel: drm/radeon: fix UBSAN warning in kv_dpm.c (CVE-2024-40988)

    * kernel: bpf: Fix overrunning reservations in ringbuf (CVE-2024-41009)

    * kernel: xfs: add bounds checking to xlog_recover_process_data (CVE-2024-41014)

    * kernel: udp: Set SOCK_RCU_FREE earlier in udp_lib_get_port() (CVE-2024-41041)

    * kernel: drm/amdgpu: avoid using null object of framebuffer (CVE-2024-41093)

    * kernel: tcp_metrics: validate source addr length (CVE-2024-42154)

    * kernel: x86/bhi: Avoid warning in #DB handler due to BHI mitigation (CVE-2024-42240)

    * kernel: block: initialize integrity buffer to zero before writing it to media (CVE-2024-43854)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise 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 Redhat Enterprise Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2024:10772 advisory.

    The kernel packages contain the Linux kernel, the core of any Linux operating system.

    Security Fix(es):

    * kernel: x86/mm: Randomize per-cpu entry area (CVE-2023-0597)

    * kernel: TCP-spoofed ghost ACKs and leak leak initial sequence number (CVE-2023-52881,RHV-2024-1001)

    * kernel: pstore/ram: Fix crash when setting number of cpus to an odd number (CVE-2023-52619)

    * kernel: nouveau: fix instmem race condition around ptr stores (CVE-2024-26984)

    * kernel: Bluetooth: l2cap: fix null-ptr-deref in l2cap_chan_timeout (CVE-2024-27399)

    * kernel: spi: Fix null dereference on suspend (CVE-2023-52749)

    * kernel: scsi: mpi3mr: Avoid memcpy field-spanning write WARNING (CVE-2024-36920)

    * kernel: tcp: Fix shift-out-of-bounds in dctcp_update_alpha(). (CVE-2024-37356)

    * kernel: drm/radeon: fix UBSAN warning in kv_dpm.c (CVE-2024-40988)

    * kernel: bpf: Fix overrunning reservations in ringbuf (CVE-2024-41009)

    * kernel: xfs: add bounds checking to xlog_recover_process_data (CVE-2024-41014)

    * kernel: udp: Set SOCK_RCU_FREE earlier in udp_lib_get_port() (CVE-2024-41041)

    * kernel: drm/amdgpu: avoid using null object of framebuffer (CVE-2024-41093)

    * kernel: tcp_metrics: validate source addr length (CVE-2024-42154)

    * kernel: x86/bhi: Avoid warning in #DB handler due to BHI mitigation (CVE-2024-42240)

    * kernel: block: initialize integrity buffer to zero before writing it to media (CVE-2024-43854)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise 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 20.04 LTS host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-7021-4 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:

    - GPU drivers;

    - BTRFS file system;

    - F2FS file system;

    - GFS2 file system;

    - BPF subsystem;

    - Netfilter;

    - RxRPC session sockets;

    - Integrity Measurement Architecture(IMA) framework; (CVE-2024-41009, CVE-2024-26677, CVE-2024-42160,     CVE-2024-39494, CVE-2024-39496, CVE-2024-38570, CVE-2024-27012, CVE-2024-42228)

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 version of kernel installed on the remote host is prior to 5.15.164-108.161. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.15-2024-050 advisory.

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

    scsi: core: Fix a use-after-free (CVE-2022-48666)

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

    net: relax socket state check at accept time. (CVE-2024-36484)

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

    ipv6: prevent NULL dereference in ip6_output() (CVE-2024-36901)

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

    bonding: Fix out-of-bounds read in bond_option_arp_ip_targets_set() (CVE-2024-39487)

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

    ima: Avoid blocking in RCU read-side critical section (CVE-2024-40947)

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

    tcp: avoid too many retransmit packets (CVE-2024-41007)

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

    bpf: Fix overrunning reservations in ringbuf (CVE-2024-41009)

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

    filelock: Remove locks reliably when fcntl/close race is detected (CVE-2024-41012)

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

    fs/ntfs3: Validate ff offset (CVE-2024-41019)

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

    filelock: Fix fcntl/close race recovery compat path (CVE-2024-41020)

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

    Fix userfaultfd_api to return EINVAL as expected (CVE-2024-41027)

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

    USB: core: Fix duplicate endpoint bug by clearing reserved bits in the descriptor (CVE-2024-41035)

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

    udp: Set SOCK_RCU_FREE earlier in udp_lib_get_port(). (CVE-2024-41041)

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

    skmsg: Skip zero length skb in sk_msg_recvmsg (CVE-2024-41048)

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

    filelock: fix potential use-after-free in posix_lock_inode (CVE-2024-41049)

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

    mm: prevent derefencing NULL ptr in pfn_section_valid() (CVE-2024-41055)

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

    nvme: avoid double free special payload (CVE-2024-41073)

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

    null_blk: fix validation of block size (CVE-2024-41077)

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

    btrfs: qgroup: fix quota root leak after quota disable failure (CVE-2024-41078)

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

    ila: block BH in ila_output() (CVE-2024-41081)

    kernel: virtio-net: tap: mlx5_core short frame denial of service (CVE-2024-41090)

    kernel: virtio-net: tun: mlx5_core short frame denial of service (CVE-2024-41091)

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

    Revert mm/writeback: fix possible divide-by-zero in wb_dirty_limits(), again (CVE-2024-42102)

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

    btrfs: fix adding block group to a reclaim list and the unused list during reclaim (CVE-2024-42103)

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

    inet_diag: Initialize pad field in struct inet_diag_req_v2 (CVE-2024-42106)

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

    netfilter: nf_tables: unconditionally flush pending work before notifier (CVE-2024-42109)

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

    mm: avoid overflows in dirty throttling logic (CVE-2024-42131)

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

    tcp_metrics: validate source addr length (CVE-2024-42154)

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

    bpf: Avoid uninitialized value in BPF_CORE_READ_BITFIELD (CVE-2024-42161)

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

    crypto: aead,cipher - zeroize key buffer after use (CVE-2024-42229)

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

    libceph: fix race between delayed_work() and ceph_monc_stop() (CVE-2024-42232)

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

    x86/bhi: Avoid warning in #DB handler due to BHI mitigation (CVE-2024-42240)

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

    USB: serial: mos7840: fix crash on resume (CVE-2024-42244)

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

    wireguard: allowedips: avoid unaligned 64-bit memory accesses (CVE-2024-42247)

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 host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-7156-1 advisory.

    Chenyuan Yang discovered that the USB Gadget subsystem in the Linux kernel did not properly check for the     device to be enabled before writing. A local attacker could possibly use this to cause a denial of     service. (CVE-2024-25741)

    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:

    - ARM32 architecture;

    - ARM64 architecture;

    - MIPS architecture;

    - PA-RISC architecture;

    - PowerPC architecture;

    - RISC-V architecture;

    - S390 architecture;

    - User-Mode Linux (UML);

    - x86 architecture;

    - Block layer subsystem;

    - Cryptographic API;

    - Android drivers;

    - Serial ATA and Parallel ATA drivers;

    - ATM drivers;

    - Drivers core;

    - Null block device driver;

    - Ublk userspace block driver;

    - Bluetooth drivers;

    - Cdrom driver;

    - Character device driver;

    - Clock framework and drivers;

    - Hardware crypto device drivers;

    - CXL (Compute Express Link) drivers;

    - Buffer Sharing and Synchronization framework;

    - DMA engine subsystem;

    - Cirrus firmware drivers;

    - Qualcomm firmware drivers;

    - GPIO subsystem;

    - GPU drivers;

    - HID subsystem;

    - Hardware monitoring drivers;

    - I2C subsystem;

    - I3C subsystem;

    - IIO subsystem;

    - InfiniBand drivers;

    - Input Device core drivers;

    - Input Device (Miscellaneous) drivers;

    - IOMMU subsystem;

    - IRQ chip drivers;

    - ISDN/mISDN subsystem;

    - LED subsystem;

    - Mailbox framework;

    - Multiple devices driver;

    - Media drivers;

    - Fastrpc Driver;

    - VMware VMCI Driver;

    - MMC subsystem;

    - Ethernet bonding driver;

    - Network drivers;

    - Mellanox network drivers;

    - Microsoft Azure Network Adapter (MANA) driver;

    - Near Field Communication (NFC) drivers;

    - NVME drivers;

    - NVMEM (Non Volatile Memory) drivers;

    - Device tree and open firmware driver;

    - Parport drivers;

    - PCI subsystem;

    - Pin controllers subsystem;

    - x86 platform drivers;

    - Power supply drivers;

    - Remote Processor subsystem;

    - S/390 drivers;

    - SCSI subsystem;

    - QCOM SoC drivers;

    - SPI subsystem;

    - Direct Digital Synthesis drivers;

    - Thermal drivers;

    - Thunderbolt and USB4 drivers;

    - TTY drivers;

    - UFS subsystem;

    - Userspace I/O drivers;

    - USB DSL drivers;

    - USB core drivers;

    - DesignWare USB3 driver;

    - USB Gadget drivers;

    - USB Host Controller drivers;

    - USB Serial drivers;

    - USB Type-C Connector System Software Interface driver;

    - USB over IP driver;

    - VFIO drivers;

    - Virtio Host (VHOST) subsystem;

    - Framebuffer layer;

    - Xen hypervisor drivers;

    - File systems infrastructure;

    - BTRFS file system;

    - Ext4 file system;

    - F2FS file system;

    - GFS2 file system;

    - JFFS2 file system;

    - JFS file system;

    - Network file systems library;

    - Network file system (NFS) client;

    - Network file system (NFS) server daemon;

    - NILFS2 file system;

    - File system notification infrastructure;

    - NTFS3 file system;

    - Proc file system;

    - SMB network file system;

    - Tracing file system;

    - Bitmap API;

    - BPF subsystem;

    - Syscall compatibility layer;

    - Memory Management;

    - Memory management;

    - Objagg library;

    - Perf events;

    - Syscall interfaces;

    - Virtio network driver;

    - VMware vSockets driver;

    - KCM (Kernel Connection Multiplexor) sockets driver;

    - Netfilter;

    - Tracing infrastructure;

    - io_uring subsystem;

    - Control group (cgroup);

    - DMA mapping infrastructure;

    - Locking primitives;

    - Padata parallel execution mechanism;

    - Scheduler infrastructure;

    - Closures library;

    - Radix Tree data structure library;

    - Kernel userspace event delivery library;

    - KUnit for arithmetic overflow checks;

    - Bluetooth subsystem;

    - Ethernet bridge;

    - CAN network layer;

    - Ceph Core library;

    - Networking core;

    - Ethtool driver;

    - IPv4 networking;

    - IPv6 networking;

    - IUCV driver;

    - MAC80211 subsystem;

    - Multipath TCP;

    - Network traffic control;

    - SCTP protocol;

    - Sun RPC protocol;

    - TIPC protocol;

    - Wireless networking;

    - AppArmor security module;

    - Landlock security;

    - SELinux security module;

    - Simplified Mandatory Access Control Kernel framework;

    - FireWire sound drivers;

    - AMD SoC Alsa drivers;

    - Texas InstrumentS Audio (ASoC/HDA) drivers;

    - SoC Audio for Freescale CPUs drivers;

    - Intel ASoC drivers;

    - MediaTek ASoC drivers;

    - Amlogic Meson SoC drivers;

    - SoC audio core drivers;

    - SOF drivers;

    - Sound sequencer drivers;

    - USB sound devices;

    - Real-Time Linux Analysis tools; (CVE-2024-43911, CVE-2024-46762, CVE-2024-46794, CVE-2024-43843,     CVE-2024-42229, CVE-2024-43888, CVE-2024-44978, CVE-2024-46693, CVE-2024-46695, CVE-2024-42290,     CVE-2024-42067, CVE-2024-45012, CVE-2024-42316, CVE-2024-47665, CVE-2024-41052, CVE-2024-42074,     CVE-2024-41058, CVE-2024-44975, CVE-2024-46709, CVE-2024-46871, CVE-2024-42090, CVE-2024-42296,     CVE-2024-42096, CVE-2024-42146, CVE-2024-46855, CVE-2024-39487, CVE-2024-43825, CVE-2024-42066,     CVE-2024-42126, CVE-2024-41022, CVE-2024-41025, CVE-2023-52888, CVE-2024-46702, CVE-2024-42269,     CVE-2024-41082, CVE-2024-42284, CVE-2024-42227, CVE-2024-41017, CVE-2024-42250, CVE-2024-46778,     CVE-2024-47661, CVE-2024-46727, CVE-2024-46845, CVE-2024-44953, CVE-2024-47659, CVE-2024-42137,     CVE-2024-42245, CVE-2024-41096, CVE-2024-46829, CVE-2024-41053, CVE-2024-46782, CVE-2024-44972,     CVE-2024-41095, CVE-2024-42239, CVE-2024-42127, CVE-2024-42292, CVE-2024-46752, CVE-2024-46679,     CVE-2024-41076, CVE-2024-46784, CVE-2024-46786, CVE-2024-46678, CVE-2024-44957, CVE-2024-46755,     CVE-2024-47660, CVE-2024-41067, CVE-2024-46838, CVE-2024-43879, CVE-2024-45007, CVE-2024-45025,     CVE-2024-45001, CVE-2024-41009, CVE-2024-41051, CVE-2024-46836, CVE-2024-49984, CVE-2024-45028,     CVE-2024-43871, CVE-2024-46783, CVE-2024-42272, CVE-2024-42087, CVE-2024-46785, CVE-2024-42276,     CVE-2024-47658, CVE-2024-46761, CVE-2024-46715, CVE-2024-46676, CVE-2024-43824, CVE-2024-42100,     CVE-2024-46745, CVE-2024-41084, CVE-2024-41086, CVE-2024-45015, CVE-2024-46797, CVE-2024-42160,     CVE-2024-46706, CVE-2024-46803, CVE-2024-46708, CVE-2024-47669, CVE-2024-45009, CVE-2024-41021,     CVE-2024-42159, CVE-2024-42321, CVE-2024-46868, CVE-2024-41078, CVE-2024-42303, CVE-2024-45027,     CVE-2024-42309, CVE-2024-43849, CVE-2024-43907, CVE-2024-43899, CVE-2024-43823, CVE-2024-42232,     CVE-2024-44937, CVE-2024-41046, CVE-2024-42237, CVE-2024-42063, CVE-2024-42065, CVE-2024-42154,     CVE-2024-42259, CVE-2024-46698, CVE-2024-46741, CVE-2024-45020, CVE-2024-42151, CVE-2024-41073,     CVE-2024-46719, CVE-2024-42295, CVE-2024-46859, CVE-2024-41035, CVE-2024-46751, CVE-2024-47667,     CVE-2024-46728, CVE-2024-46824, CVE-2024-42121, CVE-2024-46776, CVE-2024-46768, CVE-2024-43908,     CVE-2024-43900, CVE-2024-46707, CVE-2024-44934, CVE-2024-41062, CVE-2024-42304, CVE-2024-42312,     CVE-2024-42157, CVE-2024-41092, CVE-2024-41041, CVE-2024-43832, CVE-2024-41039, CVE-2024-44962,     CVE-2024-46858, CVE-2024-43856, CVE-2024-41060, CVE-2024-45010, CVE-2024-41044, CVE-2024-44942,     CVE-2024-42307, CVE-2024-44984, CVE-2024-41075, CVE-2024-43817, CVE-2024-46791, CVE-2024-46853,     CVE-2024-42301, CVE-2024-44993, CVE-2024-41094, CVE-2024-27022, CVE-2024-41088, CVE-2024-43883,     CVE-2024-41087, CVE-2024-46780, CVE-2024-42070, CVE-2024-44965, CVE-2024-46823, CVE-2024-46737,     CVE-2024-44982, CVE-2024-46697, CVE-2024-45021, CVE-2024-44987, CVE-2024-41072, CVE-2024-41063,     CVE-2024-46757, CVE-2024-46831, CVE-2024-44966, CVE-2024-42322, CVE-2024-42231, CVE-2024-46717,     CVE-2024-41065, CVE-2024-44969, CVE-2023-52887, CVE-2024-42105, CVE-2024-44971, CVE-2024-46798,     CVE-2024-42262, CVE-2024-44938, CVE-2024-42088, CVE-2024-44970, CVE-2024-43876, CVE-2024-46800,     CVE-2024-42086, CVE-2024-43826, CVE-2024-46729, CVE-2024-46747, CVE-2024-46691, CVE-2024-46723,     CVE-2024-41018, CVE-2024-42258, CVE-2024-41081, CVE-2024-41049, CVE-2024-43837, CVE-2024-45008,     CVE-2024-41047, CVE-2024-41019, CVE-2024-42152, CVE-2024-41090, CVE-2024-46716, CVE-2024-42104,     CVE-2024-46804, CVE-2024-43852, CVE-2024-42129, CVE-2024-46870, CVE-2024-41093, CVE-2024-45011,     CVE-2024-41064, CVE-2024-46722, CVE-2024-42286, CVE-2024-45026, CVE-2024-46818, CVE-2024-42281,     CVE-2024-43854, CVE-2024-41037, CVE-2024-44946, CVE-2024-41012, CVE-2024-41098, CVE-2024-42263,     CVE-2024-42095, CVE-2024-46756, CVE-2024-43913, CVE-2024-46822, CVE-2024-44944, CVE-2024-42156,     CVE-2024-42073, CVE-2024-42093, CVE-2024-44931, CVE-2024-42223, CVE-2024-42264, CVE-2024-42278,     CVE-2024-46759, CVE-2024-46826, CVE-2024-43828, CVE-2024-42318, CVE-2024-42240, CVE-2024-45000,     CVE-2024-43909, CVE-2024-46792, CVE-2024-42109, CVE-2024-43867, CVE-2024-42130, CVE-2024-42244,     CVE-2024-44977, CVE-2024-46774, CVE-2024-41030, CVE-2024-42310, CVE-2024-42138, CVE-2024-42317,     CVE-2024-42224, CVE-2024-46694, CVE-2024-46815, CVE-2024-46677, CVE-2024-46763, CVE-2024-46860,     CVE-2024-46767, CVE-2024-42111, CVE-2024-41020, CVE-2024-46726, CVE-2024-42117, CVE-2024-43831,     CVE-2024-42285, CVE-2024-46842, CVE-2024-43857, CVE-2024-41031, CVE-2024-43834, CVE-2024-42135,     CVE-2024-42241, CVE-2024-46846, CVE-2024-44988, CVE-2024-43892, CVE-2024-44991, CVE-2024-46806,     CVE-2024-41015, CVE-2024-43906, CVE-2024-42238, CVE-2024-46779, CVE-2024-41010, CVE-2024-41068,     CVE-2024-46730, CVE-2024-46827, CVE-2024-42120, CVE-2024-41059, CVE-2024-46850, CVE-2023-52889,     CVE-2024-45017, CVE-2024-45003, CVE-2024-46844, CVE-2024-46816, CVE-2024-46811, CVE-2024-41023,     CVE-2024-44948, CVE-2024-46753, CVE-2024-45002, CVE-2024-42251, CVE-2024-46713, CVE-2024-42273,     CVE-2024-46733, CVE-2024-46739, CVE-2024-42108, CVE-2024-41085, CVE-2024-41033, CVE-2024-42298,     CVE-2024-46835, CVE-2024-39472, CVE-2024-47663, CVE-2024-43859, CVE-2024-43820, CVE-2024-42118,     CVE-2024-41036, CVE-2024-47683, CVE-2024-42161, CVE-2024-42235, CVE-2024-43861, CVE-2024-43863,     CVE-2024-47668, CVE-2024-46685, CVE-2024-43864, CVE-2024-46749, CVE-2024-44983, CVE-2024-46841,     CVE-2024-42082, CVE-2024-43818, CVE-2024-41071, CVE-2024-45006, CVE-2024-42080, CVE-2024-46825,     CVE-2024-46687, CVE-2024-44959, CVE-2024-43835, CVE-2024-43891, CVE-2024-46851, CVE-2024-42248,     CVE-2024-42103, CVE-2024-42079, CVE-2024-42068, CVE-2024-47664, CVE-2024-46854, CVE-2024-44973,     CVE-2024-42077, CVE-2024-46821, CVE-2024-43886, CVE-2024-41089, CVE-2024-43850, CVE-2024-44995,     CVE-2024-46809, CVE-2024-42084, CVE-2024-46758, CVE-2024-47662, CVE-2024-43839, CVE-2024-46738,     CVE-2024-41034, CVE-2024-42228, CVE-2024-42147, CVE-2024-43855, CVE-2024-41032, CVE-2024-46819,     CVE-2024-44989, CVE-2024-42265, CVE-2024-42110, CVE-2024-42155, CVE-2024-45005, CVE-2024-45016,     CVE-2024-42141, CVE-2024-43821, CVE-2024-42299, CVE-2024-44950, CVE-2024-42279, CVE-2024-44943,     CVE-2024-43904, CVE-2024-42268, CVE-2024-42089, CVE-2024-46807, CVE-2024-44996, CVE-2024-42069,     CVE-2024-46672, CVE-2024-44940, CVE-2024-42270, CVE-2024-46735, CVE-2024-42319, CVE-2024-46754,     CVE-2024-46861, CVE-2024-42277, CVE-2024-41054, CVE-2024-42131, CVE-2024-41056, CVE-2024-44963,     CVE-2024-42267, CVE-2024-42283, CVE-2024-42320, CVE-2024-46740, CVE-2024-46787, CVE-2024-43895,     CVE-2024-43881, CVE-2024-44961, CVE-2024-43910, CVE-2024-43875, CVE-2024-42289, CVE-2024-43853,     CVE-2024-42315, CVE-2024-43884, CVE-2024-46867, CVE-2024-43912, CVE-2024-41007, CVE-2024-46743,     CVE-2024-46675, CVE-2024-43877, CVE-2024-39486, CVE-2024-41050, CVE-2024-43858, CVE-2024-45018,     CVE-2024-46744, CVE-2024-46750, CVE-2024-46840, CVE-2024-42150, CVE-2024-41028, CVE-2024-42091,     CVE-2024-43894, CVE-2024-43869, CVE-2024-42132, CVE-2024-46777, CVE-2024-42106, CVE-2024-46848,     CVE-2024-41038, CVE-2024-46711, CVE-2024-43833, CVE-2024-46710, CVE-2024-46812, CVE-2024-42311,     CVE-2024-46701, CVE-2024-46683, CVE-2024-45029, CVE-2024-46830, CVE-2024-46857, CVE-2024-44979,     CVE-2024-44999, CVE-2024-44985, CVE-2024-46773, CVE-2024-45022, CVE-2024-46772, CVE-2024-44960,     CVE-2024-42243, CVE-2024-42158, CVE-2024-43819, CVE-2024-45030, CVE-2024-42085, CVE-2024-42274,     CVE-2024-44986, CVE-2024-41048, CVE-2024-42098, CVE-2024-46680, CVE-2023-52918, CVE-2024-46673,     CVE-2024-46834, CVE-2024-42288, CVE-2024-44998, CVE-2024-42113, CVE-2024-42094, CVE-2024-42225,     CVE-2024-42112, CVE-2024-42153, CVE-2024-43880, CVE-2024-43905, CVE-2024-43902, CVE-2024-46681,     CVE-2024-42236, CVE-2024-42294, CVE-2024-46793, CVE-2024-43882, CVE-2024-44947, CVE-2024-46849,     CVE-2024-44954, CVE-2024-46852, CVE-2024-41070, CVE-2024-41069, CVE-2024-46864, CVE-2024-46703,     CVE-2024-43829, CVE-2024-46802, CVE-2024-42101, CVE-2024-44990, CVE-2024-43830, CVE-2024-41029,     CVE-2024-43866, CVE-2024-43889, CVE-2024-42230, CVE-2024-46692, CVE-2024-42133, CVE-2024-45013,     CVE-2024-42076, CVE-2024-46810, CVE-2024-42128, CVE-2024-46718, CVE-2024-46814, CVE-2024-43841,     CVE-2024-43873, CVE-2024-42092, CVE-2024-41074, CVE-2024-41083, CVE-2024-46731, CVE-2024-43842,     CVE-2024-41077, CVE-2024-46720, CVE-2024-46795, CVE-2024-46813, CVE-2024-46805, CVE-2024-42142,     CVE-2024-42291, CVE-2024-43846, CVE-2024-41057, CVE-2024-43870, CVE-2024-44980, CVE-2024-46866,     CVE-2024-43827, CVE-2024-43840, CVE-2024-42280, CVE-2024-42261, CVE-2024-42246, CVE-2024-42115,     CVE-2024-46686, CVE-2024-43860, CVE-2024-46808, CVE-2024-42149, CVE-2024-46828, CVE-2024-44935,     CVE-2024-43847, CVE-2024-44967, CVE-2024-46817, CVE-2024-46721, CVE-2024-42305, CVE-2024-46766,     CVE-2024-43914, CVE-2024-46760, CVE-2024-41061, CVE-2024-41091, CVE-2024-43890, CVE-2024-42314,     CVE-2024-42064, CVE-2024-42302, CVE-2024-43887, CVE-2024-46832, CVE-2024-46765, CVE-2024-46770,     CVE-2024-41080, CVE-2024-42253, CVE-2024-44941, CVE-2024-42306, CVE-2024-41027, CVE-2024-46689,     CVE-2024-46781, CVE-2024-42247, CVE-2024-41066, CVE-2024-42287, CVE-2024-41097, CVE-2024-44939,     CVE-2024-45019, CVE-2024-47674, CVE-2024-46705, CVE-2024-42119, CVE-2024-46725, CVE-2024-46746,     CVE-2024-46732, CVE-2024-41042, CVE-2024-44958, CVE-2024-42114, CVE-2024-43893, CVE-2024-47666,     CVE-2024-46843, CVE-2024-42252, CVE-2024-42102, CVE-2024-42136, CVE-2024-41045, CVE-2024-42260,     CVE-2024-46771, CVE-2024-42124, CVE-2024-42297, CVE-2024-42271, CVE-2024-43845, CVE-2024-46775,     CVE-2024-41079, CVE-2024-43868, CVE-2024-42140, CVE-2024-42313, CVE-2024-42145, CVE-2024-46724,     CVE-2024-46788, CVE-2024-42234, CVE-2024-42144, CVE-2024-44974, CVE-2024-42097, CVE-2024-46714,     CVE-2024-41055, CVE-2024-44956)

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

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

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

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

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

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

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

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

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

ID	Name	Product	Family	Published	Updated	Severity
210893	Oracle Linux 8 / 9 : Unbreakable Enterprise kernel (ELSA-2024-12815)	Nessus	Oracle Linux Local Security Checks	11/13/2024	2/9/2026	high
215688	Azure Linux 3.0 Security Update: kernel (CVE-2024-41009)	Nessus	Azure Linux Local Security Checks	2/10/2025	9/15/2025	medium
209785	EulerOS Virtualization 2.12.0 : kernel (EulerOS-SA-2024-2781)	Nessus	Huawei Local Security Checks	10/27/2024	1/6/2026	high
206955	SUSE SLES15: cluster-md-kmp-rt / dlm-kmp-rt / gfs2-kmp-rt / kernel-devel-rt / etc (SUSE-SU-2024:3195-1)	Nessus	SuSE Local Security Checks	9/11/2024	6/26/2026	high
210004	Ubuntu 22.04 LTS : Linux kernel vulnerabilities (USN-7021-5)	Nessus	Ubuntu Local Security Checks	10/31/2024	10/31/2024	high
212042	RHEL 9 : kernel-rt (RHSA-2024:10773)	Nessus	Red Hat Local Security Checks	12/3/2024	11/4/2025	high
212048	RHEL 9 : kernel (RHSA-2024:10772)	Nessus	Red Hat Local Security Checks	12/4/2024	11/4/2025	high
208067	Ubuntu 20.04 LTS : Linux kernel vulnerabilities (USN-7021-4)	Nessus	Ubuntu Local Security Checks	10/3/2024	10/3/2024	high
205728	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.15-2024-050 (ALASKERNEL-5.15-2024-050)	Nessus	Amazon Linux Local Security Checks	8/17/2024	1/26/2026	high
212721	Ubuntu 24.04 LTS : Linux kernel (GKE) vulnerabilities (USN-7156-1)	Nessus	Ubuntu Local Security Checks	12/12/2024	2/3/2026	high
242830	NewStart CGSL MAIN 7.02 : kernel Multiple Vulnerabilities (NS-SA-2025-0118)	Nessus	NewStart CGSL Local Security Checks	7/25/2025	1/6/2026	high

Detections

Analytics

Plugins Search

high

medium

high

high

high

high

high

high

high

high

high