AlmaLinux 9.2 主机上存在安装的程序包，该程序包受到 TuxCare ALMALINUX9.2：CLSA-2026：2026：1780516677公告中提及的多个漏洞的影响。

  - 已修复 Linux 内核中的下列漏洞：can: isotp: fix potential CAN frame reception race in isotp_rcv() When receiving a CAN frame the current code logic does not consider concurrently receiving processes which do not show up in real world usage. Ziyang Xuan writes: The following syz problem is one of the scenarios. so->rx.len is changed by isotp_rcv_ff() during isotp_rcv_cf(), so->rx.len equals 0 before alloc_skb() and equals 4096 after alloc_skb(). That will trigger skb_over_panic() in skb_put(). ======================================================= CPU: 1 PID:
    19 Comm: ksoftirqd/1 Not tainted 5.16.0-rc8-syzkaller #0 RIP: 0010:skb_panic+0x16c/0x16e net/core/skbuff.c:113 Call Trace: <TASK> skb_over_panic net/core/skbuff.c:118 [inline] skb_put.cold+0x24/0x24 net/core/skbuff.c:1990 isotp_rcv_cf net/can/isotp.c:570 [inline] isotp_rcv+0xa38/0x1e30 net/can/isotp.c:668 deliver net/can/af_can.c:574 [inline] can_rcv_filter+0x445/0x8d0 net/can/af_can.c:635 can_receive+0x31d/0x580 net/can/af_can.c:665 can_rcv+0x120/0x1c0 net/can/af_can.c:696 __netif_receive_skb_one_core+0x114/0x180 net/core/dev.c:5465
    __netif_receive_skb+0x24/0x1b0 net/core/dev.c:5579 Therefore we make sure the state changes and data structures stay consistent at CAN frame reception time by adding a spin_lock in isotp_rcv(). This fixes the issue reported by syzkaller but does not affect real world operation. (CVE-2022-48830)

  - 已修复 Linux 内核中的下列漏洞：wifi: mac80211: sdata can be NULL during AMPDU start ieee80211_tx_ba_session_handle_start() may get NULL for sdata when a deauthentication is ongoing. Here a trace triggering the race with the hostapd test multi_ap_fronthaul_on_ap: (gdb) list
    *drv_ampdu_action+0x46 0x8b16 is in drv_ampdu_action (net/mac80211/driver-ops.c:396). 391 int ret =
    -EOPNOTSUPP; 392 393 might_sleep(); 394 395 sdata = get_bss_sdata(sdata); 396 if (!check_sdata_in_driver(sdata)) 397 return -EIO; 398 399 trace_drv_ampdu_action(local, sdata, params); 400 wlan0: moving STA 02:00:00:00:03:00 to state 3 wlan0: associated wlan0: deauthenticating from 02:00:00:00:03:00 by local choice (Reason: 3=DEAUTH_LEAVING) wlan3.sta1: Open BA session requested for 02:00:00:00:00:00 tid 0 wlan3.sta1: dropped frame to 02:00:00:00:00:00 (unauthorized port) wlan0: moving STA 02:00:00:00:03:00 to state 2 wlan0: moving STA 02:00:00:00:03:00 to state 1 wlan0: Removed STA 02:00:00:00:03:00 wlan0: Destroyed STA 02:00:00:00:03:00 BUG: unable to handle page fault for address:
    fffffffffffffb48 PGD 11814067 P4D 11814067 PUD 11816067 PMD 0 Oops: 0000 [#1] PREEMPT SMP PTI CPU: 2 PID:
    133397 Comm: kworker/u16:1 Tainted: G W 6.1.0-rc8-wt+ #59 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.0-20220807_005459-localhost 04/01/2014 Workqueue: phy3 ieee80211_ba_session_work [mac80211] RIP: 0010:drv_ampdu_action+0x46/0x280 [mac80211] Code: 53 48 89 f3 be 89 01 00 00 e8 d6 43 bf ef e8 21 46 81 f0 83 bb a0 1b 00 00 04 75 0e 48 8b 9b 28 0d 00 00 48 81 eb 10 0e 00 00 <8b> 93 58 09 00 00 f6 c2 20 0f 84 3b 01 00 00 8b 05 dd 1c 0f 00 85 RSP: 0018:ffffc900025ebd20 EFLAGS: 00010287 RAX:
    0000000000000000 RBX: fffffffffffff1f0 RCX: ffff888102228240 RDX: 0000000080000000 RSI: ffffffff918c5de0 RDI: ffff888102228b40 RBP: ffffc900025ebd40 R08: 0000000000000001 R09: 0000000000000001 R10:
    0000000000000001 R11: 0000000000000000 R12: ffff888118c18ec0 R13: 0000000000000000 R14: ffffc900025ebd60 R15: ffff888018b7efb8 FS: 0000000000000000(0000) GS:ffff88817a600000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: fffffffffffffb48 CR3: 0000000105228006 CR4: 0000000000170ee0 Call Trace: <TASK> ieee80211_tx_ba_session_handle_start+0xd0/0x190 [mac80211] ieee80211_ba_session_work+0xff/0x2e0 [mac80211] process_one_work+0x29f/0x620 worker_thread+0x4d/0x3d0 ? process_one_work+0x620/0x620 kthread+0xfb/0x120 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork+0x22/0x30 </TASK> (CVE-2022-48875)

  - 已修复 Linux 内核中的下列漏洞：udf: Fix preallocation discarding at indirect extent boundary When preallocation extent is the first one in the extent block, the code would corrupt extent tree header instead. Fix the problem and use udf_delete_aext() for deleting extent to avoid some code duplication. (CVE-2022-48946)

  - 已修复 Linux 内核中的下列漏洞：Bluetooth: Fix crash when replugging CSR fake controllers It seems fake CSR 5.0 clones can cause the suspend notifier to be registered twice causing the following kernel panic: [ 71.986122] Call Trace: [ 71.986124] <TASK> [ 71.986125] blocking_notifier_chain_register+0x33/0x60 [ 71.986130] hci_register_dev+0x316/0x3d0 [bluetooth 99b5497ea3d09708fa1366c1dc03288bf3cca8da] [ 71.986154] btusb_probe+0x979/0xd85 [btusb e1e0605a4f4c01984a4b9c8ac58c3666ae287477] [ 71.986159] ? __pm_runtime_set_status+0x1a9/0x300 [ 71.986162] ? ktime_get_mono_fast_ns+0x3e/0x90 [ 71.986167] usb_probe_interface+0xe3/0x2b0 [ 71.986171] really_probe+0xdb/0x380 [ 71.986174] ? pm_runtime_barrier+0x54/0x90 [ 71.986177]
    __driver_probe_device+0x78/0x170 [ 71.986180] driver_probe_device+0x1f/0x90 [ 71.986183]
    __device_attach_driver+0x89/0x110 [ 71.986186] ? driver_allows_async_probing+0x70/0x70 [ 71.986189] bus_for_each_drv+0x8c/0xe0 [ 71.986192] __device_attach+0xb2/0x1e0 [ 71.986195] bus_probe_device+0x92/0xb0 [ 71.986198] device_add+0x422/0x9a0 [ 71.986201] ? sysfs_merge_group+0xd4/0x110 [ 71.986205] usb_set_configuration+0x57a/0x820 [ 71.986208] usb_generic_driver_probe+0x4f/0x70 [ 71.986211] usb_probe_device+0x3a/0x110 [ 71.986213] really_probe+0xdb/0x380 [ 71.986216] ? pm_runtime_barrier+0x54/0x90 [ 71.986219] __driver_probe_device+0x78/0x170 [ 71.986221] driver_probe_device+0x1f/0x90 [ 71.986224] __device_attach_driver+0x89/0x110 [ 71.986227] ? driver_allows_async_probing+0x70/0x70 [ 71.986230] bus_for_each_drv+0x8c/0xe0 [ 71.986232]
    __device_attach+0xb2/0x1e0 [ 71.986235] bus_probe_device+0x92/0xb0 [ 71.986237] device_add+0x422/0x9a0 [71.986239] ? _dev_info+0x7d/0x98 [ 71.986242] ? blake2s_update+0x4c/0xc0 [ 71.986246] usb_new_device.cold+0x148/0x36d [ 71.986250] hub_event+0xa8a/0x1910 [ 71.986255] process_one_work+0x1c4/0x380 [ 71.986259] worker_thread+0x51/0x390 [ 71.986262] ? rescuer_thread+0x3b0/0x3b0 [ 71.986264] kthread+0xdb/0x110 [ 71.986266] ? kthread_complete_and_exit+0x20/0x20 [ 71.986268] ret_from_fork+0x1f/0x30 [ 71.986273] </TASK> [ 71.986274]
    ---[ end trace 0000000000000000 ]--- [ 71.986284] btusb: probe of 2-1.6:1.0 failed with error -17 (CVE-2022-48982)

  - 已修复 Linux 内核中的下列漏洞：can: m_can: pci: add missing m_can_class_free_dev() in probe/remove methods In m_can_pci_remove() and error handling path of m_can_pci_probe(), m_can_class_free_dev() should be called to free resource allocated by m_can_class_allocate_dev(), otherwise there will be memleak. (CVE-2022-49024)

请注意，Nessus 尚未测试这些问题，而是只依据应用程序自我报告的版本号进行判断。

Linux/Unix 主機上安裝了一個或多個受到弱點影響的套件，且供應商未提供可用的修補程式。

  - 已解決 Linux 核心中的下列弱點：device property: fix of node refcount leak in fwnode_graph_get_next_endpoint() The 'parent' returned by fwnode_graph_get_port_parent() with refcount incremented when 'prev' is not NULL, it needs be put when finish using it. Because the parent is const, introduce a new variable to store the returned fwnode, then put it before returning from fwnode_graph_get_next_endpoint(). (CVE-2022-49752)

請注意，Nessus 依賴供應商報告的套件存在。

AlmaLinux 9.2 主機已安裝的套件會受到 TuxCare ALMALINUX9.2：CLSA-2026：1780516677 公告中提及的多個弱點影響。

  - 已解決 Linux 核心中的下列弱點：can: isotp: fix potential CAN frame reception race in isotp_rcv() When receiving a CAN frame the current code logic does not consider concurrently receiving processes which do not show up in real world usage. Ziyang Xuan writes: The following syz problem is one of the scenarios. so->rx.len is changed by isotp_rcv_ff() during isotp_rcv_cf(), so->rx.len equals 0 before alloc_skb() and equals 4096 after alloc_skb(). That will trigger skb_over_panic() in skb_put(). ======================================================= CPU: 1 PID:
    19 Comm: ksoftirqd/1 Not tainted 5.16.0-rc8-syzkaller #0 RIP: 0010:skb_panic+0x16c/0x16e net/core/skbuff.c:113 Call Trace: <TASK> skb_over_panic net/core/skbuff.c:118 [inline] skb_put.cold+0x24/0x24 net/core/skbuff.c:1990 isotp_rcv_cf net/can/isotp.c:570 [inline] isotp_rcv+0xa38/0x1e30 net/can/isotp.c:668 deliver net/can/af_can.c:574 [inline] can_rcv_filter+0x445/0x8d0 net/can/af_can.c:635 can_receive+0x31d/0x580 net/can/af_can.c:665 can_rcv+0x120/0x1c0 net/can/af_can.c:696 __netif_receive_skb_one_core+0x114/0x180 net/core/dev.c:5465
    __netif_receive_skb+0x24/0x1b0 net/core/dev.c:5579 Therefore we make sure the state changes and data structures stay consistent at CAN frame reception time by adding a spin_lock in isotp_rcv(). This fixes the issue reported by syzkaller but does not affect real world operation. (CVE-2022-48830)

  - 已解決 Linux 核心中的下列弱點：wifi: mac80211: sdata can be NULL during AMPDU start ieee80211_tx_ba_session_handle_start() may get NULL for sdata when a deauthentication is ongoing. Here a trace triggering the race with the hostapd test multi_ap_fronthaul_on_ap: (gdb) list
    *drv_ampdu_action+0x46 0x8b16 is in drv_ampdu_action (net/mac80211/driver-ops.c:396). 391 int ret =
    -EOPNOTSUPP; 392 393 might_sleep(); 394 395 sdata = get_bss_sdata(sdata); 396 if (!check_sdata_in_driver(sdata)) 397 return -EIO; 398 399 trace_drv_ampdu_action(local, sdata, params); 400 wlan0: moving STA 02:00:00:00:03:00 to state 3 wlan0: associated wlan0: deauthenticating from 02:00:00:00:03:00 by local choice (Reason: 3=DEAUTH_LEAVING) wlan3.sta1: Open BA session requested for 02:00:00:00:00:00 tid 0 wlan3.sta1: dropped frame to 02:00:00:00:00:00 (unauthorized port) wlan0: moving STA 02:00:00:00:03:00 to state 2 wlan0: moving STA 02:00:00:00:03:00 to state 1 wlan0: Removed STA 02:00:00:00:03:00 wlan0: Destroyed STA 02:00:00:00:03:00 BUG: unable to handle page fault for address:
    fffffffffffffb48 PGD 11814067 P4D 11814067 PUD 11816067 PMD 0 Oops: 0000 [#1] PREEMPT SMP PTI CPU: 2 PID:
    133397 Comm: kworker/u16:1 Tainted: G W 6.1.0-rc8-wt+ #59 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.0-20220807_005459-localhost 04/01/2014 Workqueue: phy3 ieee80211_ba_session_work [mac80211] RIP: 0010:drv_ampdu_action+0x46/0x280 [mac80211] Code: 53 48 89 f3 be 89 01 00 00 e8 d6 43 bf ef e8 21 46 81 f0 83 bb a0 1b 00 00 04 75 0e 48 8b 9b 28 0d 00 00 48 81 eb 10 0e 00 00 <8b> 93 58 09 00 00 f6 c2 20 0f 84 3b 01 00 00 8b 05 dd 1c 0f 00 85 RSP: 0018:ffffc900025ebd20 EFLAGS: 00010287 RAX:
    0000000000000000 RBX: fffffffffffff1f0 RCX: ffff888102228240 RDX: 0000000080000000 RSI: ffffffff918c5de0 RDI: ffff888102228b40 RBP: ffffc900025ebd40 R08: 0000000000000001 R09: 0000000000000001 R10:
    0000000000000001 R11: 0000000000000000 R12: ffff888118c18ec0 R13: 0000000000000000 R14: ffffc900025ebd60 R15: ffff888018b7efb8 FS: 0000000000000000(0000) GS:ffff88817a600000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: fffffffffffffb48 CR3: 0000000105228006 CR4: 0000000000170ee0 Call Trace: <TASK> ieee80211_tx_ba_session_handle_start+0xd0/0x190 [mac80211] ieee80211_ba_session_work+0xff/0x2e0 [mac80211] process_one_work+0x29f/0x620 worker_thread+0x4d/0x3d0 ? process_one_work+0x620/0x620 kthread+0xfb/0x120 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork+0x22/0x30 </TASK> (CVE-2022-48875)

  - 已解決 Linux 核心中的下列弱點：udf: Fix preallocation discarding at indirect extent boundary When preallocation extent is the first one in the extent block, the code would corrupt extent tree header instead. Fix the problem and use udf_delete_aext() for deleting extent to avoid some code duplication. (CVE-2022-48946)

  - 已解決 Linux 核心中的下列弱點：Bluetooth: Fix crash when replugging CSR fake controllers It seems fake CSR 5.0 clones can cause the suspend notifier to be registered twice causing the following kernel panic: [ 71.986122] Call Trace: [ 71.986124] <TASK> [ 71.986125] blocking_notifier_chain_register+0x33/0x60 [ 71.986130] hci_register_dev+0x316/0x3d0 [bluetooth 99b5497ea3d09708fa1366c1dc03288bf3cca8da] [ 71.986154] btusb_probe+0x979/0xd85 [btusb e1e0605a4f4c01984a4b9c8ac58c3666ae287477] [ 71.986159] ? __pm_runtime_set_status+0x1a9/0x300 [ 71.986162] ? ktime_get_mono_fast_ns+0x3e/0x90 [ 71.986167] usb_probe_interface+0xe3/0x2b0 [ 71.986171] really_probe+0xdb/0x380 [ 71.986174] ? pm_runtime_barrier+0x54/0x90 [ 71.986177]
    __driver_probe_device+0x78/0x170 [ 71.986180] driver_probe_device+0x1f/0x90 [ 71.986183]
    __device_attach_driver+0x89/0x110 [ 71.986186] ? driver_allows_async_probing+0x70/0x70 [ 71.986189] bus_for_each_drv+0x8c/0xe0 [ 71.986192] __device_attach+0xb2/0x1e0 [ 71.986195] bus_probe_device+0x92/0xb0 [ 71.986198] device_add+0x422/0x9a0 [ 71.986201] ? sysfs_merge_group+0xd4/0x110 [ 71.986205] usb_set_configuration+0x57a/0x820 [ 71.986208] usb_generic_driver_probe+0x4f/0x70 [ 71.986211] usb_probe_device+0x3a/0x110 [ 71.986213] really_probe+0xdb/0x380 [ 71.986216] ? pm_runtime_barrier+0x54/0x90 [ 71.986219] __driver_probe_device+0x78/0x170 [ 71.986221] driver_probe_device+0x1f/0x90 [ 71.986224] __device_attach_driver+0x89/0x110 [ 71.986227] ? driver_allows_async_probing+0x70/0x70 [ 71.986230] bus_for_each_drv+0x8c/0xe0 [ 71.986232]
    __device_attach+0xb2/0x1e0 [ 71.986235] bus_probe_device+0x92/0xb0 [ 71.986237] device_add+0x422/0x9a0 [71.986239] ? _dev_info+0x7d/0x98 [ 71.986242] ? blake2s_update+0x4c/0xc0 [ 71.986246] usb_new_device.cold+0x148/0x36d [ 71.986250] hub_event+0xa8a/0x1910 [ 71.986255] process_one_work+0x1c4/0x380 [ 71.986259] worker_thread+0x51/0x390 [ 71.986262] ? rescuer_thread+0x3b0/0x3b0 [ 71.986264] kthread+0xdb/0x110 [ 71.986266] ? kthread_complete_and_exit+0x20/0x20 [ 71.986268] ret_from_fork+0x1f/0x30 [ 71.986273] </TASK> [ 71.986274]
    ---[ end trace 0000000000000000 ]--- [ 71.986284] btusb: probe of 2-1.6:1.0 failed with error -17 (CVE-2022-48982)

  - 已解決 Linux 核心中的下列弱點：can: m_can: pci: add missing m_can_class_free_dev() in probe/remove methods In m_can_pci_remove() and error handling path of m_can_pci_probe(), m_can_class_free_dev() should be called to free resource allocated by m_can_class_allocate_dev(), otherwise there will be memleak. (CVE-2022-49024)

請注意，Nessus 並未測試這些問題，而是僅依據應用程式自我報告的版本號碼作出判斷。

遠端主機上安裝的核心版本早於 5.15.93-55.139。因此，會受到 ALAS2KERNEL-515-2024-037 公告中所提及的多個弱點影響。

    在 Linux 核心的第 2 層通道通訊協定 (L2TP) 中發現一個缺陷。清除 sk_user_data 時遺漏鎖定可導致爭用條件和 NULL 指標解除參照弱點。本機使用者可利用此缺陷造成系統當機，進而引發拒絕服務。(CVE-2022-4129)

    在 Linux 核心中，下列弱點已解決：

    cpufreq省長使用 kobject release() 方法釋放 dbs_data (CVE-2022-49513)

    在 Linux 核心中，下列弱點已解決：

    ovl針對 memcpy() 目的地使用 buf 彈性陣列 (CVE-2022-49743)

    在 Linux 核心中，下列弱點已解決：

    perf/x86/amd修正 int 移位時可能發生的整數溢位 (CVE-2022-49748)

    在 Linux 核心中，下列弱點已解決：

    裝置屬性fwnode_graph_get_next_endpoint() 中節點 refcount 洩漏的修正 (CVE-2022-49752)

    在 Linux 核心中，下列弱點已解決：

    dmaengine：修正 dma_chan_get() 中 client_count 的雙重遞增 (CVE-2022-49753)

    在 Linux 核心中發現一個缺陷。在使用者將 capable 檔案從一個 nosuid 掛載區複製到另一個掛載時，在 Linux 核心的 OverlayFS 子系統中發現未經授權使用 capabilities 執行 setuid 檔案的情況。本機使用者可利用此 uid 對應錯誤提升自己的系統權限。(CVE-2023-0386)

    在 Linux 核心的人體介面裝置 (HID) 子系統中，使用者插入惡意 USB 裝置的方式中存在記憶體損毀缺陷。本機使用者可利用此缺陷造成系統當機，或可能提升自己的系統權限。(CVE-2023-1073)

    在 Linux 核心的 NFS 檔案系統中，發現 fs/nfsd/nfs4proc.c 的 nfsd4_ssc_setup_dul 中存在釋放後使用缺陷。本機攻擊者可利用此問題造成系統當機或導致核心資訊洩漏問題。(CVE-2023-1652)

    在 Linux 核心 6.0.8 中，fs/fs-writeback.c 的 inode_cgwb_move_to_attached 中存在與 __list_del_entry_valid 相關的釋放後使用問題。(CVE-2023-26605)

    在 Linux 核心的 Framebuffer Console (fbcon) 中發現一個缺陷。為 fbcon_set_font 提供大於 32 的 font->width 和 font->height 時，由於沒有適當的檢查，會發生移位超出邊界，進而導致未定義的行為且可能造成拒絕服務。(CVE-2023-3161)

    在 Linux 核心的 vc_screen 中，發現 drivers/tty/vt/vc_screen.c 的 vcs_read 中存在釋放後使用瑕疵。具有本機使用者存取權的攻擊者可利用此瑕疵，來造成系統當機或洩漏核心內部資訊。(CVE-2023-3567)

    在 Linux 核心中，下列弱點已解決：

    bpf略過 backtrack_insn 中的無效 kfunc 呼叫 (CVE-2023-52928)

    在 Linux 核心中，下列弱點已解決：

    drm/i915修正可能發生的 bit_17 重複釋放 (CVE-2023-52930)

    在 Linux 核心中，下列弱點已解決：

    mm/swapfile在 get_swap_pages() 中新增 cond_resched() (CVE-2023-52932)

    在 Linux 核心中，下列弱點已解決：

    Squashfs修正 xattr_ids 計數的處理和功能健全檢查 (CVE-2023-52933)

    在 Linux 核心中，下列弱點已解決：

    kernel/irq/irqdomain.c透過使用 debugfs_lookup() 修正記憶體洩漏 (CVE-2023-52936)

    在 Linux 核心中，下列弱點已解決：

    vc_screen：移動 vcs_read() 中的 struct vc_data 指標載入以避免 UAF (CVE-2023-52973)

    在 Linux 核心中，下列弱點已解決：

    efi修正 efi_mem_reserve_persistent 中潛在的 NULL 解除參照 (CVE-2023-52976)

    在 Linux 核心中，下列弱點已解決：

    netopenvswitch修正 ovs_flow_cmd_new 中的流程記憶體洩漏 (CVE-2023-52977)

    在 Linux 核心中，下列弱點已解決：

    squashfs加強 squashfs_read_xattr_id_table 中的功能健全檢查 (CVE-2023-52979)

    在 Linux 核心中，下列弱點已解決：

    block、bfq修正 bic_set_bfqq() 中 bfqq 的 uaf (CVE-2023-52983)

    在 Linux 核心中，下列弱點已解決：

    bpf、sockmap複製接聽程式時檢查任何 tcp_bpf_prots (CVE-2023-52986)

    在 Linux 核心中，下列弱點已解決：

    net修正 skb_segment_list 中的 NULL 指標 (CVE-2023-52991)

    在 Linux 核心中，下列弱點已解決：

    bpf略過 send_signal_common() 中 pid=1 的工作 (CVE-2023-52992)

    在 Linux 核心中，下列弱點已解決：

    x86/i8259使用 IRQ_LEVEL 標記舊版 PIC 中斷 (CVE-2023-52993)

    在 Linux 核心中，下列弱點已解決：

    ipv4防止 fib_metrics_match() 中潛在的 spectre v1 小工具 (CVE-2023-52996)

    在 Linux 核心中，下列弱點已解決：

    ipv4防止 ip_metrics_convert() 中潛在的 spectre v1 小工具 (CVE-2023-52997)

    在 Linux 核心中，下列弱點已解決：

    net修正 netns ops 註冊錯誤路徑中的 UaF (CVE-2023-52999)

    在 Linux 核心中，下列弱點已解決：

    netlink防止潛在的 spectre v1 小工具 (CVE-2023-53000)

    在 Linux 核心中，下列弱點已解決：

    cifs修正因重新連線時未清除的 server->smbd_conn 導致的 oops (CVE-2023-53006)

    在 Linux 核心中，下列弱點已解決：

    追踪確保 trace_printk() 可以在使用時立即輸出 (CVE-2023-53007)

    在 Linux 核心中，下列弱點已解決：

    netmdio驗證 mdiobus_get_phy() 中的參數 addr (CVE-2023-53019)

    在 Linux 核心中，下列弱點已解決：

    net/schedsch_taprio修正可能的釋放後使用 (CVE-2023-53021)

    在 Linux 核心中，下列弱點已解決：

    bpf修正推測儲存繞過緩和措施不足所導致的指標洩漏 (CVE-2023-53024)

    在 Linux 核心中，下列弱點已解決：

    NFSD修正 nfsd4_ssc_setup_dul() 中的釋放後使用 (CVE-2023-53025)

    在 Linux 核心中，下列弱點已解決：

    RDMA/core修正 ib 區塊迭代器計數器溢位 (CVE-2023-53026)

Tenable 已直接從所測試產品的安全公告擷取前置描述區塊。

請注意，Nessus 並未測試這些問題，而是僅依據應用程式自我報告的版本號碼作出判斷。

远程主机上安装的内核版本低于 5.15.93-55.139。因此，会受到 ALAS2KERNEL-5.15-2024-037 公告中提及的多个漏洞影响。

    在 Linux 内核的第 2 层隧道协议 (L2TP) 中发现了一个缺陷。清除 sk_user_data 时缺少的锁定可导致争用条件和空指针取消引用。本地用户可能利用此缺陷来导致系统崩溃，从而发起拒绝服务攻击。(CVE-2022-4129)

    在 Linux 内核中，以下漏洞已修复：

    cpufreqgovernor使用 kobject release() 方法释放 dbs_data (CVE-2022-49513)

    在 Linux 内核中，以下漏洞已修复：

    ovl将 buf 灵活数组用于 memcpy() 目标 (CVE-2022-49743)

    在 Linux 内核中，以下漏洞已修复：

    perf/x86/amd修复位移 int 时的潜在整数溢出 (CVE-2022-49748)

    在 Linux 内核中，以下漏洞已修复：

    设备属性修复 fwnode_graph_get_next_endpoint() 中的节点引用计数泄漏 (CVE-2022-49752)

    在 Linux 内核中，以下漏洞已修复：

    dmaengine：修复 dma_chan_get() 中 client_count 的双倍递增 (CVE-2022-49753)

    在 Linux 内核中发现了一个缺陷。在用户将 capable 文件从一个 nosuid 挂载分区复制到另一个挂载分区时，在 Linux 内核的 OverlayFS 子系统中发现使用 capabilities 未经授权访问 setuid 文件执行的情况。本地用户可利用此 uid 映射错误来提升其系统权限。(CVE-2023-0386)

    在 Linux 内核的人机接口设备 (HID) 子系统中，发现用户插入恶意 USB 设备的方式存在内存损坏缺陷。本地用户可利用此缺陷导致系统崩溃或可能升级其系统权限。(CVE-2023-1073)

    在 Linux 内核的 NFS 文件系统中，在 fs/nfsd/nfs4proc.c 中的 nfsd4_ssc_setup_dul 发现了一个释放后使用缺陷。此问题允许本地攻击者造成系统崩溃或可能导致内核信息泄露问题。(CVE-2023-1652)

    在 Linux 内核 6.0.8 中，在 fs/fs-writeback.c 的 inode_cgwb_move_to_attached 中有一个与 __list_del_entry_valid 相关的释放后使用缺陷。(CVE-2023-26605)

    在 Linux 内核的 Framebuffer 控制台 (fbcon) 中发现了一个缺陷。向 fbcon_set_font 提供大于 32 的 font->width 和 font->height 时，由于检查不到位，会发生 shift 越界，从而导致不明行为并可能导致拒绝服务。(CVE-2023-3161)

    在 Linux 内核中，发现 vc_screen 中 drivers/tty/vt/vc_screen.c 的 vcs_read 存在一个释放后使用缺陷。如果攻击者具有本地用户访问权限，他们可利用此缺陷造成系统崩溃或泄露内核内部信息。(CVE-2023-3567)

    在 Linux 内核中，以下漏洞已修复：

    bpf跳过 backtrack_insn 中无效的 kfunc 调用CVE-2023-52928

    在 Linux 内核中，以下漏洞已修复：

    drm/i915修复潜在的 bit_17 双重释放 (CVE-2023-52930)

    在 Linux 内核中，以下漏洞已修复：

    mm/swapfile在 get_swap_pages() 中添加 cond_resched() (CVE-2023-52932)

    在 Linux 内核中，以下漏洞已修复：

    Squashfs修复 xattr_ids 计数的处理和健全性检查 (CVE-2023-52933)

    在 Linux 内核中，以下漏洞已修复：

    kernel/irq/irqdomain.c使用 debugfs_lookup() 修复内存泄漏 (CVE-2023-52936)

    在 Linux 内核中，以下漏洞已修复：

    vc_screen：移动 vcs_read() 中的结构 vc_data 指针加载以避免 UAF (CVE-2023-52973)

    在 Linux 内核中，以下漏洞已修复：

    efi修复 efi_mem_reserve_persistent 中潜在的空取消引用 (CVE-2023-52976)

    在 Linux 内核中，以下漏洞已修复：

    netopenvswitch修复 ovs_flow_cmd_new 中的流内存泄漏 (CVE-2023-52977)

    在 Linux 内核中，以下漏洞已修复：

    squashfs强化 squashfs_read_xattr_id_table 中健全性检查 (CVE-2023-52979)

    在 Linux 内核中，以下漏洞已修复：

    blockbfq修复 bic_set_bfqq() 中 bfqq 的 uafCVE-2023-52983

    在 Linux 内核中，以下漏洞已修复：

    bpfsockmap克隆侦听器时检查任何 tcp_bpf_prots (CVE-2023-52986)

    在 Linux 内核中，以下漏洞已修复：

    net修复 skb_segment_list 中的空指针 (CVE-2023-52991)

    在 Linux 内核中，以下漏洞已修复：

    bpf跳过 send_signal_common() 中 pid=1 的任务 (CVE-2023-52992)

    在 Linux 内核中，以下漏洞已修复：

    x86/i8259以 IRQ_LEVEL 标记旧版 PIC 中断 (CVE-2023-52993)

    在 Linux 内核中，以下漏洞已修复：

    ipv4阻止 fib_metrics_match() 中潜在的 spectre v1 小工具 (CVE-2023-52996)

    在 Linux 内核中，以下漏洞已修复：

    ipv4阻止 ip_metrics_convert() 中潜在的 spectre v1 小工具 (CVE-2023-52997)

    在 Linux 内核中，以下漏洞已修复：

    net修复 netns ops 注册错误路径中的 UaF (CVE-2023-52999)

    在 Linux 内核中，以下漏洞已修复：

    netlink阻止潜在的 spectre v1 小工具 (CVE-2023-53000)

    在 Linux 内核中，以下漏洞已修复：

    cifs修复因重新连接中未清除 server->smbd_conn 所导致的 oops (CVE-2023-53006)

    在 Linux 内核中，以下漏洞已修复：

    tracing确保 trace_printk() 在可以使用时可以输出 (CVE-2023-53007)

    在 Linux 内核中，以下漏洞已修复：

    netmdio验证 mdiobus_get_phy() 中的参数地址 (CVE-2023-53019)

    在 Linux 内核中，以下漏洞已修复：

    net/schedsch_taprio修复可能的释放后使用 (CVE-2023-53021)

    在 Linux 内核中，以下漏洞已修复：

    bpf修复因推测存储绕过缓解措施不充分而造成的指针泄漏 (CVE-2023-53024)

    在 Linux 内核中，以下漏洞已修复：

    NFSD修复 nfsd4_ssc_setup_dul() 中的释放后使用 (CVE-2023-53025)

    在 Linux 内核中，以下漏洞已修复：

    RDMA/core修复 ib 块迭代器计数器溢出 (CVE-2023-53026)

Tenable 已直接从测试产品的安全公告中提取上述描述块。

请注意，Nessus 尚未测试这些问题，而是只依据应用程序自我报告的版本号进行判断。

Linux/Unix 主机中安装的一个或多个程序包受到一个漏洞影响，而供应商没有提供补丁程序。

  - 已修复 Linux 内核中的下列漏洞：device property: fix of node refcount leak in fwnode_graph_get_next_endpoint() The 'parent' returned by fwnode_graph_get_port_parent() with refcount incremented when 'prev' is not NULL, it needs be put when finish using it. Because the parent is const, introduce a new variable to store the returned fwnode, then put it before returning from fwnode_graph_get_next_endpoint(). (CVE-2022-49752)

请注意，Nessus 依赖供应商报告的程序包是否存在进行判断。

Linux/Unix ホストには、ベンダーが提供するパッチが利用できない脆弱性の影響を受ける複数のパッケージがインストールされています。

  - Linux カーネルでは、以下の脆弱性が解決されています: device property: fix of node refcount leak in fwnode_graph_get_next_endpoint() The 'parent' returned by fwnode_graph_get_port_parent() with refcount incremented when 'prev' is not NULL, it needs be put when finish using it. Because the parent is const, introduce a new variable to store the returned fwnode, then put it before returning from fwnode_graph_get_next_endpoint(). (CVE-2022-49752)

Nessus は、ベンダーによって報告されたパッケージの存在に依存していることに注意してください。

リモートホストにインストールされているカーネルのバージョンは、5.15.93-55.139より前のものです。したがって、ALAS2KERNEL-5.15-2024-037 のアドバイザリに記載されている複数の脆弱性の影響を受けます。

    Linux カーネルの Layer 2 Tunneling Protocol (L2TP) に欠陥が見つかりました。sk_user_data をクリアする際にロックがないため、競合状態と NULL ポインターデリファレンスを引き起こす可能性があります。ローカルユーザーは、この欠陥を利用して、システムをクラッシュさせ、サービス拒否を引き起こす可能性があります。(CVE-2022-4129)

    Linux カーネルで、以下の脆弱性は解決されています。

    cpufreq governorkobject release() メソッドを使用して dbs_data を解放しますCVE-2022-49513

    Linux カーネルで、以下の脆弱性は解決されています。

    ovlmemcpy() の宛先に対して buf 柔軟配列を使用しますCVE-2022-49743

    Linux カーネルで、以下の脆弱性は解決されています。

    perf/x86/amdint のシフトにおける潜在的な整数オーバーフローを修正しますCVE-2022-49748

    Linux カーネルで、以下の脆弱性は解決されています。

    デバイスプロパティfwnode_graph_get_next_endpoint() でのノード refcount 漏洩の修正CVE-2022-49752]

    Linux カーネルで、以下の脆弱性は解決されています。

    dmaengine: dma_chan_get() の client_count の二重増分を修正 (CVE-2022-49753)

    Linux カーネルに欠陥が見つかりました。この欠陥では、ユーザーが nosuid マウントから別のマウントに対応ファイルをコピーする方法で、機能を持つ setuid ファイルの実行への不正アクセスが Linux カーネルの OverlayFS サブシステムで見つかりました。この uid のマッピングのバグにより、ローカルのユーザーがシステムで権限を昇格させる可能性があります。(CVE-2023-0386)

    Linux カーネルのヒューマンインターフェースデバイス (HID) サブシステムで、ユーザーが悪意のある USB デバイスを挿入する方法に、メモリ破損の欠陥が見つかりました。この欠陥によりローカルユーザーがクラッシュさせたり、システムで自分の権限を昇格させたりする可能性があります。(CVE-2023-1073)

    Linux カーネルの NFS ファイルシステムの fs/nfsd/nfs4proc.c の nfsd4_ssc_setup_dul にメモリ解放後使用 (Use After Free) の欠陥が見つかりました。この問題により、ローカルの攻撃者がシステムをクラッシュさせたり、カーネル情報の漏洩問題を引き起こしたりする可能性があります。(CVE-2023-1652)

    Linux カーネル 6.0.8において、fs/fs-writeback.c の inode_cgwb_move_to_attached に、__ list_del_entry_valid に関連するメモリ解放後使用 (use-after-free) があります。(CVE-2023-26605)

    Linux カーネルのフレームバッファコンソール (fbcon) で欠陥が見つかりました。fbcon_set_font に 32 より大きい font->width と font->height を指定すると、チェックが行われないため、shift-out-of-bounds が発生し、未定義の動作やサービス拒否を引き起こす可能性があります。(CVE-2023-3161)

    Linux カーネルの vc_screen の中の drivers/tty/vt/vc_screen.c の vcs_read に、メモリ解放後使用 (Use After Free) の欠陥が見つかりました。この欠陥により、ローカルのユーザーアクセス権限を持つ攻撃者がシステムをクラッシュさせたりカーネル内部情報を漏洩させたりする可能性があります。(CVE-2023-3567)

    Linux カーネルで、以下の脆弱性は解決されています。

    bpfbacktrack_insn で無効な kfunc 呼び出しをスキップしますCVE-2023-52928

    Linux カーネルで、以下の脆弱性は解決されています。

    drm/i915潜在的な bit_17 の二重解放を修正しますCVE-2023-52930

    Linux カーネルで、以下の脆弱性は解決されています。

    mm/swapfileget_swap_pages() の cond_resched() を追加CVE-2023-52932

    Linux カーネルで、以下の脆弱性は解決されています。

    Squashfsxattr_ids カウントの処理およびサニティチェックを修正しますCVE-2023-52933

    Linux カーネルで、以下の脆弱性は解決されています。

    kernel/irq/irqdomain.cdebugfs_lookup() を使用したメモリリークを修正しますCVE-2023-52936

    Linux カーネルで、以下の脆弱性は解決されています。

    vc_screen: vcs_read() の中の struct vc_data ポインターのロードを移動し、UAF を回避 (CVE-2023-52973)

    Linux カーネルで、以下の脆弱性は解決されています。

    efiefi_mem_reserve_persistent にある潜在的な NULL デリファレンスを修正しますCVE-2023-52976

    Linux カーネルで、以下の脆弱性は解決されています。

    netopenvswitchovs_flow_cmd_new のフローメモリリークを修正しますCVE-2023-52977

    Linux カーネルで、以下の脆弱性は解決されています。

    squashfssquashfs_read_xattr_id_table のサニティチェックを強化しますCVE-2023-52979

    Linux カーネルで、以下の脆弱性は解決されています。

    ブロック、bfqbic_set_bfqq() の bfqq に対する uaf を修正しますCVE-2023-52983

    Linux カーネルで、以下の脆弱性は解決されています。

    bpf、sockmapリスナーを複製する際に tcp_bpf_prots がないかチェックしますCVE-2023-52986

    Linux カーネルで、以下の脆弱性は解決されています。

    netskb_segment_list の NULL ポインターを修正しますCVE-2023-52991

    Linux カーネルで、以下の脆弱性は解決されています。

    bpfsend_signal_common() 内の pid=1 でタスクをスキップしますCVE-2023-52992

    Linux カーネルで、以下の脆弱性は解決されています。

    x86/i8259IRQ_LEVEL でレガシー PIC 割り込みをマークしますCVE-2023-52993

    Linux カーネルで、以下の脆弱性は解決されています。

    ipv4fib_metrics_match() 内の spectre v1 ガジェットの可能性を阻止CVE-2023-52996

    Linux カーネルで、以下の脆弱性は解決されています。

    ipv4ip_metrics_convert() 内の spectre v1 ガジェットの可能性を阻止CVE-2023-52997

    Linux カーネルで、以下の脆弱性は解決されています。

    netnetns ops 登録エラーパスの UaF を修正CVE-2023-52999

    Linux カーネルで、以下の脆弱性は解決されています。

    netlink潜在的な Spectre v1 ガジェットを防止CVE-2023-53000

    Linux カーネルで、以下の脆弱性は解決されています。

    cifs再接続の不明確な server->smbd_conn による oops を修正しますCVE-2023-53006

    Linux カーネルで、以下の脆弱性は解決されています。

    tracingtrace_printk() が使用可能になったらすぐに出力できるようにしますCVE-2023-53007

    Linux カーネルで、以下の脆弱性は解決されています。

    netmdiomdiobus_get_phy() でのパラメーター addr を検証CVE-2023-53019

    Linux カーネルで、以下の脆弱性は解決されています。

    net/schedsch_taprio潜在的な use-after-free を修正しますCVE-2023-53021

    Linux カーネルで、以下の脆弱性は解決されています。

    bpf投機的ストアバイパス緩和が不十分なためのポインター漏洩を修正しますCVE-2023-53024

    Linux カーネルで、以下の脆弱性は解決されています。

    NFSDnfsd4_ssc_setup_dul() での use-after-free を修正CVE-2023-53025]

    Linux カーネルで、以下の脆弱性は解決されています。

    RDMA/coreib ブロック反復子カウンターのオーバーフローを修正しますCVE-2023-53026

Tenable は、前述の記述ブロックをテスト済み製品のセキュリティアドバイザリから直接抽出しています。

Nessus はこれらの問題をテストしておらず、代わりにアプリケーションが自己報告するバージョン番号にのみ依存していることに注意してください。

AlmaLinux 9.2 ホストには、TuxCare ALMALINUX9.2:CLSA-2026:1780516677アドバイザリに記載されている複数の脆弱性の影響を受けるパッケージがインストールされています。

  - Linux カーネルでは、以下の脆弱性が解決されています: can: isotp: fix potential CAN frame reception race in isotp_rcv() When receiving a CAN frame the current code logic does not consider concurrently receiving processes which do not show up in real world usage. Ziyang Xuan writes: The following syz problem is one of the scenarios. so->rx.len is changed by isotp_rcv_ff() during isotp_rcv_cf(), so->rx.len equals 0 before alloc_skb() and equals 4096 after alloc_skb(). That will trigger skb_over_panic() in skb_put(). ======================================================= CPU: 1 PID:
    19 Comm: ksoftirqd/1 Not tainted 5.16.0-rc8-syzkaller #0 RIP: 0010:skb_panic+0x16c/0x16e net/core/skbuff.c:113 Call Trace: <TASK> skb_over_panic net/core/skbuff.c:118 [inline] skb_put.cold+0x24/0x24 net/core/skbuff.c:1990 isotp_rcv_cf net/can/isotp.c:570 [inline] isotp_rcv+0xa38/0x1e30 net/can/isotp.c:668 deliver net/can/af_can.c:574 [inline] can_rcv_filter+0x445/0x8d0 net/can/af_can.c:635 can_receive+0x31d/0x580 net/can/af_can.c:665 can_rcv+0x120/0x1c0 net/can/af_can.c:696 __netif_receive_skb_one_core+0x114/0x180 net/core/dev.c:5465
    __netif_receive_skb+0x24/0x1b0 net/core/dev.c:5579 Therefore we make sure the state changes and data structures stay consistent at CAN frame reception time by adding a spin_lock in isotp_rcv(). This fixes the issue reported by syzkaller but does not affect real world operation. (CVE-2022-48830)

  - Linux カーネルでは、以下の脆弱性が解決されています: wifi: mac80211: sdata can be NULL during AMPDU start ieee80211_tx_ba_session_handle_start() may get NULL for sdata when a deauthentication is ongoing. Here a trace triggering the race with the hostapd test multi_ap_fronthaul_on_ap: (gdb) list
    *drv_ampdu_action+0x46 0x8b16 is in drv_ampdu_action (net/mac80211/driver-ops.c:396). 391 int ret =
    -EOPNOTSUPP; 392 393 might_sleep(); 394 395 sdata = get_bss_sdata(sdata); 396 if (!check_sdata_in_driver(sdata)) 397 return -EIO; 398 399 trace_drv_ampdu_action(local, sdata, params); 400 wlan0: moving STA 02:00:00:00:03:00 to state 3 wlan0: associated wlan0: deauthenticating from 02:00:00:00:03:00 by local choice (Reason: 3=DEAUTH_LEAVING) wlan3.sta1: Open BA session requested for 02:00:00:00:00:00 tid 0 wlan3.sta1: dropped frame to 02:00:00:00:00:00 (unauthorized port) wlan0: moving STA 02:00:00:00:03:00 to state 2 wlan0: moving STA 02:00:00:00:03:00 to state 1 wlan0: Removed STA 02:00:00:00:03:00 wlan0: Destroyed STA 02:00:00:00:03:00 BUG: unable to handle page fault for address:
    fffffffffffffb48 PGD 11814067 P4D 11814067 PUD 11816067 PMD 0 Oops: 0000 [#1] PREEMPT SMP PTI CPU: 2 PID:
    133397 Comm: kworker/u16:1 Tainted: G W 6.1.0-rc8-wt+ #59 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.0-20220807_005459-localhost 04/01/2014 Workqueue: phy3 ieee80211_ba_session_work [mac80211] RIP: 0010:drv_ampdu_action+0x46/0x280 [mac80211] Code: 53 48 89 f3 be 89 01 00 00 e8 d6 43 bf ef e8 21 46 81 f0 83 bb a0 1b 00 00 04 75 0e 48 8b 9b 28 0d 00 00 48 81 eb 10 0e 00 00 <8b> 93 58 09 00 00 f6 c2 20 0f 84 3b 01 00 00 8b 05 dd 1c 0f 00 85 RSP: 0018:ffffc900025ebd20 EFLAGS: 00010287 RAX:
    0000000000000000 RBX: fffffffffffff1f0 RCX: ffff888102228240 RDX: 0000000080000000 RSI: ffffffff918c5de0 RDI: ffff888102228b40 RBP: ffffc900025ebd40 R08: 0000000000000001 R09: 0000000000000001 R10:
    0000000000000001 R11: 0000000000000000 R12: ffff888118c18ec0 R13: 0000000000000000 R14: ffffc900025ebd60 R15: ffff888018b7efb8 FS: 0000000000000000(0000) GS:ffff88817a600000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: fffffffffffffb48 CR3: 0000000105228006 CR4: 0000000000170ee0 Call Trace: <TASK> ieee80211_tx_ba_session_handle_start+0xd0/0x190 [mac80211] ieee80211_ba_session_work+0xff/0x2e0 [mac80211] process_one_work+0x29f/0x620 worker_thread+0x4d/0x3d0 ? process_one_work+0x620/0x620 kthread+0xfb/0x120 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork+0x22/0x30 </TASK> (CVE-2022-48875)

  - Linux カーネルでは、以下の脆弱性が解決されています: udf: Fix preallocation discarding at indirect extent boundary When preallocation extent is the first one in the extent block, the code would corrupt extent tree header instead. Fix the problem and use udf_delete_aext() for deleting extent to avoid some code duplication. (CVE-2022-48946)

  - Linux カーネルでは、以下の脆弱性が解決されています: Bluetooth: Fix crash when replugging CSR fake controllers It seems fake CSR 5.0 clones can cause the suspend notifier to be registered twice causing the following kernel panic: [ 71.986122] Call Trace: [ 71.986124] <TASK> [ 71.986125] blocking_notifier_chain_register+0x33/0x60 [ 71.986130] hci_register_dev+0x316/0x3d0 [bluetooth 99b5497ea3d09708fa1366c1dc03288bf3cca8da] [ 71.986154] btusb_probe+0x979/0xd85 [btusb e1e0605a4f4c01984a4b9c8ac58c3666ae287477] [ 71.986159] ? __pm_runtime_set_status+0x1a9/0x300 [ 71.986162] ? ktime_get_mono_fast_ns+0x3e/0x90 [ 71.986167] usb_probe_interface+0xe3/0x2b0 [ 71.986171] really_probe+0xdb/0x380 [ 71.986174] ? pm_runtime_barrier+0x54/0x90 [ 71.986177]
    __driver_probe_device+0x78/0x170 [ 71.986180] driver_probe_device+0x1f/0x90 [ 71.986183]
    __device_attach_driver+0x89/0x110 [ 71.986186] ? driver_allows_async_probing+0x70/0x70 [ 71.986189] bus_for_each_drv+0x8c/0xe0 [ 71.986192] __device_attach+0xb2/0x1e0 [ 71.986195] bus_probe_device+0x92/0xb0 [ 71.986198] device_add+0x422/0x9a0 [ 71.986201] ? sysfs_merge_group+0xd4/0x110 [ 71.986205] usb_set_configuration+0x57a/0x820 [ 71.986208] usb_generic_driver_probe+0x4f/0x70 [ 71.986211] usb_probe_device+0x3a/0x110 [ 71.986213] really_probe+0xdb/0x380 [ 71.986216] ? pm_runtime_barrier+0x54/0x90 [ 71.986219] __driver_probe_device+0x78/0x170 [ 71.986221] driver_probe_device+0x1f/0x90 [ 71.986224] __device_attach_driver+0x89/0x110 [ 71.986227] ? driver_allows_async_probing+0x70/0x70 [ 71.986230] bus_for_each_drv+0x8c/0xe0 [ 71.986232]
    __device_attach+0xb2/0x1e0 [ 71.986235] bus_probe_device+0x92/0xb0 [ 71.986237] device_add+0x422/0x9a0 [71.986239] ? _dev_info+0x7d/0x98 [ 71.986242] ? blake2s_update+0x4c/0xc0 [ 71.986246] usb_new_device.cold+0x148/0x36d [ 71.986250] hub_event+0xa8a/0x1910 [ 71.986255] process_one_work+0x1c4/0x380 [ 71.986259] worker_thread+0x51/0x390 [ 71.986262] ? rescuer_thread+0x3b0/0x3b0 [ 71.986264] kthread+0xdb/0x110 [ 71.986266] ? kthread_complete_and_exit+0x20/0x20 [ 71.986268] ret_from_fork+0x1f/0x30 [ 71.986273] </TASK> [ 71.986274]
    ---[ end trace 0000000000000000 ]--- [ 71.986284] btusb: probe of 2-1.6:1.0 failed with error -17 (CVE-2022-48982)

  - Linux カーネルでは、以下の脆弱性が解決されています: can: m_can: pci: add missing m_can_class_free_dev() in probe/remove methods In m_can_pci_remove() and error handling path of m_can_pci_probe(), m_can_class_free_dev() should be called to free resource allocated by m_can_class_allocate_dev(), otherwise there will be memleak. (CVE-2022-49024)

Nessus はこれらの問題をテストしておらず、代わりにアプリケーションが自己報告するバージョン番号にのみ依存していることに注意してください。

The version of kernel installed on the remote host is prior to 5.15.93-55.139. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.15-2024-037 advisory.

    A flaw was found in the Linux kernel's Layer 2 Tunneling Protocol (L2TP). A missing lock when clearing     sk_user_data can lead to a race condition and NULL pointer dereference. A local user could use this flaw     to potentially crash the system causing a denial of service. (CVE-2022-4129)

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

    cpufreq: governor: Use kobject release() method to free dbs_data (CVE-2022-49513)

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

    ovl: Use buf flexible array for memcpy() destination (CVE-2022-49743)

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

    perf/x86/amd: fix potential integer overflow on shift of a int (CVE-2022-49748)

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

    device property: fix of node refcount leak in fwnode_graph_get_next_endpoint() (CVE-2022-49752)

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

    dmaengine: Fix double increment of client_count in dma_chan_get() (CVE-2022-49753)

    A flaw was found in the Linux kernel, where unauthorized access to the execution of the setuid file with     capabilities was found in the Linux kernel's OverlayFS subsystem in how a user copies a capable file from     a nosuid mount into another mount. This uid mapping bug allows a local user to escalate their privileges     on the system. (CVE-2023-0386)

    A memory corruption flaw was found in the Linux kernel's human interface device (HID) subsystem in how a     user inserts a malicious USB device. This flaw allows a local user to crash or potentially escalate their     privileges on the system. (CVE-2023-1073)

    A use-after-free flaw was found in nfsd4_ssc_setup_dul in fs/nfsd/nfs4proc.c in the NFS filesystem in the     Linux Kernel. This issue could allow a local attacker to crash the system or it may lead to a kernel     information leak problem. (CVE-2023-1652)

    In the Linux kernel 6.0.8, there is a use-after-free in inode_cgwb_move_to_attached in fs/fs-writeback.c,     related to __list_del_entry_valid. (CVE-2023-26605)

    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)

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

    bpf: Skip invalid kfunc call in backtrack_insn (CVE-2023-52928)

    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:

    kernel/irq/irqdomain.c: fix memory leak with using debugfs_lookup() (CVE-2023-52936)

    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:

    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:

    block, bfq: fix uaf for bfqq in bic_set_bfqq() (CVE-2023-52983)

    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:

    net: fix NULL pointer in skb_segment_list (CVE-2023-52991)

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

    bpf: Skip task with pid=1 in send_signal_common() (CVE-2023-52992)

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

    x86/i8259: Mark legacy PIC interrupts with IRQ_LEVEL (CVE-2023-52993)

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

    ipv4: prevent potential spectre v1 gadget in fib_metrics_match() (CVE-2023-52996)

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

    ipv4: prevent potential spectre v1 gadget in ip_metrics_convert() (CVE-2023-52997)

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

    net: fix UaF in netns ops registration error path (CVE-2023-52999)

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

    netlink: prevent potential spectre v1 gadgets (CVE-2023-53000)

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

    cifs: Fix oops due to uncleared server->smbd_conn in reconnect (CVE-2023-53006)

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

    tracing: Make sure trace_printk() can output as soon as it can be used (CVE-2023-53007)

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

    net: mdio: validate parameter addr in mdiobus_get_phy() (CVE-2023-53019)

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

    net/sched: sch_taprio: fix possible use-after-free (CVE-2023-53021)

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

    bpf: Fix pointer-leak due to insufficient speculative store bypass mitigation (CVE-2023-53024)

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

    NFSD: fix use-after-free in nfsd4_ssc_setup_dul() (CVE-2023-53025)

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

    RDMA/core: Fix ib block iterator counter overflow (CVE-2023-53026)

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 AlmaLinux 9.2 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.2:CLSA-2026:1780516677 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: can: isotp: fix potential CAN frame     reception race in isotp_rcv() When receiving a CAN frame the current code logic does not consider     concurrently receiving processes which do not show up in real world usage. Ziyang Xuan writes: The     following syz problem is one of the scenarios. so->rx.len is changed by isotp_rcv_ff() during     isotp_rcv_cf(), so->rx.len equals 0 before alloc_skb() and equals 4096 after alloc_skb(). That will     trigger skb_over_panic() in skb_put(). ======================================================= CPU: 1 PID:
    19 Comm: ksoftirqd/1 Not tainted 5.16.0-rc8-syzkaller #0 RIP: 0010:skb_panic+0x16c/0x16e     net/core/skbuff.c:113 Call Trace: <TASK> skb_over_panic net/core/skbuff.c:118 [inline]     skb_put.cold+0x24/0x24 net/core/skbuff.c:1990 isotp_rcv_cf net/can/isotp.c:570 [inline]     isotp_rcv+0xa38/0x1e30 net/can/isotp.c:668 deliver net/can/af_can.c:574 [inline]     can_rcv_filter+0x445/0x8d0 net/can/af_can.c:635 can_receive+0x31d/0x580 net/can/af_can.c:665     can_rcv+0x120/0x1c0 net/can/af_can.c:696 __netif_receive_skb_one_core+0x114/0x180 net/core/dev.c:5465
    __netif_receive_skb+0x24/0x1b0 net/core/dev.c:5579 Therefore we make sure the state changes and data     structures stay consistent at CAN frame reception time by adding a spin_lock in isotp_rcv(). This fixes     the issue reported by syzkaller but does not affect real world operation. (CVE-2022-48830)

  - In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: sdata can be NULL     during AMPDU start ieee80211_tx_ba_session_handle_start() may get NULL for sdata when a deauthentication     is ongoing. Here a trace triggering the race with the hostapd test multi_ap_fronthaul_on_ap: (gdb) list
    *drv_ampdu_action+0x46 0x8b16 is in drv_ampdu_action (net/mac80211/driver-ops.c:396). 391 int ret =
    -EOPNOTSUPP; 392 393 might_sleep(); 394 395 sdata = get_bss_sdata(sdata); 396 if     (!check_sdata_in_driver(sdata)) 397 return -EIO; 398 399 trace_drv_ampdu_action(local, sdata, params); 400     wlan0: moving STA 02:00:00:00:03:00 to state 3 wlan0: associated wlan0: deauthenticating from     02:00:00:00:03:00 by local choice (Reason: 3=DEAUTH_LEAVING) wlan3.sta1: Open BA session requested for     02:00:00:00:00:00 tid 0 wlan3.sta1: dropped frame to 02:00:00:00:00:00 (unauthorized port) wlan0: moving     STA 02:00:00:00:03:00 to state 2 wlan0: moving STA 02:00:00:00:03:00 to state 1 wlan0: Removed STA     02:00:00:00:03:00 wlan0: Destroyed STA 02:00:00:00:03:00 BUG: unable to handle page fault for address:
    fffffffffffffb48 PGD 11814067 P4D 11814067 PUD 11816067 PMD 0 Oops: 0000 [#1] PREEMPT SMP PTI CPU: 2 PID:
    133397 Comm: kworker/u16:1 Tainted: G W 6.1.0-rc8-wt+ #59 Hardware name: QEMU Standard PC (Q35 + ICH9,     2009), BIOS 1.16.0-20220807_005459-localhost 04/01/2014 Workqueue: phy3 ieee80211_ba_session_work     [mac80211] RIP: 0010:drv_ampdu_action+0x46/0x280 [mac80211] Code: 53 48 89 f3 be 89 01 00 00 e8 d6 43 bf     ef e8 21 46 81 f0 83 bb a0 1b 00 00 04 75 0e 48 8b 9b 28 0d 00 00 48 81 eb 10 0e 00 00 <8b> 93 58 09 00 00     f6 c2 20 0f 84 3b 01 00 00 8b 05 dd 1c 0f 00 85 RSP: 0018:ffffc900025ebd20 EFLAGS: 00010287 RAX:
    0000000000000000 RBX: fffffffffffff1f0 RCX: ffff888102228240 RDX: 0000000080000000 RSI: ffffffff918c5de0     RDI: ffff888102228b40 RBP: ffffc900025ebd40 R08: 0000000000000001 R09: 0000000000000001 R10:
    0000000000000001 R11: 0000000000000000 R12: ffff888118c18ec0 R13: 0000000000000000 R14: ffffc900025ebd60     R15: ffff888018b7efb8 FS: 0000000000000000(0000) GS:ffff88817a600000(0000) knlGS:0000000000000000 CS: 0010     DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: fffffffffffffb48 CR3: 0000000105228006 CR4: 0000000000170ee0     Call Trace: <TASK> ieee80211_tx_ba_session_handle_start+0xd0/0x190 [mac80211]     ieee80211_ba_session_work+0xff/0x2e0 [mac80211] process_one_work+0x29f/0x620 worker_thread+0x4d/0x3d0 ?     process_one_work+0x620/0x620 kthread+0xfb/0x120 ? kthread_complete_and_exit+0x20/0x20     ret_from_fork+0x22/0x30 </TASK> (CVE-2022-48875)

  - In the Linux kernel, the following vulnerability has been resolved: udf: Fix preallocation discarding at     indirect extent boundary When preallocation extent is the first one in the extent block, the code would     corrupt extent tree header instead. Fix the problem and use udf_delete_aext() for deleting extent to avoid     some code duplication. (CVE-2022-48946)

  - In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Fix crash when replugging     CSR fake controllers It seems fake CSR 5.0 clones can cause the suspend notifier to be registered twice     causing the following kernel panic: [ 71.986122] Call Trace: [ 71.986124] <TASK> [ 71.986125]     blocking_notifier_chain_register+0x33/0x60 [ 71.986130] hci_register_dev+0x316/0x3d0 [bluetooth     99b5497ea3d09708fa1366c1dc03288bf3cca8da] [ 71.986154] btusb_probe+0x979/0xd85 [btusb     e1e0605a4f4c01984a4b9c8ac58c3666ae287477] [ 71.986159] ? __pm_runtime_set_status+0x1a9/0x300 [ 71.986162]     ? ktime_get_mono_fast_ns+0x3e/0x90 [ 71.986167] usb_probe_interface+0xe3/0x2b0 [ 71.986171]     really_probe+0xdb/0x380 [ 71.986174] ? pm_runtime_barrier+0x54/0x90 [ 71.986177]
    __driver_probe_device+0x78/0x170 [ 71.986180] driver_probe_device+0x1f/0x90 [ 71.986183]
    __device_attach_driver+0x89/0x110 [ 71.986186] ? driver_allows_async_probing+0x70/0x70 [ 71.986189]     bus_for_each_drv+0x8c/0xe0 [ 71.986192] __device_attach+0xb2/0x1e0 [ 71.986195] bus_probe_device+0x92/0xb0     [ 71.986198] device_add+0x422/0x9a0 [ 71.986201] ? sysfs_merge_group+0xd4/0x110 [ 71.986205]     usb_set_configuration+0x57a/0x820 [ 71.986208] usb_generic_driver_probe+0x4f/0x70 [ 71.986211]     usb_probe_device+0x3a/0x110 [ 71.986213] really_probe+0xdb/0x380 [ 71.986216] ?     pm_runtime_barrier+0x54/0x90 [ 71.986219] __driver_probe_device+0x78/0x170 [ 71.986221]     driver_probe_device+0x1f/0x90 [ 71.986224] __device_attach_driver+0x89/0x110 [ 71.986227] ?     driver_allows_async_probing+0x70/0x70 [ 71.986230] bus_for_each_drv+0x8c/0xe0 [ 71.986232]
    __device_attach+0xb2/0x1e0 [ 71.986235] bus_probe_device+0x92/0xb0 [ 71.986237] device_add+0x422/0x9a0 [     71.986239] ? _dev_info+0x7d/0x98 [ 71.986242] ? blake2s_update+0x4c/0xc0 [ 71.986246]     usb_new_device.cold+0x148/0x36d [ 71.986250] hub_event+0xa8a/0x1910 [ 71.986255]     process_one_work+0x1c4/0x380 [ 71.986259] worker_thread+0x51/0x390 [ 71.986262] ?     rescuer_thread+0x3b0/0x3b0 [ 71.986264] kthread+0xdb/0x110 [ 71.986266] ?     kthread_complete_and_exit+0x20/0x20 [ 71.986268] ret_from_fork+0x1f/0x30 [ 71.986273] </TASK> [ 71.986274]
    ---[ end trace 0000000000000000 ]--- [ 71.986284] btusb: probe of 2-1.6:1.0 failed with error -17     (CVE-2022-48982)

  - In the Linux kernel, the following vulnerability has been resolved: can: m_can: pci: add missing     m_can_class_free_dev() in probe/remove methods In m_can_pci_remove() and error handling path of     m_can_pci_probe(), m_can_class_free_dev() should be called to free resource allocated by     m_can_class_allocate_dev(), otherwise there will be memleak. (CVE-2022-49024)

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.

  - In the Linux kernel, the following vulnerability has been resolved: device property: fix of node refcount     leak in fwnode_graph_get_next_endpoint() The 'parent' returned by fwnode_graph_get_port_parent() with     refcount incremented when 'prev' is not NULL, it needs be put when finish using it. Because the parent is     const, introduce a new variable to store the returned fwnode, then put it before returning from     fwnode_graph_get_next_endpoint(). (CVE-2022-49752)

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

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
351689	AlmaLinux 9.2 [TuxCare] 安全更新：bpftool / kernel / kernel-64k / kernel-64k-core / kernel-64k-debug 等多个漏洞（ALMALINUX9.2：CLSA-2026：1780516677）	Nessus	Alma Linux Local Security Checks	2026/9/30	2026/10/19	high
246852	Linux Distros 未修補的弱點：CVE-2022-49752	Nessus	Misc.	2025/8/9	2026/9/30	medium
351689	AlmaLinux 9.2 [TuxCare] 安全性更新：bpftool / kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc 多個弱點（ALMALINUX9.2：CLSA-2026：1780516677）	Nessus	Alma Linux Local Security Checks	2026/9/30	2026/10/19	high
190056	Amazon Linux 2：kernel (ALASKERNEL-5.15-2024-037)	Nessus	Amazon Linux Local Security Checks	2024/2/6	2026/2/26	high
190056	Amazon Linux 2：内核 (ALASKERNEL-5.15-2024-037)	Nessus	Amazon Linux Local Security Checks	2024/2/6	2026/2/26	high
246852	Linux Distros 未修补的漏洞：CVE-2022-49752	Nessus	Misc.	2025/8/9	2026/9/30	medium
246852	Linux Distros のパッチ未適用の脆弱性: CVE-2022-49752	Nessus	Misc.	2025/8/9	2026/9/30	medium
190056	Amazon Linux 2 : kernel (ALASKERNEL-5.15-2024-037)	Nessus	Amazon Linux Local Security Checks	2024/2/6	2026/2/26	high
351689	AlmaLinux 9.2 [TuxCare] セキュリティ更新プログラム:bpftool/kernel/kernel-64k/kernel-64k-core/kernel-64k-debug/etcの複数の脆弱性(ALMALINUX9.2:CLSA-2026:1780516677)	Nessus	Alma Linux Local Security Checks	2026/9/30	2026/10/19	high
190056	Amazon Linux 2 : kernel (ALASKERNEL-5.15-2024-037)	Nessus	Amazon Linux Local Security Checks	2024/2/6	2026/2/26	high
351689	AlmaLinux 9.2 [TuxCare] Security Update: bpftool / kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2026:1780516677)	Nessus	Alma Linux Local Security Checks	2026/9/30	2026/10/19	high
246852	Linux Distros Unpatched Vulnerability : CVE-2022-49752	Nessus	Misc.	2025/8/9	2026/9/30	medium

检测

插件搜索

high

medium

high

high

high

medium

medium

high

high

high

high

medium