In the Linux kernel, the following vulnerability has been resolved: btrfs: fix racy bitfield write in btrfs_clear_space_info_full() From the memory-barriers.txt document regarding memory barrier ordering guarantees: (*) These guarantees do not apply to bitfields, because compilers often generate code to modify these using non-atomic read-modify-write sequences. Do not attempt to use bitfields to synchronize parallel algorithms. (*) Even in cases where bitfields are protected by locks, all fields in a given bitfield must be protected by one lock. If two fields in a given bitfield are protected by different locks, the compiler's non-atomic read-modify-write sequences can cause an update to one field to corrupt the value of an adjacent field. btrfs_space_info has a bitfield sharing an underlying word consisting of the fields full, chunk_alloc, and flush: struct btrfs_space_info { struct btrfs_fs_info * fs_info; /* 0 8 */ struct btrfs_space_info * parent; /* 8 8 */ ... int clamp; /* 172 4 */ unsigned int full:1; /* 176: 0 4 */ unsigned int chunk_alloc:1; /* 176: 1 4 */ unsigned int flush:1; /* 176: 2 4 */ ... Therefore, to be safe from parallel read-modify-writes losing a write to one of the bitfield members protected by a lock, all writes to all the bitfields must use the lock. They almost universally do, except for btrfs_clear_space_info_full() which iterates over the space_infos and writes out found->full = 0 without a lock. Imagine that we have one thread completing a transaction in which we finished deleting a block_group and are thus calling btrfs_clear_space_info_full() while simultaneously the data reclaim ticket infrastructure is running do_async_reclaim_data_space(): T1 T2 btrfs_commit_transaction btrfs_clear_space_info_full data_sinfo->full = 0 READ: full:0, chunk_alloc:0, flush:1 do_async_reclaim_data_space(data_sinfo) spin_lock(&space_info->lock); if(list_empty(tickets)) space_info->flush = 0; READ: full: 0, chunk_alloc:0, flush:1 MOD/WRITE: full: 0, chunk_alloc:0, flush:0 spin_unlock(&space_info->lock); return; MOD/WRITE: full:0, chunk_alloc:0, flush:1 and now data_sinfo->flush is 1 but the reclaim worker has exited. This breaks the invariant that flush is 0 iff there is no work queued or running. Once this invariant is violated, future allocations that go into __reserve_bytes() will add tickets to space_info->tickets but will see space_info->flush is set to 1 and not queue the work. After this, they will block forever on the resulting ticket, as it is now impossible to kick the worker again. I also confirmed by looking at the assembly of the affected kernel that it is doing RMW operations. For example, to set the flush (3rd) bit to 0, the assembly is: andb $0xfb,0x60(%rbx) and similarly for setting the full (1st) bit to 0: andb $0xfe,-0x20(%rax) So I think this is really a bug on practical systems. I have observed a number of systems in this exact state, but am currently unable to reproduce it. Rather than leaving this footgun lying around for the future, take advantage of the fact that there is room in the struct anyway, and that it is already quite large and simply change the three bitfield members to bools. This avoids writes to space_info->full having any effect on ---truncated---

The version of kernel installed on the remote host is prior to 5.15.202-141.223. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.15-2026-099 advisory.

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

    drm/ttm: fix undefined behavior in bit shift for TTM_TT_FLAG_PRIV_POPULATED (CVE-2022-50390)

    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:

    ext4: fix memory leaks in ext4_fname_{setup_filename,prepare_lookup} (CVE-2023-53662)

    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:

    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:

    btrfs: fix racy bitfield write in btrfs_clear_space_info_full() (CVE-2025-68358)

    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:

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

    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:

    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:

    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:

    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:

    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:

    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:

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

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

    mptcp: fix race in mptcp_pm_nl_flush_addrs_doit() (CVE-2026-23169)

    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:

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

    In the Linux kernel, the following vulnerability has been resolved: bus: fsl-mc: fix use-after-free in     driver_override_show() The driver_override_show() function reads the driver_override string without     holding the device_lock. However, driver_override_store() uses driver_set_override(), which modifies and     frees the string while holding the device_lock. This can result in a concurrent use-after-free if the     string is freed by the store function while being read by the show function. Fix this by holding the     device_lock around the read operation. (CVE-2026-23221)

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.

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

    Qualys discovered that several vulnerabilities existed in the AppArmor Linux kernel Security Module (LSM).
    An unprivileged local attacker could use these issues to load, replace, and remove arbitrary AppArmor     profiles causing denial of service, exposure of sensitive information (kernel memory), local privilege     escalation, or possibly escape a container. (LP: #2143853)

    It was discovered that some AMD Zen 5 processors supporting RDSEED instruction did not properly handle     entropy, potentially resulting in the consumption of insufficiently random values. A local attacker could     possibly use this issue to influence the values returned by the RDSEED instruction causing loss of     confidentiality and integrity. (CVE-2025-62626)

    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;

    - S390 architecture;

    - x86 architecture;

    - Block layer subsystem;

    - Cryptographic API;

    - Compute Acceleration Framework;

    - ATM drivers;

    - Network block device driver;

    - Bluetooth drivers;

    - Data acquisition framework and drivers;

    - Hardware crypto device drivers;

    - Device frequency scaling framework;

    - Intel Stratix 10 firmware drivers;

    - GPIO subsystem;

    - GPU drivers;

    - Microsoft Hyper-V drivers;

    - CoreSight HW tracing drivers;

    - IIO subsystem;

    - InfiniBand drivers;

    - Input Device core drivers;

    - Input Device (Tablet) drivers;

    - IOMMU subsystem;

    - IRQ chip drivers;

    - Macintosh device drivers;

    - Multiple devices driver;

    - MOST (Media Oriented Systems Transport) drivers;

    - MTD block device drivers;

    - Network drivers;

    - Mellanox network drivers;

    - Texas Instruments network drivers;

    - Ethernet team driver;

    - MediaTek network drivers;

    - NVME drivers;

    - Pin controllers subsystem;

    - x86 platform drivers;

    - Voltage and Current Regulator drivers;

    - Real Time Clock drivers;

    - S/390 drivers;

    - SCSI subsystem;

    - Texas Instruments SoC drivers;

    - SPI subsystem;

    - Media Oriented Systems Transport (MOST) driver;

    - Realtek RTL8723BS SDIO drivers;

    - TCM subsystem;

    - UFS subsystem;

    - DesignWare USB3 driver;

    - USB Gadget drivers;

    - Renesas USBHS Controller drivers;

    - USB Mass Storage drivers;

    - USB Type-C Connector System Software Interface driver;

    - Backlight driver;

    - Framebuffer layer;

    - AFS file system;

    - BFS file system;

    - BTRFS file system;

    - EROFS file system;

    - Ext4 file system;

    - FAT file system;

    - GFS2 file system;

    - Journaling layer for block devices (JBD2);

    - File systems infrastructure;

    - Network file system (NFS) client;

    - NTFS3 file system;

    - OCFS2 file system;

    - SMB network file system;

    - XFS file system;

    - BPF subsystem;

    - MediaTek SoC drivers;

    - Bluetooth subsystem;

    - io_uring subsystem;

    - Locking primitives;

    - Scheduler infrastructure;

    - Timer subsystem;

    - Tracing infrastructure;

    - Kexec HandOver (KHO);

    - Memory management;

    - Ceph Core library;

    - Networking core;

    - Devlink API;

    - IPv4 networking;

    - IPv6 networking;

    - Multipath TCP;

    - Open vSwitch;

    - Network traffic control;

    - VMware vSockets driver;

    - eXpress Data Path;

    - Integrity Measurement Architecture(IMA) framework;

    - Simplified Mandatory Access Control Kernel framework;

    - FireWire sound drivers;

    - HD-audio driver;

    - Turtle Beach Wavefront ALSA driver;

    - SoundWire (SDCA) ASoC drivers; (CVE-2025-40246, CVE-2025-40247, CVE-2025-40248, CVE-2025-40249,     CVE-2025-40250, CVE-2025-40251, CVE-2025-40252, CVE-2025-40253, CVE-2025-40254, CVE-2025-40255,     CVE-2025-40257, CVE-2025-40258, CVE-2025-40259, CVE-2025-40260, CVE-2025-40261, CVE-2025-40262,     CVE-2025-40263, CVE-2025-40264, CVE-2025-40265, CVE-2025-40266, CVE-2025-40290, CVE-2025-40345,     CVE-2025-68212, CVE-2025-68213, CVE-2025-68214, CVE-2025-68215, CVE-2025-68217, CVE-2025-68218,     CVE-2025-68219, CVE-2025-68220, CVE-2025-68221, CVE-2025-68222, CVE-2025-68223, CVE-2025-68225,     CVE-2025-68227, CVE-2025-68228, CVE-2025-68229, CVE-2025-68230, CVE-2025-68231, CVE-2025-68232,     CVE-2025-68233, CVE-2025-68234, CVE-2025-68235, CVE-2025-68236, CVE-2025-68237, CVE-2025-68238,     CVE-2025-68254, CVE-2025-68255, CVE-2025-68256, CVE-2025-68257, CVE-2025-68258, CVE-2025-68259,     CVE-2025-68261, CVE-2025-68262, CVE-2025-68263, CVE-2025-68264, CVE-2025-68265, CVE-2025-68266,     CVE-2025-68281, CVE-2025-68282, CVE-2025-68283, CVE-2025-68284, CVE-2025-68285, CVE-2025-68286,     CVE-2025-68287, CVE-2025-68288, CVE-2025-68289, CVE-2025-68290, CVE-2025-68292, CVE-2025-68293,     CVE-2025-68294, CVE-2025-68295, CVE-2025-68296, CVE-2025-68297, CVE-2025-68298, CVE-2025-68299,     CVE-2025-68300, CVE-2025-68301, CVE-2025-68302, CVE-2025-68303, CVE-2025-68304, CVE-2025-68305,     CVE-2025-68306, CVE-2025-68307, CVE-2025-68308, CVE-2025-68323, CVE-2025-68324, CVE-2025-68325,     CVE-2025-68326, CVE-2025-68327, CVE-2025-68328, CVE-2025-68329, CVE-2025-68330, CVE-2025-68331,     CVE-2025-68332, CVE-2025-68333, CVE-2025-68334, CVE-2025-68335, CVE-2025-68336, CVE-2025-68337,     CVE-2025-68338, CVE-2025-68339, CVE-2025-68340, CVE-2025-68341, CVE-2025-68342, CVE-2025-68343,     CVE-2025-68344, CVE-2025-68345, CVE-2025-68346, CVE-2025-68347, CVE-2025-68348, CVE-2025-68349,     CVE-2025-68352, CVE-2025-68354, CVE-2025-68356, CVE-2025-68358, CVE-2025-68359, CVE-2025-68360,     CVE-2025-68361, CVE-2025-68362, CVE-2025-68363, CVE-2025-68364, CVE-2025-68366, CVE-2025-68367,     CVE-2025-68369, CVE-2025-68370, CVE-2025-68371, CVE-2025-68372, CVE-2025-68373, CVE-2025-68374,     CVE-2025-68375, CVE-2025-68376, CVE-2025-68378, CVE-2025-68379, CVE-2025-68380, CVE-2025-68724,     CVE-2025-68726, CVE-2025-68727, CVE-2025-68728, CVE-2025-68729, CVE-2025-68730, CVE-2025-68732,     CVE-2025-68733, CVE-2025-68735, CVE-2025-68738, CVE-2025-68739, CVE-2025-68740, CVE-2025-68741,     CVE-2025-68742, CVE-2025-68743, CVE-2025-68744, CVE-2025-68746, CVE-2025-68747, CVE-2025-68748,     CVE-2025-68749, CVE-2025-68751, CVE-2025-68752, CVE-2025-68753, CVE-2025-68754, CVE-2025-68755,     CVE-2025-68756, CVE-2025-68757, CVE-2025-68758, CVE-2025-68759, CVE-2025-68760, CVE-2025-68762,     CVE-2025-68763, CVE-2025-68764, CVE-2025-68765, CVE-2025-68766, CVE-2025-71128)

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.

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

    -------------------------------------------------------------------------     Debian LTS Advisory DLA-4499-1                debian-lts@lists.debian.org     https://www.debian.org/lts/security/                        Ben Hutchings     March 13, 2026                                https://wiki.debian.org/LTS
    -------------------------------------------------------------------------

    Package        : linux-6.1     Version        : 6.1.164-1~deb11u1     CVE ID         : CVE-2023-53424 CVE-2024-26822 CVE-2024-57895 CVE-2025-22026                      CVE-2025-23155 CVE-2025-37786 CVE-2025-37822 CVE-2025-37920                      CVE-2025-38201 CVE-2025-38643 CVE-2025-39763 CVE-2025-40082                      CVE-2025-40251 CVE-2025-68358 CVE-2025-71089 CVE-2025-71144                      CVE-2025-71220 CVE-2025-71222 CVE-2025-71224 CVE-2025-71232                      CVE-2025-71233 CVE-2025-71235 CVE-2025-71236 CVE-2025-71237                      CVE-2025-71238 CVE-2026-23111 CVE-2026-23112 CVE-2026-23169                      CVE-2026-23176 CVE-2026-23178 CVE-2026-23180 CVE-2026-23182                      CVE-2026-23187 CVE-2026-23190 CVE-2026-23193 CVE-2026-23198                      CVE-2026-23202 CVE-2026-23205 CVE-2026-23206 CVE-2026-23209                      CVE-2026-23216 CVE-2026-23220 CVE-2026-23221 CVE-2026-23222                      CVE-2026-23228 CVE-2026-23229 CVE-2026-23230 CVE-2026-23234                      CVE-2026-23235 CVE-2026-23236 CVE-2026-23237 CVE-2026-23238     Debian Bug     : 1127597

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

    The Qualys Threat Research Unit (TRU) discovered several vulnerabilities     in Apparmor. Details can be found in the Qualys advisory at     https://www.qualys.com/2026/03/10/crack-armor.txt

    For Debian 11 bullseye, these problems have been fixed in version     6.1.164-1~deb11u1.  This version also fixes a regression in the     previous update.  It additionally includes many more bug fixes from     stable updates 6.1.163 and 6.1.164.

    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-6163 advisory.

    - -------------------------------------------------------------------------     Debian Security Advisory DSA-6163-1                   security@debian.org     https://www.debian.org/security/                     Salvatore Bonaccorso     March 12, 2026                        https://www.debian.org/security/faq
    - -------------------------------------------------------------------------

    Package        : linux     CVE ID         : CVE-2023-53424 CVE-2024-26822 CVE-2024-57895 CVE-2025-22026                      CVE-2025-23155 CVE-2025-37786 CVE-2025-37822 CVE-2025-37920                      CVE-2025-38201 CVE-2025-38643 CVE-2025-39763 CVE-2025-40082                      CVE-2025-40251 CVE-2025-68358 CVE-2025-71089 CVE-2025-71144                      CVE-2025-71220 CVE-2025-71222 CVE-2025-71224 CVE-2025-71232                      CVE-2025-71233 CVE-2025-71235 CVE-2025-71236 CVE-2025-71237                      CVE-2025-71238 CVE-2026-23111 CVE-2026-23112 CVE-2026-23169                      CVE-2026-23176 CVE-2026-23178 CVE-2026-23180 CVE-2026-23182                      CVE-2026-23187 CVE-2026-23190 CVE-2026-23193 CVE-2026-23198                      CVE-2026-23202 CVE-2026-23205 CVE-2026-23206 CVE-2026-23209                      CVE-2026-23216 CVE-2026-23220 CVE-2026-23221 CVE-2026-23222                      CVE-2026-23228 CVE-2026-23229 CVE-2026-23230 CVE-2026-23234                      CVE-2026-23235 CVE-2026-23236 CVE-2026-23237 CVE-2026-23238

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

    The Qualys Threat Research Unit (TRU) discovered several vulnerabilities     in Apparmor. Details can be found in the Qualys advisory at     https://www.qualys.com/2026/03/10/crack-armor.txt

    For the oldstable distribution (bookworm), these problems have been fixed     in version 6.1.164-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.

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

    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:

    sched_ext: Fix possible deadlock in the deferred_irq_workfn() (CVE-2025-68333)

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

    exfat: fix refcount leak in exfat_find (CVE-2025-68351)

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

    btrfs: fix racy bitfield write in btrfs_clear_space_info_full() (CVE-2025-68358)

    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:

    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/mlx5e: Don't store mlx5e_priv in mlx5e_dev devlink priv (CVE-2026-22996)

    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:

    net/mlx5e: Fix crash on profile change rollback failure (CVE-2026-23000)

    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:

    lib/buildid: use __kernel_read() for sleepable context (CVE-2026-23002)

    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:

    null_blk: fix kmemleak by releasing references to fault configfs items (CVE-2026-23032)

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

    net/mlx5e: Pass netdev to mlx5e_destroy_netdev instead of priv (CVE-2026-23035)

    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:

    pNFS: Fix a deadlock when returning a delegation during open() (CVE-2026-23050)

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

    NFS: Fix a deadlock involving nfs_release_folio() (CVE-2026-23053)

    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:

    vsock/virtio: Coalesce only linear skb (CVE-2026-23057)

    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:

    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:

    io_uring/io-wq: check IO_WQ_BIT_EXIT inside work run loop (CVE-2026-23113)

    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:

    btrfs: send: check for inline extents in range_is_hole_in_parent() (CVE-2026-23141)

    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)

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.

The version of kernel installed on the remote host is prior to 5.15.201-140.219. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.15-2026-098 advisory.

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

    drm/ttm: fix undefined behavior in bit shift for TTM_TT_FLAG_PRIV_POPULATED (CVE-2022-50390)

    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:

    ext4: fix memory leaks in ext4_fname_{setup_filename,prepare_lookup} (CVE-2023-53662)

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

    page_pool: Fix use-after-free in page_pool_recycle_in_ring (CVE-2025-38129)

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

    HID: core: Harden s32ton() against conversion to 0 bits (CVE-2025-38556)

    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:

    xfrm: delete x->tunnel as we delete x (CVE-2025-40215)

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

    ext4: add i_data_sem protection in ext4_destroy_inline_data_nolock() (CVE-2025-68261)

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

    ext4: refresh inline data size before write operations (CVE-2025-68264)

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

    net/sched: sch_cake: Fix incorrect qlen reduction in cake_drop (CVE-2025-68325)

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

    jbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted (CVE-2025-68337)

    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:

    NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid (CVE-2025-68349)

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

    btrfs: fix racy bitfield write in btrfs_clear_space_info_full() (CVE-2025-68358)

    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:

    nbd: defer config unlock in nbd_genl_connect (CVE-2025-68366)

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

    nbd: defer config put in recv_work (CVE-2025-68372)

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

    crypto: asymmetric_keys - prevent overflow in asymmetric_key_generate_id (CVE-2025-68724)

    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:

    ntfs3: Fix uninit buffer allocated by __getname() (CVE-2025-68727)

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

    ntfs3: fix uninit memory after failed mi_read in mi_format_new (CVE-2025-68728)

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

    ima: Handle error code returned by ima_filter_rule_match() (CVE-2025-68740)

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

    NFS: Automounted filesystems should inherit ro,noexec,nodev,sync flags (CVE-2025-68764)

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

    sched/deadline: only set free_cpus for online runqueues (CVE-2025-68780)

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

    scsi: target: Reset t_task_cdb pointer in error case (CVE-2025-68782)

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

    net: openvswitch: fix middle attribute validation in push_nsh() action (CVE-2025-68785)

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

    fsnotify: do not generate ACCESS/MODIFY events on child for special files (CVE-2025-68788)

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

    ethtool: Avoid overflowing userspace buffer on stats query (CVE-2025-68795)

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

    NFSD: NFSv4 file creation neglects setting ACL (CVE-2025-68803)

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

    ipvs: fix ipv4 null-ptr-deref in route error path (CVE-2025-68813)

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

    io_uring: fix filename leak in __io_openat_prep() (CVE-2025-68814)

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

    net/mlx5: fw_tracer, Validate format string parameters (CVE-2025-68816)

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

    ext4: xattr: fix null pointer deref in ext4_raw_inode() (CVE-2025-68820)

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

    fuse: fix readahead reclaim deadlock (CVE-2025-68821)

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

    tpm: Cap the number of PCR banks (CVE-2025-71077)

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

    drm/ttm: Avoid NULL pointer deref for evicted BOs (CVE-2025-71083)

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

    RDMA/cm: Fix leaking the multicast GID table reference (CVE-2025-71084)

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

    ipv6: BUG() in pskb_expand_head() as part of calipso_skbuff_setattr() (CVE-2025-71085)

    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:

    team: fix check for port enabled in team_queue_override_port_prio_changed() (CVE-2025-71091)

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

    e1000: fix OOB in e1000_tbi_should_accept() (CVE-2025-71093)

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

    RDMA/core: Check for the presence of LS_NLA_TYPE_DGID correctly (CVE-2025-71096)

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

    ipv4: Fix reference count leak when using error routes with nexthop objects (CVE-2025-71097)

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

    ip6_gre: make ip6gre_header() robust (CVE-2025-71098)

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

    KVM: x86: Fix VM hard lockup after prolonged inactivity with periodic HV timer (CVE-2025-71104)

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

    crypto: af_alg - zero initialize memory allocated via sock_kmalloc (CVE-2025-71113)

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

    libceph: make decode_pool() more resilient against corrupted osdmaps (CVE-2025-71116)

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

    ACPICA: Avoid walking the Namespace if start_node is NULL (CVE-2025-71118)

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

    SUNRPC: svcauth_gss: avoid NULL deref on zero length gss_token in gss_read_proxy_verf (CVE-2025-71120)

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

    tracing: Do not register unsupported perf events (CVE-2025-71125)

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

    crypto: seqiv - Do not use req->iv after crypto_aead_encrypt (CVE-2025-71131)

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

    KEYS: trusted: Fix a memory leak in tpm2_load_cmd (CVE-2025-71147)

    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: Fix NULL deref when deactivating inactive aggregate in qfq_reset (CVE-2026-22976)

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

    net: sock: fix hardened usercopy panic in sock_recv_errqueue (CVE-2026-22977)

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

    nfsd: provide locking for v4_end_grace (CVE-2026-22980)

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

    libceph: prevent potential out-of-bounds reads in handle_auth_done() (CVE-2026-22984)

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

    libceph: replace overzealous BUG_ON in osdmap_apply_incremental() (CVE-2026-22990)

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

    libceph: make free_choose_arg_map() resilient to partial allocation (CVE-2026-22991)

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

    libceph: return the handler error from mon_handle_auth_done() (CVE-2026-22992)

    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:

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

    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:

    libceph: make calc_target() set t->paused, not just clear it (CVE-2026-23047)

    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:

    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:

    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:

    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:

    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:

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

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

    mptcp: fix race in mptcp_pm_nl_flush_addrs_doit() (CVE-2026-23169)

    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:

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

    In the Linux kernel, the following vulnerability has been resolved: bus: fsl-mc: fix use-after-free in     driver_override_show() The driver_override_show() function reads the driver_override string without     holding the device_lock. However, driver_override_store() uses driver_set_override(), which modifies and     frees the string while holding the device_lock. This can result in a concurrent use-after-free if the     string is freed by the store function while being read by the show function. Fix this by holding the     device_lock around the read operation. (CVE-2026-23221)

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 13 host has packages installed that are affected by multiple vulnerabilities as referenced in the dsa-6126 advisory.

    - -------------------------------------------------------------------------     Debian Security Advisory DSA-6126-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-2024-58096 CVE-2024-58097 CVE-2025-22111 CVE-2025-38234                      CVE-2025-38248 CVE-2025-38591 CVE-2025-39872 CVE-2025-40149                      CVE-2025-40164 CVE-2025-40170 CVE-2025-40276 CVE-2025-40325                      CVE-2025-68206 CVE-2025-68333 CVE-2025-68345 CVE-2025-68351                      CVE-2025-68357 CVE-2025-68358 CVE-2025-68365 CVE-2025-68725                      CVE-2025-68749 CVE-2025-68767 CVE-2025-68769 CVE-2025-68770                      CVE-2025-68771 CVE-2025-68772 CVE-2025-68773 CVE-2025-68774                      CVE-2025-68775 CVE-2025-68776 CVE-2025-68777 CVE-2025-68778                      CVE-2025-68780 CVE-2025-68781 CVE-2025-68782 CVE-2025-68783                      CVE-2025-68784 CVE-2025-68785 CVE-2025-68786 CVE-2025-68787                      CVE-2025-68788 CVE-2025-68789 CVE-2025-68792 CVE-2025-68794                      CVE-2025-68795 CVE-2025-68796 CVE-2025-68797 CVE-2025-68798                      CVE-2025-68799 CVE-2025-68800 CVE-2025-68801 CVE-2025-68802                      CVE-2025-68803 CVE-2025-68804 CVE-2025-68806 CVE-2025-68808                      CVE-2025-68809 CVE-2025-68810 CVE-2025-68811 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-68822 CVE-2025-71064 CVE-2025-71065 CVE-2025-71066                      CVE-2025-71067 CVE-2025-71068 CVE-2025-71069 CVE-2025-71071                      CVE-2025-71072 CVE-2025-71073 CVE-2025-71075 CVE-2025-71076                      CVE-2025-71077 CVE-2025-71078 CVE-2025-71079 CVE-2025-71080                      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-71089 CVE-2025-71091 CVE-2025-71093 CVE-2025-71094                      CVE-2025-71095 CVE-2025-71096 CVE-2025-71097 CVE-2025-71098                      CVE-2025-71099 CVE-2025-71100 CVE-2025-71101 CVE-2025-71102                      CVE-2025-71104 CVE-2025-71105 CVE-2025-71107 CVE-2025-71108                      CVE-2025-71109 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-71122 CVE-2025-71123                      CVE-2025-71125 CVE-2025-71126 CVE-2025-71127 CVE-2025-71129                      CVE-2025-71130 CVE-2025-71131 CVE-2025-71132 CVE-2025-71133                      CVE-2025-71134 CVE-2025-71135 CVE-2025-71136 CVE-2025-71137                      CVE-2025-71138 CVE-2025-71140 CVE-2025-71143 CVE-2025-71144                      CVE-2025-71146 CVE-2025-71147 CVE-2025-71148 CVE-2025-71149                      CVE-2025-71150 CVE-2025-71151 CVE-2025-71153 CVE-2025-71154                      CVE-2025-71156 CVE-2025-71157 CVE-2025-71160 CVE-2025-71162                      CVE-2025-71163 CVE-2025-71180 CVE-2025-71182 CVE-2025-71183                      CVE-2025-71184 CVE-2025-71185 CVE-2025-71186 CVE-2025-71189                      CVE-2025-71190 CVE-2025-71191 CVE-2025-71192 CVE-2025-71193                      CVE-2025-71194 CVE-2025-71195 CVE-2025-71196 CVE-2025-71197                      CVE-2025-71198 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-22989 CVE-2026-22990 CVE-2026-22991                      CVE-2026-22992 CVE-2026-22994 CVE-2026-22996 CVE-2026-22997                      CVE-2026-22998 CVE-2026-22999 CVE-2026-23000 CVE-2026-23001                      CVE-2026-23002 CVE-2026-23003 CVE-2026-23005 CVE-2026-23006                      CVE-2026-23010 CVE-2026-23011 CVE-2026-23013 CVE-2026-23019                      CVE-2026-23020 CVE-2026-23021 CVE-2026-23023 CVE-2026-23025                      CVE-2026-23026 CVE-2026-23030 CVE-2026-23031 CVE-2026-23032                      CVE-2026-23033 CVE-2026-23035 CVE-2026-23037 CVE-2026-23038                      CVE-2026-23047 CVE-2026-23049 CVE-2026-23050 CVE-2026-23053                      CVE-2026-23054 CVE-2026-23055 CVE-2026-23056 CVE-2026-23057                      CVE-2026-23058 CVE-2026-23059 CVE-2026-23060 CVE-2026-23061                      CVE-2026-23062 CVE-2026-23063 CVE-2026-23064 CVE-2026-23065                      CVE-2026-23068 CVE-2026-23069 CVE-2026-23071 CVE-2026-23072                      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-23088                      CVE-2026-23089 CVE-2026-23090 CVE-2026-23091 CVE-2026-23093                      CVE-2026-23094 CVE-2026-23095 CVE-2026-23096 CVE-2026-23097                      CVE-2026-23098 CVE-2026-23099 CVE-2026-23101 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 stable distribution (trixie), these problems have been fixed in     version 6.12.69-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.

  - btrfs: fix racy bitfield write in btrfs_clear_space_info_full() From the memory-barriers.txt document     regarding memory barrier ordering guarantees: (*) These guarantees do not apply to bitfields, because     compilers often generate code to modify these using non-atomic read-modify-write sequences. Do not attempt     to use bitfields to synchronize parallel algorithms. (*) Even in cases where bitfields are protected by     locks, all fields in a given bitfield must be protected by one lock. If two fields in a given bitfield are     protected by different locks, the compiler's non-atomic read-modify-write sequences can cause an update to     one field to corrupt the value of an adjacent field. btrfs_space_info has a bitfield sharing an underlying     word consisting of the fields full, chunk_alloc, and flush: struct btrfs_space_info { struct btrfs_fs_info
    * fs_info; /* 0 8 */ struct btrfs_space_info * parent; /* 8 8 */ ... int clamp; /* 172 4 */ unsigned int     full:1; /* 176: 0 4 */ unsigned int chunk_alloc:1; /* 176: 1 4 */ unsigned int flush:1; /* 176: 2 4 */ ...
    Therefore, to be safe from parallel read-modify-writes losing a write to one of the bitfield members     protected by a lock, all writes to all the bitfields must use the lock. They almost universally do, except     for btrfs_clear_space_info_full() which iterates over the space_infos and writes out found->full = 0     without a lock. Imagine that we have one thread completing a transaction in which we finished deleting a     block_group and are thus calling btrfs_clear_space_info_full() while simultaneously the data reclaim     ticket infrastructure is running do_async_reclaim_data_space(): T1 T2 btrfs_commit_transaction     btrfs_clear_space_info_full data_sinfo->full = 0 READ: full:0, chunk_alloc:0, flush:1     do_async_reclaim_data_space(data_sinfo) spin_lock(&space_info->lock); if(list_empty(tickets))     space_info->flush = 0; READ: full: 0, chunk_alloc:0, flush:1 MOD/WRITE: full: 0, chunk_alloc:0, flush:0     spin_unlock(&space_info->lock); return; MOD/WRITE: full:0, chunk_alloc:0, flush:1 and now     data_sinfo->flush is 1 but the reclaim worker has exited. This breaks the invariant that flush is 0 iff     there is no work queued or running. Once this invariant is violated, future allocations that go into
    __reserve_bytes() will add tickets to space_info->tickets but will see space_info->flush is set to 1 and     not queue the work. After this, they will block forever on the resulting ticket, as it is now impossible     to kick the worker again. I also confirmed by looking at the assembly of the affected kernel that it is     doing RMW operations. For example, to set the flush (3rd) bit to 0, the assembly is: andb $0xfb,0x60(%rbx)     and similarly for setting the full (1st) bit to 0: andb $0xfe,-0x20(%rax) So I think this is really a bug     on practical systems. I have observed a number of systems in this exact state, but am currently unable to     reproduce it. Rather than leaving this footgun lying around for the future, take advantage of the fact     that there is room in the struct anyway, and that it is already quite large and simply change the three     bitfield members to bools. This avoids writes to space_info->full having any effect on ---truncated---     (CVE-2025-68358)

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

ID	Name	Product	Family	Severity
303082	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.15-2026-099 (ALASKERNEL-5.15-2026-099)	Nessus	Amazon Linux Local Security Checks	high
302766	Ubuntu 24.04 LTS / 25.10 : Linux kernel vulnerabilities (USN-8094-1)	Nessus	Ubuntu Local Security Checks	high
302188	Debian dla-4499 : linux-config-6.1 - security update	Nessus	Debian Local Security Checks	critical
302008	Debian dsa-6163 : affs-modules-6.1.0-43-4kc-malta-di - security update	Nessus	Debian Local Security Checks	critical
301337	Amazon Linux 2023 : bpftool6.12, kernel6.12, kernel6.12-devel (ALAS2023-2026-1455)	Nessus	Amazon Linux Local Security Checks	high
301269	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.15-2026-098 (ALASKERNEL-5.15-2026-098)	Nessus	Amazon Linux Local Security Checks	high
300899	Photon OS 5.0: Linux PHSA-2026-5.0-0779	Nessus	PhotonOS Local Security Checks	medium
298403	Debian dsa-6126 : ata-modules-6.12.31-armmp-di - security update	Nessus	Debian Local Security Checks	high
279768	Linux Distros Unpatched Vulnerability : CVE-2025-68358	Nessus	Misc.	medium

Detections

Analytics

CVE-2025-68358

medium

Tenable Plugins

high

high

critical

critical

high

high

medium

high

medium