In the Linux kernel, the following vulnerability has been resolved: bpf: Use array_map_meta_equal for percpu array inner map replacement percpu_array_map_ops.map_meta_equal points to the generic bpf_map_meta_equal(), which does not compare max_entries. When a percpu array serves as an inner map, replacing it with one that has fewer max_entries bypasses the check. Since percpu_array_map_gen_lookup() inlines the original template's index_mask as a JIT immediate, a lookup on the replacement map can access pptrs[] out of bounds. Point percpu_array_map_ops.map_meta_equal to array_map_meta_equal(), which already enforces the max_entries equality check. Add a selftest to verify that replacing a percpu array inner map with a differently-sized one is rejected.

The Rocky Linux 9.6 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.6:CLSA-2026:1793100968 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: udf: Avoid double brelse() in     udf_rename() syzbot reported a warning like below [1]: VFS: brelse: Trying to free free buffer WARNING:
    CPU: 2 PID: 7301 at fs/buffer.c:1145 __brelse+0x67/0xa0 ... Call Trace: <TASK>     invalidate_bh_lru+0x99/0x150 smp_call_function_many_cond+0xe2a/0x10c0 ?     generic_remap_file_range_prep+0x50/0x50 ? __brelse+0xa0/0xa0 ? __mutex_lock+0x21c/0x12d0 ?     smp_call_on_cpu+0x250/0x250 ? rcu_read_lock_sched_held+0xb/0x60 ? lock_release+0x587/0x810 ?
    __brelse+0xa0/0xa0 ? generic_remap_file_range_prep+0x50/0x50 on_each_cpu_cond_mask+0x3c/0x80     blkdev_flush_mapping+0x13a/0x2f0 blkdev_put_whole+0xd3/0xf0 blkdev_put+0x222/0x760     deactivate_locked_super+0x96/0x160 deactivate_super+0xda/0x100 cleanup_mnt+0x222/0x3d0     task_work_run+0x149/0x240 ? task_work_cancel+0x30/0x30 do_exit+0xb29/0x2a40 ?     reacquire_held_locks+0x4a0/0x4a0 ? do_raw_spin_lock+0x12a/0x2b0 ? mm_update_next_owner+0x7c0/0x7c0 ?     rwlock_bug.part.0+0x90/0x90 ? zap_other_threads+0x234/0x2d0 do_group_exit+0xd0/0x2a0
    __x64_sys_exit_group+0x3a/0x50 do_syscall_64+0x34/0xb0 entry_SYSCALL_64_after_hwframe+0x63/0xcd The cause     of the issue is that brelse() is called on both ofibh.sbh and ofibh.ebh by udf_find_entry() when it     returns NULL. However, brelse() is called by udf_rename(), too. So, b_count on buffer_head becomes     unbalanced. This patch fixes the issue by not calling brelse() by udf_rename() when udf_find_entry()     returns NULL. (CVE-2022-50755)

  - In the Linux kernel, the following vulnerability has been resolved: soc: qcom: qmi_encdec: Restrict string     length in decode The QMI TLV value for strings in a lot of qmi element info structures account for null     terminated strings with MAX_LEN + 1. If a string is actually MAX_LEN + 1 length, this will cause an out of     bounds access when the NULL character is appended in decoding. (CVE-2023-53729)

  - In the Linux kernel, the following vulnerability has been resolved: can: isotp: check CAN address family     in isotp_bind() Add missing check to block non-AF_CAN binds. Syzbot created some code which matched the     right sockaddr struct size but used AF_XDP (0x2C) instead of AF_CAN (0x1D) in the address family field:
    bind$xdp(r2, &(0x7f0000000540)={0x2c, 0x0, r4, 0x0, r2}, 0x10) ^^^^ This has no funtional impact but the     userspace should be notified about the wrong address family field content. (CVE-2023-54105)

  - In the Linux kernel, the following vulnerability has been resolved: usb: rndis_host: Secure rndis_query     check against int overflow Variables off and len typed as uint32 in rndis_query function are controlled by     incoming RNDIS response message thus their value may be manipulated. Setting off to a unexpectetly large     value will cause the sum with len and 8 to overflow and pass the implemented validation step. Consequently     the response pointer will be referring to a location past the expected buffer boundaries allowing     information leakage e.g. via RNDIS_OID_802_3_PERMANENT_ADDRESS OID. (CVE-2023-54110)

  - In the Linux kernel, the following vulnerability has been resolved: mtd: spi-nor: Fix shift-out-of-bounds     in spi_nor_set_erase_type spi_nor_set_erase_type() was used either to set or to mask out an erase type.
    When we used it to mask out an erase type a shift-out-of-bounds was hit: UBSAN: shift-out-of-bounds in     drivers/mtd/spi-nor/core.c:2237:24 shift exponent 4294967295 is too large for 32-bit type 'int' The     setting of the size_{shift, mask} and of the opcode are unnecessary when the erase size is zero, as     throughout the code just the erase size is considered to determine whether an erase type is supported or     not. Setting the opcode to 0xFF was wrong too as nobody guarantees that 0xFF is an unused opcode. Thus     when masking out an erase type, just set the erase size to zero. This will fix the shift-out-of-bounds.
    [ta: refine changes, new commit message, fix compilation error] (CVE-2023-54295)

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

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

  - In the Linux kernel, the following vulnerability has been resolved: udf: Avoid double brelse() in     udf_rename() syzbot reported a warning like below [1]: VFS: brelse: Trying to free free buffer WARNING:
    CPU: 2 PID: 7301 at fs/buffer.c:1145 __brelse+0x67/0xa0 ... Call Trace: <TASK>     invalidate_bh_lru+0x99/0x150 smp_call_function_many_cond+0xe2a/0x10c0 ?     generic_remap_file_range_prep+0x50/0x50 ? __brelse+0xa0/0xa0 ? __mutex_lock+0x21c/0x12d0 ?     smp_call_on_cpu+0x250/0x250 ? rcu_read_lock_sched_held+0xb/0x60 ? lock_release+0x587/0x810 ?
    __brelse+0xa0/0xa0 ? generic_remap_file_range_prep+0x50/0x50 on_each_cpu_cond_mask+0x3c/0x80     blkdev_flush_mapping+0x13a/0x2f0 blkdev_put_whole+0xd3/0xf0 blkdev_put+0x222/0x760     deactivate_locked_super+0x96/0x160 deactivate_super+0xda/0x100 cleanup_mnt+0x222/0x3d0     task_work_run+0x149/0x240 ? task_work_cancel+0x30/0x30 do_exit+0xb29/0x2a40 ?     reacquire_held_locks+0x4a0/0x4a0 ? do_raw_spin_lock+0x12a/0x2b0 ? mm_update_next_owner+0x7c0/0x7c0 ?     rwlock_bug.part.0+0x90/0x90 ? zap_other_threads+0x234/0x2d0 do_group_exit+0xd0/0x2a0
    __x64_sys_exit_group+0x3a/0x50 do_syscall_64+0x34/0xb0 entry_SYSCALL_64_after_hwframe+0x63/0xcd The cause     of the issue is that brelse() is called on both ofibh.sbh and ofibh.ebh by udf_find_entry() when it     returns NULL. However, brelse() is called by udf_rename(), too. So, b_count on buffer_head becomes     unbalanced. This patch fixes the issue by not calling brelse() by udf_rename() when udf_find_entry()     returns NULL. (CVE-2022-50755)

  - In the Linux kernel, the following vulnerability has been resolved: soc: qcom: qmi_encdec: Restrict string     length in decode The QMI TLV value for strings in a lot of qmi element info structures account for null     terminated strings with MAX_LEN + 1. If a string is actually MAX_LEN + 1 length, this will cause an out of     bounds access when the NULL character is appended in decoding. (CVE-2023-53729)

  - In the Linux kernel, the following vulnerability has been resolved: can: isotp: check CAN address family     in isotp_bind() Add missing check to block non-AF_CAN binds. Syzbot created some code which matched the     right sockaddr struct size but used AF_XDP (0x2C) instead of AF_CAN (0x1D) in the address family field:
    bind$xdp(r2, &(0x7f0000000540)={0x2c, 0x0, r4, 0x0, r2}, 0x10) ^^^^ This has no funtional impact but the     userspace should be notified about the wrong address family field content. (CVE-2023-54105)

  - In the Linux kernel, the following vulnerability has been resolved: usb: rndis_host: Secure rndis_query     check against int overflow Variables off and len typed as uint32 in rndis_query function are controlled by     incoming RNDIS response message thus their value may be manipulated. Setting off to a unexpectetly large     value will cause the sum with len and 8 to overflow and pass the implemented validation step. Consequently     the response pointer will be referring to a location past the expected buffer boundaries allowing     information leakage e.g. via RNDIS_OID_802_3_PERMANENT_ADDRESS OID. (CVE-2023-54110)

  - In the Linux kernel, the following vulnerability has been resolved: mtd: spi-nor: Fix shift-out-of-bounds     in spi_nor_set_erase_type spi_nor_set_erase_type() was used either to set or to mask out an erase type.
    When we used it to mask out an erase type a shift-out-of-bounds was hit: UBSAN: shift-out-of-bounds in     drivers/mtd/spi-nor/core.c:2237:24 shift exponent 4294967295 is too large for 32-bit type 'int' The     setting of the size_{shift, mask} and of the opcode are unnecessary when the erase size is zero, as     throughout the code just the erase size is considered to determine whether an erase type is supported or     not. Setting the opcode to 0xFF was wrong too as nobody guarantees that 0xFF is an unused opcode. Thus     when masking out an erase type, just set the erase size to zero. This will fix the shift-out-of-bounds.
    [ta: refine changes, new commit message, fix compilation error] (CVE-2023-54295)

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.

  - bpf: Use array_map_meta_equal for percpu array inner map replacement percpu_array_map_ops.map_meta_equal     points to the generic bpf_map_meta_equal(), which does not compare max_entries. When a percpu array serves     as an inner map, replacing it with one that has fewer max_entries bypasses the check. Since     percpu_array_map_gen_lookup() inlines the original template's index_mask as a JIT immediate, a lookup on     the replacement map can access pptrs[] out of bounds. Point percpu_array_map_ops.map_meta_equal to     array_map_meta_equal(), which already enforces the max_entries equality check. Add a selftest to verify     that replacing a percpu array inner map with a differently-sized one is rejected. (CVE-2026-98376)

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

ID	Name	Product	Family	Type	Severity
373466	Amazon Linux 2023 : bpftool6.12, kernel6.12, kernel6.12-devel (ALAS2023-2026-3335)	Nessus	Amazon Linux Local Security Checks	Local	medium
373068	Rocky Linux 9.6 [TuxCare] Security Update: kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1793100968)	Nessus	Rocky Linux Local Security Checks	Local	high
373062	AlmaLinux 9.6 [TuxCare] Security Update: kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1793100968)	Nessus	Alma Linux Local Security Checks	Local	high
364540	Linux Distros Unpatched Vulnerability : CVE-2026-98376	Nessus	Misc.	Local	high

Detections

Analytics

CVE-2026-98376

high

Tenable Plugins

medium

high

high

high