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

  - In the Linux kernel, the following vulnerability has been resolved: ipv4: start using dst_dev_rcu() Change     icmpv4_xrlim_allow(), ip_defrag() to prevent possible UAF. Change ipmr_prepare_xmit(),     ipmr_queue_fwd_xmit(), ip_mr_output(), ipv4_neigh_lookup() to use lockdep enabled dst_dev_rcu().
    (CVE-2025-40074)

  - In the Linux kernel, the following vulnerability has been resolved: tcp_metrics: use dst_dev_net_rcu()     Replace three dst_dev() with a lockdep enabled helper. (CVE-2025-40075)

  - In the Linux kernel, the following vulnerability has been resolved: ipv6: use RCU in ip6_xmit() Use RCU in     ip6_xmit() in order to use dst_dev_rcu() to prevent possible UAF. (CVE-2025-40135)

  - In the Linux kernel, the following vulnerability has been resolved: tls: Use __sk_dst_get() and     dst_dev_rcu() in get_netdev_for_sock(). get_netdev_for_sock() is called during setsockopt(), so not under     RCU. Using sk_dst_get(sk)->dev could trigger UAF. Let's use __sk_dst_get() and dst_dev_rcu(). Note that     the only ->ndo_sk_get_lower_dev() user is bond_sk_get_lower_dev(), which uses RCU. (CVE-2025-40149)

  - In the Linux kernel, the following vulnerability has been resolved: ipv6: use RCU in ip6_output() Use RCU     in ip6_output() in order to use dst_dev_rcu() to prevent possible UAF. We can remove     rcu_read_lock()/rcu_read_unlock() pairs from ip6_finish_output2(). (CVE-2025-40158)

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

Detections

Analytics

AlmaLinux 9.2 [TuxCare] Security Update: bpftool / kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2026:1784287739)

high Nessus Plugin ID 362162

Version 1.2