The CentOS Linux 7 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare CENTOS7:CLSA-2026:1768895798 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: HID: core: fix shift-out-of-bounds in     hid_report_raw_event Syzbot reported shift-out-of-bounds in hid_report_raw_event. microsoft     0003:045E:07DA.0001: hid_field_extract() called with n (128) > 32! (swapper/0)     ====================================================================== UBSAN: shift-out-of-bounds in     drivers/hid/hid-core.c:1323:20 shift exponent 127 is too large for 32-bit type 'int' CPU: 0 PID: 0 Comm:
    swapper/0 Not tainted 6.1.0-rc4-syzkaller-00159-g4bbf3422df78 #0 Hardware name: Google Compute     Engine/Google Compute Engine, BIOS Google 10/26/2022 Call Trace: <IRQ> __dump_stack lib/dump_stack.c:88     [inline] dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106 ubsan_epilogue lib/ubsan.c:151 [inline]
    __ubsan_handle_shift_out_of_bounds+0x3a6/0x420 lib/ubsan.c:322 snto32 drivers/hid/hid-core.c:1323 [inline]     hid_input_fetch_field drivers/hid/hid-core.c:1572 [inline] hid_process_report drivers/hid/hid-core.c:1665     [inline] hid_report_raw_event+0xd56/0x18b0 drivers/hid/hid-core.c:1998 hid_input_report+0x408/0x4f0     drivers/hid/hid-core.c:2066 hid_irq_in+0x459/0x690 drivers/hid/usbhid/hid-core.c:284
    __usb_hcd_giveback_urb+0x369/0x530 drivers/usb/core/hcd.c:1671 dummy_timer+0x86b/0x3110     drivers/usb/gadget/udc/dummy_hcd.c:1988 call_timer_fn+0xf5/0x210 kernel/time/timer.c:1474 expire_timers     kernel/time/timer.c:1519 [inline] __run_timers+0x76a/0x980 kernel/time/timer.c:1790     run_timer_softirq+0x63/0xf0 kernel/time/timer.c:1803 __do_softirq+0x277/0x75b kernel/softirq.c:571
    __irq_exit_rcu+0xec/0x170 kernel/softirq.c:650 irq_exit_rcu+0x5/0x20 kernel/softirq.c:662     sysvec_apic_timer_interrupt+0x91/0xb0 arch/x86/kernel/apic/apic.c:1107     ====================================================================== If the size of the integer     (unsigned n) is bigger than 32 in snto32(), shift exponent will be too large for 32-bit type 'int',     resulting in a shift-out-of-bounds bug. Fix this by adding a check on the size of the integer (unsigned n)     in snto32(). To add support for n greater than 32 bits, set n to 32, if n is greater than 32.
    (CVE-2022-48978)

  - In the Linux kernel, the following vulnerability has been resolved: net: sched: sfb: fix null pointer     access issue when sfb_init() fails When the default qdisc is sfb, if the qdisc of dev_queue fails to be     inited during mqprio_init(), sfb_reset() is invoked to clear resources. In this case, the q->qdisc is     NULL, and it will cause gpf issue. The process is as follows: qdisc_create_dflt() sfb_init()     tcf_block_get() --->failed, q->qdisc is NULL ... qdisc_put() ... sfb_reset() qdisc_reset(q->qdisc)
    --->q->qdisc is NULL ops = qdisc->ops The following is the Call Trace information: general protection     fault, probably for non-canonical address 0xdffffc0000000003: 0000 [#1] PREEMPT SMP KASAN KASAN: null-ptr-     deref in range [0x0000000000000018-0x000000000000001f] RIP: 0010:qdisc_reset+0x2b/0x6f0 Call Trace: <TASK>     sfb_reset+0x37/0xd0 qdisc_reset+0xed/0x6f0 qdisc_destroy+0x82/0x4c0 qdisc_put+0x9e/0xb0     qdisc_create_dflt+0x2c3/0x4a0 mqprio_init+0xa71/0x1760 qdisc_create+0x3eb/0x1000     tc_modify_qdisc+0x408/0x1720 rtnetlink_rcv_msg+0x38e/0xac0 netlink_rcv_skb+0x12d/0x3a0     netlink_unicast+0x4a2/0x740 netlink_sendmsg+0x826/0xcc0 sock_sendmsg+0xc5/0x100
    ____sys_sendmsg+0x583/0x690 ___sys_sendmsg+0xe8/0x160 __sys_sendmsg+0xbf/0x160 do_syscall_64+0x35/0x80     entry_SYSCALL_64_after_hwframe+0x46/0xb0 RIP: 0033:0x7f2164122d04 </TASK> (CVE-2022-50356)

  - In the Linux kernel, the following vulnerability has been resolved: nfsd: don't ignore the return code of     svc_proc_register() Currently, nfsd_proc_stat_init() ignores the return value of svc_proc_register(). If     the procfile creation fails, then the kernel will WARN when it tries to remove the entry later. Fix     nfsd_proc_stat_init() to return the same type of pointer as svc_proc_register(), and fix up     nfsd_net_init() to check that and fail the nfsd_net construction if it occurs. svc_proc_register() can     fail if the dentry can't be allocated, or if an identical dentry already exists. The second case is pretty     unlikely in the nfsd_net construction codepath, so if this happens, return -ENOMEM. (CVE-2025-22026)

  - In the Linux kernel, the following vulnerability has been resolved: fs/proc: fix uaf in proc_readdir_de()     Pde is erased from subdir rbtree through rb_erase(), but not set the node to EMPTY, which may result in     uaf access. We should use RB_CLEAR_NODE() set the erased node to EMPTY, then pde_subdir_next() will return     NULL to avoid uaf access. We found an uaf issue while using stress-ng testing, need to run testcase     getdent and tun in the same time. The steps of the issue is as follows: 1) use getdent to traverse dir     /proc/pid/net/dev_snmp6/, and current pde is tun3; 2) in the [time windows] unregister netdevice tun3 and     tun2, and erase them from rbtree. erase tun3 first, and then erase tun2. the pde(tun2) will be released to     slab; 3) continue to getdent process, then pde_subdir_next() will return pde(tun2) which is released, it     will case uaf access. CPU 0 | CPU 1
    ------------------------------------------------------------------------- traverse dir     /proc/pid/net/dev_snmp6/ | unregister_netdevice(tun->dev) //tun3 tun2 sys_getdents64() | iterate_dir() |     proc_readdir() | proc_readdir_de() | snmp6_unregister_dev() pde_get(de); | proc_remove()     read_unlock(&proc_subdir_lock); | remove_proc_subtree() | write_lock(&proc_subdir_lock); [time window] |     rb_erase(&root->subdir_node, &parent->subdir); | write_unlock(&proc_subdir_lock);
    read_lock(&proc_subdir_lock); | next = pde_subdir_next(de); | pde_put(de); | de = next; //UAF | rbtree of     dev_snmp6 | pde(tun3) / \ NULL pde(tun2) (CVE-2025-40271)

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 7 [TuxCare] Security Update: bpftool / kernel / kernel-debug / kernel-debug-devel / kernel-devel / etc Multiple Vulnerabilities (CENTOS7:CLSA-2026:1768895798)

medium Nessus Plugin ID 352982

Version 1.2