遠端 Redhat Enterprise Linux 9 主機上安裝的多個套件受到 RHSA-2022:8267 公告中提及的多個弱點影響。

    核心套件中包含 Linux 核心，後者是任何 Linux 作業系統的核心。

    安全性修正：

    * 路徑外攻擊者可插入資料或終止受害者的 TCP 工作階段 (CVE-2020-36516)

    * 函式 sco_sock_sendmsg() 中的釋放後使用弱點 (CVE-2021-3640)

    * smb2_ioctl_query_info NULL 指標解除參照 (CVE-2022-0168)

    * 回寫期間 udf_expand_file_adinicbdue() 中發生 NULL 指標解除參照 (CVE-2022-0617)

    * 因 DMA_FROM_DEVICE 的 swiotlb 資訊洩漏 (CVE-2022-0854)

    * nft_do_chain 中堆疊上的未初始化暫存器可造成核心指標洩漏至 UM (CVE-2022-1016)

    * snd_pcm_hw_free 中的爭用情形會導致釋放後使用 (CVE-2022-1048)

    * 在損毀的影像上掛載並操作時ext4 中發生釋放後使用和記憶體錯誤 (CVE-2022-1184)

    * drm_setmaster_ioctl 和 drm_mode_getresources 之間的並行釋放後使用 (CVE-2022-1280)

    * pfkey_register 中有核心資訊洩漏問題 (CVE-2022-1353)

    * ath9k_htc_probe_device() 中的釋放後使用問題可造成權限提升 (CVE-2022-1679)

    * x86_emulate_insn 中的 NULL 指標解除參照可能導致 DoS (CVE-2022-1852)

    * fanotify 誤用可導致釋放後使用的 fd_install() (CVE-2022-1998)

    * nf_tables 跨表格潛在釋放後使用可能導致本機權限提升 (CVE-2022-2586)

    * 整數反向溢位導致 reserve_sfa_size() 中的超出邊界寫入 (CVE-2022-2639)

    * packet_recvmsg() 中的 slab 超出邊界存取 (CVE-2022-20368)

    * 不完整的多核心共用緩衝區清理 (即 SBDR) (CVE-2022-21123)

    * 微架構填補緩衝區 (即 SBDS) 的不完整清理 (CVE-2022-21125)

    * 特定特殊暫存器寫入作業中的不完整清理 (即 DRPW) (CVE-2022-21166)

    * 可使用除錯程式將零寫入所選位置 (CVE-2022-21499)

    * AMDRetBleed 任意推測程式碼執行及傳回指示 (CVE-2022-23816、 CVE-2022-29900)

    * AMD分支類型混淆 (非 retbleed) (CVE-2022-23825)

    * IntelPost-barrier 傳回堆疊緩衝區預測 (CVE-2022-26373)

    * drivers/net/can/usb/ems_usb.c 中的 ems_usb_start_xmit 中存在雙重釋放 (CVE-2022-28390)

    * SUNRPC 子系統中的釋放後使用 (CVE-2022-28893)

    * 不當更新 net/sched/cls_u32.c 中的參照計數所導致的釋放後使用 (CVE-2022-29581)

    * IntelRetBleed 任意推測程式碼執行及傳回指示 (CVE-2022-29901)

    * net/netfilter/nfnetlink_queue.c 中 nfqnl_mangle 中的 DoS (CVE-2022-36946)

    * nf_tables 不允許系結至已系結鏈結 (CVE-2022-39190)

    * nfs_atomic_open() 傳回未初始化的資料而非 ENOTDIR (CVE-2022-24448)

    如需安全性問題的詳細資料，包括影響、CVSS 評分、致謝及其他相關資訊，請參閱〈參照〉一節列出的 CVE 頁面。

    其他變更：

    如需有關此發行版本的詳細變更資訊，請參閱可從「參考資料」一節連結的 Red Hat Enterprise Linux 9.1 版本資訊。

Tenable 已直接從 Red Hat Enterprise Linux 安全公告擷取前置描述區塊。

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

远程 Redhat Enterprise Linux 9 主机上安装的程序包受到 RHSA-2022:8267 公告中提及的多个漏洞影响。

    内核程序包中包含 Linux 内核，后者是任何 Linux 操作系统的核心。

    安全修复：

    * 路径外攻击者可注入数据或终止受害者的 TCP 会话 (CVE-2020-36516)

    * 函数 sco_sock_sendmsg() 中存在释放后使用漏洞 (CVE-2021-3640)

    * smb2_ioctl_query_info 空指针取消引用 (CVE-2022-0168)

    * 回写期间 udf_expand_file_adinicb CPU 中发生空指针取消引用 (CVE-2022-0617)

    * DMA_FROM_DEVICE 的 swiotlb 信息泄漏 (CVE-2022-0854)

    * nft_do_chain 中堆栈上未初始化的寄存器可导致内核指针泄漏给 UM (CVE-2022-1016)

    * snd_pcm_hw_free 中的争用条件导致释放后使用 (CVE-2022-1048)

    * 装载损坏的图像并进行操作时 ext4 中存在释放后使用和内存错误 (CVE-2022-1184)

    * drm_setmaster_ioctl 与 drm_mode_getresources 之间的并发释放后使用 (CVE-2022-1280)

    * pfkey_register 中的内核信息泄漏问题 (CVE-2022-1353)

    * ath9k_htc_probe_device() 中的释放后使用可导致权限升级 (CVE-2022-1679)

    * x86_emulate_insn 中的空指针取消引用可能导致 DoSCVE-2022-1852

    * fanotify 滥用 fd_install() 可导致释放后使用 (CVE-2022-1998)

    * nf_tables 跨表潜在的释放后使用可能导致本地权限升级 (CVE-2022-2586)

    * 整数下溢导致 reserve_sfa_size() 中的越界写入 (CVE-2022-2639)

    * packet_recvmsg() 中的 slab 越界访问 (CVE-2022-20368)

    * 多核心共享缓冲区的不完整清理也称为 SBDRCVE-2022-21123

    * 微架构填充缓冲区的不完整清理也称为 SBDS (CVE-2022-21125)

    * 特定的特殊寄存器写入操作中的清理不完整又称为 DRPW (CVE-2022-21166)

    * 可以使用调试程序将零写入所选位置 (CVE-2022-21499)

    * AMD通过返回指令的 RetBleed 任意推测代码执行CVE-2022-23816、 CVE-2022-29900

    * AMD分支类型混淆non-retbleed(CVE-2022-23825)

    * IntelPost-barrier 返回堆栈缓冲区预测 (CVE-2022-26373)

    * drivers/net/can/usb/ems_usb.c 中 ems_usb_start_xmit 中存在的双重释放 (CVE-2022-28390)

    * SUNRPC 子系统中的释放后使用 (CVE-2022-28893)

    * 由于未正确更新 net/sched/cls_u32.c 中的引用计数导致释放后使用 (CVE-2022-29581)

    * IntelRetBleed 含返回指令的任意推测代码执行 (CVE-2022-29901)

    * net/netfilter/nfnetlink_queue.c 中的 nfqnl_mangle 中的 DoS (CVE-2022-36946)

    * nf_tables 不允许绑定到已绑定的链 (CVE-2022-39190)

    * nfs_atomic_open() 返回未初始化的数据而不是 ENOTDIR (CVE-2022-24448)

    有关上述安全问题的更多详细信息，包括其影响、CVSS 得分、致谢，以及其他相关信息，请参阅列于“参考”部分的 CVE 页面。

    其他变更：

    如需有关此发行版本的详细变更信息，请参阅可从“参考”部分链接的 Red Hat Enterprise Linux 9.1 版本说明。

Tenable 已直接从 Red Hat Enterprise Linux 安全公告中提取上述描述块。

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

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

  - net保留 skb_unclone_keeptruesize() 中的 skb_end_offset() syzbot 發現在 skb_try_coalesce() 中觸發有名之 WARN_ON_ONCE(delta < len) 的其他方法 [1] 我能夠從根本造成 kfence 的問題。
    當 kfence 處於作用中時下列宣告不再為 true int size = xxxx; void *ptr1 = kmalloc(size, gfp); void *ptr2 = kmalloc(size, gfp); if (ptr1 && ptr2) ASSERT(ksize(ptr1) == ksize(ptr2));
    我們嘗試在受到責備的提交中修正這些問題但忘記了 TCP 可能在使用 skb_unclone_keeptruesize() 後移動資料特別是來自 tcp_retrans_try_collapse() 的資料。因此我們不僅需要保持相同的 skb->truesize 值我們也需要確保 TCP 不會填入 pskb_expand_head() 能夠從 addr = kmalloc(...) (隨後是 ksize(addr) 分割) 取得的新 tailroom skb_unclone_keeptruesize() 分成兩部分1) 內嵌 skb_unclone_keeptruesize() 針對一般情況 (未復制 skb 時)。 2) 「慢速路徑」超出行 __skb_unclone_keeptruesize()。警告 CPU1 PID
    6490 at net/core/skbuff.c:5295 skb_try_coalesce+0x1235/0x1560 net/core/skbuff.c:5295 連結的模組
    CPU1 PID6490 Commsyz-executor161 未受污染 5.17.0-rc4-syzkaller-00229-g4f12b742eb2b #0 硬體名稱 Google Google Compute Engine/Google Compute Engine、BIOS Google 2011 年 1 月 1 日 RIP
    0010:skb_try_coalesce+0x1235/0x1560 net/core/skbuff.c:5295 程式碼 bf 01 00 00 00 0f b7 c0 89 c6 89 44 24 20 e8 62 24 4e fa 8b 44 24 20 83 e8 01 0f 85 e5 f0 ff ff e9 87 f4 ff ff e8 cb 20 4e fa <0f> 0b e9 06 f9 ff ff e8 af b2 95 fa e9 69 f0 ff ff e8 95 b2 95 fa RSP0018:ffffc900063af268 EFLAGS00010293 RAX
    0000000000000000 RBX: 00000000ffffffd5 RCX: 0000000000000000 RDX: ffff88806fc05700 RSI: ffffffff872abd55 RDI: 0000000000000003 RBP: ffff88806e675500 R08: 00000000ffffffd5 R09: 0000000000000000 R10:
     R11ffffffff872ab659  : 0000000000000000 R12: ffff88806dd554e8 R13: ffff88806dd9bac0 R14: ffff88806dd9a2c0 R15: 0000000000000155 FS: 00007f18014f9700(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020002000 CR3: 000000006be7a000 CR4: 0000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 00000000000000000 DR30: 000000000 DR3: 000000000000000 DR30: 000000060
    00000000ffffe0ff0 DR7: 0000000000000400 呼叫追踪 <TASK> tcp_try_coalesce net/ipv4/tcp_input.c:4651 [inline] tcp_try_coalesce+0x393/0x920 net/ipv4/tcp_input.c:4630 tcp_queue_rcv+0x8/tcp_queue_rcv+0x8/tcp_xinput0rcv+0x8/tcp_xinput0rcv+0x8/tcp_xinput6: tcp_data_queue+0x11fd/0x4bb0 net/ipv4/tcp_input.c:5025 tcp_rcv_established+0x81e/0x1ff0 net/ipv4/tcp_input.c:5947 tcp_v4_do_rcv+0x65e/0x980 net/ipv4/tcp_ipv4.c:1719 sk_backlog_rcvinclude/backlog_rcv。 :1037 [內嵌] __release_sock+0x134/0x3b0 net/core/sock.c:2779 release_sock+0x54/0x1b0 net/core/sock.c:3311 sk_wait_data+0x177/0x450 net/core/sock.c:2821 tcp_recvmsg_locked+0xe28 /0x1fd0 net/ipv4/tcp.c:2457 tcp_recvmsg+0x137/0x610 net/ipv4/tcp.c:2572 inet_recvmsg+0x11b/0x5e0 net/ipv4/af_inet.c:850 sock_recvmsg_nosec net/socket.c:948 [內嵌] sock_recvmsg net/socket.c:966 [內嵌] sock_recvmsg net/socket.c:962 [內嵌]
    ____sys_recvmsg+0x2c4/0x600 net/socket.c:2632 ___sys_recvmsg+0x127/0x200 net/socket.c:2674
    __sys_recvmsg+0xe2/0x1a0 net/socket.c:2704 do_syscall_x64 arch/x86/entry/common.c:50 [內嵌] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae (CVE-2022-49142)

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

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

  - net保留 skb_unclone_keeptruesize() 中的 skb_end_offset() syzbot 发现另一种方式可在 skb_try_coalesce() 中触发声名远播的 WARN_ON_ONCE(delta < len) [1] 我能够根除 kfence 的问题。
    当 kfence 运行时以下断言不再正确 int size = xxxx void *ptr1 = kmalloc(size, gfp); void *ptr2 = kmalloc(size, gfp); if (ptr1 && ptr2) ASSERT(ksize(ptr1) == ksize(ptr2));
    我们尝试在受到阻止的提交中修复这些问题但是忘记了TCP 可能在使用了 skb_unclone_keeptruesize() 之后移动了数据尤其是 tcp_retrans_try_collapse() 中的数据。因此我们不仅需要保持相同的 skb->truesize 值还需要确保 TCP 不会填充 pskb_expand_head() 从 addr = kmalloc(...) 后跟 ksize(addr) 获得的新 tailroom。 skb_unclone_keeptruesize() 拆分为两部分1) 当未克隆 skb 时通常情况的内联 skb_unclone_keeptruesize()。 2) “慢速路径”的 __skb_unclone_keeptruesize() 不一致。警告CPU1 PID
    6490 at net/core/skbuff.c:5295 skb_try_coalesce+0x1235/0x1560 net/core/skbuff.c:5295 模块中有链接
    CPU1 PID6490 Commsyz-executor161 Not tainted 5.17.0-rc4-syzkaller-00229-g4f12b742eb2b #0 Hardware nameGoogle Google Compute Engine/Google Compute EngineBIOS Google 01/01/2011 RIP
    0010:skb_try_coalesce+0x1235/0x1560 net/core/skbuff.c:5295 代码 bf 01 00 00 00 0f b7 c0 89 c6 89 44 24 20 e8 62 24 4e fa 8b 44 24 20 83 e8 01 0f 85 e5 f0 ff ff ff e9 87 f4 ff ff e8 cb 20 4e fa <0f> 0b e9 06 f9 ff ff e8 af b2 95 fa e9 69 f0 ff ff e8 95 b2 95 fa RSP: 0018:ffffc900063af268 EFLAGS: 00010293 RAX
    0000000000000000 RBX: 00000000ffffffd5 RCX: 0000000000000000 RDX: ffff88806fc05700 RSI: ffffffff872abd55 RDI: 0000000000000003 RBP: ffff88806e675500 R08: 00000000ffffffd5 R09: 0000000000000000 R10:
     R11ffffffff872ab659  : 0000000000000000 R12: ffff88806dd554e8 R13: ffff88806dd9bac0 R14: ffff88806dd9a2c0 R15: 0000000000000155 FS: 00007f18014f9700(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020002000 CR3: 000000006be7a000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3:000000DR000000DR000000DR00000000000000
    00000000fffe0ff0 DR7: 0000000000000400 调用跟踪 <TASK> tcp_try_coalesce net/ipv4/tcp_input.c:4651 [inline] tcp_try_coalesce+0x393/0x920 net/ipv4/tcp_input.c:4630 tcp_queue_rcv+0x8a010ipxinput.c:4630 tcp_queue_rcv+0x8a010ipxinput.490ipx6c tcp_data_queue+0x11fd/0x4bb0 net/ipv4/tcp_input.c:5025 tcp_rcv_established+0x81e/0x1ff0 net/ipv4/tcp_input.c:5947 tcp_v4_do_rcv+0x65e/0x980 net/ipv4/tcp_ipv4.c:1719 sk_backlog_srch/include :1037 [inline] __release_sock+0x134/0x3b0 net/core/sock.c:2779 release_sock+0x54/0x1b0 net/core/sock.c:3311 sk_wait_data+0x177/0x450 net/core/sock.c:2821 tcp_recvmsg_locked+0xe28 /0x1fd0 net/ipv4/tcp.c:2457 tcp_recvmsg+0x137/0x610 net/ipv4/tcp.c:2572 inet_recvmsg+0x11b/0x5e0 net/ipv4/af_inet.c:850 sock_recvmsg_nosec net/socket.c:948 [内联] sock_recvmsg net/socket.c:966 [内联] sock_recvmsg net/socket.c:962 [内联]
    ____sys_recvmsg+0x2c4/0x600 net/socket.c:2632 ___sys_recvmsg+0x127/0x200 net/socket.c:2674
    __sys_recvmsg+0xe2/0x1a0 net/socket.c:2704 do_syscall_x64 arch/x86/entry/common.c:50 [内联] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae (CVE-2022-49142)

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

リモート Redhat Enterprise Linux 9 ホストに、RHSA-2022:8267 アドバイザリに記載されている複数の脆弱性の影響を受けるパッケージがインストールされています。

    カーネルパッケージには、Linux オペレーティングシステムのコアである Linux カーネルが含まれています。

    セキュリティ修正プログラム:

    * オフパス攻撃者がデータを注入するか、被害者の TCP セッションを終了させる可能性がありますCVE-2020-36516

    * 関数 sco_sock_sendmsg() での use-after-free の脆弱性CVE-2021-3640

    * smb2_ioctl_query_info NULL ポインターデリファレンスCVE-2022-0168

    * writeback 中の udf_expand_file_adinicbdue() における NULL ポインターデリファレンスCVE-2022-0617

    * DMA_FROM_DEVICE による swiotlb 情報漏洩CVE-2022-0854

    * nft_do_chain のスタック上の初期化されていないレジスターが、UM へのカーネルポインター漏洩を引き起こす可能性がありますCVE-2022-1016

    * use-after-free につながる snd_pcm_hw_free の競合状態CVE-2022-1048

    * 破損したイメージをマウントし操作する際の ext4 における use-after-free およびメモリエラーCVE-2022-1184

    * drm_setmaster_ioctl と drm_mode_getresources の間の同時実行 use-after-freeCVE-2022-1280

    * pfkey_register のカーネル情報漏洩の問題CVE-2022-1353

    * ath9k_htc_probe_device() の use-after-free は、権限昇格を引き起こす可能性がありますCVE-2022-1679

    * x86_emulate_insn の NULL ポインターデリファレンスにより、DoS が引き起こされる可能性がありますCVE-2022-1852

    * fanotify が fd_install() を誤って使用します。これにより、use-after-free が引き起こされる可能性がありますCVE-2022-1998

    * nf_tables のクロステーブルにおける潜在的な use-after-free により、ローカルの権限昇格が発生する可能性がありますCVE-2022-2586

    * 整数アンダーフローにより、 reserve_sfa_size() での領域外の書き込みが引き起こされますCVE-2022-2639

    * packet_recvmsg() での slab-out-of-bounds アクセスCVE-2022-20368

    * マルチコア共有バッファ別名 SBDR の不完全なクリーンアップCVE-2022-21123

    * マイクロアーキテクチャフィルバッファ別名 SBDSの不完全なクリーンアップCVE-2022-21125

    * 特定の特殊なレジスター書き込み操作別名 DRPWで不完全なクリーンアップCVE-2022-21166

    * デバッガーを使用して、選択したロケーションにゼロを書き込むことが可能ですCVE-2022-21499

    * AMDReturn 命令による任意の投機的コードの実行CVE-2022-23816、 CVE-2022-29900

    * AMDブランチの型の取り違えnon-retbleedCVE-2022-23825

    * IntelPost-barrier Return Stack Buffer PredictionsCVE-2022-26373

    * drivers/net/can/usb/ems_usb.c の ems_usb_start_xmit における二重解放CVE-2022-28390

    * SUNRPC サブシステムでの use-after-freeCVE-2022-28893

    * net/sched/cls_u32.c の参照カウントの不適切な更新による use-after-freeCVE-2022-29581

    * IntelReturn 命令による RetBleed の任意の投機的コードの実行CVE-2022-29901

    * net/netfilter/nfnetlink_queue.c の nfqnl_mangle での DoSCVE-2022-36946

    * nf_tables は、すでにバインドされたチェーンへのバインドを許可しませんCVE-2022-39190

    * nfs_atomic_open() は、ENOTDIR の代わりに、初期化されていないデータを返しますCVE-2022-24448]

    影響、CVSS スコア、謝辞、その他の関連情報を含むセキュリティ問題の詳細については、「参照」セクションに記載されている CVE のページを参照してください。

    追加の変更:

    このリリースの変更に関する詳細については、「参照」セクションからリンクされている Red Hat Enterprise Linux 9.1 リリースノートを参照してください。

Tenable は、前述の記述ブロックを Red Hat Enterprise Linux セキュリティアドバイザリから直接抽出しています。

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

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

  - netskb_unclone_keeptruesize() の skb_end_offset() を保持します syzbot は skb_try_coalesce() の悪名高い WARN_ON_ONCE(delta < len) を発生させる別の方法を見つけました [1] kfence の問題を root 引き起こすことができました。
    kfence が動作しているとき、次のアサーションはもはや真ではありません int size = xxxx; void *ptr1 = kmalloc(size, gfp); void *ptr2 = kmalloc(size, gfp); if (ptr1 && ptr2) ASSERT(ksize(ptr1) == ksize(ptr2));
    責任のあるコミットでこれらの問題を修正しようとしましたが、特に tcp_retrans_try_collapse() から、skb_unclone_keeptruesize() が使用された後に TCP がデータをシフトしている可能性があることを発見しました。そのため、同じ skb->truesize の値を維持するだけでなく、TCP が新しいテールルームを満たさないようにする必要もあります。pskb_expand_head() は、ksize(addr) 分割が後に続く addr = kmalloc(...) から取得できました。 skb_unclone_keeptruesize() を 2 つの部分に分割します 1) skb が複製されない一般的なケースのインライン skb_unclone_keeptruesize()。 2) 「slow path」に対する行外 __skb_unclone_keeptruesize()。警告: CPU: 1 PID:
    6490 at net/core/skbuff.c:5295 skb_try_coalesce+0x1235/0x1560 net/core/skbuff.c:5295 リンクされているモジュール
    CPU1 PID6490 通信syz-executor161 汚染されていない 5.17.0-rc4-syzkaller-00229-g4f12b742eb2b #0 ハードウェア名Google Google Compute Engine/Google Compute Engine、BIOS Google 2011/01/01 RIP
    0010:skb_try_coalesce+0x1235/0x1560 net/core/skbuff.c:5295 コード: bf 01 00 00 00 0f b7 c0 89 c6 89 44 24 20 e8 62 24 4e fa 8b 44 24 20 83 e8 01 0f 85 eff f0 ff e9 87 f4 ff ff e8 cb 20 4e fa <0f> 0b e9 06 f9 ff e8 af b2 95 fa e9 69 f0 ff ff e8 95 b2 95 fa RSP 0018 : ffffc900063af268 EFLAGS : 00010293 RAX
    0000000000000000 RBX: 00000000ffffffd5 RCX: 0000000000000000 RDX: ffff88806fc05700 RSI: ffffffff872abd55 RDI: 0000000000000003 RBP: ffff88806e675500 R08: 00000000ffffffd5 R09: 0000000000000000 R10:
     R11ffffffff872ab659  : 0000000000000000 R12: ffff88806dd554e8 R13: ffff88806dd9bac0 R14: ffff88806dd9a2c0 R15: 0000000000000155 FS: 00007f18014f9700(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020002000 CR3: 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> tcp_try_coalesce net/ipv4/tcp_input.c:4651 [inline] tcp_try_coalesce+0x393/0x920 net/ipv4/tcp_input.c:4630 tcp_queue_rcv+0x8a/0x6e0 net/ipv4/tcp_input.c:4914 tcp_data_queue+0x11fd/0x4bb0 net/ipv4/tcp_input.c:5025 tcp_rcv_確立+0x81e/0x1ff0 net/ipv4/tcp_input.c:5947 tcp_v4_do_rcv+0x65e/0x980 net/ipv4/tcp_ipv4.c:1719 tcp_ipv4.c:1719 :1037 [inline] __release_sock+0x134/0x3b0 net/core/sock.c:2779 release_sock+0x54/0x1b0 net/core/sock.c:3311 sk_wait_data+0x177/0x450 net/core/sock.c:2821 tcp_recvmsg_locked+0xe28 /0x1fd0 net/ipv4/tcp.c:2457 tcp_recvmsg+0x137/0x610 net/ipv4/tcp.c:2572 inet_recvmsg+0x11b/0x5e0 net/ipv4/af_inet.c:850 sock_recvmsg_nosec net/socket.c:948 [inline] sock_recvmsg net/socket.c:966 [インライン] sock_recvmsg net/socket.c:962 [インライン]
    __sys_recvmsg+0x2c4/0x600 net/socket.c:2632 __sys_recvmsg+0x127/0x200 net/socket.c:2674
    __sys_recvmsg+0xe2/0x1a0 net/socket.c:2704 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xaeCVE-2022-49142

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

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

  - net: preserve skb_end_offset() in skb_unclone_keeptruesize() syzbot found another way to trigger the     infamous WARN_ON_ONCE(delta < len) in skb_try_coalesce() [1] I was able to root cause the issue to kfence.
    When kfence is in action, the following assertion is no longer true: int size = xxxx; void *ptr1 =     kmalloc(size, gfp); void *ptr2 = kmalloc(size, gfp); if (ptr1 && ptr2) ASSERT(ksize(ptr1) == ksize(ptr2));
    We attempted to fix these issues in the blamed commits, but forgot that TCP was possibly shifting data     after skb_unclone_keeptruesize() has been used, notably from tcp_retrans_try_collapse(). So we not only     need to keep same skb->truesize value, we also need to make sure TCP wont fill new tailroom that     pskb_expand_head() was able to get from a addr = kmalloc(...) followed by ksize(addr) Split     skb_unclone_keeptruesize() into two parts: 1) Inline skb_unclone_keeptruesize() for the common case, when     skb is not cloned. 2) Out of line __skb_unclone_keeptruesize() for the 'slow path'. WARNING: CPU: 1 PID:
    6490 at net/core/skbuff.c:5295 skb_try_coalesce+0x1235/0x1560 net/core/skbuff.c:5295 Modules linked in:
    CPU: 1 PID: 6490 Comm: syz-executor161 Not tainted 5.17.0-rc4-syzkaller-00229-g4f12b742eb2b #0 Hardware     name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP:
    0010:skb_try_coalesce+0x1235/0x1560 net/core/skbuff.c:5295 Code: bf 01 00 00 00 0f b7 c0 89 c6 89 44 24 20     e8 62 24 4e fa 8b 44 24 20 83 e8 01 0f 85 e5 f0 ff ff e9 87 f4 ff ff e8 cb 20 4e fa <0f> 0b e9 06 f9 ff ff     e8 af b2 95 fa e9 69 f0 ff ff e8 95 b2 95 fa RSP: 0018:ffffc900063af268 EFLAGS: 00010293 RAX:
    0000000000000000 RBX: 00000000ffffffd5 RCX: 0000000000000000 RDX: ffff88806fc05700 RSI: ffffffff872abd55     RDI: 0000000000000003 RBP: ffff88806e675500 R08: 00000000ffffffd5 R09: 0000000000000000 R10:
    ffffffff872ab659 R11: 0000000000000000 R12: ffff88806dd554e8 R13: ffff88806dd9bac0 R14: ffff88806dd9a2c0     R15: 0000000000000155 FS: 00007f18014f9700(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000 CS: 0010     DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020002000 CR3: 000000006be7a000 CR4: 00000000003506f0     DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6:
    00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> tcp_try_coalesce net/ipv4/tcp_input.c:4651     [inline] tcp_try_coalesce+0x393/0x920 net/ipv4/tcp_input.c:4630 tcp_queue_rcv+0x8a/0x6e0     net/ipv4/tcp_input.c:4914 tcp_data_queue+0x11fd/0x4bb0 net/ipv4/tcp_input.c:5025     tcp_rcv_established+0x81e/0x1ff0 net/ipv4/tcp_input.c:5947 tcp_v4_do_rcv+0x65e/0x980     net/ipv4/tcp_ipv4.c:1719 sk_backlog_rcv include/net/sock.h:1037 [inline] __release_sock+0x134/0x3b0     net/core/sock.c:2779 release_sock+0x54/0x1b0 net/core/sock.c:3311 sk_wait_data+0x177/0x450     net/core/sock.c:2821 tcp_recvmsg_locked+0xe28/0x1fd0 net/ipv4/tcp.c:2457 tcp_recvmsg+0x137/0x610     net/ipv4/tcp.c:2572 inet_recvmsg+0x11b/0x5e0 net/ipv4/af_inet.c:850 sock_recvmsg_nosec net/socket.c:948     [inline] sock_recvmsg net/socket.c:966 [inline] sock_recvmsg net/socket.c:962 [inline]
    ____sys_recvmsg+0x2c4/0x600 net/socket.c:2632 ___sys_recvmsg+0x127/0x200 net/socket.c:2674
    __sys_recvmsg+0xe2/0x1a0 net/socket.c:2704 do_syscall_x64 arch/x86/entry/common.c:50 [inline]     do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae     (CVE-2022-49142)

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

According to the versions of the kernel packages installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

    x86/mce: Work around an erratum on fast string copy instructions(CVE-2022-49124)

    net: preserve skb_end_offset() in skb_unclone_keeptruesize()(CVE-2022-49142)

    scsi: qla2xxx: Fix premature hw access after PCI error(CVE-2022-49157)

    scsi: qla2xxx: Fix warning message due to adisc being flushed(CVE-2022-49158)

    scsi: qla2xxx: Implement ref count for SRB(CVE-2022-49159)

    USB: core: Prevent nested device-reset calls(CVE-2022-49936)

    mmc: vub300: fix return value check of mmc_add_host()(CVE-2022-50251)

    tracing: Fix reading strings from synthetic events(CVE-2022-50255)

    kprobes: Fix check for probe enabled in kill_kprobe()(CVE-2022-50266)

    mmc: rtsx_pci: fix return value check of mmc_add_host()(CVE-2022-50267)

    pnode: terminate at peers of source(CVE-2022-50280)

    ext4: fix delayed allocation bug in ext4_clu_mapped for bigalloc + inline(CVE-2022-50286)

    ext4: fix potential out of bound read in ext4_fc_replay_scan()(CVE-2022-50306)

    drivers: serial: jsm: fix some leaks in probe(CVE-2022-50312)

    erofs: fix order = MAX_ORDER warning due to crafted negative i_size(CVE-2022-50313)

    ata: ahci: Match EM_MAX_SLOTS with SATA_PMP_MAX_PORTS(CVE-2022-50315)

    perf/x86/intel/uncore: Fix reference count leak in hswep_has_limit_sbox()(CVE-2022-50318)

    net: do not sense pfmemalloc status in skb_append_pagefrags()(CVE-2022-50323)

    jbd2: fix potential use-after-free in jbd2_fc_wait_bufs(CVE-2022-50328)

    crypto: cavium - prevent integer overflow loading firmware(CVE-2022-50330)

    ext4: fix null-ptr-deref in ext4_write_info(CVE-2022-50344)

    ext4: init quota for 'old.inode' in 'ext4_rename'(CVE-2022-50346)

    scsi: target: iscsi: Fix a race condition between login_work and the login thread(CVE-2022-50350)

    Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering     Authority.(CVE-2022-50377)

    padata: Always leave BHs disabled when running -parallel()(CVE-2022-50382)

    nvme: fix multipath crash caused by flush request when blktrace is enabled(CVE-2022-50388)

    tpm: tpm_crb: Add the missed acpi_put_table() to fix memory leak(CVE-2022-50389)

    drm/ttm: fix undefined behavior in bit shift for TTM_TT_FLAG_PRIV_POPULATED(CVE-2022-50390)

    i2c: ismt: Fix an out-of-bounds bug in ismt_access()(CVE-2022-50394)

    ACPICA: Fix error code path in acpi_ds_call_control_method()(CVE-2022-50411)

    x86/fpu: Fix copy_xstate_to_uabi() to copy init states correctly(CVE-2022-50425)

    mmc: vub300: fix warning - do not call blocking ops when !TASK_RUNNING(CVE-2022-50430)

    drm/vmwgfx: Validate the box size for the snooped cursor(CVE-2022-50440)

    cpufreq: Init completion before kobject_init_and_add()(CVE-2022-50473)

    ext4: add EXT4_IGET_BAD flag to prevent unexpected bad inode(CVE-2022-50485)

    scsi: qla2xxx: Fix crash when I/O abort times out(CVE-2022-50493)

    binfmt_misc: fix shift-out-of-bounds in check_special_flags(CVE-2022-50497)

    perf/smmuv3: Fix hotplug callback leak in arm_smmu_pmu_init()(CVE-2022-50510)

    tracing/hist: Fix out-of-bound write on 'action_data.var_ref_idx'(CVE-2022-50553)

    ext4: avoid deadlock in fs reclaim with page writeback(CVE-2023-53149)

    tracing: Fix null pointer dereference in tracing_err_log_open()(CVE-2023-53167)

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

    serial: 8250: Reinit port-pm on port specific driver unbind(CVE-2023-53176)

    mm: fix zswap writeback race condition(CVE-2023-53178)

    sched/fair: Don't balance task to its current running CPU(CVE-2023-53215)

    arm64: efi: Make efi_rt_lock a raw_spinlock(CVE-2023-53216)

    media: az6007: Fix null-ptr-deref in az6007_i2c_xfer()(CVE-2023-53220)

    bpf: Fix memleak due to fentry attach failure(CVE-2023-53221)

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

    firmware: dmi-sysfs: Fix null-ptr-deref in dmi_sysfs_register_handle(CVE-2023-53250)

    VMCI: check context-notify_page after call to get_user_pages_fast() to avoid GPF(CVE-2023-53259)

    ext4: fix i_disksize exceeding i_size problem in paritally written case(CVE-2023-53270)

    scsi: qla2xxx: Remove unused nvme_ls_waitq wait queue(CVE-2023-53280)

    ext4: add bounds checking in get_max_inline_xattr_value_size()(CVE-2023-53285)

    drm/client: Fix memory leak in drm_client_modeset_probe(CVE-2023-53288)

    ext4: fix WARNING in mb_find_extent(CVE-2023-53317)

    recordmcount: Fix memory leaks in the uwrite function(CVE-2023-53318)

    genirq/ipi: Fix NULL pointer deref in irq_data_get_affinity_mask()(CVE-2023-53332)

    tracing: Fix race issue between cpu buffer write and swap(CVE-2023-53368)

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

    tracing: Free error logs of tracing instances(CVE-2023-53375)

    ACPICA: Add AML_NO_OPERAND_RESOLVE flag to Timer(CVE-2023-53395)

    mm: kmem: fix a NULL pointer dereference in obj_stock_flush_required()(CVE-2023-53401)

    blk-cgroup: Reinit blkg_iostat_set after clearing in blkcg_reset_stats()(CVE-2023-53421)

    media: uvcvideo: Handle cameras with invalid descriptors(CVE-2023-53437)

    bpf: cpumap: Fix memory leak in cpu_map_update_elem(CVE-2023-53441)

    ext4: remove a BUG_ON in ext4_mb_release_group_pa()(CVE-2023-53450)

    scsi: qla4xxx: Add length check when parsing nlattrs(CVE-2023-53456)

    kobject: Add sanity check for kset-kobj.ktype in kset_register()(CVE-2023-53480)

    ext4: allow ext4_get_group_info() to fail(CVE-2023-53503)

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

    virtio-mmio: don't break lifecycle of vm_dev(CVE-2023-53515)

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

    scsi: qla2xxx: Use raw_smp_processor_id() instead of smp_processor_id()(CVE-2023-53530)

    tracing/histograms: Add histograms to hist_vars if they have referenced variables(CVE-2023-53560)

    null_blk: Always check queue mode setting from configfs(CVE-2023-53576)

    bpf, cpumap: Make sure kthread is running before map update returns(CVE-2023-53577)

    ring-buffer: Sync IRQ works before buffer destruction(CVE-2023-53587)

    ipmi_si: fix a memleak in try_smi_init()(CVE-2023-53611)

    ext4: fix possible double unlock when moving a directory(CVE-2023-53626)

    bnxt: avoid overflow in bnxt_get_nvram_directory()(CVE-2023-53661)

    ring-buffer: Fix deadloop issue on reading trace_pipe(CVE-2023-53668)

    A transient execution vulnerability in some AMD processors may allow an attacker to infer data in the L1D     cache, potentially resulting in the leakage of sensitive information across privileged     boundaries.(CVE-2024-36357)

    drm/dp_mst: Fix MST sideband message body length check(CVE-2024-56616)

    tls: stop recv() if initial process_rx_list gave us non-DATA(CVE-2024-58239)

    crypto: algif_hash - fix double free in hash_accept(CVE-2025-38079)

    thunderbolt: Do not double dequeue a configuration request(CVE-2025-38174)

    mm: fix uprobe pte be overwritten when expanding vma(CVE-2025-38207)

    scsi: lpfc: Use memcpy() for BIOS version(CVE-2025-38332)

    x86/sgx: Prevent attempts to reclaim poisoned pages(CVE-2025-38334)

    HID: core: do not bypass hid_hw_raw_request(CVE-2025-38494)

    clone_private_mnt(): make sure that caller has CAP_SYS_ADMIN in the right userns(CVE-2025-38499)

    bpf: Fix oob access in cgroup local storage(CVE-2025-38502)

    drm/sched: Increment job count before swapping tail spsc queue(CVE-2025-38515)

    pinctrl: qcom: msm: mark certain pins as invalid for interrupts(CVE-2025-38516)

    HID: quirks: Add quirk for 2 Chicony Electronics HP 5MP Cameras(CVE-2025-38540)

    net/sched: Restrict conditions for adding duplicating netems to qdisc tree(CVE-2025-38553)

    crypto: ccp - Fix crash when rebind ccp device for ccp.ko(CVE-2025-38581)

    padata: Fix pd UAF once and for all(CVE-2025-38584)

    net: drop UFO packets in udp_rcv_segment()(CVE-2025-38622)

    regulator: core: fix NULL dereference on unbind due to stale coupling data(CVE-2025-38668)

    media: uvcvideo: Fix 1-byte out-of-bounds read in uvc_parse_format()(CVE-2025-38680)

    fbdev: Fix vmalloc out-of-bounds write in fast_imageblit(CVE-2025-38685)

    media: dvb-frontends: w7090p: fix null-ptr-deref in w7090p_tuner_write_serpar and     w7090p_tuner_read_serpar(CVE-2025-38693)

    scsi: lpfc: Check for hdwq null ptr when cleaning up lpfc_vport structure(CVE-2025-38695)

    ext4: do not BUG when INLINE_DATA_FL lacks system.data xattr(CVE-2025-38701)

    x86/cpu/hygon: Add missing resctrl_cpu_detect() in bsp_init helper(CVE-2025-39681)

    tracing: Limit access to parser-buffer when trace_get_user failed(CVE-2025-39683)

    ftrace: Also allocate and copy hash for reading of filter files(CVE-2025-39689)

    fs/buffer: fix use-after-free when call bh_read() helper(CVE-2025-39691)

    serial: 8250: fix panic due to PSLVERR(CVE-2025-39724)

    rcu: Fix rcu_read_unlock() deadloop due to IRQ work(CVE-2025-39744)

    rcu: Protect -defer_qs_iw_pending from data race(CVE-2025-39749)

    usb: core: config: Prevent OOB read in SS endpoint companion parsing(CVE-2025-39760)

    jbd2: prevent softlockup in jbd2_log_do_checkpoint()(CVE-2025-39782)

    ftrace: Fix potential warning in trace_printk_seq during ftrace_dump(CVE-2025-39813)

    trace/fgraph: Fix the warning caused by missing unregister notifier(CVE-2025-39829)

    vxlan: Fix NPD in {arp,neigh}_reduce() when using nexthop objects(CVE-2025-39850)

    vxlan: Fix NPD when refreshing an FDB entry with a nexthop object(CVE-2025-39851)

    tee: fix NULL pointer dereference in tee_shm_put(CVE-2025-39865)

    fs: writeback: fix use-after-free in __mark_inode_dirty()(CVE-2025-39866)

    cgroup: split cgroup_destroy_wq into 3 workqueues(CVE-2025-39953)

    fbcon: fix integer overflow in fbcon_do_set_font(CVE-2025-39967)

    i40e: add max boundary check for VF filters(CVE-2025-39968)

    i40e: fix idx validation in config queues msg(CVE-2025-39971)

    i40e: add validation for ring_len param(CVE-2025-39973)

Tenable has extracted the preceding description block directly from the EulerOS kernel 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 Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2026-006660 advisory.

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

    net: preserve skb_end_offset() in skb_unclone_keeptruesize()

    syzbot found another way to trigger the infamous WARN_ON_ONCE(delta < len)     in skb_try_coalesce() [1]

    I was able to root cause the issue to kfence.

    When kfence is in action, the following assertion is no longer true:

    int size = xxxx;
    void *ptr1 = kmalloc(size, gfp);
    void *ptr2 = kmalloc(size, gfp);

    if (ptr1 && ptr2)             ASSERT(ksize(ptr1) == ksize(ptr2));

    We attempted to fix these issues in the blamed commits, but forgot     that TCP was possibly shifting data after skb_unclone_keeptruesize()     has been used, notably from tcp_retrans_try_collapse().

    So we not only need to keep same skb->truesize value,     we also need to make sure TCP wont fill new tailroom     that pskb_expand_head() was able to get from a     addr = kmalloc(...) followed by ksize(addr)

    Split skb_unclone_keeptruesize() into two parts:

    1) Inline skb_unclone_keeptruesize() for the common case,        when skb is not cloned.

    2) Out of line __skb_unclone_keeptruesize() for the 'slow path'.

    WARNING: CPU: 1 PID: 6490 at net/core/skbuff.c:5295 skb_try_coalesce+0x1235/0x1560 net/core/skbuff.c:5295     Modules linked in:
    CPU: 1 PID: 6490 Comm: syz-executor161 Not tainted 5.17.0-rc4-syzkaller-00229-g4f12b742eb2b #0     Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011     RIP: 0010:skb_try_coalesce+0x1235/0x1560 net/core/skbuff.c:5295     Code: bf 01 00 00 00 0f b7 c0 89 c6 89 44 24 20 e8 62 24 4e fa 8b 44 24 20 83 e8 01 0f 85 e5 f0 ff ff e9     87 f4 ff ff e8 cb 20 4e fa <0f> 0b e9 06 f9 ff ff e8 af b2 95 fa e9 69 f0 ff ff e8 95 b2 95 fa     RSP: 0018:ffffc900063af268 EFLAGS: 00010293     RAX: 0000000000000000 RBX: 00000000ffffffd5 RCX: 0000000000000000     RDX: ffff88806fc05700 RSI: ffffffff872abd55 RDI: 0000000000000003     RBP: ffff88806e675500 R08: 00000000ffffffd5 R09: 0000000000000000     R10: ffffffff872ab659 R11: 0000000000000000 R12: ffff88806dd554e8     R13: ffff88806dd9bac0 R14: ffff88806dd9a2c0 R15: 0000000000000155     FS:  00007f18014f9700(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000     CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033     CR2: 0000000020002000 CR3: 000000006be7a000 CR4: 00000000003506f0     DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000     DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400     Call Trace:
     <TASK>      tcp_try_coalesce net/ipv4/tcp_input.c:4651 [inline]      tcp_try_coalesce+0x393/0x920 net/ipv4/tcp_input.c:4630      tcp_queue_rcv+0x8a/0x6e0 net/ipv4/tcp_input.c:4914      tcp_data_queue+0x11fd/0x4bb0 net/ipv4/tcp_input.c:5025      tcp_rcv_established+0x81e/0x1ff0 net/ipv4/tcp_input.c:5947      tcp_v4_do_rcv+0x65e/0x980 net/ipv4/tcp_ipv4.c:1719      sk_backlog_rcv include/net/sock.h:1037 [inline]
     __release_sock+0x134/0x3b0 net/core/sock.c:2779      release_sock+0x54/0x1b0 net/core/sock.c:3311      sk_wait_data+0x177/0x450 net/core/sock.c:2821      tcp_recvmsg_locked+0xe28/0x1fd0 net/ipv4/tcp.c:2457      tcp_recvmsg+0x137/0x610 net/ipv4/tcp.c:2572      inet_recvmsg+0x11b/0x5e0 net/ipv4/af_inet.c:850      sock_recvmsg_nosec net/socket.c:948 [inline]      sock_recvmsg net/socket.c:966 [inline]      sock_recvmsg net/socket.c:962 [inline]
     ____sys_recvmsg+0x2c4/0x600 net/socket.c:2632
     ___sys_recvmsg+0x127/0x200 net/socket.c:2674
     __sys_recvmsg+0xe2/0x1a0 net/socket.c:2704      do_syscall_x64 arch/x86/entry/common.c:50 [inline]      do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80      entry_SYSCALL_64_after_hwframe+0x44/0xae

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-013482 advisory.

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

    net: preserve skb_end_offset() in skb_unclone_keeptruesize()

    syzbot found another way to trigger the infamous WARN_ON_ONCE(delta < len)     in skb_try_coalesce() [1]

    I was able to root cause the issue to kfence.

    When kfence is in action, the following assertion is no longer true:

    int size = xxxx;
    void *ptr1 = kmalloc(size, gfp);
    void *ptr2 = kmalloc(size, gfp);

    if (ptr1 && ptr2)             ASSERT(ksize(ptr1) == ksize(ptr2));

    We attempted to fix these issues in the blamed commits, but forgot     that TCP was possibly shifting data after skb_unclone_keeptruesize()     has been used, notably from tcp_retrans_try_collapse().

    So we not only need to keep same skb->truesize value,     we also need to make sure TCP wont fill new tailroom     that pskb_expand_head() was able to get from a     addr = kmalloc(...) followed by ksize(addr)

    Split skb_unclone_keeptruesize() into two parts:

    1) Inline skb_unclone_keeptruesize() for the common case,        when skb is not cloned.

    2) Out of line __skb_unclone_keeptruesize() for the 'slow path'.

    WARNING: CPU: 1 PID: 6490 at net/core/skbuff.c:5295 skb_try_coalesce+0x1235/0x1560 net/core/skbuff.c:5295     Modules linked in:
    CPU: 1 PID: 6490 Comm: syz-executor161 Not tainted 5.17.0-rc4-syzkaller-00229-g4f12b742eb2b #0     Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011     RIP: 0010:skb_try_coalesce+0x1235/0x1560 net/core/skbuff.c:5295     Code: bf 01 00 00 00 0f b7 c0 89 c6 89 44 24 20 e8 62 24 4e fa 8b 44 24 20 83 e8 01 0f 85 e5 f0 ff ff e9     87 f4 ff ff e8 cb 20 4e fa <0f> 0b e9 06 f9 ff ff e8 af b2 95 fa e9 69 f0 ff ff e8 95 b2 95 fa     RSP: 0018:ffffc900063af268 EFLAGS: 00010293     RAX: 0000000000000000 RBX: 00000000ffffffd5 RCX: 0000000000000000     RDX: ffff88806fc05700 RSI: ffffffff872abd55 RDI: 0000000000000003     RBP: ffff88806e675500 R08: 00000000ffffffd5 R09: 0000000000000000     R10: ffffffff872ab659 R11: 0000000000000000 R12: ffff88806dd554e8     R13: ffff88806dd9bac0 R14: ffff88806dd9a2c0 R15: 0000000000000155     FS:  00007f18014f9700(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000     CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033     CR2: 0000000020002000 CR3: 000000006be7a000 CR4: 00000000003506f0     DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000     DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400     Call Trace:
     <TASK>      tcp_try_coalesce net/ipv4/tcp_input.c:4651 [inline]      tcp_try_coalesce+0x393/0x920 net/ipv4/tcp_input.c:4630      tcp_queue_rcv+0x8a/0x6e0 net/ipv4/tcp_input.c:4914      tcp_data_queue+0x11fd/0x4bb0 net/ipv4/tcp_input.c:5025      tcp_rcv_established+0x81e/0x1ff0 net/ipv4/tcp_input.c:5947      tcp_v4_do_rcv+0x65e/0x980 net/ipv4/tcp_ipv4.c:1719      sk_backlog_rcv include/net/sock.h:1037 [inline]
     __release_sock+0x134/0x3b0 net/core/sock.c:2779      release_sock+0x54/0x1b0 net/core/sock.c:3311      sk_wait_data+0x177/0x450 net/core/sock.c:2821      tcp_recvmsg_locked+0xe28/0x1fd0 net/ipv4/tcp.c:2457      tcp_recvmsg+0x137/0x610 net/ipv4/tcp.c:2572      inet_recvmsg+0x11b/0x5e0 net/ipv4/af_inet.c:850      sock_recvmsg_nosec net/socket.c:948 [inline]      sock_recvmsg net/socket.c:966 [inline]      sock_recvmsg net/socket.c:962 [inline]
     ____sys_recvmsg+0x2c4/0x600 net/socket.c:2632
     ___sys_recvmsg+0x127/0x200 net/socket.c:2674
     __sys_recvmsg+0xe2/0x1a0 net/socket.c:2704      do_syscall_x64 arch/x86/entry/common.c:50 [inline]      do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80      entry_SYSCALL_64_after_hwframe+0x44/0xae

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.

According to the versions of the kernel packages installed, the EulerOS Virtualization installation on the remote host is affected by the following vulnerabilities :

    x86/mce: Work around an erratum on fast string copy instructions(CVE-2022-49124)

    net: preserve skb_end_offset() in skb_unclone_keeptruesize()(CVE-2022-49142)

    scsi: qla2xxx: Fix premature hw access after PCI error(CVE-2022-49157)

    scsi: qla2xxx: Fix warning message due to adisc being flushed(CVE-2022-49158)

    scsi: qla2xxx: Implement ref count for SRB(CVE-2022-49159)

    USB: core: Prevent nested device-reset calls(CVE-2022-49936)

    mmc: vub300: fix return value check of mmc_add_host()(CVE-2022-50251)

    tracing: Fix reading strings from synthetic events(CVE-2022-50255)

    kprobes: Fix check for probe enabled in kill_kprobe()(CVE-2022-50266)

    mmc: rtsx_pci: fix return value check of mmc_add_host()(CVE-2022-50267)

    pnode: terminate at peers of source(CVE-2022-50280)

    ext4: fix delayed allocation bug in ext4_clu_mapped for bigalloc + inline(CVE-2022-50286)

    ext4: fix potential out of bound read in ext4_fc_replay_scan()(CVE-2022-50306)

    drivers: serial: jsm: fix some leaks in probe(CVE-2022-50312)

    erofs: fix order = MAX_ORDER warning due to crafted negative i_size(CVE-2022-50313)

    ata: ahci: Match EM_MAX_SLOTS with SATA_PMP_MAX_PORTS(CVE-2022-50315)

    perf/x86/intel/uncore: Fix reference count leak in hswep_has_limit_sbox()(CVE-2022-50318)

    net: do not sense pfmemalloc status in skb_append_pagefrags()(CVE-2022-50323)

    jbd2: fix potential use-after-free in jbd2_fc_wait_bufs(CVE-2022-50328)

    crypto: cavium - prevent integer overflow loading firmware(CVE-2022-50330)

    ext4: fix null-ptr-deref in ext4_write_info(CVE-2022-50344)

    ext4: init quota for 'old.inode' in 'ext4_rename'(CVE-2022-50346)

    scsi: target: iscsi: Fix a race condition between login_work and the login thread(CVE-2022-50350)

    Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering     Authority.(CVE-2022-50377)

    padata: Always leave BHs disabled when running -parallel()(CVE-2022-50382)

    nvme: fix multipath crash caused by flush request when blktrace is enabled(CVE-2022-50388)

    tpm: tpm_crb: Add the missed acpi_put_table() to fix memory leak(CVE-2022-50389)

    drm/ttm: fix undefined behavior in bit shift for TTM_TT_FLAG_PRIV_POPULATED(CVE-2022-50390)

    i2c: ismt: Fix an out-of-bounds bug in ismt_access()(CVE-2022-50394)

    ACPICA: Fix error code path in acpi_ds_call_control_method()(CVE-2022-50411)

    x86/fpu: Fix copy_xstate_to_uabi() to copy init states correctly(CVE-2022-50425)

    mmc: vub300: fix warning - do not call blocking ops when !TASK_RUNNING(CVE-2022-50430)

    drm/vmwgfx: Validate the box size for the snooped cursor(CVE-2022-50440)

    cpufreq: Init completion before kobject_init_and_add()(CVE-2022-50473)

    ext4: add EXT4_IGET_BAD flag to prevent unexpected bad inode(CVE-2022-50485)

    scsi: qla2xxx: Fix crash when I/O abort times out(CVE-2022-50493)

    binfmt_misc: fix shift-out-of-bounds in check_special_flags(CVE-2022-50497)

    perf/smmuv3: Fix hotplug callback leak in arm_smmu_pmu_init()(CVE-2022-50510)

    tracing/hist: Fix out-of-bound write on 'action_data.var_ref_idx'(CVE-2022-50553)

    ext4: avoid deadlock in fs reclaim with page writeback(CVE-2023-53149)

    tracing: Fix null pointer dereference in tracing_err_log_open()(CVE-2023-53167)

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

    serial: 8250: Reinit port-pm on port specific driver unbind(CVE-2023-53176)

    mm: fix zswap writeback race condition(CVE-2023-53178)

    sched/fair: Don't balance task to its current running CPU(CVE-2023-53215)

    arm64: efi: Make efi_rt_lock a raw_spinlock(CVE-2023-53216)

    media: az6007: Fix null-ptr-deref in az6007_i2c_xfer()(CVE-2023-53220)

    bpf: Fix memleak due to fentry attach failure(CVE-2023-53221)

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

    firmware: dmi-sysfs: Fix null-ptr-deref in dmi_sysfs_register_handle(CVE-2023-53250)

    VMCI: check context-notify_page after call to get_user_pages_fast() to avoid GPF(CVE-2023-53259)

    ext4: fix i_disksize exceeding i_size problem in paritally written case(CVE-2023-53270)

    scsi: qla2xxx: Remove unused nvme_ls_waitq wait queue(CVE-2023-53280)

    ext4: add bounds checking in get_max_inline_xattr_value_size()(CVE-2023-53285)

    drm/client: Fix memory leak in drm_client_modeset_probe(CVE-2023-53288)

    ext4: fix WARNING in mb_find_extent(CVE-2023-53317)

    recordmcount: Fix memory leaks in the uwrite function(CVE-2023-53318)

    genirq/ipi: Fix NULL pointer deref in irq_data_get_affinity_mask()(CVE-2023-53332)

    tracing: Fix race issue between cpu buffer write and swap(CVE-2023-53368)

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

    tracing: Free error logs of tracing instances(CVE-2023-53375)

    ACPICA: Add AML_NO_OPERAND_RESOLVE flag to Timer(CVE-2023-53395)

    mm: kmem: fix a NULL pointer dereference in obj_stock_flush_required()(CVE-2023-53401)

    blk-cgroup: Reinit blkg_iostat_set after clearing in blkcg_reset_stats()(CVE-2023-53421)

    media: uvcvideo: Handle cameras with invalid descriptors(CVE-2023-53437)

    bpf: cpumap: Fix memory leak in cpu_map_update_elem(CVE-2023-53441)

    ext4: remove a BUG_ON in ext4_mb_release_group_pa()(CVE-2023-53450)

    scsi: qla4xxx: Add length check when parsing nlattrs(CVE-2023-53456)

    kobject: Add sanity check for kset-kobj.ktype in kset_register()(CVE-2023-53480)

    ext4: allow ext4_get_group_info() to fail(CVE-2023-53503)

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

    virtio-mmio: don't break lifecycle of vm_dev(CVE-2023-53515)

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

    scsi: qla2xxx: Use raw_smp_processor_id() instead of smp_processor_id()(CVE-2023-53530)

    tracing/histograms: Add histograms to hist_vars if they have referenced variables(CVE-2023-53560)

    null_blk: Always check queue mode setting from configfs(CVE-2023-53576)

    bpf, cpumap: Make sure kthread is running before map update returns(CVE-2023-53577)

    ring-buffer: Sync IRQ works before buffer destruction(CVE-2023-53587)

    ipmi_si: fix a memleak in try_smi_init()(CVE-2023-53611)

    ext4: fix possible double unlock when moving a directory(CVE-2023-53626)

    bnxt: avoid overflow in bnxt_get_nvram_directory()(CVE-2023-53661)

    ring-buffer: Fix deadloop issue on reading trace_pipe(CVE-2023-53668)

    A transient execution vulnerability in some AMD processors may allow an attacker to infer data in the L1D     cache, potentially resulting in the leakage of sensitive information across privileged     boundaries.(CVE-2024-36357)

    drm/dp_mst: Fix MST sideband message body length check(CVE-2024-56616)

    tls: stop recv() if initial process_rx_list gave us non-DATA(CVE-2024-58239)

    crypto: algif_hash - fix double free in hash_accept(CVE-2025-38079)

    thunderbolt: Do not double dequeue a configuration request(CVE-2025-38174)

    mm: fix uprobe pte be overwritten when expanding vma(CVE-2025-38207)

    scsi: lpfc: Use memcpy() for BIOS version(CVE-2025-38332)

    x86/sgx: Prevent attempts to reclaim poisoned pages(CVE-2025-38334)

    HID: core: do not bypass hid_hw_raw_request(CVE-2025-38494)

    clone_private_mnt(): make sure that caller has CAP_SYS_ADMIN in the right userns(CVE-2025-38499)

    bpf: Fix oob access in cgroup local storage(CVE-2025-38502)

    drm/sched: Increment job count before swapping tail spsc queue(CVE-2025-38515)

    pinctrl: qcom: msm: mark certain pins as invalid for interrupts(CVE-2025-38516)

    HID: quirks: Add quirk for 2 Chicony Electronics HP 5MP Cameras(CVE-2025-38540)

    net/sched: Restrict conditions for adding duplicating netems to qdisc tree(CVE-2025-38553)

    crypto: ccp - Fix crash when rebind ccp device for ccp.ko(CVE-2025-38581)

    padata: Fix pd UAF once and for all(CVE-2025-38584)

    net: drop UFO packets in udp_rcv_segment()(CVE-2025-38622)

    regulator: core: fix NULL dereference on unbind due to stale coupling data(CVE-2025-38668)

    media: uvcvideo: Fix 1-byte out-of-bounds read in uvc_parse_format()(CVE-2025-38680)

    fbdev: Fix vmalloc out-of-bounds write in fast_imageblit(CVE-2025-38685)

    media: dvb-frontends: w7090p: fix null-ptr-deref in w7090p_tuner_write_serpar and     w7090p_tuner_read_serpar(CVE-2025-38693)

    scsi: lpfc: Check for hdwq null ptr when cleaning up lpfc_vport structure(CVE-2025-38695)

    ext4: do not BUG when INLINE_DATA_FL lacks system.data xattr(CVE-2025-38701)

    x86/cpu/hygon: Add missing resctrl_cpu_detect() in bsp_init helper(CVE-2025-39681)

    tracing: Limit access to parser-buffer when trace_get_user failed(CVE-2025-39683)

    ftrace: Also allocate and copy hash for reading of filter files(CVE-2025-39689)

    fs/buffer: fix use-after-free when call bh_read() helper(CVE-2025-39691)

    serial: 8250: fix panic due to PSLVERR(CVE-2025-39724)

    rcu: Fix rcu_read_unlock() deadloop due to IRQ work(CVE-2025-39744)

    rcu: Protect -defer_qs_iw_pending from data race(CVE-2025-39749)

    usb: core: config: Prevent OOB read in SS endpoint companion parsing(CVE-2025-39760)

    jbd2: prevent softlockup in jbd2_log_do_checkpoint()(CVE-2025-39782)

    ftrace: Fix potential warning in trace_printk_seq during ftrace_dump(CVE-2025-39813)

    trace/fgraph: Fix the warning caused by missing unregister notifier(CVE-2025-39829)

    vxlan: Fix NPD in {arp,neigh}_reduce() when using nexthop objects(CVE-2025-39850)

    vxlan: Fix NPD when refreshing an FDB entry with a nexthop object(CVE-2025-39851)

    tee: fix NULL pointer dereference in tee_shm_put(CVE-2025-39865)

    fs: writeback: fix use-after-free in __mark_inode_dirty()(CVE-2025-39866)

    cgroup: split cgroup_destroy_wq into 3 workqueues(CVE-2025-39953)

    fbcon: fix integer overflow in fbcon_do_set_font(CVE-2025-39967)

    i40e: add max boundary check for VF filters(CVE-2025-39968)

    i40e: fix idx validation in config queues msg(CVE-2025-39971)

    i40e: add validation for ring_len param(CVE-2025-39973)

Tenable has extracted the preceding description block directly from the EulerOS Virtualization kernel 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 Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2026-005494 advisory.

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

    net: preserve skb_end_offset() in skb_unclone_keeptruesize()

    syzbot found another way to trigger the infamous WARN_ON_ONCE(delta < len)     in skb_try_coalesce() [1]

    I was able to root cause the issue to kfence.

    When kfence is in action, the following assertion is no longer true:

    int size = xxxx;
    void *ptr1 = kmalloc(size, gfp);
    void *ptr2 = kmalloc(size, gfp);

    if (ptr1 && ptr2)             ASSERT(ksize(ptr1) == ksize(ptr2));

    We attempted to fix these issues in the blamed commits, but forgot     that TCP was possibly shifting data after skb_unclone_keeptruesize()     has been used, notably from tcp_retrans_try_collapse().

    So we not only need to keep same skb->truesize value,     we also need to make sure TCP wont fill new tailroom     that pskb_expand_head() was able to get from a     addr = kmalloc(...) followed by ksize(addr)

    Split skb_unclone_keeptruesize() into two parts:

    1) Inline skb_unclone_keeptruesize() for the common case,        when skb is not cloned.

    2) Out of line __skb_unclone_keeptruesize() for the 'slow path'.

    WARNING: CPU: 1 PID: 6490 at net/core/skbuff.c:5295 skb_try_coalesce+0x1235/0x1560 net/core/skbuff.c:5295     Modules linked in:
    CPU: 1 PID: 6490 Comm: syz-executor161 Not tainted 5.17.0-rc4-syzkaller-00229-g4f12b742eb2b #0     Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011     RIP: 0010:skb_try_coalesce+0x1235/0x1560 net/core/skbuff.c:5295     Code: bf 01 00 00 00 0f b7 c0 89 c6 89 44 24 20 e8 62 24 4e fa 8b 44 24 20 83 e8 01 0f 85 e5 f0 ff ff e9     87 f4 ff ff e8 cb 20 4e fa <0f> 0b e9 06 f9 ff ff e8 af b2 95 fa e9 69 f0 ff ff e8 95 b2 95 fa     RSP: 0018:ffffc900063af268 EFLAGS: 00010293     RAX: 0000000000000000 RBX: 00000000ffffffd5 RCX: 0000000000000000     RDX: ffff88806fc05700 RSI: ffffffff872abd55 RDI: 0000000000000003     RBP: ffff88806e675500 R08: 00000000ffffffd5 R09: 0000000000000000     R10: ffffffff872ab659 R11: 0000000000000000 R12: ffff88806dd554e8     R13: ffff88806dd9bac0 R14: ffff88806dd9a2c0 R15: 0000000000000155     FS:  00007f18014f9700(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000     CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033     CR2: 0000000020002000 CR3: 000000006be7a000 CR4: 00000000003506f0     DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000     DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400     Call Trace:
     <TASK>      tcp_try_coalesce net/ipv4/tcp_input.c:4651 [inline]      tcp_try_coalesce+0x393/0x920 net/ipv4/tcp_input.c:4630      tcp_queue_rcv+0x8a/0x6e0 net/ipv4/tcp_input.c:4914      tcp_data_queue+0x11fd/0x4bb0 net/ipv4/tcp_input.c:5025      tcp_rcv_established+0x81e/0x1ff0 net/ipv4/tcp_input.c:5947      tcp_v4_do_rcv+0x65e/0x980 net/ipv4/tcp_ipv4.c:1719      sk_backlog_rcv include/net/sock.h:1037 [inline]
     __release_sock+0x134/0x3b0 net/core/sock.c:2779      release_sock+0x54/0x1b0 net/core/sock.c:3311      sk_wait_data+0x177/0x450 net/core/sock.c:2821      tcp_recvmsg_locked+0xe28/0x1fd0 net/ipv4/tcp.c:2457      tcp_recvmsg+0x137/0x610 net/ipv4/tcp.c:2572      inet_recvmsg+0x11b/0x5e0 net/ipv4/af_inet.c:850      sock_recvmsg_nosec net/socket.c:948 [inline]      sock_recvmsg net/socket.c:966 [inline]      sock_recvmsg net/socket.c:962 [inline]
     ____sys_recvmsg+0x2c4/0x600 net/socket.c:2632
     ___sys_recvmsg+0x127/0x200 net/socket.c:2674
     __sys_recvmsg+0xe2/0x1a0 net/socket.c:2704      do_syscall_x64 arch/x86/entry/common.c:50 [inline]      do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80      entry_SYSCALL_64_after_hwframe+0x44/0xae

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 Redhat Enterprise Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2022:8267 advisory.

    The kernel packages contain the Linux kernel, the core of any Linux operating system.

    Security Fix(es):

    * off-path attacker may inject data or terminate victim's TCP session (CVE-2020-36516)

    * use-after-free vulnerability in function sco_sock_sendmsg() (CVE-2021-3640)

    * smb2_ioctl_query_info NULL pointer dereference (CVE-2022-0168)

    * NULL pointer dereference in udf_expand_file_adinicbdue() during writeback (CVE-2022-0617)

    * swiotlb information leak with DMA_FROM_DEVICE (CVE-2022-0854)

    * uninitialized registers on stack in nft_do_chain can cause kernel pointer leakage to UM (CVE-2022-1016)

    * race condition in snd_pcm_hw_free leading to use-after-free (CVE-2022-1048)

    * use-after-free and memory errors in ext4 when mounting and operating on a corrupted image     (CVE-2022-1184)

    * concurrency use-after-free between drm_setmaster_ioctl and drm_mode_getresources (CVE-2022-1280)

    * kernel info leak issue in pfkey_register (CVE-2022-1353)

    * use-after-free in ath9k_htc_probe_device() could cause an escalation of privileges (CVE-2022-1679)

    * NULL pointer dereference in x86_emulate_insn may lead to DoS (CVE-2022-1852)

    * fanotify misuses fd_install() which could lead to use-after-free (CVE-2022-1998)

    * nf_tables cross-table potential use-after-free may lead to local privilege escalation (CVE-2022-2586)

    * integer underflow leads to out-of-bounds write in reserve_sfa_size() (CVE-2022-2639)

    * slab-out-of-bounds access in packet_recvmsg() (CVE-2022-20368)

    * incomplete clean-up of multi-core shared buffers (aka SBDR) (CVE-2022-21123)

    * incomplete clean-up of microarchitectural fill buffers (aka SBDS) (CVE-2022-21125)

    * incomplete clean-up in specific special register write operations (aka DRPW) (CVE-2022-21166)

    * possible to use the debugger to write zero into a location of choice (CVE-2022-21499)

    * AMD: RetBleed Arbitrary Speculative Code Execution with Return Instructions (CVE-2022-23816,     CVE-2022-29900)

    * AMD: Branch Type Confusion (non-retbleed) (CVE-2022-23825)

    * Intel: Post-barrier Return Stack Buffer Predictions (CVE-2022-26373)

    * double free in ems_usb_start_xmit in drivers/net/can/usb/ems_usb.c (CVE-2022-28390)

    * use after free in SUNRPC subsystem (CVE-2022-28893)

    * use-after-free due to improper update of reference count in net/sched/cls_u32.c (CVE-2022-29581)

    * Intel: RetBleed Arbitrary Speculative Code Execution with Return Instructions (CVE-2022-29901)

    * DoS in nfqnl_mangle in net/netfilter/nfnetlink_queue.c (CVE-2022-36946)

    * nf_tables disallow binding to already bound chain (CVE-2022-39190)

    * nfs_atomic_open() returns uninitialized data instead of ENOTDIR (CVE-2022-24448)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

    Additional Changes:

    For detailed information on changes in this release, see the Red Hat Enterprise Linux 9.1 Release Notes     linked from the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux 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	名称	产品	系列	发布时间	最近更新时间	严重程度
167620	RHEL 9：核心 (RHSA-2022:8267)	Nessus	Red Hat Local Security Checks	2022/11/16	2025/9/12	high
167620	RHEL 9：内核 (RHSA-2022:8267)	Nessus	Red Hat Local Security Checks	2022/11/16	2025/9/12	high
225180	Linux Distros 未修補的弱點：CVE-2022-49142	Nessus	Misc.	2025/3/5	2026/1/14	medium
225180	Linux Distros 未修补的漏洞：CVE-2022-49142	Nessus	Misc.	2025/3/5	2026/1/14	medium
167620	RHEL 9 : kernel (RHSA-2022:8267)	Nessus	Red Hat Local Security Checks	2022/11/16	2025/9/12	high
225180	Linux Distros のパッチ未適用の脆弱性: CVE-2022-49142	Nessus	Misc.	2025/3/5	2026/1/14	medium
225180	Linux Distros Unpatched Vulnerability : CVE-2022-49142	Nessus	Misc.	2025/3/5	2026/1/14	medium
278484	EulerOS 2.0 SP13 : kernel (EulerOS-SA-2025-2501)	Nessus	Huawei Local Security Checks	2025/12/11	2026/3/6	high
305508	Unity Linux 20.1050e Security Update: kernel (UTSA-2026-006660)	Nessus	Unity Linux Local Security Checks	2026/4/8	2026/4/8	medium
309400	Unity Linux 20.1070a Security Update: kernel (UTSA-2026-013482)	Nessus	Unity Linux Local Security Checks	2026/4/22	2026/4/22	medium
281563	EulerOS Virtualization 2.13.1 : kernel (EulerOS-SA-2025-2623)	Nessus	Huawei Local Security Checks	2025/12/31	2026/3/6	high
300571	Unity Linux 20.1070e Security Update: kernel (UTSA-2026-005494)	Nessus	Unity Linux Local Security Checks	2026/3/4	2026/3/4	medium
278473	EulerOS 2.0 SP13 : kernel (EulerOS-SA-2025-2522)	Nessus	Huawei Local Security Checks	2025/12/11	2026/3/6	high
281579	EulerOS Virtualization 2.13.0 : kernel (EulerOS-SA-2025-2609)	Nessus	Huawei Local Security Checks	2025/12/31	2026/3/6	high
167620	RHEL 9 : kernel (RHSA-2022:8267)	Nessus	Red Hat Local Security Checks	2022/11/16	2025/9/12	high

检测

插件搜索

high

high

medium

medium

high

medium

medium

high

medium

medium

high

medium

high

high

high