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.

amazon_alas ALAS2023-2026-1491: Amazon Linux 2023 Security Advisory:ALAS2023-2026-1491

The version of kernel installed on the remote host is prior to 5.10.251-248.983. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.10-2026-114 advisory.

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

    HID: uclogic: Correct devm device reference for hidinput input_dev name (CVE-2023-54207)

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

    driver core: fix potential null-ptr-deref in device_add() (CVE-2023-54321)

    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:

    ksm: use range-walk function to jump over holes in scan_get_next_rmap_item (CVE-2025-68211)

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

    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:

    leds: led-class: Only Add LED to leds_list when it is fully ready (CVE-2026-23101)

    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:

    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:

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

    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:

    rocker: fix memory leak in rocker_world_port_post_fini() (CVE-2026-23164)

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

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

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

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

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

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

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

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

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

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 Debian 11 host has packages installed that are affected by multiple vulnerabilities as referenced in the dla-4498 advisory.

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

    Package        : linux     Version        : 5.10.251-1     CVE ID         : CVE-2022-50516 CVE-2025-38201 CVE-2025-71222 CVE-2025-71224                      CVE-2025-71232 CVE-2025-71235 CVE-2025-71236 CVE-2025-71237                      CVE-2025-71238 CVE-2026-23112 CVE-2026-23176 CVE-2026-23190                      CVE-2026-23193 CVE-2026-23198 CVE-2026-23209 CVE-2026-23216                      CVE-2026-23222 CVE-2026-23229 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     5.10.251-1.  This version also fixes a regression in the previous     update.  It additionally includes many more bug fixes from stable     updates 5.10.250 and 5.10.251.

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

    - -------------------------------------------------------------------------     Debian Security Advisory DSA-6162-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-2025-71238 CVE-2026-23100 CVE-2026-23221 CVE-2026-23233                      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 stable distribution (trixie), these problems have been fixed in     version 6.12.74-2.

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

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

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

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

ID	Name	Product	Family	Severity
303103	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.10-2026-114 (ALASKERNEL-5.10-2026-114)	Nessus	Amazon Linux Local Security Checks	high
302189	Debian dla-4498 : ata-modules-5.10.0-38-armmp-di - security update	Nessus	Debian Local Security Checks	critical
302188	Debian dla-4499 : linux-config-6.1 - security update	Nessus	Debian Local Security Checks	critical
302010	Debian dsa-6162 : ata-modules-6.12.74+deb13+1-armmp-di - security update	Nessus	Debian Local Security Checks	high
302008	Debian dsa-6163 : affs-modules-6.1.0-43-4kc-malta-di - security update	Nessus	Debian Local Security Checks	critical
301099	Linux Distros Unpatched Vulnerability : CVE-2026-23238	Nessus	Misc.	medium

Detections

Analytics

CVE-2026-23238

medium

Tenable Plugins

Coming Soon

high

critical

critical

high

critical

medium