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

  - kcsan避免 read_instrumented_memory() 中的 READ_ONCE() Haibo Li 報告無法處理虛擬位址的核心分頁要求ffffff802a0d8d7171 | 版記憶體中止資訊o ESR = 0x9600002121 | EC = 0x25DABT (目前 EL)、IL = 32 bitsts | SET = 0FnV = 0 0 | EA = 0, S1PTW = 0 0 | FSC = 0x21對齊錯誤資料中止資訊o ISV = 0, ISS = 0x0000002121 | CM = 0, WnR = 0 0 | swapper pgtable4k 頁面39 位元 VA pgdp=000000002835200000 | [ffffff802a0d8d71] pgd=180000005fbf9003、p4d=180000005fbf9003、| pud=180000005fbf9003, pmd=180000005fbe8003, pte=006800002a0d8707 |內部錯誤Oops 96000021 [#1] PREEMPT SMP |連結下列的模組 | CPU: 2 PID: 45 Comm: kworker/u8:2 未受污染 | 5.15.78-android13-8-g63561175bbda-dirty #1 | ... | pckcsan_setup_watchpoint+0x26c/0x6bc | lr
    kcsan_setup_watchpoint+0x88/0x6bc | sp ffffffc00ab4b7f0 | x29ffffffc00ab4b800 x28ffffff80294fe588 x270000000000000001 | x260000000000000019 x250000000000000001 x24ffffff80294fdb80 | x23
    000000000000000 x22ffffffc00a70fb68 x21ffffff802a0d8d71 | x200000000000000002 x190000000000000000 x18ffffffc00a9bd060 | x170000000000000001 x160000000000000000 x15ffffffc00a59f000 | x14
    0000000000000001 x130000000000000000 x12ffffffc00a70faa0 | x1100000000aaaaaaab x100000000000000054 x9ffffffc00839adf8 | x8 ffffffc009b4cf00 x7 0000000000000000 x6 0000000000000007 | x5
    0000000000000000 x4 0000000000000000 x3 ffffffc00a70fb70 | x2 0005ff802a0d8d71 x1 0000000000000000 x0 0000000000000000 |呼叫追踪| kcsan_setup_watchpoint+0x26c/0x6bc | __tsan_read2+0x1f0/0x234 | 版inflate_fast+0x498/0x750 | zlib_inflate+0x1304/0x2384 | __gunzip+0x3a0/0x45c | 版gunzip+0x20/0x30 | unpack_to_rootfs+0x2a8/0x3fc | do_populate_rootfs+0xe8/0x11c | async_run_entry_fn+0x58/0x1bc | process_one_work+0x3ec/0x738 | worker_thread+0x4c4/0x838 | kthread+0x20c/0x258 | ret_from_fork+0x10/0x20 | 版代碼b8bfc2a8 2a0803f7 14000007 d503249f (78bfc2a8) ) | ---[ end trace 613a943cb0a572b6 ]-------- 之所以會這樣是因為 e35123d83ee3 (arm64: lto: Enhanced READ_ONCE() to acquire when CONFIG_LTO=y) 以來的特定 arm64、READ_ONCE() 可能提升為無法在未對齊的位址上使用之完整不可部分完成的取得指示。修正方法是避免在 read_instrumented_memory() 中使用 READ_ONCE()並藉由轉換為適當的 volatile 類型來強制編譯器執行所需的存取。就產生的程式碼而言這目前僅影響不使用預設 READ_ONCE() 實作的架構。唯一的問題是雖然在大多數架構上最多機器字大小的純文字載入仍應為不可部分但我們無法保證存取本身的不可部分完成性 (事實上預設 READ_ONCE() 仍依賴其本身)。 (CVE-2023-53742)

請注意，Nessus 的判定取決於廠商所報告的套件是否存在。

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

  - kcsanHaibo Li 报告的 read_instrumented_memory() 中避免 READ_ONCE() | 无法处理虚拟地址处的内核分页请求| ffffff802a0d8d7171 |内存中止信息| ESR = 0x9600002121 | | EC = 0x25DABT当前 ELIL = 32 bitsts | 0 | SET = 0FnV = 0 0 0 | EA = 0S1PTW = 0 0 | FSC = 0x21对齐错误 |数据中止信息o | ISV = 0ISS = 0x0000002121 0 | CM = 0WnR = 0 0 swapper pgtable4k 页面39 位 VA pgdp=000000002835200000 | | swapper [ffffff802a0d8d71] pgd=180000005fbf9003、p4d=180000005fbf9003、| pud=180000005fbf9003、 pmd=180000005fbe8003、[] | | [] 、[] 、 pte=006800002a0d8707 内部错误Oops96000021 [#1] PREEMPT SMP | |中链接的模块| | CPU2 PID45 Commkworker/u8:2 未受感染 | 5.15.78-android13-8-g63561175bbda-dirty #1 | | ... | pc kcsan_setup_watchpoint+0x26c/0x6bc | lr
    | kcsan_setup_watchpoint+0x88/0x6bc | | sp ffffffc00ab4b7f0 | sp x29ffffffc00ab4b800 x28ffffff80294fe588 x270000000000000001 | x260000000000000019 x250000000000000001 x24ffffff80294fdb80 | x23
    0000000000000000 x22ffffffc00a70fb68 x21ffffff802a0d8d71 | x200000000000000002 x190000000000000000 x18ffffffc00a9bd060 | x170000000000000001 x160000000000000000 x15ffffffc00a59f000 | x14
    ffffffc00a70faa0 | 0000000000000001 x130000000000000000 x12 | x1100000000aaaaaaab x100000000000000054 x9 : ffffffc00839adf8 | | x8 : ffffffc009b4cf00 x7 : 0000000000000000 x6 : 0000000000000007 | x5
    0000000000000000 x4 : 0000000000000000 x3 : ffffffc00a70fb70 | | x2 0005ff802a0d8d71 x1 0000000000000000 x0 0000000000000000 |调用跟踪| kcsan_setup_watchpoint+0x26c/0x6bc | | __tsan_read2+0x1f0/0x234 | | inflate_fast+0x498/0x750 | | zlib_inflate+0x1304/0x2384 | __gunzip+0x3a0/0x45c | |gunzip+0x20/0x30| | unpack_to_rootfs+0x2a8/0x3fc | | do_populate_rootfs+0xe8/0x11c | | async_run_entry_fn+0x58/0x1bc | | process_one_work+0x3ec/0x738 | work_thread+0x4c4/0x838 | | kthread+0x20c/0x258 | | ret_from_fork+0x10/0x20 |代码b8bfc2a8 2a0803f7 14000007 d503249f (78bfc2a8) ) | ---[ end trace 613a943cb0a572b6 ]----- 其原因是在 e35123d83ee3 之后的某些 arm64 配置中arm64lto当 CONFIG_LTO=y 时加强 READ_ONCE() 进行采集READ_ONCE() 可能会提升为无法在未对齐地址上使用的完整原子获取指令。修复此问题的方法是避免使用 read_instrumented_memory() 中的 READ_ONCE()而只需强制编译器通过转换为适当的易失性类型来执行所需的访问。就生成的代码而言此问题当前仅影响不使用默认 READ_ONCE() 实现的架构。唯一的不足是无法保证访问本身的原子性尽管在大多数架构上符合计算机字大小的普通加载仍应具有原子性默认 READ_ONCE() 仍然依赖于自身这一事实。 (CVE-2023-53742)

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

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

  - kcsanread_instrumented_memory() での READ_ONCE() を回避します Haibo Li の報告 |カーネルページングリクエストを仮想アドレスで処理できません | ffffff802a0d8d7171 | Mem abort info:o: | ESR = 0x9600002121 | EC = 0x25DABT現在の EL、IL = 32 bitsts | SET = 0, FnV = 0 0 | EA = 0, S1PTW = 0 0 | FSC = 0x21アライメント違反 |データ中止 info:o: | ISV = 0, ISS = 0x0000002121 | CM = 0、WnR = 0 0 | swapper pgtable4k ページ、39 ビット VA、 pgdp=000000002835200000 | [ffffff802a0d8d71] pgd=180000005fbf9003、p4d=180000005fbf9003、| pud=180000005fbf9003、 pmd=180000005fbe8003、 pte=006800002a0d8707 |内部エラーOops96000021 [#1] PREEMPT SMP |リンクされているモジュール| CPU2 PID45 Commmkworker/u8:2 汚染されていない | 5.15.78-android13-8-g63561175bbda-dirty #1 | ... | pckcsan_setup_watchpoint+0x26c/0x6bc | lr
    kcsan_setup_watchpoint+0x88/0x6bc | sp : fffffc00ab4b7f0 | x29: fffffc00ab4b800 x28: ffffff80294fe588 x27: 0000000000000001 | x26: 000000000000019 x25: 0000000000000001 x24: ffffff80294fdb80 | x23
    0000000000000000 x22: fffffc00a70fb68 x21: ffffff802a0d8d71 | x20: 000000000000002 x19: 0000000000000000 x18: fffffc00a9bd060 | x17: 000000000000001 x16: 0000000000000000 x15: ffffffc00a59f000 | x14
    0000000000000001 x13: 0000000000000000 x12: fffffc00a70faa0 | x11: 00000000aaaaaaab x10: 0000000000000054 x9: ffffffc00839adf8 | x8 : ffffffc009b4cf00 x7 : 0000000000000000 x6 : 000000000000000000000000000000000000000000000000000000000000000000000000 x5
    0000000000000000 x4 : 0000000000000000 x3 : fffffc00a70fb70 | x2 : 0005ff802a0d8d71 x1 : 000000000000000 x0 : 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 trace: | kcsan_setup_watchpoint+0x26c/0x6bc | __tsan_read2+0x1f0/0x234 | inflate_fast+0x498/0x750 | zlib_inflate+0x1304/0x2384 | __ Gunzip+0x3a0/0x45c | Gunzip+0x20/0x30 | unpack_to_rootfs+0x2a8/0x3fc | do_populate_rootfs+0xe8/0x11c | async_run_entry_fn+0x58/0x1bc | process_one_work+0x3ec/0x738 | worker_thread+0x4c4/0x838 | kthread+0x20c/0x258 | ret_from_fork+0x10/0x20 |コードb8bfc2a8 2a0803f7 14000007 d503249f78bfc2a8) | ---[ end trace 613a943cb0a572b6 ]----- :アラインされていないアドレスで使用できない完全アトミック取得命令。read_instrumented_memory() の READ_ONCE() を回避し、適切な volatile 型へキャストして必要なアクセスを行うようにコンパイラに単純に強制することで、これを修正します。生成コードに関しては、現在、デフォルトの READ_ONCE() 実装を使用しないアーキテクチャのみに影響を与えます。唯一の弱点は、アクセス自体の原子性が保証されていないことです。ただし、ほとんどのアーキテクチャでは、マシンワードサイズへのプレーンロードは依然としてアトミックである必要があります事実、デフォルトの READ_ONCE() は依然として自身に依存しています。CVE-2023-53742

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

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

  - kcsan: Avoid READ_ONCE() in read_instrumented_memory() Haibo Li reported: | Unable to handle kernel paging     request at virtual address | ffffff802a0d8d7171 | Mem abort info:o: | ESR = 0x9600002121 | EC = 0x25: DABT     (current EL), IL = 32 bitsts | SET = 0, FnV = 0 0 | EA = 0, S1PTW = 0 0 | FSC = 0x21: alignment fault |     Data abort info:o: | ISV = 0, ISS = 0x0000002121 | CM = 0, WnR = 0 0 | swapper pgtable: 4k pages, 39-bit     VAs, pgdp=000000002835200000 | [ffffff802a0d8d71] pgd=180000005fbf9003, p4d=180000005fbf9003, |     pud=180000005fbf9003, pmd=180000005fbe8003, pte=006800002a0d8707 | Internal error: Oops: 96000021 [#1]     PREEMPT SMP | Modules linked in: | CPU: 2 PID: 45 Comm: kworker/u8:2 Not tainted |     5.15.78-android13-8-g63561175bbda-dirty #1 | ... | pc : kcsan_setup_watchpoint+0x26c/0x6bc | lr :
    kcsan_setup_watchpoint+0x88/0x6bc | sp : ffffffc00ab4b7f0 | x29: ffffffc00ab4b800 x28: ffffff80294fe588     x27: 0000000000000001 | x26: 0000000000000019 x25: 0000000000000001 x24: ffffff80294fdb80 | x23:
    0000000000000000 x22: ffffffc00a70fb68 x21: ffffff802a0d8d71 | x20: 0000000000000002 x19: 0000000000000000     x18: ffffffc00a9bd060 | x17: 0000000000000001 x16: 0000000000000000 x15: ffffffc00a59f000 | x14:
    0000000000000001 x13: 0000000000000000 x12: ffffffc00a70faa0 | x11: 00000000aaaaaaab x10: 0000000000000054     x9 : ffffffc00839adf8 | x8 : ffffffc009b4cf00 x7 : 0000000000000000 x6 : 0000000000000007 | x5 :
    0000000000000000 x4 : 0000000000000000 x3 : ffffffc00a70fb70 | x2 : 0005ff802a0d8d71 x1 : 0000000000000000     x0 : 0000000000000000 | Call trace: | kcsan_setup_watchpoint+0x26c/0x6bc | __tsan_read2+0x1f0/0x234 |     inflate_fast+0x498/0x750 | zlib_inflate+0x1304/0x2384 | __gunzip+0x3a0/0x45c | gunzip+0x20/0x30 |     unpack_to_rootfs+0x2a8/0x3fc | do_populate_rootfs+0xe8/0x11c | async_run_entry_fn+0x58/0x1bc |     process_one_work+0x3ec/0x738 | worker_thread+0x4c4/0x838 | kthread+0x20c/0x258 | ret_from_fork+0x10/0x20 |     Code: b8bfc2a8 2a0803f7 14000007 d503249f (78bfc2a8) ) | ---[ end trace 613a943cb0a572b6 ]----- The reason     for this is that on certain arm64 configuration since e35123d83ee3 (arm64: lto: Strengthen READ_ONCE() to     acquire when CONFIG_LTO=y), READ_ONCE() may be promoted to a full atomic acquire instruction which cannot     be used on unaligned addresses. Fix it by avoiding READ_ONCE() in read_instrumented_memory(), and simply     forcing the compiler to do the required access by casting to the appropriate volatile type. In terms of     generated code this currently only affects architectures that do not use the default READ_ONCE()     implementation. The only downside is that we are not guaranteed atomicity of the access itself, although     on most architectures a plain load up to machine word size should still be atomic (a fact the default     READ_ONCE() still relies on itself). (CVE-2023-53742)

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

ID	Name	Product	Family	Published	Updated	Severity
277645	Linux Distros 未修補的弱點：CVE-2023-53742	Nessus	Misc.	12/8/2025	9/2/2026	high
277645	Linux Distros 未修补的漏洞：CVE-2023-53742	Nessus	Misc.	12/8/2025	9/2/2026	high
277645	Linux Distros のパッチ未適用の脆弱性: CVE-2023-53742	Nessus	Misc.	12/8/2025	9/2/2026	high
277645	Linux Distros Unpatched Vulnerability : CVE-2023-53742	Nessus	Misc.	12/8/2025	9/2/2026	high

Detections

Analytics

Plugins Search

high

high

high

high