In the Linux kernel, the following vulnerability has been resolved: arm64/fpsimd: signal: Fix restoration of SVE context When SME is supported, Restoring SVE signal context can go wrong in a few ways, including placing the task into an invalid state where the kernel may read from out-of-bounds memory (and may potentially take a fatal fault) and/or may kill the task with a SIGKILL. (1) Restoring a context with SVE_SIG_FLAG_SM set can place the task into an invalid state where SVCR.SM is set (and sve_state is non-NULL) but TIF_SME is clear, consequently resuting in out-of-bounds memory reads and/or killing the task with SIGKILL. This can only occur in unusual (but legitimate) cases where the SVE signal context has either been modified by userspace or was saved in the context of another task (e.g. as with CRIU), as otherwise the presence of an SVE signal context with SVE_SIG_FLAG_SM implies that TIF_SME is already set. While in this state, task_fpsimd_load() will NOT configure SMCR_ELx (leaving some arbitrary value configured in hardware) before restoring SVCR and attempting to restore the streaming mode SVE registers from memory via sve_load_state(). As the value of SMCR_ELx.LEN may be larger than the task's streaming SVE vector length, this may read memory outside of the task's allocated sve_state, reading unrelated data and/or triggering a fault. While this can result in secrets being loaded into streaming SVE registers, these values are never exposed. As TIF_SME is clear, fpsimd_bind_task_to_cpu() will configure CPACR_ELx.SMEN to trap EL0 accesses to streaming mode SVE registers, so these cannot be accessed directly at EL0. As fpsimd_save_user_state() verifies the live vector length before saving (S)SVE state to memory, no secret values can be saved back to memory (and hence cannot be observed via ptrace, signals, etc). When the live vector length doesn't match the expected vector length for the task, fpsimd_save_user_state() will send a fatal SIGKILL signal to the task. Hence the task may be killed after executing userspace for some period of time. (2) Restoring a context with SVE_SIG_FLAG_SM clear does not clear the task's SVCR.SM. If SVCR.SM was set prior to restoring the context, then the task will be left in streaming mode unexpectedly, and some register state will be combined inconsistently, though the task will be left in legitimate state from the kernel's PoV. This can only occur in unusual (but legitimate) cases where ptrace has been used to set SVCR.SM after entry to the sigreturn syscall, as syscall entry clears SVCR.SM. In these cases, the the provided SVE register data will be loaded into the task's sve_state using the non-streaming SVE vector length and the FPSIMD registers will be merged into this using the streaming SVE vector length. Fix (1) by setting TIF_SME when setting SVCR.SM. This also requires ensuring that the task's sme_state has been allocated, but as this could contain live ZA state, it should not be zeroed. Fix (2) by clearing SVCR.SM when restoring a SVE signal context with SVE_SIG_FLAG_SM clear. For consistency, I've pulled the manipulation of SVCR, TIF_SVE, TIF_SME, and fp_type earlier, immediately after the allocation of sve_state/sme_state, before the restore of the actual register state. This makes it easier to ensure that these are always modified consistently, even if a fault is taken while reading the register data from the signal context. I do not expect any software to depend on the exact state restored when a fault is taken while reading the context.

The remote SUSE Linux SLES15 host has a package installed that is affected by multiple vulnerabilities as referenced in the SUSE-SU-2026:0962-1 advisory.

    The SUSE Linux Enterprise 15 SP7 RT kernel was updated to receive various security bugfixes.


    The following security bugs were fixed:

    - CVE-2023-53817: crypto: lib/mpi - avoid null pointer deref in mpi_cmp_ui() (bsc#1254992).
    - CVE-2025-39748: bpf: Forget ranges when refining tnum after JSET (bsc#1249587).
    - CVE-2025-39817: efivarfs: Fix slab-out-of-bounds in efivarfs_d_compare (bsc#1249998).
    - CVE-2025-39964: crypto: af_alg - Disallow concurrent writes in af_alg_sendmsg (bsc#1251966).
    - CVE-2025-40099: cifs: parse_dfs_referrals: prevent oob on malformed input (bsc#1252911).
    - CVE-2025-40103: smb: client: Fix refcount leak for cifs_sb_tlink (bsc#1252924).
    - CVE-2025-40201: kernel/sys.c: fix the racy usage of task_lock(tsk->group_leader) in sys_prlimit64()     paths
    - CVE-2025-40253: s390/ctcm: Fix double-kfree (bsc#1255084).
    - CVE-2025-68283: libceph: replace BUG_ON with bounds check for map->max_osd (bsc#1255379).
    - CVE-2025-68295: smb: client: fix memory leak in cifs_construct_tcon() (bsc#1255129).
    - CVE-2025-68374: md: fix rcu protection in md_wakeup_thread (bsc#1255530).
    - CVE-2025-68735: drm/panthor: Prevent potential UAF in group creation (bsc#1255811).
    - CVE-2025-68736: landlock: Fix handling of disconnected directories (bsc#1255698).
    - CVE-2025-68778: btrfs: don't log conflicting inode if it's a dir moved in the current transaction     (bsc#1256683).
    - CVE-2025-68785: net: openvswitch: fix middle attribute validation in push_nsh() action (bsc#1256640).
    - CVE-2025-68810: KVM: Disallow toggling KVM_MEM_GUEST_MEMFD on an existing memslot (bsc#1256679).
    - CVE-2025-71071: iommu/mediatek: fix use-after-free on probe deferral (bsc#1256802).
    - CVE-2025-71104: KVM: x86: Fix VM hard lockup after prolonged inactivity with periodic HV timer     (bsc#1256708).
    - CVE-2025-71113: crypto: af_alg - zero initialize memory allocated via sock_kmalloc (bsc#1256716).
    - CVE-2025-71125: tracing: Do not register unsupported perf events (bsc#1256784).
    - CVE-2025-71126: mptcp: reset fallback status gracefully at disconnect() time (bsc#1256755).
    - CVE-2025-71148: net/handshake: restore destructor on submit failure (bsc#1257159).
    - CVE-2025-71184: btrfs: fix NULL dereference on root when tracing inode eviction (bsc#1257635).
    - CVE-2025-71194: btrfs: fix deadlock in wait_current_trans() due to ignored transaction type     (bsc#1257687).
    - CVE-2025-71225: md: suspend array while updating raid_disks via sysfs (bsc#1258411).
    - CVE-2026-22979: net: fix memory leak in skb_segment_list for GRO packets (bsc#1257228).
    - CVE-2026-22982: net: mscc: ocelot: Fix crash when adding interface under a lag (bsc#1257179).
    - CVE-2026-22998: nvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec (bsc#1257209).
    - CVE-2026-23003: geneve: Fix incorrect inner network header offset when innerprotoinherit is set     (bsc#1257246).
    - CVE-2026-23004: dst: fix races in rt6_uncached_list_del() and rt_del_uncached_list() (bsc#1257231).
    - CVE-2026-23010: ipv6: Fix use-after-free in inet6_addr_del() (bsc#1257332).
    - CVE-2026-23017: idpf: fix error handling in the init_task on load (bsc#1257552).
    - CVE-2026-23023: idpf: fix memory leak in idpf_vport_rel() (bsc#1257556).
    - CVE-2026-23035: net/mlx5e: Pass netdev to mlx5e_destroy_netdev instead of priv (bsc#1257559).
    - CVE-2026-23053: NFS: Fix a deadlock involving nfs_release_folio() (bsc#1257718).
    - CVE-2026-23057: vsock/virtio: Coalesce only linear skb (bsc#1257740).
    - CVE-2026-23060: crypto: authencesn - reject too-short AAD (assoclen<8) to match ESP/ESN spec     (bsc#1257735).
    - CVE-2026-23064: net/sched: act_ife: avoid possible NULL deref (bsc#1257765).
    - CVE-2026-23069: vsock/virtio: fix potential underflow in virtio_transport_get_credit() (bsc#1257755).
    - CVE-2026-23070: Octeontx2-af: Add proper checks for fwdata (bsc#1257709).
    - CVE-2026-23074: net/sched: Enforce that teql can only be used as root qdisc (bsc#1257749).
    - CVE-2026-23083: fou: Don't allow 0 for FOU_ATTR_IPPROTO (bsc#1257745).
    - CVE-2026-23084: be2net: Fix NULL pointer dereference in be_cmd_get_mac_from_list (bsc#1257830).
    - CVE-2026-23085: irqchip/gic-v3-its: Avoid truncating memory addresses (bsc#1257758).
    - CVE-2026-23086: vsock/virtio: cap TX credit to local buffer size (bsc#1257757).
    - CVE-2026-23088: tracing: Fix crash on synthetic stacktrace field usage (bsc#1257814).
    - CVE-2026-23089: ALSA: usb-audio: Fix use-after-free in snd_usb_mixer_free() (bsc#1257790).
    - CVE-2026-23095: gue: Fix skb memleak with inner IP protocol 0 (bsc#1257808).
    - CVE-2026-23099: bonding: limit BOND_MODE_8023AD to Ethernet devices (bsc#1257816).
    - CVE-2026-23102: arm64/fpsimd: signal: Mandate SVE payload for streaming-mode state (bsc#1257772).
    - CVE-2026-23104: ice: fix devlink reload call trace (bsc#1257763).
    - CVE-2026-23105: net/sched: qfq: Use cl_is_active to determine whether class is active in qfq_rm_from_ag     (bsc#1257775).
    - CVE-2026-23107: arm64/fpsimd: signal: Allocate SSVE storage when restoring ZA (bsc#1257762).
    - CVE-2026-23110: scsi: core: Wake up the error handler when final completions race against each other     (bsc#1257761).
    - CVE-2026-23111: netfilter: nf_tables: fix inverted genmask check in nft_map_catchall_activate()     (bsc#1258181).
    - CVE-2026-23112: nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec (bsc#1258184).
    - CVE-2026-23113: io_uring/io-wq: check IO_WQ_BIT_EXIT inside work run loop (bsc#1258278).
    - CVE-2026-23116: pmdomain: imx8m-blk-ctrl: Remove separate rst and clk mask for 8mq vpu (bsc#1258277).
    - CVE-2026-23119: bonding: provide a net pointer to __skb_flow_dissect() (bsc#1258273).
    - CVE-2026-23125: sctp: move SCTP_CMD_ASSOC_SHKEY right after SCTP_CMD_PEER_INIT (bsc#1258293).
    - CVE-2026-23139: netfilter: nf_conncount: update last_gc only when GC has been performed (bsc#1258304).
    - CVE-2026-23141: btrfs: send: check for inline extents in range_is_hole_in_parent() (bsc#1258377).
    - CVE-2026-23154: net: fix segmentation of forwarding fraglist GRO (bsc#1258286).
    - CVE-2026-23166: ice: Fix NULL pointer dereference in ice_vsi_set_napi_queues (bsc#1258272).
    - CVE-2026-23169: mptcp: fix race in mptcp_pm_nl_flush_addrs_doit() (bsc#1258389).
    - CVE-2026-23171: net: bonding: update the slave array for broadcast mode (bsc#1258349).
    - CVE-2026-23173: net/mlx5e: TC, delete flows only for existing peers (bsc#1258520).
    - CVE-2026-23179: nvmet-tcp: fixup hang in nvmet_tcp_listen_data_ready() (bsc#1258394).
    - CVE-2026-23191: ALSA: aloop: Fix racy access at PCM trigger (bsc#1258395).
    - CVE-2026-23198: KVM: Don't clobber irqfd routing type when deassigning irqfd (bsc#1258321).
    - CVE-2026-23204: net/sched: cls_u32: use skb_header_pointer_careful() (bsc#1258340).
    - CVE-2026-23208: ALSA: usb-audio: Prevent excessive number of frames (bsc#1258468).
    - CVE-2026-23209: macvlan: fix error recovery in macvlan_common_newlink() (bsc#1258518).
    - CVE-2026-23210: ice: Fix PTP NULL pointer dereference during VSI rebuild (bsc#1258517).
    - CVE-2026-23213: drm/amd/pm: Disable MMIO access during SMU Mode 1 reset (bsc#1258465).
    - CVE-2026-23214: btrfs: reject new transactions if the fs is fully read-only (bsc#1258464).
    - CVE-2026-23268: apparmor: fix unprivileged local user can do privileged policy management
    - CVE-2026-23269: apparmor: validate DFA start states are in bounds in unpack_pdb


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

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

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2026-1468 advisory.

    In the Linux kernel, the following vulnerability has been resolved:

    blk-cgroup: Reinit blkg_iostat_set after clearing in blkcg_reset_stats() (CVE-2023-53421)

    In the Linux kernel, the following vulnerability has been resolved:

    iomap: Fix possible overflow condition in iomap_write_delalloc_scan (CVE-2023-54285)

    In the Linux kernel, the following vulnerability has been resolved:

    bpf: Reject narrower access to pointer ctx fields (CVE-2025-38591)

    In the Linux kernel, the following vulnerability has been resolved:

    sctp: linearize cloned gso packets in sctp_rcv (CVE-2025-38718)

    In the Linux kernel, the following vulnerability has been resolved:

    smb: client: fix potential UAF in smb2_close_cached_fid() (CVE-2025-40328)

    In the Linux kernel, the following vulnerability has been resolved:

    team: Move team device type change at the end of team_port_add (CVE-2025-68340)

    In the Linux kernel, the following vulnerability has been resolved:

    fs/ntfs3: Initialize allocated memory before use (CVE-2025-68365)

    In the Linux kernel, the following vulnerability has been resolved:

    bpf: Do not let BPF test infra emit invalid GSO types to stack (CVE-2025-68725)

    In the Linux kernel, the following vulnerability has been resolved:

    iommu: disable SVA when CONFIG_X86 is set (CVE-2025-71089)

    In the Linux kernel, the following vulnerability has been resolved:

    btrfs: fix deadlock in wait_current_trans() due to ignored transaction type (CVE-2025-71194)

    In the Linux kernel, the following vulnerability has been resolved:

    net/sched: sch_qfq: do not free existing class in qfq_change_class() (CVE-2026-22999)

    In the Linux kernel, the following vulnerability has been resolved:

    macvlan: fix possible UAF in macvlan_forward_source() (CVE-2026-23001)

    In the Linux kernel, the following vulnerability has been resolved:

    ip6_tunnel: use skb_vlan_inet_prepare() in __ip6_tnl_rcv() (CVE-2026-23003)

    In the Linux kernel, the following vulnerability has been resolved:

    x86/fpu: Clear XSTATE_BV[i] in guest XSAVE state whenever XFD[i]=1 (CVE-2026-23005)

    In the Linux kernel, the following vulnerability has been resolved:

    ipv6: Fix use-after-free in inet6_addr_del(). (CVE-2026-23010)

    In the Linux kernel, the following vulnerability has been resolved:

    ipv4: ip_gre: make ipgre_header() robust (CVE-2026-23011)

    In the Linux kernel, the following vulnerability has been resolved:

    mm/page_alloc: prevent pcp corruption with SMP=n (CVE-2026-23025)

    In the Linux kernel, the following vulnerability has been resolved:

    pnfs/flexfiles: Fix memory leak in nfs4_ff_alloc_deviceid_node() (CVE-2026-23038)

    In the Linux kernel, the following vulnerability has been resolved:

    net: hv_netvsc: reject RSS hash key programming without RX indirection table (CVE-2026-23054)

    In the Linux kernel, the following vulnerability has been resolved:

    crypto: authencesn - reject too-short AAD (assoclen<8) to match ESP/ESN spec (CVE-2026-23060)

    In the Linux kernel, the following vulnerability has been resolved:

    vsock/virtio: fix potential underflow in virtio_transport_get_credit() (CVE-2026-23069)

    In the Linux kernel, the following vulnerability has been resolved:

    regmap: Fix race condition in hwspinlock irqsave routine (CVE-2026-23071)

    In the Linux kernel, the following vulnerability has been resolved:

    net/sched: Enforce that teql can only be used as root qdisc (CVE-2026-23074)

    In the Linux kernel, the following vulnerability has been resolved:

    fou: Don't allow 0 for FOU_ATTR_IPPROTO. (CVE-2026-23083)

    In the Linux kernel, the following vulnerability has been resolved:

    irqchip/gic-v3-its: Avoid truncating memory addresses (CVE-2026-23085)

    In the Linux kernel, the following vulnerability has been resolved:

    vsock/virtio: cap TX credit to local buffer size (CVE-2026-23086)

    In the Linux kernel, the following vulnerability has been resolved:

    gue: Fix skb memleak with inner IP protocol 0. (CVE-2026-23095)

    In the Linux kernel, the following vulnerability has been resolved:

    migrate: correct lock ordering for hugetlb file folios (CVE-2026-23097)

    In the Linux kernel, the following vulnerability has been resolved:

    bonding: limit BOND_MODE_8023AD to Ethernet devices (CVE-2026-23099)

    In the Linux kernel, the following vulnerability has been resolved:

    arm64/fpsimd: signal: Fix restoration of SVE context (CVE-2026-23102)

    In the Linux kernel, the following vulnerability has been resolved:

    ipvlan: Make the addrs_lock be per port (CVE-2026-23103)

    In the Linux kernel, the following vulnerability has been resolved:

    net/sched: qfq: Use cl_is_active to determine whether class is active in qfq_rm_from_ag (CVE-2026-23105)

    In the Linux kernel, the following vulnerability has been resolved:

    arm64/fpsimd: signal: Allocate SSVE storage when restoring ZA (CVE-2026-23107)

    In the Linux kernel, the following vulnerability has been resolved:

    scsi: core: Wake up the error handler when final completions race against each other (CVE-2026-23110)

    In the Linux kernel, the following vulnerability has been resolved:

    netfilter: nf_tables: fix inverted genmask check in nft_map_catchall_activate() (CVE-2026-23111)

    In the Linux kernel, the following vulnerability has been resolved:

    bonding: provide a net pointer to __skb_flow_dissect() (CVE-2026-23119)

    In the Linux kernel, the following vulnerability has been resolved:

    ipv6: annotate data-race in ndisc_router_discovery() (CVE-2026-23124)

    In the Linux kernel, the following vulnerability has been resolved:

    sctp: move SCTP_CMD_ASSOC_SHKEY right after SCTP_CMD_PEER_INIT (CVE-2026-23125)

    In the Linux kernel, the following vulnerability has been resolved:

    netdevsim: fix a race issue related to the operation on bpf_bound_progs list (CVE-2026-23126)

    In the Linux kernel, the following vulnerability has been resolved:

    arm64: Set __nocfi on swsusp_arch_resume() (CVE-2026-23128)

    In the Linux kernel, the following vulnerability has been resolved:

    mm/damon/sysfs-scheme: cleanup access_pattern subdirs on scheme dir setup failure (CVE-2026-23142)

    In the Linux kernel, the following vulnerability has been resolved:

    mm/damon/sysfs: cleanup attrs subdirs on context dir setup failure (CVE-2026-23144)

    In the Linux kernel, the following vulnerability has been resolved:

    ext4: fix iloc.bh leak in ext4_xattr_inode_update_ref (CVE-2026-23145)

    In the Linux kernel, the following vulnerability has been resolved:

    efivarfs: fix error propagation in efivar_entry_get() (CVE-2026-23156)

    In the Linux kernel, the following vulnerability has been resolved:

    flex_proportions: make fprop_new_period() hardirq safe (CVE-2026-23168)

    In the Linux kernel, the following vulnerability has been resolved:

    scsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count() (CVE-2026-23193)

    In the Linux kernel, the following vulnerability has been resolved:

    KVM: Don't clobber irqfd routing type when deassigning irqfd (CVE-2026-23198)

    In the Linux kernel, the following vulnerability has been resolved:

    smb/client: fix memory leak in smb2_open_file() (CVE-2026-23205)

    In the Linux kernel, the following vulnerability has been resolved:

    macvlan: fix error recovery in macvlan_common_newlink() (CVE-2026-23209)

    In the Linux kernel, the following vulnerability has been resolved:

    bonding: annotate data-races around slave->last_rx (CVE-2026-23212)

    In the Linux kernel, the following vulnerability has been resolved:

    scsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count() (CVE-2026-23216)

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

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

An update of the linux package has been released.

The remote Debian 11 host has packages installed that are affected by multiple vulnerabilities as referenced in the dla-4476 advisory.

    -------------------------------------------------------------------------     Debian LTS Advisory DLA-4476-1                debian-lts@lists.debian.org     https://www.debian.org/lts/security/                        Ben Hutchings     February 10, 2026                             https://wiki.debian.org/LTS
    -------------------------------------------------------------------------

    Package        : linux-6.1     Version        : 6.1.162-1~deb11u1     CVE ID         : CVE-2023-52658 CVE-2023-53421 CVE-2023-54285 CVE-2024-42079                      CVE-2024-46786 CVE-2024-49968 CVE-2025-21946 CVE-2025-22022                      CVE-2025-22083 CVE-2025-22090 CVE-2025-22107 CVE-2025-22111                      CVE-2025-22121 CVE-2025-37926 CVE-2025-38022 CVE-2025-38104                      CVE-2025-38125 CVE-2025-38129 CVE-2025-38232 CVE-2025-38361                      CVE-2025-38408 CVE-2025-38591 CVE-2025-38718 CVE-2025-39721                      CVE-2025-39871 CVE-2025-40039 CVE-2025-40110 CVE-2025-40149                      CVE-2025-40164 CVE-2025-40215 CVE-2025-68211 CVE-2025-68223                      CVE-2025-68254 CVE-2025-68255 CVE-2025-68256 CVE-2025-68257                      CVE-2025-68258 CVE-2025-68259 CVE-2025-68261 CVE-2025-68263                      CVE-2025-68264 CVE-2025-68266 CVE-2025-68291 CVE-2025-68325                      CVE-2025-68332 CVE-2025-68335 CVE-2025-68336 CVE-2025-68337                      CVE-2025-68340 CVE-2025-68344 CVE-2025-68345 CVE-2025-68346                      CVE-2025-68347 CVE-2025-68349 CVE-2025-68354 CVE-2025-68362                      CVE-2025-68363 CVE-2025-68364 CVE-2025-68365 CVE-2025-68366                      CVE-2025-68367 CVE-2025-68369 CVE-2025-68371 CVE-2025-68372                      CVE-2025-68380 CVE-2025-68724 CVE-2025-68725 CVE-2025-68727                      CVE-2025-68728 CVE-2025-68732 CVE-2025-68733 CVE-2025-68740                      CVE-2025-68742 CVE-2025-68746 CVE-2025-68753 CVE-2025-68757                      CVE-2025-68758 CVE-2025-68759 CVE-2025-68764 CVE-2025-68765                      CVE-2025-68766 CVE-2025-68767 CVE-2025-68769 CVE-2025-68771                      CVE-2025-68772 CVE-2025-68773 CVE-2025-68774 CVE-2025-68776                      CVE-2025-68777 CVE-2025-68778 CVE-2025-68780 CVE-2025-68781                      CVE-2025-68782 CVE-2025-68783 CVE-2025-68785 CVE-2025-68786                      CVE-2025-68787 CVE-2025-68788 CVE-2025-68795 CVE-2025-68796                      CVE-2025-68797 CVE-2025-68798 CVE-2025-68799 CVE-2025-68800                      CVE-2025-68801 CVE-2025-68803 CVE-2025-68804 CVE-2025-68806                      CVE-2025-68808 CVE-2025-68813 CVE-2025-68814 CVE-2025-68815                      CVE-2025-68816 CVE-2025-68817 CVE-2025-68818 CVE-2025-68819                      CVE-2025-68820 CVE-2025-68821 CVE-2025-71064 CVE-2025-71066                      CVE-2025-71069 CVE-2025-71071 CVE-2025-71075 CVE-2025-71077                      CVE-2025-71078 CVE-2025-71079 CVE-2025-71081 CVE-2025-71082                      CVE-2025-71083 CVE-2025-71084 CVE-2025-71085 CVE-2025-71086                      CVE-2025-71087 CVE-2025-71088 CVE-2025-71091 CVE-2025-71093                      CVE-2025-71094 CVE-2025-71095 CVE-2025-71096 CVE-2025-71097                      CVE-2025-71098 CVE-2025-71102 CVE-2025-71104 CVE-2025-71105                      CVE-2025-71108 CVE-2025-71111 CVE-2025-71112 CVE-2025-71113                      CVE-2025-71114 CVE-2025-71116 CVE-2025-71118 CVE-2025-71119                      CVE-2025-71120 CVE-2025-71121 CVE-2025-71123 CVE-2025-71125                      CVE-2025-71126 CVE-2025-71127 CVE-2025-71130 CVE-2025-71131                      CVE-2025-71132 CVE-2025-71133 CVE-2025-71136 CVE-2025-71137                      CVE-2025-71147 CVE-2025-71149 CVE-2025-71150 CVE-2025-71154                      CVE-2025-71162 CVE-2025-71163 CVE-2025-71180 CVE-2025-71182                      CVE-2025-71183 CVE-2025-71185 CVE-2025-71186 CVE-2025-71189                      CVE-2025-71190 CVE-2025-71191 CVE-2025-71192 CVE-2025-71194                      CVE-2025-71196 CVE-2025-71197 CVE-2025-71199 CVE-2026-22976                      CVE-2026-22977 CVE-2026-22978 CVE-2026-22979 CVE-2026-22980                      CVE-2026-22982 CVE-2026-22984 CVE-2026-22990 CVE-2026-22991                      CVE-2026-22992 CVE-2026-22994 CVE-2026-22997 CVE-2026-22998                      CVE-2026-22999 CVE-2026-23001 CVE-2026-23003 CVE-2026-23005                      CVE-2026-23006 CVE-2026-23010 CVE-2026-23011 CVE-2026-23019                      CVE-2026-23020 CVE-2026-23021 CVE-2026-23025 CVE-2026-23026                      CVE-2026-23030 CVE-2026-23031 CVE-2026-23033 CVE-2026-23037                      CVE-2026-23038 CVE-2026-23047 CVE-2026-23049 CVE-2026-23054                      CVE-2026-23056 CVE-2026-23058 CVE-2026-23060 CVE-2026-23061                      CVE-2026-23063 CVE-2026-23064 CVE-2026-23068 CVE-2026-23069                      CVE-2026-23071 CVE-2026-23073 CVE-2026-23074 CVE-2026-23075                      CVE-2026-23076 CVE-2026-23078 CVE-2026-23080 CVE-2026-23083                      CVE-2026-23084 CVE-2026-23085 CVE-2026-23086 CVE-2026-23087                      CVE-2026-23089 CVE-2026-23090 CVE-2026-23091 CVE-2026-23093                      CVE-2026-23095 CVE-2026-23096 CVE-2026-23097 CVE-2026-23098                      CVE-2026-23099 CVE-2026-23101 CVE-2026-23102 CVE-2026-23103                      CVE-2026-23105 CVE-2026-23107 CVE-2026-23108 CVE-2026-23110     Debian Bug     : 1121535 1122193

    Several vulnerabilities have been discovered in the Linux kernel that     may lead to a privilege escalation, denial of service or information     leaks.

    For Debian 11 bullseye, these problems have been fixed in version     6.1.162-1~deb11u1.  This update also fixes several bugs reported to     Debian.  It additionally includes many more bug fixes from stable     updates 6.1.160-6.1.162 inclusive.

    We recommend that you upgrade your linux-6.1 packages.

    For the detailed security status of linux-6.1 please refer to     its security tracker page at:
    https://security-tracker.debian.org/tracker/linux-6.1

    Further information about Debian LTS security advisories, how to apply     these updates to your system and frequently asked questions can be     found at: https://wiki.debian.org/LTS     Attachment:
    signature.asc     Description: PGP signature

Tenable has extracted the preceding description block directly from the Debian 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 Debian 12 host has packages installed that are affected by multiple vulnerabilities as referenced in the dsa-6127 advisory.

    - -------------------------------------------------------------------------     Debian Security Advisory DSA-6127-1                   security@debian.org     https://www.debian.org/security/                     Salvatore Bonaccorso     February 09, 2026                     https://www.debian.org/security/faq
    - -------------------------------------------------------------------------

    Package        : linux     CVE ID         : CVE-2023-52658 CVE-2023-53421 CVE-2023-54285 CVE-2024-42079                      CVE-2024-46786 CVE-2024-49968 CVE-2025-21946 CVE-2025-22022                      CVE-2025-22083 CVE-2025-22090 CVE-2025-22107 CVE-2025-22111                      CVE-2025-22121 CVE-2025-37926 CVE-2025-38022 CVE-2025-38104                      CVE-2025-38125 CVE-2025-38129 CVE-2025-38232 CVE-2025-38361                      CVE-2025-38408 CVE-2025-38591 CVE-2025-38718 CVE-2025-39721                      CVE-2025-39871 CVE-2025-40039 CVE-2025-40110 CVE-2025-40149                      CVE-2025-40164 CVE-2025-40215 CVE-2025-68211 CVE-2025-68223                      CVE-2025-68254 CVE-2025-68255 CVE-2025-68256 CVE-2025-68257                      CVE-2025-68258 CVE-2025-68259 CVE-2025-68261 CVE-2025-68263                      CVE-2025-68264 CVE-2025-68266 CVE-2025-68291 CVE-2025-68325                      CVE-2025-68332 CVE-2025-68335 CVE-2025-68336 CVE-2025-68337                      CVE-2025-68340 CVE-2025-68344 CVE-2025-68345 CVE-2025-68346                      CVE-2025-68347 CVE-2025-68349 CVE-2025-68354 CVE-2025-68362                      CVE-2025-68363 CVE-2025-68364 CVE-2025-68365 CVE-2025-68366                      CVE-2025-68367 CVE-2025-68369 CVE-2025-68371 CVE-2025-68372                      CVE-2025-68380 CVE-2025-68724 CVE-2025-68725 CVE-2025-68727                      CVE-2025-68728 CVE-2025-68732 CVE-2025-68733 CVE-2025-68740                      CVE-2025-68742 CVE-2025-68746 CVE-2025-68753 CVE-2025-68757                      CVE-2025-68758 CVE-2025-68759 CVE-2025-68764 CVE-2025-68765                      CVE-2025-68766 CVE-2025-68767 CVE-2025-68769 CVE-2025-68771                      CVE-2025-68772 CVE-2025-68773 CVE-2025-68774 CVE-2025-68776                      CVE-2025-68777 CVE-2025-68778 CVE-2025-68780 CVE-2025-68781                      CVE-2025-68782 CVE-2025-68783 CVE-2025-68785 CVE-2025-68786                      CVE-2025-68787 CVE-2025-68788 CVE-2025-68789 CVE-2025-68795                      CVE-2025-68796 CVE-2025-68797 CVE-2025-68798 CVE-2025-68799                      CVE-2025-68800 CVE-2025-68801 CVE-2025-68803 CVE-2025-68804                      CVE-2025-68806 CVE-2025-68808 CVE-2025-68813 CVE-2025-68814                      CVE-2025-68815 CVE-2025-68816 CVE-2025-68817 CVE-2025-68818                      CVE-2025-68819 CVE-2025-68820 CVE-2025-68821 CVE-2025-71064                      CVE-2025-71066 CVE-2025-71069 CVE-2025-71071 CVE-2025-71075                      CVE-2025-71077 CVE-2025-71078 CVE-2025-71079 CVE-2025-71081                      CVE-2025-71082 CVE-2025-71083 CVE-2025-71084 CVE-2025-71085                      CVE-2025-71086 CVE-2025-71087 CVE-2025-71088 CVE-2025-71091                      CVE-2025-71093 CVE-2025-71094 CVE-2025-71095 CVE-2025-71096                      CVE-2025-71097 CVE-2025-71098 CVE-2025-71102 CVE-2025-71104                      CVE-2025-71105 CVE-2025-71108 CVE-2025-71111 CVE-2025-71112                      CVE-2025-71113 CVE-2025-71114 CVE-2025-71116 CVE-2025-71118                      CVE-2025-71119 CVE-2025-71120 CVE-2025-71121 CVE-2025-71123                      CVE-2025-71125 CVE-2025-71126 CVE-2025-71127 CVE-2025-71130                      CVE-2025-71131 CVE-2025-71132 CVE-2025-71133 CVE-2025-71136                      CVE-2025-71137 CVE-2025-71147 CVE-2025-71149 CVE-2025-71150                      CVE-2025-71154 CVE-2025-71162 CVE-2025-71163 CVE-2025-71180                      CVE-2025-71182 CVE-2025-71183 CVE-2025-71185 CVE-2025-71186                      CVE-2025-71189 CVE-2025-71190 CVE-2025-71191 CVE-2025-71192                      CVE-2025-71194 CVE-2025-71196 CVE-2025-71197 CVE-2025-71199                      CVE-2026-22976 CVE-2026-22977 CVE-2026-22978 CVE-2026-22979                      CVE-2026-22980 CVE-2026-22982 CVE-2026-22984 CVE-2026-22990                      CVE-2026-22991 CVE-2026-22992 CVE-2026-22994 CVE-2026-22997                      CVE-2026-22998 CVE-2026-22999 CVE-2026-23001 CVE-2026-23003                      CVE-2026-23005 CVE-2026-23006 CVE-2026-23010 CVE-2026-23011                      CVE-2026-23019 CVE-2026-23020 CVE-2026-23021 CVE-2026-23025                      CVE-2026-23026 CVE-2026-23030 CVE-2026-23031 CVE-2026-23033                      CVE-2026-23037 CVE-2026-23038 CVE-2026-23047 CVE-2026-23049                      CVE-2026-23054 CVE-2026-23056 CVE-2026-23058 CVE-2026-23060                      CVE-2026-23061 CVE-2026-23063 CVE-2026-23064 CVE-2026-23068                      CVE-2026-23069 CVE-2026-23071 CVE-2026-23073 CVE-2026-23074                      CVE-2026-23075 CVE-2026-23076 CVE-2026-23078 CVE-2026-23080                      CVE-2026-23083 CVE-2026-23084 CVE-2026-23085 CVE-2026-23086                      CVE-2026-23087 CVE-2026-23089 CVE-2026-23090 CVE-2026-23091                      CVE-2026-23093 CVE-2026-23095 CVE-2026-23096 CVE-2026-23097                      CVE-2026-23098 CVE-2026-23099 CVE-2026-23101 CVE-2026-23102                      CVE-2026-23103 CVE-2026-23105 CVE-2026-23107 CVE-2026-23108                      CVE-2026-23110

    Several vulnerabilities have been discovered in the Linux kernel that     may lead to a privilege escalation, denial of service or information     leaks.

    For the oldstable distribution (bookworm), these problems have been fixed     in version 6.1.162-1.

    We recommend that you upgrade your linux packages.

    For the detailed security status of linux please refer to its security     tracker page at:
    https://security-tracker.debian.org/tracker/linux

    Further information about Debian Security Advisories, how to apply     these updates to your system and frequently asked questions can be     found at: https://www.debian.org/security/

    Mailing list: debian-security-announce@lists.debian.org

Tenable has extracted the preceding description block directly from the Debian 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.

  - arm64/fpsimd: signal: Fix restoration of SVE context When SME is supported, Restoring SVE signal context     can go wrong in a few ways, including placing the task into an invalid state where the kernel may read     from out-of-bounds memory (and may potentially take a fatal fault) and/or may kill the task with a     SIGKILL. (1) Restoring a context with SVE_SIG_FLAG_SM set can place the task into an invalid state where     SVCR.SM is set (and sve_state is non-NULL) but TIF_SME is clear, consequently resuting in out-of-bounds     memory reads and/or killing the task with SIGKILL. This can only occur in unusual (but legitimate) cases     where the SVE signal context has either been modified by userspace or was saved in the context of another     task (e.g. as with CRIU), as otherwise the presence of an SVE signal context with SVE_SIG_FLAG_SM implies     that TIF_SME is already set. While in this state, task_fpsimd_load() will NOT configure SMCR_ELx (leaving     some arbitrary value configured in hardware) before restoring SVCR and attempting to restore the streaming     mode SVE registers from memory via sve_load_state(). As the value of SMCR_ELx.LEN may be larger than the     task's streaming SVE vector length, this may read memory outside of the task's allocated sve_state,     reading unrelated data and/or triggering a fault. While this can result in secrets being loaded into     streaming SVE registers, these values are never exposed. As TIF_SME is clear, fpsimd_bind_task_to_cpu()     will configure CPACR_ELx.SMEN to trap EL0 accesses to streaming mode SVE registers, so these cannot be     accessed directly at EL0. As fpsimd_save_user_state() verifies the live vector length before saving (S)SVE     state to memory, no secret values can be saved back to memory (and hence cannot be observed via ptrace,     signals, etc). When the live vector length doesn't match the expected vector length for the task,     fpsimd_save_user_state() will send a fatal SIGKILL signal to the task. Hence the task may be killed after     executing userspace for some period of time. (2) Restoring a context with SVE_SIG_FLAG_SM clear does not     clear the task's SVCR.SM. If SVCR.SM was set prior to restoring the context, then the task will be left in     streaming mode unexpectedly, and some register state will be combined inconsistently, though the task will     be left in legitimate state from the kernel's PoV. This can only occur in unusual (but legitimate) cases     where ptrace has been used to set SVCR.SM after entry to the sigreturn syscall, as syscall entry clears     SVCR.SM. In these cases, the the provided SVE register data will be loaded into the task's sve_state using     the non-streaming SVE vector length and the FPSIMD registers will be merged into this using the streaming     SVE vector length. Fix (1) by setting TIF_SME when setting SVCR.SM. This also requires ensuring that the     task's sme_state has been allocated, but as this could contain live ZA state, it should not be zeroed. Fix     (2) by clearing SVCR.SM when restoring a SVE signal context with SVE_SIG_FLAG_SM clear. For consistency,     I've pulled the manipulation of SVCR, TIF_SVE, TIF_SME, and fp_type earlier, immediately after the     allocation of sve_state/sme_state, before the restore of the actual register state. This makes it easier     to ensure that these are always modified consistently, even if a fault is taken while reading the register     data from the signal context. I do not expect any software to depend on the exact state restored when a     fault is taken while reading the context. (CVE-2026-23102)

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

ID	Name	Product	Family	Severity
303406	SUSE SLES15 Security Update : kernel (SUSE-SU-2026:0962-1)	Nessus	SuSE Local Security Checks	critical
301346	Amazon Linux 2023 : bpftool, kernel, kernel-devel (ALAS2023-2026-1468)	Nessus	Amazon Linux Local Security Checks	high
299743	Photon OS 5.0: Linux PHSA-2026-5.0-0770	Nessus	PhotonOS Local Security Checks	critical
298659	Debian dla-4476 : linux-config-6.1 - security update	Nessus	Debian Local Security Checks	high
298404	Debian dsa-6127 : affs-modules-6.1.0-37-4kc-malta-di - security update	Nessus	Debian Local Security Checks	high
297969	Linux Distros Unpatched Vulnerability : CVE-2026-23102	Nessus	Misc.	high

Detections

Analytics

CVE-2026-23102

high

Tenable Plugins

critical

high

critical

high

high

high