In the Linux kernel, the following vulnerability has been resolved: bpf: Fix softlockup in arena_map_free on 64k page kernel On an aarch64 kernel with CONFIG_PAGE_SIZE_64KB=y, arena_htab tests cause a segmentation fault and soft lockup. The same failure is not observed with 4k pages on aarch64. It turns out arena_map_free() is calling apply_to_existing_page_range() with the address returned by bpf_arena_get_kern_vm_start(). If this address is not page-aligned the code ends up calling apply_to_pte_range() with that unaligned address causing soft lockup. Fix it by round up GUARD_SZ to PAGE_SIZE << 1 so that the division by 2 in bpf_arena_get_kern_vm_start() returns a page-aligned value.

The remote Oracle Linux 10 / 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the ELSA-2025-20530 advisory.

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

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

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

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - In the Linux kernel, the following vulnerability has been resolved: bpf: Fix softlockup in arena_map_free     on 64k page kernel On an aarch64 kernel with CONFIG_PAGE_SIZE_64KB=y, arena_htab tests cause a     segmentation fault and soft lockup. The same failure is not observed with 4k pages on aarch64. It turns     out arena_map_free() is calling apply_to_existing_page_range() with the address returned by     bpf_arena_get_kern_vm_start(). If this address is not page-aligned the code ends up calling     apply_to_pte_range() with that unaligned address causing soft lockup. Fix it by round up GUARD_SZ to     PAGE_SIZE << 1 so that the division by 2 in bpf_arena_get_kern_vm_start() returns a page-aligned value.
    (CVE-2025-21851)

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

The remote Oracle Linux 10 / 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the ELSA-2025-20480 advisory.

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

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

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

The remote CentOS Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the kernel-5.14.0-598.el9 build changelog.

  - In the Linux kernel, the following vulnerability has been resolved: udf: Fix a slab-out-of-bounds write     bug in udf_find_entry() Syzbot reported a slab-out-of-bounds Write bug: loop0: detected capacity change     from 0 to 2048 ================================================================== BUG: KASAN: slab-out-of-     bounds in udf_find_entry+0x8a5/0x14f0 fs/udf/namei.c:253 Write of size 105 at addr ffff8880123ff896 by     task syz-executor323/3610 CPU: 0 PID: 3610 Comm: syz-executor323 Not tainted     6.1.0-rc2-syzkaller-00105-gb229b6ca5abb #0 Hardware name: Google Compute Engine/Google Compute Engine,     BIOS Google 10/11/2022 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline]     dump_stack_lvl+0x1b1/0x28e lib/dump_stack.c:106 print_address_description+0x74/0x340 mm/kasan/report.c:284     print_report+0x107/0x1f0 mm/kasan/report.c:395 kasan_report+0xcd/0x100 mm/kasan/report.c:495     kasan_check_range+0x2a7/0x2e0 mm/kasan/generic.c:189 memcpy+0x3c/0x60 mm/kasan/shadow.c:66     udf_find_entry+0x8a5/0x14f0 fs/udf/namei.c:253 udf_lookup+0xef/0x340 fs/udf/namei.c:309 lookup_open     fs/namei.c:3391 [inline] open_last_lookups fs/namei.c:3481 [inline] path_openat+0x10e6/0x2df0     fs/namei.c:3710 do_filp_open+0x264/0x4f0 fs/namei.c:3740 do_sys_openat2+0x124/0x4e0 fs/open.c:1310     do_sys_open fs/open.c:1326 [inline] __do_sys_creat fs/open.c:1402 [inline] __se_sys_creat fs/open.c:1396     [inline] __x64_sys_creat+0x11f/0x160 fs/open.c:1396 do_syscall_x64 arch/x86/entry/common.c:50 [inline]     do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP:
    0033:0x7ffab0d164d9 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48     89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89     01 48 RSP: 002b:00007ffe1a7e6bb8 EFLAGS: 00000246 ORIG_RAX: 0000000000000055 RAX: ffffffffffffffda RBX:
    0000000000000000 RCX: 00007ffab0d164d9 RDX: 00007ffab0d164d9 RSI: 0000000000000000 RDI: 0000000020000180     RBP: 00007ffab0cd5a10 R08: 0000000000000000 R09: 0000000000000000 R10: 00005555573552c0 R11:
    0000000000000246 R12: 00007ffab0cd5aa0 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000     </TASK> Allocated by task 3610: kasan_save_stack mm/kasan/common.c:45 [inline] kasan_set_track+0x3d/0x60     mm/kasan/common.c:52 ____kasan_kmalloc mm/kasan/common.c:371 [inline] __kasan_kmalloc+0x97/0xb0     mm/kasan/common.c:380 kmalloc include/linux/slab.h:576 [inline] udf_find_entry+0x7b6/0x14f0     fs/udf/namei.c:243 udf_lookup+0xef/0x340 fs/udf/namei.c:309 lookup_open fs/namei.c:3391 [inline]     open_last_lookups fs/namei.c:3481 [inline] path_openat+0x10e6/0x2df0 fs/namei.c:3710     do_filp_open+0x264/0x4f0 fs/namei.c:3740 do_sys_openat2+0x124/0x4e0 fs/open.c:1310 do_sys_open     fs/open.c:1326 [inline] __do_sys_creat fs/open.c:1402 [inline] __se_sys_creat fs/open.c:1396 [inline]
    __x64_sys_creat+0x11f/0x160 fs/open.c:1396 do_syscall_x64 arch/x86/entry/common.c:50 [inline]     do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd The buggy     address belongs to the object at ffff8880123ff800 which belongs to the cache kmalloc-256 of size 256 The     buggy address is located 150 bytes inside of 256-byte region [ffff8880123ff800, ffff8880123ff900) The     buggy address belongs to the physical page: page:ffffea000048ff80 refcount:1 mapcount:0     mapping:0000000000000000 index:0x0 pfn:0x123fe head:ffffea000048ff80 order:1 compound_mapcount:0     compound_pincount:0 flags: 0xfff00000010200(slab|head|node=0|zone=1|lastcpupid=0x7ff) raw:
    00fff00000010200 ffffea00004b8500 dead000000000003 ffff888012041b40 raw: 0000000000000000 0000000080100010     00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected page_owner tracks the     page as allocated page last allocated via order 0, migratetype Unmovable, gfp_mask 0x0(), pid 1, tgid 1     (swapper/0), ts 1841222404, free_ts 0 create_dummy_stack mm/page_owner.c: ---truncated--- (CVE-2022-49846)

  - In the Linux kernel, the following vulnerability has been resolved: bpf: Fix deadlock when freeing cgroup     storage The following commit bc235cdb423a (bpf: Prevent deadlock from recursive     bpf_task_storage_[get|delete]) first introduced deadlock prevention for fentry/fexit programs attaching     on bpf_task_storage helpers. That commit also employed the logic in map free path in its v6 version. Later     bpf_cgrp_storage was first introduced in c4bcfb38a95e (bpf: Implement cgroup storage available to non-     cgroup-attached bpf progs) which faces the same issue as bpf_task_storage, instead of its busy counter,     NULL was passed to bpf_local_storage_map_free() which opened a window to cause deadlock: <TASK> (acquiring     local_storage->lock) _raw_spin_lock_irqsave+0x3d/0x50 bpf_local_storage_update+0xd1/0x460     bpf_cgrp_storage_get+0x109/0x130 bpf_prog_a4d4a370ba857314_cgrp_ptr+0x139/0x170 ?
    __bpf_prog_enter_recur+0x16/0x80 bpf_trampoline_6442485186+0x43/0xa4 cgroup_storage_ptr+0x9/0x20 (holding     local_storage->lock) bpf_selem_unlink_storage_nolock.constprop.0+0x135/0x160     bpf_selem_unlink_storage+0x6f/0x110 bpf_local_storage_map_free+0xa2/0x110 bpf_map_free_deferred+0x5b/0x90     process_one_work+0x17c/0x390 worker_thread+0x251/0x360 kthread+0xd2/0x100 ret_from_fork+0x34/0x50     ret_from_fork_asm+0x1a/0x30 </TASK> Progs: - A: SEC(fentry/cgroup_storage_ptr) - cgid     (BPF_MAP_TYPE_HASH) Record the id of the cgroup the current task belonging to in this hash map, using the     address of the cgroup as the map key. - cgrpa (BPF_MAP_TYPE_CGRP_STORAGE) If current task is a kworker,     lookup the above hash map using function parameter @owner as the key to get its corresponding cgroup id     which is then used to get a trusted pointer to the cgroup through bpf_cgroup_from_id(). This trusted     pointer can then be passed to bpf_cgrp_storage_get() to finally trigger the deadlock issue. - B:
    SEC(tp_btf/sys_enter) - cgrpb (BPF_MAP_TYPE_CGRP_STORAGE) The only purpose of this prog is to fill Prog     A's hash map by calling bpf_cgrp_storage_get() for as many userspace tasks as possible. Steps to     reproduce: - Run A; - while (true) { Run B; Destroy B; } Fix this issue by passing its busy counter to the     free procedure so it can be properly incremented before storage/smap locking. (CVE-2024-58088)

  - In the Linux kernel, the following vulnerability has been resolved: mm: zswap: properly synchronize     freeing resources during CPU hotunplug In zswap_compress() and zswap_decompress(), the per-CPU acomp_ctx     of the current CPU at the beginning of the operation is retrieved and used throughout. However, since     neither preemption nor migration are disabled, it is possible that the operation continues on a different     CPU. If the original CPU is hotunplugged while the acomp_ctx is still in use, we run into a UAF bug as     some of the resources attached to the acomp_ctx are freed during hotunplug in zswap_cpu_comp_dead() (i.e.
    acomp_ctx.buffer, acomp_ctx.req, or acomp_ctx.acomp). The problem was introduced in commit 1ec3b5fe6eec     (mm/zswap: move to use crypto_acomp API for hardware acceleration) when the switch to the crypto_acomp     API was made. Prior to that, the per-CPU crypto_comp was retrieved using get_cpu_ptr() which disables     preemption and makes sure the CPU cannot go away from under us. Preemption cannot be disabled with the     crypto_acomp API as a sleepable context is needed. Use the acomp_ctx.mutex to synchronize CPU hotplug     callbacks allocating and freeing resources with compression/decompression paths. Make sure that     acomp_ctx.req is NULL when the resources are freed. In the compression/decompression paths, check if     acomp_ctx.req is NULL after acquiring the mutex (meaning the CPU was offlined) and retry on the new CPU.
    The initialization of acomp_ctx.mutex is moved from the CPU hotplug callback to the pool initialization     where it belongs (where the mutex is allocated). In addition to adding clarity, this makes sure that CPU     hotplug cannot reinitialize a mutex that is already locked by compression/decompression. Previously a fix     was attempted by holding cpus_read_lock() [1]. This would have caused a potential deadlock as it is     possible for code already holding the lock to fall into reclaim and enter zswap (causing a deadlock). A     fix was also attempted using SRCU for synchronization, but Johannes pointed out that synchronize_srcu()     cannot be used in CPU hotplug notifiers [2]. Alternative fixes that were considered/attempted and could     have worked: - Refcounting the per-CPU acomp_ctx. This involves complexity in handling the race between     the refcount dropping to zero in zswap_[de]compress() and the refcount being re-initialized when the CPU     is onlined. - Disabling migration before getting the per-CPU acomp_ctx [3], but that's discouraged and is     a much bigger hammer than needed, and could result in subtle performance issues.
    [1]https://lkml.kernel.org/20241219212437.2714151-1-yosryahmed@google.com/     [2]https://lkml.kernel.org/20250107074724.1756696-2-yosryahmed@google.com/     [3]https://lkml.kernel.org/20250107222236.2715883-2-yosryahmed@google.com/ [yosryahmed@google.com: remove     comment] (CVE-2025-21693)

  - In the Linux kernel, the following vulnerability has been resolved: bpf: Send signals asynchronously if     !preemptible BPF programs can execute in all kinds of contexts and when a program running in a non-     preemptible context uses the bpf_send_signal() kfunc, it will cause issues because this kfunc can sleep.
    Change `irqs_disabled()` to `!preemptible()`. (CVE-2025-21728)

  - In the Linux kernel, the following vulnerability has been resolved: ipv6: mcast: extend RCU protection in     igmp6_send() igmp6_send() can be called without RTNL or RCU being held. Extend RCU protection so that we     can safely fetch the net pointer and avoid a potential UAF. Note that we no longer can use     sock_alloc_send_skb() because ipv6.igmp_sk uses GFP_KERNEL allocations which can sleep. Instead use     alloc_skb() and charge the net->ipv6.igmp_sk socket under RCU protection. (CVE-2025-21759)

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

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

    Several security issues were discovered in the Linux kernel. An attacker could possibly use these to     compromise the system. This update corrects flaws in the following subsystems:

    - ARM64 architecture;

    - PowerPC architecture;

    - x86 architecture;

    - Block layer subsystem;

    - Serial ATA and Parallel ATA drivers;

    - Drivers core;

    - Network block device driver;

    - Bluetooth drivers;

    - Character device driver;

    - TPM device driver;

    - Clock framework and drivers;

    - Hardware crypto device drivers;

    - FireWire subsystem;

    - EFI core;

    - Qualcomm firmware drivers;

    - GPIO subsystem;

    - GPU drivers;

    - HID subsystem;

    - I2C subsystem;

    - I3C subsystem;

    - InfiniBand drivers;

    - Input Device (Mouse) drivers;

    - IOMMU subsystem;

    - Multiple devices driver;

    - Media drivers;

    - NVIDIA Tegra memory controller driver;

    - Fastrpc Driver;

    - Network drivers;

    - Operating Performance Points (OPP) driver;

    - PCI subsystem;

    - x86 platform drivers;

    - PPS (Pulse Per Second) driver;

    - PTP clock framework;

    - Remote Processor subsystem;

    - Real Time Clock drivers;

    - S/390 drivers;

    - SCSI subsystem;

    - QCOM SoC drivers;

    - SPI subsystem;

    - Media staging drivers;

    - Trusted Execution Environment drivers;

    - TTY drivers;

    - UFS subsystem;

    - USB Device Class drivers;

    - USB core drivers;

    - USB Gadget drivers;

    - USB Host Controller drivers;

    - Framebuffer layer;

    - File systems infrastructure;

    - BTRFS file system;

    - Ceph distributed file system;

    - Network file system (NFS) client;

    - Network file system (NFS) server daemon;

    - NILFS2 file system;

    - Overlay file system;

    - SMB network file system;

    - UBI file system;

    - BPF subsystem;

    - Timer subsystem;

    - KVM subsystem;

    - Networking core;

    - ptr_ring data structure definitions;

    - Networking subsytem;

    - Amateur Radio drivers;

    - L3 Master device support module;

    - TCP network protocol;

    - XFRM subsystem;

    - Tracing infrastructure;

    - io_uring subsystem;

    - Process Accounting mechanism;

    - Perf events;

    - Padata parallel execution mechanism;

    - printk logging mechanism;

    - Scheduler infrastructure;

    - Workqueue subsystem;

    - Memory management;

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

    - Bluetooth subsystem;

    - IPv4 networking;

    - IPv6 networking;

    - MAC80211 subsystem;

    - Multipath TCP;

    - Netfilter;

    - NFC subsystem;

    - Open vSwitch;

    - Rose network layer;

    - RxRPC session sockets;

    - Network traffic control;

    - Wireless networking;

    - Key management;

    - Landlock security;

    - Linux Security Modules (LSM) Framework;

    - Tomoyo security module;

    - SoC audio core drivers;

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

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

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

ID	Name	Product	Family	Severity
252244	Oracle Linux 10 / 9 : Unbreakable Enterprise kernel (ELSA-2025-20530)	Nessus	Oracle Linux Local Security Checks	medium
248993	Linux Distros Unpatched Vulnerability : CVE-2025-21851	Nessus	Misc.	low
242347	Oracle Linux 10 / 9 : Unbreakable Enterprise kernel (ELSA-2025-20480)	Nessus	Oracle Linux Local Security Checks	medium
242070	CentOS 9 : kernel-5.14.0-598.el9	Nessus	CentOS Local Security Checks	high
236983	Ubuntu 24.04 LTS / 24.10 : Linux kernel vulnerabilities (USN-7521-1)	Nessus	Ubuntu Local Security Checks	high

Detections

Analytics

CVE-2025-21851

low

Tenable Plugins

medium

low

medium

high

high