In the Linux kernel, the following vulnerability has been resolved: l2tp: Avoid possible recursive deadlock in l2tp_tunnel_register() When a file descriptor of pppol2tp socket is passed as file descriptor of UDP socket, a recursive deadlock occurs in l2tp_tunnel_register(). This situation is reproduced by the following program: int main(void) { int sock; struct sockaddr_pppol2tp addr; sock = socket(AF_PPPOX, SOCK_DGRAM, PX_PROTO_OL2TP); if (sock < 0) { perror("socket"); return 1; } addr.sa_family = AF_PPPOX; addr.sa_protocol = PX_PROTO_OL2TP; addr.pppol2tp.pid = 0; addr.pppol2tp.fd = sock; addr.pppol2tp.addr.sin_family = PF_INET; addr.pppol2tp.addr.sin_port = htons(0); addr.pppol2tp.addr.sin_addr.s_addr = inet_addr("192.168.0.1"); addr.pppol2tp.s_tunnel = 1; addr.pppol2tp.s_session = 0; addr.pppol2tp.d_tunnel = 0; addr.pppol2tp.d_session = 0; if (connect(sock, (const struct sockaddr *)&addr, sizeof(addr)) < 0) { perror("connect"); return 1; } return 0; } This program causes the following lockdep warning: ============================================ WARNING: possible recursive locking detected 6.2.0-rc5-00205-gc96618275234 #56 Not tainted -------------------------------------------- repro/8607 is trying to acquire lock: ffff8880213c8130 (sk_lock-AF_PPPOX){+.+.}-{0:0}, at: l2tp_tunnel_register+0x2b7/0x11c0 but task is already holding lock: ffff8880213c8130 (sk_lock-AF_PPPOX){+.+.}-{0:0}, at: pppol2tp_connect+0xa82/0x1a30 other info that might help us debug this: Possible unsafe locking scenario: CPU0 ---- lock(sk_lock-AF_PPPOX); lock(sk_lock-AF_PPPOX); *** DEADLOCK *** May be due to missing lock nesting notation 1 lock held by repro/8607: #0: ffff8880213c8130 (sk_lock-AF_PPPOX){+.+.}-{0:0}, at: pppol2tp_connect+0xa82/0x1a30 stack backtrace: CPU: 0 PID: 8607 Comm: repro Not tainted 6.2.0-rc5-00205-gc96618275234 #56 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.1-2.fc37 04/01/2014 Call Trace: <TASK> dump_stack_lvl+0x100/0x178 __lock_acquire.cold+0x119/0x3b9 ? lockdep_hardirqs_on_prepare+0x410/0x410 lock_acquire+0x1e0/0x610 ? l2tp_tunnel_register+0x2b7/0x11c0 ? lock_downgrade+0x710/0x710 ? __fget_files+0x283/0x3e0 lock_sock_nested+0x3a/0xf0 ? l2tp_tunnel_register+0x2b7/0x11c0 l2tp_tunnel_register+0x2b7/0x11c0 ? sprintf+0xc4/0x100 ? l2tp_tunnel_del_work+0x6b0/0x6b0 ? debug_object_deactivate+0x320/0x320 ? lockdep_init_map_type+0x16d/0x7a0 ? lockdep_init_map_type+0x16d/0x7a0 ? l2tp_tunnel_create+0x2bf/0x4b0 ? l2tp_tunnel_create+0x3c6/0x4b0 pppol2tp_connect+0x14e1/0x1a30 ? pppol2tp_put_sk+0xd0/0xd0 ? aa_sk_perm+0x2b7/0xa80 ? aa_af_perm+0x260/0x260 ? bpf_lsm_socket_connect+0x9/0x10 ? pppol2tp_put_sk+0xd0/0xd0 __sys_connect_file+0x14f/0x190 __sys_connect+0x133/0x160 ? __sys_connect_file+0x190/0x190 ? lockdep_hardirqs_on+0x7d/0x100 ? ktime_get_coarse_real_ts64+0x1b7/0x200 ? ktime_get_coarse_real_ts64+0x147/0x200 ? __audit_syscall_entry+0x396/0x500 __x64_sys_connect+0x72/0xb0 do_syscall_64+0x38/0xb0 entry_SYSCALL_64_after_hwframe+0x63/0xcd This patch fixes the issue by getting/creating the tunnel before locking the pppol2tp socket.

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2026-013666 advisory.

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

    l2tp: Avoid possible recursive deadlock in l2tp_tunnel_register()

    When a file descriptor of pppol2tp socket is passed as file descriptor     of UDP socket, a recursive deadlock occurs in l2tp_tunnel_register().
    This situation is reproduced by the following program:

    int main(void)     {             int sock;
            struct sockaddr_pppol2tp addr;

            sock = socket(AF_PPPOX, SOCK_DGRAM, PX_PROTO_OL2TP);
            if (sock < 0) {                     perror(socket);
                    return 1;
            }

            addr.sa_family = AF_PPPOX;
            addr.sa_protocol = PX_PROTO_OL2TP;
            addr.pppol2tp.pid = 0;
            addr.pppol2tp.fd = sock;
            addr.pppol2tp.addr.sin_family = PF_INET;
            addr.pppol2tp.addr.sin_port = htons(0);
            addr.pppol2tp.addr.sin_addr.s_addr = inet_addr(192.168.0.1);
            addr.pppol2tp.s_tunnel = 1;
            addr.pppol2tp.s_session = 0;
            addr.pppol2tp.d_tunnel = 0;
            addr.pppol2tp.d_session = 0;

            if (connect(sock, (const struct sockaddr *)&addr, sizeof(addr)) < 0) {                     perror(connect);
                    return 1;
            }

            return 0;
    }

    This program causes the following lockdep warning:

     ============================================      WARNING: possible recursive locking detected      6.2.0-rc5-00205-gc96618275234 #56 Not tainted
     --------------------------------------------      repro/8607 is trying to acquire lock:
     ffff8880213c8130 (sk_lock-AF_PPPOX){+.+.}-{0:0}, at: l2tp_tunnel_register+0x2b7/0x11c0

     but task is already holding lock:
     ffff8880213c8130 (sk_lock-AF_PPPOX){+.+.}-{0:0}, at: pppol2tp_connect+0xa82/0x1a30

     other info that might help us debug this:
      Possible unsafe locking scenario:

            CPU0
            ----        lock(sk_lock-AF_PPPOX);
       lock(sk_lock-AF_PPPOX);

      *** DEADLOCK ***

      May be due to missing lock nesting notation

     1 lock held by repro/8607:
      #0: ffff8880213c8130 (sk_lock-AF_PPPOX){+.+.}-{0:0}, at: pppol2tp_connect+0xa82/0x1a30

     stack backtrace:
     CPU: 0 PID: 8607 Comm: repro Not tainted 6.2.0-rc5-00205-gc96618275234 #56      Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.1-2.fc37 04/01/2014      Call Trace:
      <TASK>       dump_stack_lvl+0x100/0x178
      __lock_acquire.cold+0x119/0x3b9       ? lockdep_hardirqs_on_prepare+0x410/0x410       lock_acquire+0x1e0/0x610       ? l2tp_tunnel_register+0x2b7/0x11c0       ? lock_downgrade+0x710/0x710       ? __fget_files+0x283/0x3e0       lock_sock_nested+0x3a/0xf0       ? l2tp_tunnel_register+0x2b7/0x11c0       l2tp_tunnel_register+0x2b7/0x11c0       ? sprintf+0xc4/0x100       ? l2tp_tunnel_del_work+0x6b0/0x6b0       ? debug_object_deactivate+0x320/0x320       ? lockdep_init_map_type+0x16d/0x7a0       ? lockdep_init_map_type+0x16d/0x7a0       ? l2tp_tunnel_create+0x2bf/0x4b0       ? l2tp_tunnel_create+0x3c6/0x4b0       pppol2tp_connect+0x14e1/0x1a30       ? pppol2tp_put_sk+0xd0/0xd0       ? aa_sk_perm+0x2b7/0xa80       ? aa_af_perm+0x260/0x260       ? bpf_lsm_socket_connect+0x9/0x10       ? pppol2tp_put_sk+0xd0/0xd0
      __sys_connect_file+0x14f/0x190
      __sys_connect+0x133/0x160       ? __sys_connect_file+0x190/0x190       ? lockdep_hardirqs_on+0x7d/0x100       ? ktime_get_coarse_real_ts64+0x1b7/0x200       ? ktime_get_coarse_real_ts64+0x147/0x200       ? __audit_syscall_entry+0x396/0x500
      __x64_sys_connect+0x72/0xb0       do_syscall_64+0x38/0xb0       entry_SYSCALL_64_after_hwframe+0x63/0xcd

    This patch fixes the issue by getting/creating the tunnel before     locking the pppol2tp socket.

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

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

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2026-011071 advisory.

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

    l2tp: Avoid possible recursive deadlock in l2tp_tunnel_register()

    When a file descriptor of pppol2tp socket is passed as file descriptor     of UDP socket, a recursive deadlock occurs in l2tp_tunnel_register().
    This situation is reproduced by the following program:

    int main(void)     {             int sock;
            struct sockaddr_pppol2tp addr;

            sock = socket(AF_PPPOX, SOCK_DGRAM, PX_PROTO_OL2TP);
            if (sock < 0) {                     perror(socket);
                    return 1;
            }

            addr.sa_family = AF_PPPOX;
            addr.sa_protocol = PX_PROTO_OL2TP;
            addr.pppol2tp.pid = 0;
            addr.pppol2tp.fd = sock;
            addr.pppol2tp.addr.sin_family = PF_INET;
            addr.pppol2tp.addr.sin_port = htons(0);
            addr.pppol2tp.addr.sin_addr.s_addr = inet_addr(192.168.0.1);
            addr.pppol2tp.s_tunnel = 1;
            addr.pppol2tp.s_session = 0;
            addr.pppol2tp.d_tunnel = 0;
            addr.pppol2tp.d_session = 0;

            if (connect(sock, (const struct sockaddr *)&addr, sizeof(addr)) < 0) {                     perror(connect);
                    return 1;
            }

            return 0;
    }

    This program causes the following lockdep warning:

     ============================================      WARNING: possible recursive locking detected      6.2.0-rc5-00205-gc96618275234 #56 Not tainted
     --------------------------------------------      repro/8607 is trying to acquire lock:
     ffff8880213c8130 (sk_lock-AF_PPPOX){+.+.}-{0:0}, at: l2tp_tunnel_register+0x2b7/0x11c0

     but task is already holding lock:
     ffff8880213c8130 (sk_lock-AF_PPPOX){+.+.}-{0:0}, at: pppol2tp_connect+0xa82/0x1a30

     other info that might help us debug this:
      Possible unsafe locking scenario:

            CPU0
            ----        lock(sk_lock-AF_PPPOX);
       lock(sk_lock-AF_PPPOX);

      *** DEADLOCK ***

      May be due to missing lock nesting notation

     1 lock held by repro/8607:
      #0: ffff8880213c8130 (sk_lock-AF_PPPOX){+.+.}-{0:0}, at: pppol2tp_connect+0xa82/0x1a30

     stack backtrace:
     CPU: 0 PID: 8607 Comm: repro Not tainted 6.2.0-rc5-00205-gc96618275234 #56      Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.1-2.fc37 04/01/2014      Call Trace:
      <TASK>       dump_stack_lvl+0x100/0x178
      __lock_acquire.cold+0x119/0x3b9       ? lockdep_hardirqs_on_prepare+0x410/0x410       lock_acquire+0x1e0/0x610       ? l2tp_tunnel_register+0x2b7/0x11c0       ? lock_downgrade+0x710/0x710       ? __fget_files+0x283/0x3e0       lock_sock_nested+0x3a/0xf0       ? l2tp_tunnel_register+0x2b7/0x11c0       l2tp_tunnel_register+0x2b7/0x11c0       ? sprintf+0xc4/0x100       ? l2tp_tunnel_del_work+0x6b0/0x6b0       ? debug_object_deactivate+0x320/0x320       ? lockdep_init_map_type+0x16d/0x7a0       ? lockdep_init_map_type+0x16d/0x7a0       ? l2tp_tunnel_create+0x2bf/0x4b0       ? l2tp_tunnel_create+0x3c6/0x4b0       pppol2tp_connect+0x14e1/0x1a30       ? pppol2tp_put_sk+0xd0/0xd0       ? aa_sk_perm+0x2b7/0xa80       ? aa_af_perm+0x260/0x260       ? bpf_lsm_socket_connect+0x9/0x10       ? pppol2tp_put_sk+0xd0/0xd0
      __sys_connect_file+0x14f/0x190
      __sys_connect+0x133/0x160       ? __sys_connect_file+0x190/0x190       ? lockdep_hardirqs_on+0x7d/0x100       ? ktime_get_coarse_real_ts64+0x1b7/0x200       ? ktime_get_coarse_real_ts64+0x147/0x200       ? __audit_syscall_entry+0x396/0x500
      __x64_sys_connect+0x72/0xb0       do_syscall_64+0x38/0xb0       entry_SYSCALL_64_after_hwframe+0x63/0xcd

    This patch fixes the issue by getting/creating the tunnel before     locking the pppol2tp socket.

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

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

The remote SUSE Linux SLES12 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2026:0316-1 advisory.

    The SUSE Linux Enterprise 12 SP5 kernel was updated to fix various security issues

    The following security issues were fixed:

    - CVE-2022-49604,CVE-2025-40074: ip: Fix data-races around sysctl_ip_fwd_use_pmtu (bsc#1238414     bsc#1252794).
    - CVE-2022-50527: drm/amdgpu: Fix size validation for non-exclusive domains (v4) (bsc#1251738).
    - CVE-2022-50625: serial: amba-pl011: avoid SBSA UART accessing DMACR register (bsc#1254559).
    - CVE-2022-50630: mm: hugetlb: fix UAF in hugetlb_handle_userfault (bsc#1254785).
    - CVE-2022-50656: nfc: pn533: Clear nfc_target before being used (bsc#1254745).
    - CVE-2022-50678: wifi: brcmfmac: fix invalid address access when enabling SCAN log level (bsc#1254902).
    - CVE-2022-50700: wifi: ath10k: Delay the unmapping of the buffer (bsc#1255576).
    - CVE-2023-53454: HID: multitouch: Correct devm device reference for hidinput input_dev name     (bsc#1250759).
    - CVE-2023-53718: ring-buffer: Do not swap cpu_buffer during resize process (bsc#1252564).
    - CVE-2023-53748: media: mediatek: vcodec: Fix potential array out-of-bounds in decoder queue_setup     (bsc#1254907).
    - CVE-2023-53765: dm cache: free background tracker's queued work in btracker_destroy (bsc#1254912).
    - CVE-2023-53781: smc: Fix use-after-free in tcp_write_timer_handler() (bsc#1254751).
    - CVE-2023-53788: ALSA: hda/ca0132: fixup buffer overrun at tuning_ctl_set() (bsc#1254917).
    - CVE-2023-53819: amdgpu: validate offset_in_bo of drm_amdgpu_gem_va (bsc#1254712).
    - CVE-2023-53850: iavf: use internal state to free traffic IRQs (bsc#1254677).
    - CVE-2023-54120: Bluetooth: Fix race condition in hidp_session_thread (bsc#1256133).
    - CVE-2023-54214: Bluetooth: L2CAP: Fix potential user-after-free (bsc#1255954).
    - CVE-2023-54236: net/net_failover: fix txq exceeding warning (bsc#1255922).
    - CVE-2023-54286: wifi: iwlwifi: dvm: Fix memcpy: detected field-spanning write backtrace (bsc#1255803).
    - CVE-2023-54300: wifi: ath9k: avoid referencing uninit memory in ath9k_wmi_ctrl_rx (bsc#1255790).
    - CVE-2025-38085: mm/hugetlb: fix huge_pmd_unshare() vs GUP-fast race (bsc#1245431 bsc#1245499).
    - CVE-2025-38336: ata: pata_via: Force PIO for ATAPI devices on VT6415/VT6330 (bsc#1246370).
    - CVE-2025-38728: smb3: fix for slab out of bounds on mount to ksmbd (bsc#1249256).
    - CVE-2025-40006: mm/hugetlb: fix folio is still mapped when deleted (bsc#1252342).
    - CVE-2025-40035: Input: uinput - zero-initialize uinput_ff_upload_compat to avoid info leak     (bsc#1252866).
    - CVE-2025-40053: net: dlink: handle copy_thresh allocation failure (bsc#1252808).
    - CVE-2025-40064: smc: Fix use-after-free in __pnet_find_base_ndev() (bsc#1252845).
    - CVE-2025-40075: tcp_metrics: use dst_dev_net_rcu() (bsc#1252795).
    - CVE-2025-40081: perf: arm_spe: Prevent overflow in PERF_IDX2OFF() (bsc#1252776).
    - CVE-2025-40110: drm/vmwgfx: Fix a null-ptr access in the cursor snooper (bsc#1253275).
    - CVE-2025-40123: bpf: Enforce expected_attach_type for tailcall compatibility (bsc#1253365).
    - CVE-2025-40135: ipv6: use RCU in ip6_xmit() (bsc#1253342).
    - CVE-2025-40139: smc: Use __sk_dst_get() and dst_dev_rcu() in in smc_clc_prfx_set() (bsc#1253409).
    - CVE-2025-40149: tls: Use __sk_dst_get() and dst_dev_rcu() in get_netdev_for_sock() (bsc#1253355).
    - CVE-2025-40153: mm: hugetlb: avoid soft lockup when mprotect to large memory area (bsc#1253408).
    - CVE-2025-40158: ipv6: use RCU in ip6_output() (bsc#1253402).
    - CVE-2025-40160: xen/events: Cleanup find_virq() return codes (bsc#1253400).
    - CVE-2025-40164: usbnet: Fix using smp_processor_id() in preemptible code warnings (bsc#1253407).
    - CVE-2025-40167: ext4: detect invalid INLINE_DATA + EXTENTS flag combination (bsc#1253458).
    - CVE-2025-40168: smc: Use __sk_dst_get() and dst_dev_rcu() in smc_clc_prfx_match() (bsc#1253427).
    - CVE-2025-40170: net: use dst_dev_rcu() in sk_setup_caps() (bsc#1253413).
    - CVE-2025-40178: pid: Add a judgment for ns null in pid_nr_ns (bsc#1253463).
    - CVE-2025-40198: ext4: avoid potential buffer over-read in parse_apply_sb_mount_options() (bsc#1253453).
    - CVE-2025-40200: Squashfs: reject negative file sizes in squashfs_read_inode() (bsc#1253448).
    - CVE-2025-40215: kABI: xfrm: delete x->tunnel as we delete x (bsc#1254959).
    - CVE-2025-40219: PCI/IOV: Add PCI rescan-remove locking when enabling/disabling SR-IOV (bsc#1254518).
    - CVE-2025-40233: ocfs2: clear extent cache after moving/defragmenting extents (bsc#1254813).
    - CVE-2025-40240: sctp: avoid NULL dereference when chunk data buffer is missing (bsc#1254869).
    - CVE-2025-40244: hfsplus: fix KMSAN uninit-value issue in __hfsplus_ext_cache_extent() (bsc#1255033).
    - CVE-2025-40248: vsock: Ignore signal/timeout on connect() if already established (bsc#1254864).
    - CVE-2025-40252: net: qlogic/qede: fix potential out-of-bounds read in qede_tpa_cont() and qede_tpa_end()     (bsc#1254849).
    - CVE-2025-40269: ALSA: usb-audio: Fix potential overflow of PCM transfer buffer (bsc#1255035).
    - CVE-2025-40275: ALSA: usb-audio: Fix NULL pointer dereference in snd_usb_mixer_controls_badd     (bsc#1254829).
    - CVE-2025-40278: net: sched: act_ife: initialize struct tc_ife to fix KMSAN kernel-infoleak     (bsc#1254825).
    - CVE-2025-40279: net: sched: act_connmark: initialize struct tc_ife to fix kernel leak (bsc#1254846).
    - CVE-2025-40283: Bluetooth: btusb: reorder cleanup in btusb_disconnect to avoid UAF (bsc#1254858).
    - CVE-2025-40304: fbdev: Add bounds checking in bit_putcs to fix vmalloc-out-of-bounds (bsc#1255034).
    - CVE-2025-40308: Bluetooth: bcsp: receive data only if registered (bsc#1255064).
    - CVE-2025-40321: wifi: brcmfmac: fix crash while sending Action Frames in standalone AP Mode     (bsc#1254795).
    - CVE-2025-40322: fbdev: bitblit: bound-check glyph index in bit_putcs* (bsc#1255092).
    - CVE-2025-40331: sctp: Prevent TOCTOU out-of-bounds write (bsc#1254615).
    - CVE-2025-40337: net: stmmac: Correctly handle Rx checksum offload errors (bsc#1255081).
    - CVE-2025-40349: hfs: validate record offset in hfsplus_bmap_alloc (bsc#1255280).
    - CVE-2025-40351: hfsplus: fix KMSAN uninit-value issue in hfsplus_delete_cat() (bsc#1255281).
    - CVE-2025-68206: netfilter: nft_ct: add seqadj extension for natted connections (bsc#1255142).
    - CVE-2025-68340: team: Move team device type change at the end of team_port_add (bsc#1255507).

    The following non security issues were fixed:

    - HID: multitouch: Add NULL check in mt_input_configured (bsc#1250759).
    - Squashfs: add additional inode sanity checking (bsc#1253448).
    - drm/amdgpu: Fix potential NULL dereference (bsc#1251238).

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

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

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

  - l2tp: Avoid possible recursive deadlock in l2tp_tunnel_register() When a file descriptor of pppol2tp     socket is passed as file descriptor of UDP socket, a recursive deadlock occurs in l2tp_tunnel_register().
    This situation is reproduced by the following program: int main(void) { int sock; struct sockaddr_pppol2tp     addr; sock = socket(AF_PPPOX, SOCK_DGRAM, PX_PROTO_OL2TP); if (sock < 0) { perror(socket); return 1; }     addr.sa_family = AF_PPPOX; addr.sa_protocol = PX_PROTO_OL2TP; addr.pppol2tp.pid = 0; addr.pppol2tp.fd =     sock; addr.pppol2tp.addr.sin_family = PF_INET; addr.pppol2tp.addr.sin_port = htons(0);
    addr.pppol2tp.addr.sin_addr.s_addr = inet_addr(192.168.0.1); addr.pppol2tp.s_tunnel = 1;
    addr.pppol2tp.s_session = 0; addr.pppol2tp.d_tunnel = 0; addr.pppol2tp.d_session = 0; if (connect(sock,     (const struct sockaddr *)&addr, sizeof(addr)) < 0) { perror(connect); return 1; } return 0; } This     program causes the following lockdep warning: ============================================ WARNING:
    possible recursive locking detected 6.2.0-rc5-00205-gc96618275234 #56 Not tainted
    -------------------------------------------- repro/8607 is trying to acquire lock: ffff8880213c8130     (sk_lock-AF_PPPOX){+.+.}-{0:0}, at: l2tp_tunnel_register+0x2b7/0x11c0 but task is already holding lock:
    ffff8880213c8130 (sk_lock-AF_PPPOX){+.+.}-{0:0}, at: pppol2tp_connect+0xa82/0x1a30 other info that might     help us debug this: Possible unsafe locking scenario: CPU0 ---- lock(sk_lock-AF_PPPOX); lock(sk_lock-     AF_PPPOX); *** DEADLOCK *** May be due to missing lock nesting notation 1 lock held by repro/8607: #0:
    ffff8880213c8130 (sk_lock-AF_PPPOX){+.+.}-{0:0}, at: pppol2tp_connect+0xa82/0x1a30 stack backtrace: CPU: 0     PID: 8607 Comm: repro Not tainted 6.2.0-rc5-00205-gc96618275234 #56 Hardware name: QEMU Standard PC     (i440FX + PIIX, 1996), BIOS 1.16.1-2.fc37 04/01/2014 Call Trace: <TASK> dump_stack_lvl+0x100/0x178
    __lock_acquire.cold+0x119/0x3b9 ? lockdep_hardirqs_on_prepare+0x410/0x410 lock_acquire+0x1e0/0x610 ?     l2tp_tunnel_register+0x2b7/0x11c0 ? lock_downgrade+0x710/0x710 ? __fget_files+0x283/0x3e0     lock_sock_nested+0x3a/0xf0 ? l2tp_tunnel_register+0x2b7/0x11c0 l2tp_tunnel_register+0x2b7/0x11c0 ?     sprintf+0xc4/0x100 ? l2tp_tunnel_del_work+0x6b0/0x6b0 ? debug_object_deactivate+0x320/0x320 ?     lockdep_init_map_type+0x16d/0x7a0 ? lockdep_init_map_type+0x16d/0x7a0 ? l2tp_tunnel_create+0x2bf/0x4b0 ?     l2tp_tunnel_create+0x3c6/0x4b0 pppol2tp_connect+0x14e1/0x1a30 ? pppol2tp_put_sk+0xd0/0xd0 ?     aa_sk_perm+0x2b7/0xa80 ? aa_af_perm+0x260/0x260 ? bpf_lsm_socket_connect+0x9/0x10 ?     pppol2tp_put_sk+0xd0/0xd0 __sys_connect_file+0x14f/0x190 __sys_connect+0x133/0x160 ?
    __sys_connect_file+0x190/0x190 ? lockdep_hardirqs_on+0x7d/0x100 ? ktime_get_coarse_real_ts64+0x1b7/0x200 ?     ktime_get_coarse_real_ts64+0x147/0x200 ? __audit_syscall_entry+0x396/0x500 __x64_sys_connect+0x72/0xb0     do_syscall_64+0x38/0xb0 entry_SYSCALL_64_after_hwframe+0x63/0xcd This patch fixes the issue by     getting/creating the tunnel before locking the pppol2tp socket. (CVE-2023-53809)

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

The version of kernel installed on the remote host is prior to 5.10.173-154.642. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.10-2023-028 advisory.

    A regression exists in the Linux Kernel within KVM: nVMX that allowed for speculative execution attacks.
    L2 can carry out Spectre v2 attacks on L1 due to L1 thinking it doesn't need retpolines or IBPB after     running L2 due to KVM (L0) advertising eIBRS support to L1. An attacker at L2 with code execution can     execute code on an indirect branch on the host machine. We recommend upgrading to Kernel 6.2 or past     commit 2e7eab81425a (CVE-2022-2196)

    It has been discovered that on some AMD CPUs, the RAS (Return Address Stack, also called RAP - Return     Address Predictor - in some AMD documentation, and RSB - Return Stack Buffer - in Intel terminology) is     dynamically partitioned between non-idle threads.  This allows an attacker to control speculative     execution on the adjacent thread. (CVE-2022-27672)

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

    netfilter: nft_tproxy: restrict to prerouting hook (CVE-2022-50001)

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

    drm: Fix potential null-ptr-deref due to drmm_mode_config_init() (CVE-2022-50556)

    Detected a few exploitable gadgets that could leak secret memory through a side-channel such as MDS as     well as insufficient hardening of the usercopy functions against spectre-v1. (CVE-2023-0458)

    Due to a type confusion during initializations, the tun and tap sockets in the Linux Kernel have their     socket UID hardcoded to 0, i.e. root. While it will be often correct, as TUN/TAP devices require     CAP_NET_ADMIN, it may not always be the case. The socket UID may be used for network filtering and     routing, thus TUN/TAP sockets may be incorrectly managed, potentially bypassing network filters based on     UID. (CVE-2023-1076)

    kernel: Type confusion in pick_next_rt_entity(), which can result in memory corruption. (CVE-2023-1077)

    The upstream bug report describes this issue as follows:

    A flaw found in the Linux Kernel in RDS (Reliable Datagram Sockets) protocol. The     rds_rm_zerocopy_callback() uses list_entry() on the head of a list causing a type confusion. Local user     can trigger this with rds_message_put(). Type confusion leads to `struct rds_msg_zcopy_info *info`     actually points to something else that is potentially controlled by local user. It is known how to trigger     this, which causes an OOB access, and a lock corruption. (CVE-2023-1078)

    Use After Free vulnerability in Linux kernel traffic control index filter (tcindex) allows Privilege     Escalation. The imperfect hash area can be updated while packets are traversing, which will cause a use-     after-free when 'tcf_exts_exec()' is called with the destroyed tcf_ext. A local attacker user can use this     vulnerability to elevate its privileges to root.This issue affects Linux Kernel: from 4.14 before git     commit ee059170b1f7e94e55fa6cadee544e176a6e59c2. (CVE-2023-1281)

    A use-after-free vulnerability in the Linux Kernel traffic control index filter (tcindex) can be exploited     to achieve local privilege escalation. The tcindex_delete function which does not properly deactivate     filters in case of a perfect hashes while deleting the underlying structure which can later lead to double     freeing the structure. A local attacker user can use this vulnerability to elevate its privileges to     root.We recommend upgrading past commit 8c710f75256bb3cf05ac7b1672c82b92c43f3d28. (CVE-2023-1829)

    A use-after-free vulnerability in the Linux Kernel io_uring system can be exploited to achieve local     privilege escalation.

    The io_file_get_fixed function lacks the presence of ctx->uring_lock which can lead to a Use-After-Free     vulnerability due a race condition with fixed files getting unregistered.

    We recommend upgrading past commit da24142b1ef9fd5d36b76e36bab328a5b27523e8. (CVE-2023-1872)

    When plain IBRS is enabled (not enhanced IBRS), the logic in spectre_v2_user_select_mitigation()     determines that STIBP is not needed. The IBRS bit implicitly protects against cross-thread branch     targetinjection. However, with legacy IBRS, the IBRS bit is cleared on returning to userspace for     performance reasons which leaves userspace threads vulnerable to cross-thread branch target injection     against which STIBP protects. (CVE-2023-1998)

    A use-after-free flaw was found in iscsi_sw_tcp_session_create in drivers/scsi/iscsi_tcp.c in the SCSI     sub-component in the Linux Kernel. This issue could allow an attacker to leak kernel internal information.
    (CVE-2023-2162)

    In the Linux kernel before 6.0.3, drivers/gpu/drm/virtio/virtgpu_object.c misinterprets the     drm_gem_shmem_get_sg_table return value (expects it to be NULL in the error case, whereas it is actually     an error pointer). (CVE-2023-22998)

    In the Linux kernel before 6.1.13, there is a double free in net/mpls/af_mpls.c upon an allocation failure     (for registering the sysctl table under a new location) during the renaming of a device. (CVE-2023-26545)

    A use-after-free flaw was found in hfsplus_put_super in fs/hfsplus/super.c in the Linux Kernel. This flaw     could allow a local user to cause a denial of service. (CVE-2023-2985)

    A flaw was found in the Framebuffer Console (fbcon) in the Linux Kernel. When providing a font->width and     font->height greater than 32 to the fbcon_set_font, since there are no checks in place, a shift-out-of-     bounds occurs, leading to undefined behavior and possible denial of service. (CVE-2023-3161)

    A use-after-free flaw was found in vcs_read in drivers/tty/vt/vc_screen.c in vc_screen in the Linux     Kernel. In this flaw an attacker with local user access may lead to a system crash or a leak of internal     kernel information. (CVE-2023-3567)

    An issue was discovered in drivers/usb/storage/ene_ub6250.c for the ENE UB6250 reader driver in the Linux     kernel before 6.2.5. An object could potentially extend beyond the end of an allocation. (CVE-2023-45862)

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

    aio: fix mremap after fork null-deref (CVE-2023-52646)

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

    net: openvswitch: fix possible memory leak in ovs_meter_cmd_set() (CVE-2023-52702)

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

    net/usb: kalmia: Don't pass act_len in usb_bulk_msg error path (CVE-2023-52703)

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

    nilfs2: fix underflow in second superblock position calculations (CVE-2023-52705)

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

    mmc: mmc_spi: fix error handling in mmc_spi_probe() (CVE-2023-52708)

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

    mmc: sdio: fix possible resource leaks in some error paths (CVE-2023-52730)

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

    Fix page corruption caused by racy check in __free_pages (CVE-2023-52739)

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

    cifs: Fix use-after-free in rdata->read_into_pages() (CVE-2023-52741)

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

    net: USB: Fix wrong-direction WARNING in plusb.c (CVE-2023-52742)

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

    IB/IPoIB: Fix legacy IPoIB due to wrong number of queues (CVE-2023-52745)

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

    xfrm/compat: prevent potential spectre v1 gadget in xfrm_xlate32_attr() (CVE-2023-52746)

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

    drm/i915: Fix potential bit_17 double-free (CVE-2023-52930)

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

    mm/swapfile: add cond_resched() in get_swap_pages() (CVE-2023-52932)

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

    Squashfs: fix handling and sanity checking of xattr_ids count (CVE-2023-52933)

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

    vc_screen: move load of struct vc_data pointer in vcs_read() to avoid UAF (CVE-2023-52973)

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

    scsi: iscsi_tcp: Fix UAF during login when accessing the shost ipaddress (CVE-2023-52974)

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

    efi: fix potential NULL deref in efi_mem_reserve_persistent (CVE-2023-52976)

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

    net: openvswitch: fix flow memory leak in ovs_flow_cmd_new (CVE-2023-52977)

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

    squashfs: harden sanity check in squashfs_read_xattr_id_table (CVE-2023-52979)

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

    bpf, sockmap: Check for any of tcp_bpf_prots when cloning a listener (CVE-2023-52986)

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

    vfio/type1: prevent underflow of locked_vm via exec() (CVE-2023-53171)

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

    ext4: Fix function prototype mismatch for ext4_feat_ktype (CVE-2023-53224)

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

    watchdog: Fix kmemleak in watchdog_cdev_register (CVE-2023-53234)

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

    thermal/drivers/hisi: Drop second sensor hi3660 (CVE-2023-53242)

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

    ubi: ensure that VID header offset + VID header size <= alloc, size (CVE-2023-53265)

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

    ubi: Fix unreferenced object reported by kmemleak in ubi_resize_volume() (CVE-2023-53271)

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

    udf: Do not update file length for failed writes to inline files (CVE-2023-53295)

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

    rbd: avoid use-after-free in do_rbd_add() when rbd_dev_create() fails (CVE-2023-53307)

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

    crypto: seqiv - Handle EBUSY correctly (CVE-2023-53373)

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

    PM: EM: fix memory leak with using debugfs_lookup() (CVE-2023-53411)

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

    objtool: Fix memory leak in create_static_call_sections() (CVE-2023-53423)

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

    cifs: Fix warning and UAF when destroy the MR list (CVE-2023-53427)

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

    scsi: ses: Don't attach if enclosure has no components (CVE-2023-53431)

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

    drm/radeon: free iio for atombios when driver shutdown (CVE-2023-53453)

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

    ipv6: Add lwtunnel encap size of all siblings in nexthop calculation (CVE-2023-53477)

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

    ubi: ubi_wl_put_peb: Fix infinite loop when wear-leveling work failed (CVE-2023-53481)

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

    crypto: xts - Handle EBUSY correctly (CVE-2023-53494)

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

    udf: Do not bother merging very long extents (CVE-2023-53506)

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

    scsi: mpt3sas: Fix a memory leak (CVE-2023-53512)

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

    scsi: ses: Fix slab-out-of-bounds in ses_intf_remove() (CVE-2023-53521)

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

    sctp: add a refcnt in sctp_stream_priorities to avoid a nested loop (CVE-2023-53590)

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

    irqchip: Fix refcount leak in platform_irqchip_probe (CVE-2023-53610)

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

    scsi: ses: Fix possible desc_ptr out-of-bounds accesses (CVE-2023-53675)

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

    udf: Detect system inodes linked into directory hierarchy (CVE-2023-53695)

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

    ring-buffer: Handle race between rb_move_tail and rb_check_pages (CVE-2023-53709)

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

    blk-iocost: fix divide by 0 error in calc_lcoefs() (CVE-2023-53783)

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

    ubi: Fix use-after-free when volume resizing failed (CVE-2023-53800)

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

    scsi: ses: Fix slab-out-of-bounds in ses_enclosure_data_process() (CVE-2023-53803)

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

    l2tp: Avoid possible recursive deadlock in l2tp_tunnel_register() (CVE-2023-53809)

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

    loop: loop_set_status_from_info() check before assignment (CVE-2023-53820)

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

    ubi: Fix UAF wear-leveling entry in eraseblk_count_seq_show() (CVE-2023-53826)

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

    hfs: fix missing hfs_bnode_get() in __hfs_bnode_create (CVE-2023-53862)

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

    KVM: Destroy target device if coalesced MMIO unregistration fails (CVE-2023-54024)

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

    crypto: essiv - Handle EBUSY correctly (CVE-2023-54046)

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

    ubi: Fix possible null-ptr-deref in ubi_free_volume() (CVE-2023-54087)

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

    scsi: qla2xxx: Fix DMA-API call trace on NVMe LS requests (CVE-2023-54108)

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

    leds: led-core: Fix refcount leak in of_led_get() (CVE-2023-54190)

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

    tty: fix out-of-bounds access in tty_driver_lookup_tty() (CVE-2023-54198)

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

    netfilter: ebtables: fix table blob use-after-free (CVE-2023-54243)

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

    cifs: Fix lost destroy smbd connection when MR allocate failed (CVE-2023-54260)

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

    ext4: refuse to create ea block when umounted (CVE-2023-54305)

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

    net: tls: avoid hanging tasks on the tx_lock (CVE-2023-54306)

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

    dm flakey: don't corrupt the zero page (CVE-2023-54317)

    kernel: refcount leak in ctnetlink_create_conntrack() (CVE-2023-7192)

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

    scsi: ses: Fix possible addl_desc_ptr out-of-bounds accesses (CVE-2023-7324)

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	Severity
309569	Unity Linux 20.1070a Security Update: kernel (UTSA-2026-013666)	Nessus	Unity Linux Local Security Checks	medium
308916	Unity Linux 20.1060e / 20.1070e Security Update: kernel (UTSA-2026-011071)	Nessus	Unity Linux Local Security Checks	medium
297090	SUSE SLES12 Security Update : kernel (SUSE-SU-2026:0316-1)	Nessus	SuSE Local Security Checks	high
278100	Linux Distros Unpatched Vulnerability : CVE-2023-53809	Nessus	Misc.	medium
173228	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.10-2023-028 (ALASKERNEL-5.10-2023-028)	Nessus	Amazon Linux Local Security Checks	high

Detections

Analytics

CVE-2023-53809

medium

Tenable Plugins

medium

medium

high

medium

high