The CentOS Linux 8.5 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare CENTOS8.5:CLSA-2026:1771077729 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: pid: take a reference when     initializing `cad_pid` During boot, kernel_init_freeable() initializes `cad_pid` to the init task's struct     pid. Later on, we may change `cad_pid` via a sysctl, and when this happens proc_do_cad_pid() will     increment the refcount on the new pid via get_pid(), and will decrement the refcount on the old pid via     put_pid(). As we never called get_pid() when we initialized `cad_pid`, we decrement a reference we never     incremented, can therefore free the init task's struct pid early. As there can be dangling references to     the struct pid, we can later encounter a use-after-free (e.g. when delivering signals). This was spotted     when fuzzing v5.13-rc3 with Syzkaller, but seems to have been around since the conversion of `cad_pid` to     struct pid in commit 9ec52099e4b8 ([PATCH] replace cad_pid by a struct pid) from the pre-KASAN stone age     of v2.6.19. Fix this by getting a reference to the init task's struct pid when we assign it to `cad_pid`.
    Full KASAN splat below. ================================================================== BUG: KASAN:
    use-after-free in ns_of_pid include/linux/pid.h:153 [inline] BUG: KASAN: use-after-free in     task_active_pid_ns+0xc0/0xc8 kernel/pid.c:509 Read of size 4 at addr ffff23794dda0004 by task syz-     executor.0/273 CPU: 1 PID: 273 Comm: syz-executor.0 Not tainted 5.12.0-00001-g9aef892b2d15 #1 Hardware     name: linux,dummy-virt (DT) Call trace: ns_of_pid include/linux/pid.h:153 [inline]     task_active_pid_ns+0xc0/0xc8 kernel/pid.c:509 do_notify_parent+0x308/0xe60 kernel/signal.c:1950     exit_notify kernel/exit.c:682 [inline] do_exit+0x2334/0x2bd0 kernel/exit.c:845 do_group_exit+0x108/0x2c8     kernel/exit.c:922 get_signal+0x4e4/0x2a88 kernel/signal.c:2781 do_signal arch/arm64/kernel/signal.c:882     [inline] do_notify_resume+0x300/0x970 arch/arm64/kernel/signal.c:936 work_pending+0xc/0x2dc Allocated by     task 0: slab_post_alloc_hook+0x50/0x5c0 mm/slab.h:516 slab_alloc_node mm/slub.c:2907 [inline] slab_alloc     mm/slub.c:2915 [inline] kmem_cache_alloc+0x1f4/0x4c0 mm/slub.c:2920 alloc_pid+0xdc/0xc00 kernel/pid.c:180     copy_process+0x2794/0x5e18 kernel/fork.c:2129 kernel_clone+0x194/0x13c8 kernel/fork.c:2500     kernel_thread+0xd4/0x110 kernel/fork.c:2552 rest_init+0x44/0x4a0 init/main.c:687     arch_call_rest_init+0x1c/0x28 start_kernel+0x520/0x554 init/main.c:1064 0x0 Freed by task 270:
    slab_free_hook mm/slub.c:1562 [inline] slab_free_freelist_hook+0x98/0x260 mm/slub.c:1600 slab_free     mm/slub.c:3161 [inline] kmem_cache_free+0x224/0x8e0 mm/slub.c:3177 put_pid.part.4+0xe0/0x1a8     kernel/pid.c:114 put_pid+0x30/0x48 kernel/pid.c:109 proc_do_cad_pid+0x190/0x1b0 kernel/sysctl.c:1401     proc_sys_call_handler+0x338/0x4b0 fs/proc/proc_sysctl.c:591 proc_sys_write+0x34/0x48     fs/proc/proc_sysctl.c:617 call_write_iter include/linux/fs.h:1977 [inline] new_sync_write+0x3ac/0x510     fs/read_write.c:518 vfs_write fs/read_write.c:605 [inline] vfs_write+0x9c4/0x1018 fs/read_write.c:585     ksys_write+0x124/0x240 fs/read_write.c:658 __do_sys_write fs/read_write.c:670 [inline] __se_sys_write     fs/read_write.c:667 [inline] __arm64_sys_write+0x78/0xb0 fs/read_write.c:667 __invoke_syscall     arch/arm64/kernel/syscall.c:37 [inline] invoke_syscall arch/arm64/kernel/syscall.c:49 [inline]     el0_svc_common.constprop.1+0x16c/0x388 arch/arm64/kernel/syscall.c:129 do_el0_svc+0xf8/0x150     arch/arm64/kernel/syscall.c:168 el0_svc+0x28/0x38 arch/arm64/kernel/entry-common.c:416     el0_sync_handler+0x134/0x180 arch/arm64/kernel/entry-common.c:432 el0_sync+0x154/0x180     arch/arm64/kernel/entry.S:701 The buggy address belongs to the object at ffff23794dda0000 which belongs to     the cache pid of size 224 The buggy address is located 4 bytes inside of 224-byte region [ff
    ---truncated--- (CVE-2021-47118)

  - In the Linux kernel, the following vulnerability has been resolved: scsi: target: Fix WRITE_SAME No Data     Buffer crash In newer version of the SBC specs, we have a NDOB bit that indicates there is no data buffer     that gets written out. If this bit is set using commands like sg_write_same --ndob we will crash in     target_core_iblock/file's execute_write_same handlers when we go to access the se_cmd->t_data_sg because     its NULL. This patch adds a check for the NDOB bit in the common WRITE SAME code because we don't support     it. And, it adds a check for zero SG elements in each handler in case the initiator tries to send a normal     WRITE SAME with no data buffer. (CVE-2022-21546)

  - In the Linux kernel, the following vulnerability has been resolved: be2net: Fix buffer overflow in     be_get_module_eeprom be_cmd_read_port_transceiver_data assumes that it is given a buffer that is at least     PAGE_DATA_LEN long, or twice that if the module supports SFF 8472. However, this is not always the case.
    Fix this by passing the desired offset and length to be_cmd_read_port_transceiver_data so that we only     copy the bytes once. (CVE-2022-49581)

  - In the Linux kernel, the following vulnerability has been resolved: dm raid: fix accesses beyond end of     raid member array On dm-raid table load (using raid_ctr), dm-raid allocates an array     rs->devs[rs->raid_disks] for the raid device members. rs->raid_disks is defined by the number of raid     metadata and image tupples passed into the target's constructor. In the case of RAID layout changes being     requested, that number can be different from the current number of members for existing raid sets as     defined in their superblocks. Example RAID layout changes include: - raid1 legs being added/removed -     raid4/5/6/10 number of stripes changed (stripe reshaping) - takeover to higher raid level (e.g. raid5 ->     raid6) When accessing array members, rs->raid_disks must be used in control loops instead of the     potentially larger value in rs->md.raid_disks. Otherwise it will cause memory access beyond the end of the     rs->devs array. Fix this by changing code that is prone to out-of-bounds access. Also fix     validate_raid_redundancy() to validate all devices that are added. Also, use braces to help clean up     raid_iterate_devices(). The out-of-bounds memory accesses was discovered using KASAN. This commit was     verified to pass all LVM2 RAID tests (with KASAN enabled). (CVE-2022-49674)

  - In the Linux kernel, the following vulnerability has been resolved: tracing: Fix wild-memory-access in     register_synth_event() In register_synth_event(), if set_synth_event_print_fmt() failed, then both     trace_remove_event_call() and unregister_trace_event() will be called, which means the trace_event_call     will call __unregister_trace_event() twice. As the result, the second unregister will causes the wild-     memory-access. register_synth_event set_synth_event_print_fmt failed trace_remove_event_call event_remove     if call->event.funcs then __unregister_trace_event (first call) unregister_trace_event
    __unregister_trace_event (second call) Fix the bug by avoiding to call the second
    __unregister_trace_event() by checking if the first one is called. general protection fault, probably for     non-canonical address 0xfbd59c0000000024: 0000 [#1] SMP KASAN PTI KASAN: maybe wild-memory-access in range     [0xdead000000000120-0xdead000000000127] CPU: 0 PID: 3807 Comm: modprobe Not tainted     6.1.0-rc1-00186-g76f33a7eedb4 #299 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS     rel-1.15.0-0-g2dd4b9b3f840-prebuilt.qemu.org 04/01/2014 RIP: 0010:unregister_trace_event+0x6e/0x280 Code:
    00 fc ff df 4c 89 ea 48 c1 ea 03 80 3c 02 00 0f 85 0e 02 00 00 48 b8 00 00 00 00 00 fc ff df 4c 8b 63 08     4c 89 e2 48 c1 ea 03 <80> 3c 02 00 0f 85 e2 01 00 00 49 89 2c 24 48 85 ed 74 28 e8 7a 9b RSP:
    0018:ffff88810413f370 EFLAGS: 00010a06 RAX: dffffc0000000000 RBX: ffff888105d050b0 RCX: 0000000000000000     RDX: 1bd5a00000000024 RSI: ffff888119e276e0 RDI: ffffffff835a8b20 RBP: dead000000000100 R08:
    0000000000000000 R09: fffffbfff0913481 R10: ffffffff8489a407 R11: fffffbfff0913480 R12: dead000000000122     R13: ffff888105d050b8 R14: 0000000000000000 R15: ffff888105d05028 FS: 00007f7823e8d540(0000)     GS:ffff888119e00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2:
    00007f7823e7ebec CR3: 000000010a058002 CR4: 0000000000330ef0 DR0: 0000000000000000 DR1: 0000000000000000     DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK>
    __create_synth_event+0x1e37/0x1eb0 create_or_delete_synth_event+0x110/0x250     synth_event_run_command+0x2f/0x110 test_gen_synth_cmd+0x170/0x2eb [synth_event_gen_test]     synth_event_gen_test_init+0x76/0x9bc [synth_event_gen_test] do_one_initcall+0xdb/0x480     do_init_module+0x1cf/0x680 load_module+0x6a50/0x70a0 __do_sys_finit_module+0x12f/0x1c0     do_syscall_64+0x3f/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd (CVE-2022-49799)

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

Detections

Analytics

CentOS Linux 8.5 [TuxCare] Security Update: bpftool / kernel / kernel-core / kernel-cross-headers / etc Multiple Vulnerabilities (CENTOS8.5:CLSA-2026:1771077729)

high Nessus Plugin ID 360928

Version 1.2

Version 1.1

Version 1.2 Oct 18, 2026, 10:57 AM CVE (set "CVE" coverage to "CVE-2021-47118,CVE-2021-47153,CVE-2022-21546,CVE-2022-48883,CVE-2022-49581,CVE-2022-49674,CVE-2022-49799,CVE-2022-49865,CVE-2022-49907,CVE-2022-49934,CVE-2022-49975,CVE-2022-50030,CVE-2022-50050,CVE-2022-50085,CVE-2022-50093,CVE-2022-50103,CVE-2022-50164,CVE-2022-50185,CVE-2022-50220,CVE-2022-50243,CVE-2022-50252,CVE-2022-50279,CVE-2022-50406,CVE-2022-50497,CVE-2022-50706,CVE-2023-52578,CVE-2023-52594,CVE-2023-52764,CVE-2023-52835,CVE-2023-52864,CVE-2023-52885,CVE-2023-53000,CVE-2023-53039,CVE-2023-53075,CVE-2023-53077,CVE-2023-53084,CVE-2023-53090,CVE-2023-53111,CVE-2023-53117,CVE-2023-53153,CVE-2023-53259,CVE-2023-53305,CVE-2023-53432,CVE-2023-53484,CVE-2023-53513,CVE-2023-53668,CVE-2023-53673,CVE-2023-53676,CVE-2023-54015,CVE-2023-54072,CVE-2023-54102,CVE-2023-54148,CVE-2024-26872,CVE-2024-26958,CVE-2024-26961,CVE-2024-26982,CVE-2024-27395,CVE-2024-35855,CVE-2024-35886,CVE-2024-38555,CVE-2024-38586,CVE-2024-38627,CVE-2024-39487,CVE-2024-40978,CVE-2024-42120,CVE-2024-42292,CVE-2024-43830,CVE-2025-37749,CVE-2025-37780,CVE-2025-37797,CVE-2025-37823,CVE-2025-37839,CVE-2025-37923,CVE-2025-37927,CVE-2025-38024,CVE-2025-38051,CVE-2025-38157,CVE-2025-38180,CVE-2025-38198,CVE-2025-38212,CVE-2025-38245,CVE-2025-38323,CVE-2025-38346,CVE-2025-38403,CVE-2025-38415,CVE-2025-38556,CVE-2025-38572,CVE-2025-38574,CVE-2025-38680,CVE-2025-38702,CVE-2025-38724,CVE-2025-38729,CVE-2025-39691,CVE-2025-39797,CVE-2025-39853,CVE-2025-39863,CVE-2025-39955,CVE-2025-39971,CVE-2025-39993,CVE-2025-40154,CVE-2025-40186,CVE-2025-40248,CVE-2025-40258,CVE-2025-40269,CVE-2025-40277,CVE-2025-40322,CVE-2025-68285,CVE-2025-68349") Detection (updated detection logic) Plugin metadata Plugin Feed: 202610181057
Version 1.1 Oct 1, 2026, 9:59 PM New Plugin Feed: 202610012159