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

  - firmwarearm_ffa将互斥体替换为 rwlock以避免原子上下文中的休眠 当前使用互斥体保护通知者哈希表访问的情况可导致原子上下文中出现问题。这样做会导致出现以下内核警告| BUG休眠从 kernel/locking/mutex.c:258 的无效上下文调用的函数in_atomic()1、irqs_disabled()1、non_block0、pid9、名称kworker/0:0 | | preempt_count1预期0 | | RCU 嵌套深度 0 预期 0 | CPU0 UID0 PID9 Commkworker/0:0 未受感染 6.14.0 #4 | | | | Workqueueffa_pcpu_irq_notification notif_pcpu_irq_work_fn | Workqueueffa_pcpu_irq_notification notif_pcpu_irq_work_fn调用跟踪show_stack+0x18/0x24 (C) | dump_stack_lvl+0x78/0x90 | dump_stack+0x18/0x24 | dump_stack+0x18/0x24 | __might_resched+0x114/0x170 | | __might_sleep+0x48/0x98 | | mutex_lock+0x24/0x80 | handle_notif_callbacks+0x54/0xe0 | handle_notif_callbacks+0x54/0xe0 | handle_notif_callbacks+0x54/0xe0 | notif_get_and_handle+0x40/0x88 | | generic_exec_single+0x80/0xc0 | | smp_call_function_single+0xfc/0x1a0 | | notif_pcpu_irq_work_fn+0x2c/0x38 | | process_one_work+0x14c/0x2b4 | work_thread+0x2e4/0x3e0 | | kthread+0x13c/0x210 ret_from_fork+0x10/0x20 要解决此问题请使用 rwlock 替换 mutex 以保护通知程序哈希表访问。这可确保读取端锁定不会休眠，并且多个读取方可并发获取锁定，从而避免不必要的争用和潜在的死锁。编写器访问保持独占，以保持正确性。
    此更改解决了 lockdep 有关 atomic 上下文中潜在睡眠的警告。 (CVE-2025-38388)

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

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

  - firmwarearm_ffa將 mutex 取代為 rwlock以避免在不可部分完成內容中進入睡眠。目前使用 mutex 來保護通知程式雜湊表存取會導致不可部分內容內容中發生問題。這會導致以下核心警告錯誤從 kernel/locking/mutex.c:258 的無效內容呼叫休眠函式 | in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 9, name: kworker/0:0 | preempt_count1、 預期0 RCU 巢狀深度0、預期0 | CPU: 0 UID: 0 PID: 9 Comm: kworker/0:0 未受污染 6.14.0 #4 | Workqueueffa_pcpu_irq_notification notif_pcpu_irq_work_fn |呼叫追踪| show_stack+0x18/0x24 (C) | dump_stack_lvl+0x78/0x90 | dump_stack+0x18/0x24 | __might_resched+0x114/0x170 | 版__might_sleep+0x48/0x98 | 版mutex_lock+0x24/0x80 | handle_notif_callbacks+0x54/0xe0 | notif_get_and_handle+0x40/0x88 | generic_exec_single+0x80/0xc0 | smp_call_function_single+0xfc/0x1a0 | 版notif_pcpu_irq_work_fn+0x2c/0x38| process_one_work+0x14c/0x2b4 | worker_thread+0x2e4/0x3e0 | kthread+0x13c/0x210 | ret_from_fork+0x10/0x20 若要解決此問題請將 mutex 取代為 rwlock以保護通知程式雜湊表存取。這可確保讀取端鎖定不會進入休眠狀態且多個讀取器可同時取得鎖定以避免不必要的爭用和潛在的鎖死。寫入器存取權維持獨占性進而保留正確性。
    此變更可解決來自 lockdep 的有關不可部分完成內容中潛在睡眠的警告。 (CVE-2025-38388)

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

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

  - ファームウェアarm_ffamutex を rwlock で置換し、アトミックコンテキストでのスリープを回避します。通知者ハッシュテーブルアクセスを保護するために mutex を現在使用しています。これは、アトミックコンテキストで問題を引き起こす可能性があります。これにより、以下のカーネル警告が表示されます。|バグ kernel/locking/mutex.c:258 で無効なコンテキストから呼び出されたスリープ関数 | in_atomic(): 1、irqs_disabled(): 1、non_block: 0、pid: 9、name: kworker/0:0 | preempt_count: 1、 expected: 0 | RCU ネストの深さ: 0、予期: 0 | CPU0 UID0 PID9 通信kworker/0:0 汚染されていない 6.14.0 #4 |ワークキュー ffa_pcpu_irq_notification notif_pcpu_irq_work_fn | trace: | show_stack+0x18/0x24 (C) | dump_stack_lvl+0x78/0x90 | dump_stack+0x18/0x24 | __might_resched+0x114/0x170 | __might_sleep+0x48/0x98 | mutex_lock+0x24/0x80 | handle_notif_callbacks+0x54/0xe0 | notif_get_and_handle+0x40/0x88 | generic_exec_single+0x80/0xc0 | smp_call_function_single+0xfc/0x1a0 | notif_pcpu_irq_work_fn+0x2c/0x38 | process_one_work+0x14c/0x2b4 | worker_thread+0x2e4/0x3e0 | kthread+0x13c/0x210 | ret_from_fork+0x10/0x20 これに対処するには、mutex を rwlock で置換して通知者のハッシュテーブルアクセスを保護します。これにより、リードサイドロックがスリープしないようにし、複数のリーダーが同時にロックを取得できるようにして、不要な競合や潜在的なデッドロックを回避します。Writer アクセスは排他的のままで、正確性を維持します。
    この変更により、アトミックなコンテキストの潜在的なスリープに関する lockdep からの警告が解決されます。CVE-2025-38388

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

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

  - firmware: arm_ffa: Replace mutex with rwlock to avoid sleep in atomic context The current use of a mutex     to protect the notifier hashtable accesses can lead to issues in the atomic context. It results in the     below kernel warnings: | BUG: sleeping function called from invalid context at kernel/locking/mutex.c:258     | in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 9, name: kworker/0:0 | preempt_count: 1,     expected: 0 | RCU nest depth: 0, expected: 0 | CPU: 0 UID: 0 PID: 9 Comm: kworker/0:0 Not tainted 6.14.0     #4 | Workqueue: ffa_pcpu_irq_notification notif_pcpu_irq_work_fn | Call trace: | show_stack+0x18/0x24 (C)     | dump_stack_lvl+0x78/0x90 | dump_stack+0x18/0x24 | __might_resched+0x114/0x170 | __might_sleep+0x48/0x98     | mutex_lock+0x24/0x80 | handle_notif_callbacks+0x54/0xe0 | notif_get_and_handle+0x40/0x88 |     generic_exec_single+0x80/0xc0 | smp_call_function_single+0xfc/0x1a0 | notif_pcpu_irq_work_fn+0x2c/0x38 |     process_one_work+0x14c/0x2b4 | worker_thread+0x2e4/0x3e0 | kthread+0x13c/0x210 | ret_from_fork+0x10/0x20     To address this, replace the mutex with an rwlock to protect the notifier hashtable accesses. This ensures     that read-side locking does not sleep and multiple readers can acquire the lock concurrently, avoiding     unnecessary contention and potential deadlocks. Writer access remains exclusive, preserving correctness.
    This change resolves warnings from lockdep about potential sleep in atomic context. (CVE-2025-38388)

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

因此，此版本會受到 ALAS2023-2025-1130 公告中提及的一個弱點影響。

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

    virtio中斷並重設 device_shutdown() 上的 virtio 裝置 (CVE-2025-38064)

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

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

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

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

    virtio: break and reset virtio devices on device_shutdown() (CVE-2025-38064)

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

    netfs: Fix oops in write-retry from mis-resetting the subreq iterator (CVE-2025-38139)

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

    af_unix: Don't leave consecutive consumed OOB skbs. (CVE-2025-38236)

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

    mm: userfaultfd: fix race of userfaultfd_move and swap cache (CVE-2025-38242)

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

    smb: client: fix potential deadlock when reconnecting channels (CVE-2025-38244)

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

    lib/group_cpus: fix NULL pointer dereference from group_cpus_evenly() (CVE-2025-38255)

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

    io_uring/rsrc: fix folio unpinning (CVE-2025-38256)

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

    mm/damon/sysfs-schemes: free old damon_sysfs_scheme_filter->memcg_path on write (CVE-2025-38258)

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

    btrfs: handle csum tree error with rescue=ibadroots correctly (CVE-2025-38260)

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

    tty: serial: uartlite: register uart driver in init (CVE-2025-38262)

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

    bcache: fix NULL pointer in cache_set_flush() (CVE-2025-38263)

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

    nvme-tcp: sanitize request list handling (CVE-2025-38264)

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

    bpf: Do not include stack ptr register in precision backtracking bookkeeping (CVE-2025-38279)

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

    net/sched: Always pass notifications when child class becomes empty (CVE-2025-38350)

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

    btrfs: fix a race between renames and directory logging (CVE-2025-38365)

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

    RDMA/mlx5: Fix unsafe xarray access in implicit ODP handling (CVE-2025-38372)

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

    IB/mlx5: Fix potential deadlock in MR deregistration (CVE-2025-38373)

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

    virtio-net: ensure the received length does not exceed allocated size (CVE-2025-38375)

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

    smb: client: fix warning when reconnecting channel (CVE-2025-38379)

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

    mm/vmalloc: fix data race in show_numa_info() (CVE-2025-38383)

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

    ACPICA: Refuse to evaluate a method if arguments are missing (CVE-2025-38386)

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

    firmware: arm_ffa: Replace mutex with rwlock to avoid sleep in atomic context (CVE-2025-38388)

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

    drm/i915/gt: Fix timeline left held on VMA alloc error (CVE-2025-38389)

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

    firmware: arm_ffa: Fix memory leak by freeing notifier callback node (CVE-2025-38390)

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

    NFSv4/pNFS: Fix a race to wake on NFS_LAYOUT_DRAIN (CVE-2025-38393)

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

    fs: export anon_inode_make_secure_inode() and fix secretmem LSM bypass (CVE-2025-38396)

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

    scsi: target: Fix NULL pointer dereference in core_scsi3_decode_spec_i_port() (CVE-2025-38399)

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

    nfs: Clean up /proc/net/rpc/nfs when nfs_fs_proc_net_init() fails. (CVE-2025-38400)

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

    vsock/vmci: Clear the vmci transport packet properly when initializing it (CVE-2025-38403)

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

    virtio-net: xsk: rx: fix the frame's length check (CVE-2025-38413)

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

    cifs: Fix the smbd_response slab to allow usercopy (CVE-2025-38523)

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.

因此，该程序受到 ALAS2023-2025-1130 公告中提及的一个漏洞影响。

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

    virtio中断并重置 device_shutdown() 上的 virtio 设备 (CVE-2025-38064)

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

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

したがって、ALAS2023-2025-1130 のアドバイザリに記載されている脆弱性の影響を受けます。

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

    virtiodevice_shutdown() で virtio デバイスを破損してリセットしますCVE-2025-38064

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

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

ID	名前	製品	ファミリー	公開日	更新日	深刻度
252202	Linux Distros 未修补的漏洞：CVE-2025-38388	Nessus	Misc.	2025/8/19	2025/9/4	medium
252202	Linux Distros 未修補的弱點：CVE-2025-38388	Nessus	Misc.	2025/8/19	2025/9/4	medium
252202	Linux Distros のパッチ未適用の脆弱性: CVE-2025-38388	Nessus	Misc.	2025/8/19	2025/9/4	medium
252202	Linux Distros Unpatched Vulnerability : CVE-2025-38388	Nessus	Misc.	2025/8/19	2025/9/4	medium
243505	Amazon Linux 2023bpftool6.12、kernel6.12、kernel6.12-devel (ALAS2023-2025-1130)	Nessus	Amazon Linux Local Security Checks	2025/8/4	2025/9/11	high
243505	Amazon Linux 2023 : bpftool6.12, kernel6.12, kernel6.12-devel (ALAS2023-2025-1130)	Nessus	Amazon Linux Local Security Checks	2025/8/4	2025/9/11	high
243505	Amazon Linux 2023 bpftool6.12、kernel6.12、kernel6.12-devel (ALAS2023-2025-1130)	Nessus	Amazon Linux Local Security Checks	2025/8/4	2025/9/11	high
243505	Amazon Linux 2023bpftool6.12、kernel6.12、kernel6.12-develALAS2023-2025-1130	Nessus	Amazon Linux Local Security Checks	2025/8/4	2025/9/11	high

検出

プラグインの検索

medium

medium

medium

medium

high

high

high

high