In the Linux kernel, the following vulnerability has been resolved: Revert "wireguard: device: enable threaded NAPI" This reverts commit 933466fc50a8e4eb167acbd0d8ec96a078462e9c which is commit db9ae3b6b43c79b1ba87eea849fd65efa05b4b2e upstream. We have had three independent production user reports in combination with Cilium utilizing WireGuard as encryption underneath that k8s Pod E/W traffic to certain peer nodes fully stalled. The situation appears as follows: - Occurs very rarely but at random times under heavy networking load. - Once the issue triggers the decryption side stops working completely for that WireGuard peer, other peers keep working fine. The stall happens also for newly initiated connections towards that particular WireGuard peer. - Only the decryption side is affected, never the encryption side. - Once it triggers, it never recovers and remains in this state, the CPU/mem on that node looks normal, no leak, busy loop or crash. - bpftrace on the affected system shows that wg_prev_queue_enqueue fails, thus the MAX_QUEUED_PACKETS (1024 skbs!) for the peer's rx_queue is reached. - Also, bpftrace shows that wg_packet_rx_poll for that peer is never called again after reaching this state for that peer. For other peers wg_packet_rx_poll does get called normally. - Commit db9ae3b ("wireguard: device: enable threaded NAPI") switched WireGuard to threaded NAPI by default. The default has not been changed for triggering the issue, neither did CPU hotplugging occur (i.e. 5bd8de2 ("wireguard: queueing: always return valid online CPU in wg_cpumask_choose_online()")). - The issue has been observed with stable kernels of v5.15 as well as v6.1. It was reported to us that v5.10 stable is working fine, and no report on v6.6 stable either (somewhat related discussion in [0] though). - In the WireGuard driver the only material difference between v5.10 stable and v5.15 stable is the switch to threaded NAPI by default. [0] https://lore.kernel.org/netdev/CA+wXwBTT74RErDGAnj98PqS=wvdh8eM1pi4q6tTdExtjnokKqA@mail.gmail.com/ Breakdown of the problem: 1) skbs arriving for decryption are enqueued to the peer->rx_queue in wg_packet_consume_data via wg_queue_enqueue_per_device_and_peer. 2) The latter only moves the skb into the MPSC peer queue if it does not surpass MAX_QUEUED_PACKETS (1024) which is kept track in an atomic counter via wg_prev_queue_enqueue. 3) In case enqueueing was successful, the skb is also queued up in the device queue, round-robin picks a next online CPU, and schedules the decryption worker. 4) The wg_packet_decrypt_worker, once scheduled, picks these up from the queue, decrypts the packets and once done calls into wg_queue_enqueue_per_peer_rx. 5) The latter updates the state to PACKET_STATE_CRYPTED on success and calls napi_schedule on the per peer->napi instance. 6) NAPI then polls via wg_packet_rx_poll. wg_prev_queue_peek checks on the peer->rx_queue. It will wg_prev_queue_dequeue if the queue->peeked skb was not cached yet, or just return the latter otherwise. (wg_prev_queue_drop_peeked later clears the cache.) 7) From an ordering perspective, the peer->rx_queue has skbs in order while the device queue with the per-CPU worker threads from a global ordering PoV can finish the decryption and signal the skb PACKET_STATE_CRYPTED out of order. 8) A situation can be observed that the first packet coming in will be stuck waiting for the decryption worker to be scheduled for a longer time when the system is under pressure. 9) While this is the case, the other CPUs in the meantime finish decryption and call into napi_schedule. 10) Now in wg_packet_rx_poll it picks up the first in-order skb from the peer->rx_queue and sees that its state is still PACKET_STATE_UNCRYPTED. The NAPI poll routine then exits e ---truncated---

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - In the Linux kernel, the following vulnerability has been resolved: Revert "wireguard: device: enable
    threaded NAPI" This reverts commit 933466fc50a8e4eb167acbd0d8ec96a078462e9c which is commit
    db9ae3b6b43c79b1ba87eea849fd65efa05b4b2e upstream. We have had three independent production user reports
    in combination with Cilium utilizing WireGuard as encryption underneath that k8s Pod E/W traffic to
    certain peer nodes fully stalled. The situation appears as follows: - Occurs very rarely but at random
    times under heavy networking load. - Once the issue triggers the decryption side stops working completely
    for that WireGuard peer, other peers keep working fine. The stall happens also for newly initiated
    connections towards that particular WireGuard peer. - Only the decryption side is affected, never the
    encryption side. - Once it triggers, it never recovers and remains in this state, the CPU/mem on that node
    looks normal, no leak, busy loop or crash. - bpftrace on the affected system shows that
    wg_prev_queue_enqueue fails, thus the MAX_QUEUED_PACKETS (1024 skbs!) for the peer's rx_queue is reached.
    - Also, bpftrace shows that wg_packet_rx_poll for that peer is never called again after reaching this
    state for that peer. For other peers wg_packet_rx_poll does get called normally. - Commit db9ae3b
    ("wireguard: device: enable threaded NAPI") switched WireGuard to threaded NAPI by default. The default
    has not been changed for triggering the issue, neither did CPU hotplugging occur (i.e. 5bd8de2
    ("wireguard: queueing: always return valid online CPU in wg_cpumask_choose_online()")). - The issue has
    been observed with stable kernels of v5.15 as well as v6.1. It was reported to us that v5.10 stable is
    working fine, and no report on v6.6 stable either (somewhat related discussion in [0] though). - In the
    WireGuard driver the only material difference between v5.10 stable and v5.15 stable is the switch to
    threaded NAPI by default. [0]
    https://lore.kernel.org/netdev/CA+wXwBTT74RErDGAnj98PqS=wvdh8eM1pi4q6tTdExtjnokKqA@mail.gmail.com/
    Breakdown of the problem: 1) skbs arriving for decryption are enqueued to the peer->rx_queue in
    wg_packet_consume_data via wg_queue_enqueue_per_device_and_peer. 2) The latter only moves the skb into the
    MPSC peer queue if it does not surpass MAX_QUEUED_PACKETS (1024) which is kept track in an atomic counter
    via wg_prev_queue_enqueue. 3) In case enqueueing was successful, the skb is also queued up in the device
    queue, round-robin picks a next online CPU, and schedules the decryption worker. 4) The
    wg_packet_decrypt_worker, once scheduled, picks these up from the queue, decrypts the packets and once
    done calls into wg_queue_enqueue_per_peer_rx. 5) The latter updates the state to PACKET_STATE_CRYPTED on
    success and calls napi_schedule on the per peer->napi instance. 6) NAPI then polls via wg_packet_rx_poll.
    wg_prev_queue_peek checks on the peer->rx_queue. It will wg_prev_queue_dequeue if the queue->peeked skb
    was not cached yet, or just return the latter otherwise. (wg_prev_queue_drop_peeked later clears the
    cache.) 7) From an ordering perspective, the peer->rx_queue has skbs in order while the device queue with
    the per-CPU worker threads from a global ordering PoV can finish the decryption and signal the skb
    PACKET_STATE_CRYPTED out of order. 8) A situation can be observed that the first packet coming in will be
    stuck waiting for the decryption worker to be scheduled for a longer time when the system is under
    pressure. 9) While this is the case, the other CPUs in the meantime finish decryption and call into
    napi_schedule. 10) Now in wg_packet_rx_poll it picks up the first in-order skb from the peer->rx_queue and
    sees that its state is still PACKET_STATE_UNCRYPTED. The NAPI poll routine then exits e ---truncated---
    (CVE-2026-52945)

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - Revert wireguard: device: enable threaded NAPI This reverts commit     933466fc50a8e4eb167acbd0d8ec96a078462e9c which is commit db9ae3b6b43c79b1ba87eea849fd65efa05b4b2e     upstream. We have had three independent production user reports in combination with Cilium utilizing     WireGuard as encryption underneath that k8s Pod E/W traffic to certain peer nodes fully stalled. The     situation appears as follows: - Occurs very rarely but at random times under heavy networking load. - Once     the issue triggers the decryption side stops working completely for that WireGuard peer, other peers keep     working fine. The stall happens also for newly initiated connections towards that particular WireGuard     peer. - Only the decryption side is affected, never the encryption side. - Once it triggers, it never     recovers and remains in this state, the CPU/mem on that node looks normal, no leak, busy loop or crash. -     bpftrace on the affected system shows that wg_prev_queue_enqueue fails, thus the MAX_QUEUED_PACKETS (1024     skbs!) for the peer's rx_queue is reached. - Also, bpftrace shows that wg_packet_rx_poll for that peer is     never called again after reaching this state for that peer. For other peers wg_packet_rx_poll does get     called normally. - Commit db9ae3b (wireguard: device: enable threaded NAPI) switched WireGuard to     threaded NAPI by default. The default has not been changed for triggering the issue, neither did CPU     hotplugging occur (i.e. 5bd8de2 (wireguard: queueing: always return valid online CPU in     wg_cpumask_choose_online())). - The issue has been observed with stable kernels of v5.15 as well as v6.1.
    It was reported to us that v5.10 stable is working fine, and no report on v6.6 stable either (somewhat     related discussion in [0] though). - In the WireGuard driver the only material difference between v5.10     stable and v5.15 stable is the switch to threaded NAPI by default. [0]     https://lore.kernel.org/netdev/CA+wXwBTT74RErDGAnj98PqS=wvdh8eM1pi4q6tTdExtjnokKqA@mail.gmail.com/     Breakdown of the problem: 1) skbs arriving for decryption are enqueued to the peer->rx_queue in     wg_packet_consume_data via wg_queue_enqueue_per_device_and_peer. 2) The latter only moves the skb into the     MPSC peer queue if it does not surpass MAX_QUEUED_PACKETS (1024) which is kept track in an atomic counter     via wg_prev_queue_enqueue. 3) In case enqueueing was successful, the skb is also queued up in the device     queue, round-robin picks a next online CPU, and schedules the decryption worker. 4) The     wg_packet_decrypt_worker, once scheduled, picks these up from the queue, decrypts the packets and once     done calls into wg_queue_enqueue_per_peer_rx. 5) The latter updates the state to PACKET_STATE_CRYPTED on     success and calls napi_schedule on the per peer->napi instance. 6) NAPI then polls via wg_packet_rx_poll.
    wg_prev_queue_peek checks on the peer->rx_queue. It will wg_prev_queue_dequeue if the queue->peeked skb     was not cached yet, or just return the latter otherwise. (wg_prev_queue_drop_peeked later clears the     cache.) 7) From an ordering perspective, the peer->rx_queue has skbs in order while the device queue with     the per-CPU worker threads from a global ordering PoV can finish the decryption and signal the skb     PACKET_STATE_CRYPTED out of order. 8) A situation can be observed that the first packet coming in will be     stuck waiting for the decryption worker to be scheduled for a longer time when the system is under     pressure. 9) While this is the case, the other CPUs in the meantime finish decryption and call into     napi_schedule. 10) Now in wg_packet_rx_poll it picks up the first in-order skb from the peer->rx_queue and     sees that its state is still PACKET_STATE_UNCRYPTED. The NAPI poll routine then exits e ---truncated---     (CVE-2026-52945)

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

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

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

    clk: mediatek: fix of_iomap memory leak (CVE-2023-53424)

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

    wifi: cfg80211: Add missing lock in cfg80211_check_and_end_cac() (CVE-2025-38643)

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

    ACPI: APEI: send SIGBUS to current task if synchronous memory error not recovered (CVE-2025-39763)

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

    devlink: rate: Unset parent pointer in devl_rate_nodes_destroy (CVE-2025-40251)

    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:

    mptcp: ensure context reset on disconnect() (CVE-2025-71144)

    In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Free sp in error path     to fix system crash System crash seen during load/unload test in a loop, [61110.449331] qla2xxx     [0000:27:00.0]-0042:0: Disabled MSI-X. [61110.467494]     ============================================================================= [61110.467498] BUG     qla2xxx_srbs (Tainted: G OE -------- --- ): Objects remaining in qla2xxx_srbs on __kmem_cache_shutdown()     [61110.467501] -----------------------------------------------------------------------------     [61110.467502] Slab 0x000000000ffc8162 objects=51 used=1 fp=0x00000000e25d3d85     flags=0x57ffffc0010200(slab|head|node=1|zone=2|lastcpupid=0x1fffff) [61110.467509] CPU: 53 PID: 455206     Comm: rmmod Kdump: loaded Tainted: G OE -------- --- 5.14.0-284.11.1.el9_2.x86_64 #1 [61110.467513]     Hardware name: HPE ProLiant DL385 Gen10 Plus v2/ProLiant DL385 Gen10 Plus v2, BIOS A42 08/17/2023     [61110.467515] Call Trace: [61110.467516] <TASK> [61110.467519] dump_stack_lvl+0x34/0x48 [61110.467526]     slab_err.cold+0x53/0x67 [61110.467534] __kmem_cache_shutdown+0x16e/0x320 [61110.467540]     kmem_cache_destroy+0x51/0x160 [61110.467544] qla2x00_module_exit+0x93/0x99 [qla2xxx] [61110.467607] ?
    __do_sys_delete_module.constprop.0+0x178/0x280 [61110.467613] ?     syscall_trace_enter.constprop.0+0x145/0x1d0 [61110.467616] ? do_syscall_64+0x5c/0x90 [61110.467619] ?     exc_page_fault+0x62/0x150 [61110.467622] ? entry_SYSCALL_64_after_hwframe+0x63/0xcd [61110.467626] </TASK>     [61110.467627] Disabling lock debugging due to kernel taint [61110.467635] Object 0x0000000026f7e6e6     @offset=16000 [61110.467639] ------------[ cut here ]------------ [61110.467639] kmem_cache_destroy     qla2xxx_srbs: Slab cache still has objects when called from qla2x00_module_exit+0x93/0x99 [qla2xxx]     [61110.467659] WARNING: CPU: 53 PID: 455206 at mm/slab_common.c:520 kmem_cache_destroy+0x14d/0x160     [61110.467718] CPU: 53 PID: 455206 Comm: rmmod Kdump: loaded Tainted: G B OE -------- ---     5.14.0-284.11.1.el9_2.x86_64 #1 [61110.467720] Hardware name: HPE ProLiant DL385 Gen10 Plus v2/ProLiant     DL385 Gen10 Plus v2, BIOS A42 08/17/2023 [61110.467721] RIP: 0010:kmem_cache_destroy+0x14d/0x160     [61110.467724] Code: 99 7d 07 00 48 89 ef e8 e1 6a 07 00 eb b3 48 8b 55 60 48 8b 4c 24 20 48 c7 c6 70 fc     66 90 48 c7 c7 f8 ef a1 90 e8 e1 ed 7c 00 <0f> 0b eb 93 c3 cc cc cc cc 66 2e 0f 1f 84 00 00 00 00 00 55 48     89 [61110.467725] RSP: 0018:ffffa304e489fe80 EFLAGS: 00010282 [61110.467727] RAX: 0000000000000000 RBX:
    ffffffffc0d9a860 RCX: 0000000000000027 [61110.467729] RDX: ffff8fd5ff9598a8 RSI: 0000000000000001 RDI:
    ffff8fd5ff9598a0 [61110.467730] RBP: ffff8fb6aaf78700 R08: 0000000000000000 R09: 0000000100d863b7     [61110.467731] R10: ffffa304e489fd20 R11: ffffffff913bef48 R12: 0000000040002000 [61110.467731] R13:
    0000000000000000 R14: 0000000000000000 R15: 0000000000000000 [61110.467733] FS: 00007f64c89fb740(0000)     GS:ffff8fd5ff940000(0000) knlGS:0000000000000000 [61110.467734] CS: 0010 DS: 0000 ES: 0000 CR0:
    0000000080050033 [61110.467735] CR2: 00007f0f02bfe000 CR3: 00000020ad6dc005 CR4: 0000000000770ee0     [61110.467736] PKRU: 55555554 [61110.467737] Call Trace: [61110.467738] <TASK> [61110.467739]     qla2x00_module_exit+0x93/0x99 [qla2xxx] [61110.467755] ? __do_sys_delete_module.constprop.0+0x178/0x280     Free sp in the error path to fix the crash. (CVE-2025-71232)

    In the Linux kernel, the following vulnerability has been resolved: PCI: endpoint: Avoid creating sub-     groups asynchronously The asynchronous creation of sub-groups by a delayed work could lead to a NULL     pointer dereference when the driver directory is removed before the work completes. The crash can be     easily reproduced with the following commands: # cd /sys/kernel/config/pci_ep/functions/pci_epf_test # for     i in {1..20}; do mkdir test && rmdir test; done BUG: kernel NULL pointer dereference, address:
    0000000000000088 ... Call Trace: configfs_register_group+0x3d/0x190 pci_epf_cfs_work+0x41/0x110     process_one_work+0x18f/0x350 worker_thread+0x25a/0x3a0 Fix this issue by using     configfs_add_default_group() API which does not have the deadlock problem as configfs_register_group() and     does not require the delayed work handler. [mani: slightly reworded the description and added stable list]     (CVE-2025-71233)

    In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Delay module unload     while fabric scan in progress System crash seen during load/unload test in a loop. [105954.384919] RBP:
    ffff914589838dc0 R08: 0000000000000000 R09: 0000000000000086 [105954.384920] R10: 000000000000000f R11:
    ffffa31240904be5 R12: ffff914605f868e0 [105954.384921] R13: ffff914605f86910 R14: 0000000000008010 R15:
    00000000ddb7c000 [105954.384923] FS: 0000000000000000(0000) GS:ffff9163fec40000(0000)     knlGS:0000000000000000 [105954.384925] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [105954.384926]     CR2: 000055d31ce1d6a0 CR3: 0000000119f5e001 CR4: 0000000000770ee0 [105954.384928] PKRU: 55555554     [105954.384929] Call Trace: [105954.384931] <IRQ> [105954.384934] qla24xx_sp_unmap+0x1f3/0x2a0 [qla2xxx]     [105954.384962] ? qla_async_scan_sp_done+0x114/0x1f0 [qla2xxx] [105954.384980] ?     qla24xx_els_ct_entry+0x4de/0x760 [qla2xxx] [105954.384999] ? __wake_up_common+0x80/0x190 [105954.385004] ?     qla24xx_process_response_queue+0xc2/0xaa0 [qla2xxx] [105954.385023] ? qla24xx_msix_rsp_q+0x44/0xb0     [qla2xxx] [105954.385040] ? __handle_irq_event_percpu+0x3d/0x190 [105954.385044] ?     handle_irq_event+0x58/0xb0 [105954.385046] ? handle_edge_irq+0x93/0x240 [105954.385050] ?
    __common_interrupt+0x41/0xa0 [105954.385055] ? common_interrupt+0x3e/0xa0 [105954.385060] ?     asm_common_interrupt+0x22/0x40 The root cause of this was that there was a free (dma_free_attrs) in the     interrupt context. There was a device discovery/fabric scan in progress. A module unload was issued which     set the UNLOADING flag. As part of the discovery, after receiving an interrupt a work queue was scheduled     (which involved a work to be queued). Since the UNLOADING flag is set, the work item was not allocated and     the mapped memory had to be freed. The free occurred in interrupt context leading to system crash. Delay     the driver unload until the fabric scan is complete to avoid the crash. (CVE-2025-71235)

    In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Validate sp before     freeing associated memory System crash with the following signature [154563.214890] nvme nvme2: NVME-     FC{1}: controller connect complete [154564.169363] qla2xxx [0000:b0:00.1]-3002:2: nvme: Sched: Set ZIO     exchange threshold to 3. [154564.169405] qla2xxx [0000:b0:00.1]-ffffff:2: SET ZIO Activity exchange     threshold to 5. [154565.539974] qla2xxx [0000:b0:00.1]-5013:2: RSCN database changed - 0078 0080 0000.
    [154565.545744] qla2xxx [0000:b0:00.1]-5013:2: RSCN database changed - 0078 00a0 0000. [154565.545857]     qla2xxx [0000:b0:00.1]-11a2:2: FEC=enabled (data rate). [154565.552760] qla2xxx [0000:b0:00.1]-11a2:2:
    FEC=enabled (data rate). [154565.553079] BUG: kernel NULL pointer dereference, address: 00000000000000f8     [154565.553080] #PF: supervisor read access in kernel mode [154565.553082] #PF: error_code(0x0000) - not-     present page [154565.553084] PGD 80000010488ab067 P4D 80000010488ab067 PUD 104978a067 PMD 0     [154565.553089] Oops: 0000 1 PREEMPT SMP PTI [154565.553092] CPU: 10 PID: 858 Comm: qla2xxx_2_dpc Kdump:
    loaded Tainted: G OE ------- --- 5.14.0-503.11.1.el9_5.x86_64 #1 [154565.553096] Hardware name: HPE     Synergy 660 Gen10/Synergy 660 Gen10 Compute Module, BIOS I43 09/30/2024 [154565.553097] RIP:
    0010:qla_fab_async_scan.part.0+0x40b/0x870 [qla2xxx] [154565.553141] Code: 00 00 e8 58 a3 ec d4 49 89 e9     ba 12 20 00 00 4c 89 e6 49 c7 c0 00 ee a8 c0 48 c7 c1 66 c0 a9 c0 bf 00 80 00 10 e8 15 69 00 00 <4c> 8b 8d     f8 00 00 00 4d 85 c9 74 35 49 8b 84 24 00 19 00 00 48 8b [154565.553143] RSP: 0018:ffffb4dbc8aebdd0     EFLAGS: 00010286 [154565.553145] RAX: 0000000000000000 RBX: ffff8ec2cf0908d0 RCX: 0000000000000002     [154565.553147] RDX: 0000000000000000 RSI: ffffffffc0a9c896 RDI: ffffb4dbc8aebd47 [154565.553148] RBP:
    0000000000000000 R08: ffffb4dbc8aebd45 R09: 0000000000ffff0a [154565.553150] R10: 0000000000000000 R11:
    000000000000000f R12: ffff8ec2cf0908d0 [154565.553151] R13: ffff8ec2cf090900 R14: 0000000000000102 R15:
    ffff8ec2cf084000 [154565.553152] FS: 0000000000000000(0000) GS:ffff8ed27f800000(0000)     knlGS:0000000000000000 [154565.553154] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [154565.553155]     CR2: 00000000000000f8 CR3: 000000113ae0a005 CR4: 00000000007706f0 [154565.553157] DR0: 0000000000000000     DR1: 0000000000000000 DR2: 0000000000000000 [154565.553158] DR3: 0000000000000000 DR6: 00000000fffe0ff0     DR7: 0000000000000400 [154565.553159] PKRU: 55555554 [154565.553160] Call Trace: [154565.553162] <TASK>     [154565.553165] ? show_trace_log_lvl+0x1c4/0x2df [154565.553172] ? show_trace_log_lvl+0x1c4/0x2df     [154565.553177] ? qla_fab_async_scan.part.0+0x40b/0x870 [qla2xxx] [154565.553215] ?
    __die_body.cold+0x8/0xd [154565.553218] ? page_fault_oops+0x134/0x170 [154565.553223] ? snprintf+0x49/0x70     [154565.553229] ? exc_page_fault+0x62/0x150 [154565.553238] ? asm_exc_page_fault+0x22/0x30 Check for sp     being non NULL before freeing any associated memory (CVE-2025-71236)

    In the Linux kernel, the following vulnerability has been resolved: nilfs2: Fix potential block overflow     that cause system hang When a user executes the FITRIM command, an underflow can occur when calculating     nblocks if end_block is too small. Since nblocks is of type sector_t, which is u64, a negative nblocks     value will become a very large positive integer. This ultimately leads to the block layer function
    __blkdev_issue_discard() taking an excessively long time to process the bio chain, and the ns_segctor_sem     lock remains held for a long period. This prevents other tasks from acquiring the ns_segctor_sem lock,     resulting in the hang reported by syzbot in [1]. If the ending block is too small, typically if it is     smaller than 4KiB range, depending on the usage of the segment 0, it may be possible to attempt a discard     request beyond the device size causing the hang. Exiting successfully and assign the discarded size (0 in     this case) to range->len. Although the start and len values in the user input range are too small, a     conservative strategy is adopted here to safely ignore them, which is equivalent to a no-op; it will not     perform any trimming and will not throw an error. [1] task:segctord state:D stack:28968 pid:6093 tgid:6093     ppid:2 task_flags:0x200040 flags:0x00080000 Call Trace: rwbase_write_lock+0x3dd/0x750     kernel/locking/rwbase_rt.c:272 nilfs_transaction_lock+0x253/0x4c0 fs/nilfs2/segment.c:357     nilfs_segctor_thread_construct fs/nilfs2/segment.c:2569 [inline] nilfs_segctor_thread+0x6ec/0xe00     fs/nilfs2/segment.c:2684 [ryusuke: corrected part of the commit message about the consequences]     (CVE-2025-71237)

    In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Fix bsg_done() causing     double free Kernel panic observed on system, [5353358.825191] BUG: unable to handle page fault for     address: ff5f5e897b024000 [5353358.825194] #PF: supervisor write access in kernel mode [5353358.825195]     #PF: error_code(0x0002) - not-present page [5353358.825196] PGD 100006067 P4D 0 [5353358.825198] Oops:
    0002 [#1] PREEMPT SMP NOPTI [5353358.825200] CPU: 5 PID: 2132085 Comm: qlafwupdate.sub Kdump: loaded     Tainted: G W L ------- --- 5.14.0-503.34.1.el9_5.x86_64 #1 [5353358.825203] Hardware name: HPE ProLiant     DL360 Gen11/ProLiant DL360 Gen11, BIOS 2.44 01/17/2025 [5353358.825204] RIP: 0010:memcpy_erms+0x6/0x10     [5353358.825211] RSP: 0018:ff591da8f4f6b710 EFLAGS: 00010246 [5353358.825212] RAX: ff5f5e897b024000 RBX:
    0000000000007090 RCX: 0000000000001000 [5353358.825213] RDX: 0000000000001000 RSI: ff591da8f4fed090 RDI:
    ff5f5e897b024000 [5353358.825214] RBP: 0000000000010000 R08: ff5f5e897b024000 R09: 0000000000000000     [5353358.825215] R10: ff46cf8c40517000 R11: 0000000000000001 R12: 0000000000008090 [5353358.825216] R13:
    ff591da8f4f6b720 R14: 0000000000001000 R15: 0000000000000000 [5353358.825218] FS: 00007f1e88d47740(0000)     GS:ff46cf935f940000(0000) knlGS:0000000000000000 [5353358.825219] CS: 0010 DS: 0000 ES: 0000 CR0:
    0000000080050033 [5353358.825220] CR2: ff5f5e897b024000 CR3: 0000000231532004 CR4: 0000000000771ef0     [5353358.825221] PKRU: 55555554 [5353358.825222] Call Trace: [5353358.825223] <TASK> [5353358.825224] ?     show_trace_log_lvl+0x1c4/0x2df [5353358.825229] ? show_trace_log_lvl+0x1c4/0x2df [5353358.825232] ?     sg_copy_buffer+0xc8/0x110 [5353358.825236] ? __die_body.cold+0x8/0xd [5353358.825238] ?     page_fault_oops+0x134/0x170 [5353358.825242] ? kernelmode_fixup_or_oops+0x84/0x110 [5353358.825244] ?     exc_page_fault+0xa8/0x150 [5353358.825247] ? asm_exc_page_fault+0x22/0x30 [5353358.825252] ?     memcpy_erms+0x6/0x10 [5353358.825253] sg_copy_buffer+0xc8/0x110 [5353358.825259]     qla2x00_process_vendor_specific+0x652/0x1320 [qla2xxx] [5353358.825317] qla24xx_bsg_request+0x1b2/0x2d0     [qla2xxx] Most routines in qla_bsg.c call bsg_done() only for success cases. However a few invoke it for     failure case as well leading to a double free. Validate before calling bsg_done(). (CVE-2025-71238)

    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: 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)

    In the Linux kernel, the following vulnerability has been resolved: crypto: omap - Allocate     OMAP_CRYPTO_FORCE_COPY scatterlists correctly The existing allocation of scatterlists in     omap_crypto_copy_sg_lists() was allocating an array of scatterlist pointers, not scatterlist objects,     resulting in a 4x too small allocation. Use sizeof(*new_sg) to get the correct object size.
    (CVE-2026-23222)

    In the Linux kernel, the following vulnerability has been resolved: smb: server: fix leak of     active_num_conn in ksmbd_tcp_new_connection() On kthread_run() failure in ksmbd_tcp_new_connection(), the     transport is freed via free_transport(), which does not decrement active_num_conn, leaking this counter.
    Replace free_transport() with ksmbd_tcp_disconnect(). (CVE-2026-23228)

    In the Linux kernel, the following vulnerability has been resolved: crypto: virtio - Add spinlock     protection with virtqueue notification When VM boots with one virtio-crypto PCI device and builtin     backend, run openssl benchmark command with multiple processes, such as openssl speed -evp aes-128-cbc
    -engine afalg -seconds 10 -multi 32 openssl processes will hangup and there is error reported like this:
    virtio_crypto virtio0: dataq.0:id 3 is not a head! It seems that the data virtqueue need protection when     it is handled for virtio done notification. If the spinlock protection is added in virtcrypto_done_task(),     openssl benchmark with multiple processes works well. (CVE-2026-23229)

    In the Linux kernel, the following vulnerability has been resolved: smb: client: split cached_fid     bitfields to avoid shared-byte RMW races is_open, has_lease and on_list are stored in the same bitfield     byte in struct cached_fid but are updated in different code paths that may run concurrently. Bitfield     assignments generate byte read-modify-write operations (e.g. `orb $mask, addr` on x86_64), so updating one     flag can restore stale values of the others. A possible interleaving is: CPU1: load old byte (has_lease=1,     on_list=1) CPU2: clear both flags (store 0) CPU1: RMW store (old | IS_OPEN) -> reintroduces cleared bits     To avoid this class of races, convert these flags to separate bool fields. (CVE-2026-23230)

    In the Linux kernel, the following vulnerability has been resolved: romfs: check sb_set_blocksize() return     value romfs_fill_super() ignores the return value of sb_set_blocksize(), which can fail if the requested     block size is incompatible with the block device's configuration. This can be triggered by setting a loop     device's block size larger than PAGE_SIZE using ioctl(LOOP_SET_BLOCK_SIZE, 32768), then mounting a romfs     filesystem on that device. When sb_set_blocksize(sb, ROMBSIZE) is called with ROMBSIZE=4096 but the device     has logical_block_size=32768, bdev_validate_blocksize() fails because the requested size is smaller than     the device's logical block size. sb_set_blocksize() returns 0 (failure), but romfs ignores this and     continues mounting. The superblock's block size remains at the device's logical block size (32768). Later,     when sb_bread() attempts I/O with this oversized block size, it triggers a kernel BUG in folio_set_bh():
    kernel BUG at fs/buffer.c:1582! BUG_ON(size > PAGE_SIZE); Fix by checking the return value of     sb_set_blocksize() and failing the mount with -EINVAL if it returns 0. (CVE-2026-23238)

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

    macvlan: observe an RCU grace period in macvlan_common_newlink() error path (CVE-2026-23273)

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

    Revert wireguard: device: enable threaded NAPI (CVE-2026-52945)

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.

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

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

    mm/hugetlb: fix hugetlb_pmd_shared() (CVE-2026-23100)

    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)

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

    tracing/dma: Cap dma_map_sg tracepoint arrays to prevent buffer overflow (CVE-2026-23390)

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

    Revert wireguard: device: enable threaded NAPI (CVE-2026-52945)

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)

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

    Revert wireguard: device: enable threaded NAPI (CVE-2026-52945)

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.

ID	Name	Product	Family	Type	Severity
467758	Google: sys-kernel/csql-kernel-6_6, sys-kernel/lakitu-kernel-6_6, sys-kernel/lakitu-nc-kernel-6_6, sys-kernel/lakitu-vgpu-kernel-6_6: security update to 18867.199.19	Tenable Cloud Security	Google COS Security Checks	Local	high
467758	Google: sys-kernel/csql-kernel-6_6, sys-kernel/lakitu-kernel-6_6, sys-kernel/lakitu-nc-kernel-6_6, sys-kernel/lakitu-vgpu-kernel-6_6: security update to 18867.199.19	Tenable Self-Hosted Container Security	Google COS Security Checks	Local	high
466158	Google: sys-kernel/csql-kernel-6_1, sys-kernel/csql-kernel-6_6, sys-kernel/lakitu-kernel-6_1, sys-kernel/lakitu-kernel-6_6, sys-kernel/lakitu-nc-kernel-6_6, sys-kernel/lakitu-vgpu-kernel-6_6, sys-kernel/tpusev-kernel-6_6: security update to 18613.339.11	Tenable Cloud Security	Google COS Security Checks	Local	high
466158	Google: sys-kernel/csql-kernel-6_1, sys-kernel/csql-kernel-6_6, sys-kernel/lakitu-kernel-6_1, sys-kernel/lakitu-kernel-6_6, sys-kernel/lakitu-nc-kernel-6_6, sys-kernel/lakitu-vgpu-kernel-6_6, sys-kernel/tpusev-kernel-6_6: security update to 18613.339.11	Tenable Self-Hosted Container Security	Google COS Security Checks	Local	high
323541	Linux Distros Unpatched Vulnerability : CVE-2026-52945	Nessus	Misc.	Local	high
304299	Amazon Linux 2023 : bpftool, kernel, kernel-devel (ALAS2023-2026-1491)	Nessus	Amazon Linux Local Security Checks	Local	high
304278	Amazon Linux 2023 : bpftool6.12, kernel6.12, kernel6.12-devel (ALAS2023-2026-1489)	Nessus	Amazon Linux Local Security Checks	Local	high
301269	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.15-2026-098 (ALASKERNEL-5.15-2026-098)	Nessus	Amazon Linux Local Security Checks	Local	high

Detections

Analytics

CVE-2026-52945

high

Tenable Plugins

high

high

high

high

high

high

high

high