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

  - xsk在 Tx 路徑中較早檢查 IFF_UP Xsk Tx 可透過 sendmsg() 或 poll() 系統呼叫觸發。
    這兩個路徑共用一個內含兩個功能健全檢查的通用函式 xsk_xmit() 呼叫。顯示兩個路徑的虛擬程式碼範例 __xsk_sendmsg() : xsk_poll(): if (unlikely(!xsk_is_bound(xs))) if (unlikely(!xsk_is_bound(xs))) return -ENXIO;傳回遮罩if (unlikely(need_wait)) (...) 傳回
    -EOPNOTSUPP; xsk_xmit() 標記 napi id (...) xsk_xmit() xsk_xmit(): if (不太可能 (!(xs->dev->flags & IFF_UP))) 傳回 -ENETDOWN if (不太可能 (!xs->tx)) 傳回 -ENOBUFS如上所見在 sendmsg() 中可在尚未啟動的介面上標記 napi id進而造成 NULL 指標解除參照 [31757.505631] 錯誤核心 NULL 指標解除參照位址0000000000000018 [31757.512710] # PF在核心模式中的監督讀取存取 [31757.517936] #PFerror_code(0x0000) - 不存在的頁面 [31757.523149] PGD 0 P4D 0 [31757.525726] Oops0000 [#1] PREEMPT SMP NOPTI [31757.530154] CPU26 PID
    95641 Commxdpsock 未受污染的 6.2.0-rc5+ #40 [31757.536871] 硬體名稱Intel Corporation S2600WFT/S2600WFT、BIOS SE5C620.86B.02.01.0008.031920191559 2019 年 3 月 19 日 [31757.547457] RIP
    0010:xsk_sendmsg+0xde/0x180 [31757.551799] 代碼00 75 a2 48 8b 00 a8 04 75 9b 84 d2 74 69 8b 85 14 01 00 00 85 c0 75 1b 48 8b 85 28 03 00 00 48 080 88 0 00 48 8b 40 20 <8b> 40 18 89 85 14 01 00 00 8b bd 14 01 00 00 81 ff 00 01 00 00 0f [31757.570840] RSP: 0018:ffffc90034f27dc0 EFLAGS: 00010246 [31757.576143] RAX: 0000000000000000 RBX: ffffc90034f27e18 RCX: 0000000000000000 [31757.583389] RDX: 0000000000000001 RSI: ffffc90034f27e18 RDI: ffff88984cf3c100 [31757.590631] RBP: ffff88984714a800 R08: ffff88984714a800 R09: 0000000000000000 [31757.597877] R10: 0000000000000001 R11: 0000000000000000 R12: 00000000fffffffa [31757.605123] R130000000000000000 R140000000000000003 R150000000000000000 [31757.612364] FS
    00007fb4c5931180(0000) GS:ffff88afdfa00000(0000) knlGS:0000000000000000 [31757.620571] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [31757.626406] CR2: 0000000000000018 CR3: 000000184b41c003 CR4:
    00000000007706e0 [31757.633648] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [31757.640894] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [31757.648139] PKRU:
    55555554 [31757.650894] 呼叫追踪[31757.653385] <TASK> [31757.655524] sock_sendmsg+0x8f/0xa0 [31757.659077] ? sockfd_lookup_light+0x12/0x70 [31757.663416] __sys_sendto+0xfc/0x170 [31757.667051] ? do_sched_setscheduler+0xdb/0x1b0 [31757.671658] __x64_sys_sendto+0x20/0x30 [31757.675557] do_syscall_64+0x38/0x90 [31757.679197] entry_SYSCALL_64_after_hwframe+0x72/0xdc [31757.687969] 程式碼8e f6 ff 44 8b 4c 24 2c 4c 844 2c 4c 20 41 89 c4 44 8b 54 24 28 48 8b 54 24 18 b8 2c 00 00 00 48 8b 74 24 10 8b 7c 24 08 0f 05 <48> 3d 00 f0 ff ff 77 3a 44 89 e7 48 89 44 b 88 f6 ff 48 [31757.707007] RSP
    002b:00007ffd49c73c70 EFLAGS: 00000293 ORIG_RAX: 000000000000002c [31757.714694] RAX: ffffffffffffffda RBX: 000055a996565380 RCX: 00007fb4c5727c16 [31757.721939] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000003 [31757.729184] RBP: 0000000000000040 R08: 0000000000000000 R09: 0000000000000000 [31757.736429] R100000000000000040 R110000000000000293 R120000000000000000 [31757.743673] R13
    0000000000000000 R140000000000000000 R150000000000000000 [31757.754940] </TASK> 若要修正此問題讓我們將 xsk_xmit 製作成一個函式來負責一般 Tx其中 RCU 會得到相應處理並移除功能健全檢查和 xs->zc 處理。將功能健全檢查填入 __xsk_sendmsg() 和 xsk_poll()。
    (CVE-2023-53240)

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

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

  - xsk检查 Tx 路径中较早的 IFF_UP 可通过 sendmsg() 或 poll() syscall 触发 Xsk Tx。
    这两个路径共享对通用函数 xsk_xmit() 的调用该函数内包含两个健全性检查。显示两个路径的伪代码示例__xsk_sendmsg() : xsk_poll() if (unlikely(!xsk_is_bound(xs))) if (unlikely(!xsk_is_bound(xs))) return -ENXIO;返回掩码if (unlikely(need_wait)) (...) 返回
    -EOPNOTSUPP xsk_xmit() 标记 napi id (...) xsk_xmit() xsk_xmit()if (unlikely(!(xs->dev->flags & IFF_UP))) return -ENETDOWN; if (unlikely(!xs->tx)) return -ENOBUFS如上所见在 sendmsg() 中可在未启动的界面上标记 napi id这将造成空指针取消引用 [31757.505631] BUG内核空指针取消引用地址0000000000000018 [31757.512710] # PF内核模式中的主管读取访问 [31757.517936] #PF: error_code(0x0000) - not-present 页面 [31757.523149] PGD 0 P4D 0 [31757.525726] Oops0000 [#1] PREEMPT SMP NOPTI [31757.530154] CPU26 PID
    95641 Commxdpsock 未受感染 6.2.0-rc5+ #40 [31757.536871] 硬件名称Intel Corporation S2600WFT/S2600WFT、BIOS SE5C620.86B.02.01.0008.031920191559 2019 年 3 月 19 日 [31757.547457] RIP
    0010:xsk_sendmsg+0xde/0x180 [31757.551799] Code00 75 a2 48 8b 00 a8 04 75 9b 84 d2 74 69 8b 85 14 01 00 00 85 c0 75 1b 48 8b 85 28 03 00 00 40 9 8b 0 0 0 00 48 8b 40 20 <8b> 40 18 89 85 14 01 00 00 8b bd 14 01 00 00 81 ff 00 01 00 00 0f [31757.570840] RSP: 0018:ffffc90034f27dc0 EFLAGS: 00010246 [31757.576143] RAX: 0000000000000000 RBX: ffffc90034f27e18 RCX: 0000000000000000 [31757.583389] RDX: 0000000000000001 RSI: ffffc90034f27e18 RDI: ffff88984cf3c100 [31757.590631] RBP: ffff88984714a800 R08: ffff88984714a800 R09: 0000000000000000 [31757.597877] R10: 0000000000000001 R11: 0000000000000000 R12: 00000000fffffffa [31757.605123] R130000000000000000 R140000000000000003 R150000000000000000 [31757.612364] FS:
    00007fb4c5931180(0000) GS:ffff88afdfa00000(0000) knlGS:0000000000000000 [31757.620571] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [31757.626406] CR2: 0000000000000018 CR3: 000000184b41c003 CR4:
    00000000007706e0 [31757.633648] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [31757.640894] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [31757.648139] PKRU:
    55555554 [31757.650894] 调用跟踪[31757.653385] <TASK> [31757.655524] sock_sendmsg+0x8f/0xa0 [31757.659077] ? sockfd_lookup_light+0x12/0x70 [31757.663416] __sys_sendto+0xfc/0x170 [31757.667051] ? do_sched_setscheduler+0xdb/0x1b0 [31757.671658] __x64_sys_sendto+0x20/0x30 [31757.675557] do_syscall_64+0x38/0x90 [31757.679197] entry_SYSCALL_64_after_hwframe+0x72/0xdc [31757.687969] 代码8e f6 ff 44 8b 4c 24 8b 2c 44 8b 4c 24 8b 2c 24 20 41 89 c4 44 8b 54 24 28 48 8b 54 24 18 b8 2c 00 00 00 48 8b 74 24 10 8b 7c 24 08 0f 05 <48> 3d 00 f0 ff ff 77 3a 44 89 e7 48 89 08 e2 b8 f6 ff 48 [31757.707007] RSP
    002b:00007ffd49c73c70 EFLAGS: 00000293 ORIG_RAX: 000000000000002c [31757.714694] RAX: ffffffffffffffda RBX: 000055a996565380 RCX: 00007fb4c5727c16 [31757.721939] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000003 [31757.729184] RBP: 0000000000000040 R08: 0000000000000000 R09: 0000000000000000 [31757.736429] R100000000000000040 R110000000000000293 R120000000000000000 [31757.743673] R13
    0000000000000000 R140000000000000000 R15: 0000000000000000 [31757.754940] </TASK> 要修复此问题让我们将 xsk_xmit 设为将负责通用 Tx的函数、对 RCU 进行相应处理并执行健全性检查和 xs->zc 处理。对 __xsk_sendmsg() 和 xsk_poll() 进行健全性检查。
    (CVE-2023-53240)

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

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

  - xskTx パスの中の IFF_UP をより早くチェックします Xsk Tx は、sendmsg() または poll() syscalls のいずれかで発生する可能性があります。
    これらの 2 つのパスは、内部に 2 つのサニティチェックがある共通関数 xsk_xmit() への呼び出しを共有します。2 つのパスを示す擬似コードの例 : __xsk_sendmsg() : xsk_poll(): if (unlimited(!xsk_is_bound(xs))) if (unlimited(!xsk_is_bound(xs))) return -ENXIO;マスクを返しますif (unlimited(need_wait)) (...) return
    -EOPNOTSUPP; xsk_xmit() mark napi id をマークします...xsk_xmit() xsk_xmit(): if (unlikely(!(xs->dev->flags & IFF_UP)) が -ENETDOWN; if 可能性が低い(!xs->tx) が -ENOBUFS を返します上で観察されているように、sendmsg() では、napi id が起動されないインターフェイスでマークされる可能性があり、これにより NULL ポインターデリファレンスが引き起こされます[31757.505631] バグカーネル NULL ポインターデリファレンス、アドレス: 000000000000001831757.512710# PFカーネルモードのsupervisor読み取りアクセス[31757.517936] #PFerror_code(0x0000) - not-present page [31757.523149] PGD 0 P4D 0 [31757.525726] Oops0000 [#1]、PREEMPT SMP NOPTI [31757.530154] CPU: 26 PID:
    95641 通信xdpsock 汚染されていない 6.2.0-rc5+ #40 [31757.536871] ハードウェア名Intel Corporation S2600WFT/S2600WFT、BIOS SE5C620.86B.02.01.0008.031920191559 03/19/2019[31757.547457RIP
    0010:xsk_sendmsg+0xde/0x180 [31757.551799] コード: 00 75 a2 48 8b 00 a8 04 75 9b 84 d2 74 69 8b 85 14 01 00 00 85 c0 75 1b 48 8b 85 28 03 00 00 48 0000000000000000000000000000 00 48 8b 40 20 <8b> 40 18 89 85 14 01 00 00 8b bd 14 01 00 00 81 ff 00 01 00 00 0f [31757.570840] RSP: 0018:ffffc90034f27dc0 EFLAGS: 00010246 [31757.576143] RAX: 0000000000000000 RBX: ffffc90034f27e18 RCX: 0000000000000000 [31757.583389] RDX: 0000000000000001 RSI: ffffc90034f27e18 RDI: ffff88984cf3c100 [31757.590631] RBP: ffff88984714a800 R08: ffff88984714a800 R09: 0000000000000000 [31757.597877] R10: 0000000000000001 R11: 0000000000000000 R12: 00000000fffffffa [31757.605123] R13: 000000000000000 R15R14:31757.612364000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    00007fb4c5931180(0000) GS:ffff88afdfa00000(0000) knlGS:0000000000000000 [31757.620571] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [31757.626406] CR2: 0000000000000018 CR3: 000000184b41c003 CR4:
    00000000007706e0 [31757.633648] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [31757.640894] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [31757.648139] PKRU:
    55555554 [31757.650894] Call Trace: [31757.653385] <TASK>31757.655524] sock_sendmsg+0x8f/0xa0 [31757.659077] ? sockfd_lookup_light+0x12/0x70 [31757.663416] __sys_sendto+0xfc/0x170 [31757.667051] ? do_sched_setscheduler+0xdb/0x1b0 [31757.671658] __x64_sys_sendto+0x20/0x30 [31757.675557] do_syscall_64+0x38/0x90 [31757.679197] entry_SYSCALL_64_after_hwframe+0x72/0xdc [31757.687969 ] コード8e f6 ff 44 8b 4c 24c 24c 24b 20 41 89 c4 44 8b 54 24 28 48 8b 54 24 18 b8 2c 00 00 00 48 8b 74 10 8b 7c 24 08 0f 05 <48> 3d 00 f0 ff ff 77 3a 44 89 e7 48 e 89 48 e4e 2480648 f6 ff 48 [31757.707007] RSP
    002b:00007ffd49c73c70 EFLAGS: 00000293 ORIG_RAX: 000000000000002c [31757.714694] RAX: ffffffffffffffda RBX: 000055a996565380 RCX: 00007fb4c5727c16 [31757.721939] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000003 [31757.729184] RBP: 0000000000000040 R08: 0000000000000000 R09: 0000000000000000 [31757.736429] R10: 000000000000040 R11: 0000000000000293 R1231757.743673: R130000000000000000000000000000000000000000000000000000000000000000000
     R14000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000_これの修正のため R15に、RCUがそれに沿って処理され、サニティチェックとxs->zc31757.754940処理を引き出します </TASK> 。__xsk_sendmsg() および xsk_poll() にサニティチェックを実装します。
    (CVE-2023-53240)

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

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

  - xsk: check IFF_UP earlier in Tx path Xsk Tx can be triggered via either sendmsg() or poll() syscalls.
    These two paths share a call to common function xsk_xmit() which has two sanity checks within. A pseudo     code example to show the two paths: __xsk_sendmsg() : xsk_poll(): if (unlikely(!xsk_is_bound(xs))) if     (unlikely(!xsk_is_bound(xs))) return -ENXIO; return mask; if (unlikely(need_wait)) (...) return
    -EOPNOTSUPP; xsk_xmit() mark napi id (...) xsk_xmit() xsk_xmit(): if (unlikely(!(xs->dev->flags &     IFF_UP))) return -ENETDOWN; if (unlikely(!xs->tx)) return -ENOBUFS; As it can be observed above, in     sendmsg() napi id can be marked on interface that was not brought up and this causes a NULL ptr     dereference: [31757.505631] BUG: kernel NULL pointer dereference, address: 0000000000000018 [31757.512710]     #PF: supervisor read access in kernel mode [31757.517936] #PF: error_code(0x0000) - not-present page     [31757.523149] PGD 0 P4D 0 [31757.525726] Oops: 0000 [#1] PREEMPT SMP NOPTI [31757.530154] CPU: 26 PID:
    95641 Comm: xdpsock Not tainted 6.2.0-rc5+ #40 [31757.536871] Hardware name: Intel Corporation     S2600WFT/S2600WFT, BIOS SE5C620.86B.02.01.0008.031920191559 03/19/2019 [31757.547457] RIP:
    0010:xsk_sendmsg+0xde/0x180 [31757.551799] Code: 00 75 a2 48 8b 00 a8 04 75 9b 84 d2 74 69 8b 85 14 01 00     00 85 c0 75 1b 48 8b 85 28 03 00 00 48 8b 80 98 00 00 00 48 8b 40 20 <8b> 40 18 89 85 14 01 00 00 8b bd 14     01 00 00 81 ff 00 01 00 00 0f [31757.570840] RSP: 0018:ffffc90034f27dc0 EFLAGS: 00010246 [31757.576143]     RAX: 0000000000000000 RBX: ffffc90034f27e18 RCX: 0000000000000000 [31757.583389] RDX: 0000000000000001     RSI: ffffc90034f27e18 RDI: ffff88984cf3c100 [31757.590631] RBP: ffff88984714a800 R08: ffff88984714a800     R09: 0000000000000000 [31757.597877] R10: 0000000000000001 R11: 0000000000000000 R12: 00000000fffffffa     [31757.605123] R13: 0000000000000000 R14: 0000000000000003 R15: 0000000000000000 [31757.612364] FS:
    00007fb4c5931180(0000) GS:ffff88afdfa00000(0000) knlGS:0000000000000000 [31757.620571] CS: 0010 DS: 0000     ES: 0000 CR0: 0000000080050033 [31757.626406] CR2: 0000000000000018 CR3: 000000184b41c003 CR4:
    00000000007706e0 [31757.633648] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000     [31757.640894] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [31757.648139] PKRU:
    55555554 [31757.650894] Call Trace: [31757.653385] <TASK> [31757.655524] sock_sendmsg+0x8f/0xa0     [31757.659077] ? sockfd_lookup_light+0x12/0x70 [31757.663416] __sys_sendto+0xfc/0x170 [31757.667051] ?     do_sched_setscheduler+0xdb/0x1b0 [31757.671658] __x64_sys_sendto+0x20/0x30 [31757.675557]     do_syscall_64+0x38/0x90 [31757.679197] entry_SYSCALL_64_after_hwframe+0x72/0xdc [31757.687969] Code: 8e f6     ff 44 8b 4c 24 2c 4c 8b 44 24 20 41 89 c4 44 8b 54 24 28 48 8b 54 24 18 b8 2c 00 00 00 48 8b 74 24 10 8b     7c 24 08 0f 05 <48> 3d 00 f0 ff ff 77 3a 44 89 e7 48 89 44 24 08 e8 b5 8e f6 ff 48 [31757.707007] RSP:
    002b:00007ffd49c73c70 EFLAGS: 00000293 ORIG_RAX: 000000000000002c [31757.714694] RAX: ffffffffffffffda     RBX: 000055a996565380 RCX: 00007fb4c5727c16 [31757.721939] RDX: 0000000000000000 RSI: 0000000000000000     RDI: 0000000000000003 [31757.729184] RBP: 0000000000000040 R08: 0000000000000000 R09: 0000000000000000     [31757.736429] R10: 0000000000000040 R11: 0000000000000293 R12: 0000000000000000 [31757.743673] R13:
    0000000000000000 R14: 0000000000000000 R15: 0000000000000000 [31757.754940] </TASK> To fix this, let's     make xsk_xmit a function that will be responsible for generic Tx, where RCU is handled accordingly and     pull out sanity checks and xs->zc handling. Populate sanity checks to __xsk_sendmsg() and xsk_poll().
    (CVE-2023-53240)

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

ID	Name	Product	Family	Published	Updated	Severity
265036	Linux Distros 未修補的弱點：CVE-2023-53240	Nessus	Misc.	9/16/2025	9/20/2025	medium
265036	Linux Distros 未修补的漏洞：CVE-2023-53240	Nessus	Misc.	9/16/2025	9/20/2025	medium
265036	Linux Distros のパッチ未適用の脆弱性: CVE-2023-53240	Nessus	Misc.	9/16/2025	9/20/2025	medium
265036	Linux Distros Unpatched Vulnerability : CVE-2023-53240	Nessus	Misc.	9/16/2025	9/20/2025	medium

Detections

Analytics

Plugins Search

medium

medium

medium

medium