The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2025-989015 advisory.

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

    f2fs: fix to do sanity check on i_extra_isize in is_alive()

    syzbot found a f2fs bug:

    BUG: KASAN: slab-out-of-bounds in data_blkaddr fs/f2fs/f2fs.h:2891 [inline]     BUG: KASAN: slab-out-of-bounds in is_alive fs/f2fs/gc.c:1117 [inline]     BUG: KASAN: slab-out-of-bounds in gc_data_segment fs/f2fs/gc.c:1520 [inline]     BUG: KASAN: slab-out-of-bounds in do_garbage_collect+0x386a/0x3df0 fs/f2fs/gc.c:1734     Read of size 4 at addr ffff888076557568 by task kworker/u4:3/52

    CPU: 1 PID: 52 Comm: kworker/u4:3 Not tainted 6.1.0-rc4-syzkaller-00362-gfef7fd48922d #0     Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022     Workqueue: writeback wb_workfn (flush-7:0)     Call Trace:
    <TASK>
    __dump_stack lib/dump_stack.c:88 [inline]     dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106     print_address_description mm/kasan/report.c:284 [inline]     print_report+0x15e/0x45d mm/kasan/report.c:395     kasan_report+0xbb/0x1f0 mm/kasan/report.c:495     data_blkaddr fs/f2fs/f2fs.h:2891 [inline]     is_alive fs/f2fs/gc.c:1117 [inline]     gc_data_segment fs/f2fs/gc.c:1520 [inline]     do_garbage_collect+0x386a/0x3df0 fs/f2fs/gc.c:1734     f2fs_gc+0x88c/0x20a0 fs/f2fs/gc.c:1831     f2fs_balance_fs+0x544/0x6b0 fs/f2fs/segment.c:410     f2fs_write_inode+0x57e/0xe20 fs/f2fs/inode.c:753     write_inode fs/fs-writeback.c:1440 [inline]
    __writeback_single_inode+0xcfc/0x1440 fs/fs-writeback.c:1652     writeback_sb_inodes+0x54d/0xf90 fs/fs-writeback.c:1870     wb_writeback+0x2c5/0xd70 fs/fs-writeback.c:2044     wb_do_writeback fs/fs-writeback.c:2187 [inline]     wb_workfn+0x2dc/0x12f0 fs/fs-writeback.c:2227     process_one_work+0x9bf/0x1710 kernel/workqueue.c:2289     worker_thread+0x665/0x1080 kernel/workqueue.c:2436     kthread+0x2e4/0x3a0 kernel/kthread.c:376     ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306

    The root cause is that we forgot to do sanity check on .i_extra_isize     in below path, result in accessing invalid address later, fix it.
    - gc_data_segment
     - is_alive
      - data_blkaddr
       - offset_in_addr

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.

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

  - f2fsis_alive() の i_extra_isize でサニティーチェックを行うための修正 syzbot は、f2fs バグを見つけました バグKASANdata_blkaddr の slab-out-of-bounds fs/f2fs/f2fs.h:2891 [インライン] バグKASANslab -out-of-bounds in is_alive fs/f2fs/gc.c:1117 [インライン] バグ KASANgc_data_segment の slab-out-of-bounds fs/f2fs/gc.c:1520 [インライン] バグ KASANスラブ-out-of-bounds in do_garbage_collect+0x386a/0x3df0 fs/f2fs/gc.c:1734 タスク kworker/u4:3/52 による addr ffff888076557568 でのサイズ 4 の読み取り CPU1 PID52 通信 kworker/u4:3汚染されていない 6.1.0-rc4-syzkaller-00362-gfef7fd48922d #0 ハードウェア名Google Google Compute Engine/Google Compute Engine、BIOS Google 10/26/2022 ワークキューwriteback wb_workfnflush-7:0Call Trace <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106 print_address_description mm/kasan/report.c:284 [inline] print_report+0x15e/0x45d mm/kasan/report.c:395 kasan_report+0xbb/0x1f0 mm/kasan/report.c:495 data_blkaddr fs/f2fs/f2fs.h:2891 [inline] is_alive fs/f2fs/gc.c:1 117 [inline] gc_data_segment fs/f2fs/gc.c:1520 [inline] do_garbage_collect+0x386a/0x3df0 fs/f2fs/gc.c:1734 f2fs_gc+0x88c/0x20a0 fs/f2fs/gc.c:1831 f2fs_balance_fs+0x5b04/0x5b404 fs/f2fs/segment.c:410 f2fs_write_inode+0x57e/0xe20 fs/f2fs/inode.c:753 write_inode fs/fs-writeback.c:1440 [インライン]
    __writeback_single_inode+0xcfc/0x1440 fs/fs-writeback.c:1652 writeback_sb_inodes+0x54d/0xf90 fs/fs-writeback.c:1870 wb_writeback+0x2c5/0xd70 fs/fs-writeback.c:2044 wb_do_writeback fs/fs-writeback.c :2187 [インライン] wb_workfn+0x2dc/0x12f0 fs/fs-writeback.c:2227 process_one_work+0x9bf/0x1710 kernel/workqueue.c:2289 worker_thread+0x665/0x1080 kernel/workqueue.c:2436 kthread+0x2e4/0x3a0 kernel/ kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306 ルートの原因は、以下のパスの .i_extra_isize のサニティチェックをし忘れたことです。後で無効なアドレスにアクセスすることになります。これを修正します。 - gc_data_segment - is_alive - data_blkaddr - offset_in_addrCVE-2022-49738]

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

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

  - f2fs修复以对 is_alive() 中的 i_extra_isize 进行健全性检查 syzbot 发现一个 f2fs 缺陷 BUG: KASAN: slab-out-of-bounds in data_blkaddr fs/f2fs/f2fs.h:2891 [内联] BUG: KASAN: slab - is_alive fs/f2fs/gc.c:1117 中的越界 [内联] gc_data_segment fs/f2fs/gc.c:1520 中的 BUG: KASANslab 越界 [内联] BUG: KASAN: slab - do_garbage_collect+0x386a/0x3df0 fs/f2fs/gc.c:1734 中在地址 ffff888076557568 发生大小为 4 的读取越界由任务 kworker/u4:3/52 CPU: 1 PID: 52 Comm: kworker/u4:3未受感染 6.1.0-rc4-syzkaller-00362-gfef7fd48922d #0 硬件名称Google Google Compute Engine/Google Compute Engine、BIOS Google 10/26/2022 Workqueuewriteback wb_workfn (flush-7:0) 调用跟踪 <TASK> __dump_stack lib/dump_stack.c:88 [内联] dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106 print_address_description mm/kasan/report.c:284 [内联] print_report+0x15e/0x45d mm/kasan/report.c:395 kasan_report+0xbb/0x1f0 mm/kasan/report.c:495 data_blkaddr fs/f2fs/f2fs.h:2891 [内联] is_alive fs/f2fs/gc.c.c:1 117 [inline] gc_data_segment fs/f2fs/gc.c:1520 [inline] do_garbage_collect+0x386a/0x3df0 fs/f2fs/gc.c:1734 f2fs_gc+0x88c/0x20a0 fs/f2fs/gc.c:1831 f2fs_balance_fs+0x60544/0x60544 fs/f2fs/segment.c:410 f2fs_write_inode+0x57e/0xe20 fs/f2fs/inode.c:753 write_inode fs/fs-writeback.c:1440 [内联]
    __writeback_single_inode+0xcfc/0x1440 fs/fs-writeback.c:1652 writeback_sb_inodes+0x54d/0xf90 fs/fs-writeback.c:1870 wb_writeback+0x2c5/0xd70 fs/fs-writeback.c:2044 wb_do_writeback fs/fs-writeback.c 2187 [inline] wb_workfn+0x2dc/0x12f0 fs/fs-writeback.c:2227 process_one_work+0x9bf/0x1710 kernel/workqueue.c:2289 worker_thread+0x665/0x1080 kernel/workqueue.c:2436 kthread+0x2e4/0x3a0 kernel/ kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306 根本原因是我们忘记对下列路径中的 .i_extra_isize 执行健全性检查导致稍后访问无效地址请修复它。 - gc_data_segment - is_alive - data_blkaddr - offset_in_addr (CVE-2022-49738)

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

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

  - f2fs修正為對 is_alive() 中的 i_extra_isize 執行功能健全檢查 syzbot 發現一個 f2fs 錯誤錯誤KASANdata_blkaddr fs/f2fs/f2fs.h2891 中的 slab 超出邊界 [內嵌] 錯誤KASAN slab - is_alive fs/f2fs/gc.c:1117 中的超出邊界問題 [內嵌] 錯誤 KASANgc_data_segment fs/f2fs/gc.c:1520 中的 slab 超出邊界 [內嵌] 錯誤 KASANslab -do_garbage_collect+0x386a/0x3df0 fs/f2fs/gc.c:1734 中的超出邊界讀取位址 ffff888076557568 的大小 4 kworker/u4:3/52 CPU: 1 PID: 52 Comm: kworker/u4:3未受污染的 6.1.0-rc4-syzkaller-00362-gfef7fd48922d #0 硬體名稱: Google Google Compute Engine/Google Compute Engine、BIOS Google 2022 年 10 月 26 日 工作佇列 writeback wb_workfn (flush-7:0) 呼叫追踪 <TASK> __dump_stack lib/dump_stack.c:88 [內嵌] dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106 print_address_description mm/kasan/report.c:284 [內嵌] print_report+0x15e/0x45d mm/kasan/report.c:395 kasan_report+0xbb/0x1f0 mm/kasan/report.c:495 data_blkaddr fs/f2fs/f2fs.h:2891 [內嵌] is_alive fs/f2fs/gc.c:1 117 [內嵌] gc_data_segment fs/f2fs/gc.c:1520 [內嵌] do_garbage_collect+0x386a/0x3df0 fs/f2fs/gc.c:1734 f2fs_gc+0x88c/0x20a0 fs/f2fs/gc.c:1831 f2fs_balance_fs+0x544/0x60 fs/f2fs/segment.c:410 f2fs_write_inode+0x57e/0xe20 fs/f2fs/inode.c:753 write_inode fs/fs-writeback.c:1440 [內嵌]
    __writeback_single_inode+0xcfc/0x1440 fs/fs-writeback.c:1652 writeback_sb_inodes+0x54d/0xf90 fs/fs-writeback.c:1870 wb_writeback+0x2c5/0xd70 fs/fs-writeback.c:2044 wb_do_writeback fs/fs-writeback.c 2187 [內嵌] wb_workfn+0x2dc/0x12f0 fs/fs-writeback.c:2227 process_one_work+0x9bf/0x1710 kernel/workqueue.c:2289 worker_thread+0x665/0x1080 kernel/workqueue.c:2436 kthread+0x2e4/0x3a0 kernel/ kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306 根本原因是我們忘記對下列路徑中的 .i_extra_isize 執行功能健全檢查導致稍後存取無效位址。請修正該問題。 - gc_data_segment - is_alive - data_blkaddr - offset_in_addr (CVE-2022-49738)

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

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2025-987687 advisory.

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

    f2fs: fix to do sanity check on i_extra_isize in is_alive()

    syzbot found a f2fs bug:

    BUG: KASAN: slab-out-of-bounds in data_blkaddr fs/f2fs/f2fs.h:2891 [inline]     BUG: KASAN: slab-out-of-bounds in is_alive fs/f2fs/gc.c:1117 [inline]     BUG: KASAN: slab-out-of-bounds in gc_data_segment fs/f2fs/gc.c:1520 [inline]     BUG: KASAN: slab-out-of-bounds in do_garbage_collect+0x386a/0x3df0 fs/f2fs/gc.c:1734     Read of size 4 at addr ffff888076557568 by task kworker/u4:3/52

    CPU: 1 PID: 52 Comm: kworker/u4:3 Not tainted 6.1.0-rc4-syzkaller-00362-gfef7fd48922d #0     Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022     Workqueue: writeback wb_workfn (flush-7:0)     Call Trace:
    <TASK>
    __dump_stack lib/dump_stack.c:88 [inline]     dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106     print_address_description mm/kasan/report.c:284 [inline]     print_report+0x15e/0x45d mm/kasan/report.c:395     kasan_report+0xbb/0x1f0 mm/kasan/report.c:495     data_blkaddr fs/f2fs/f2fs.h:2891 [inline]     is_alive fs/f2fs/gc.c:1117 [inline]     gc_data_segment fs/f2fs/gc.c:1520 [inline]     do_garbage_collect+0x386a/0x3df0 fs/f2fs/gc.c:1734     f2fs_gc+0x88c/0x20a0 fs/f2fs/gc.c:1831     f2fs_balance_fs+0x544/0x6b0 fs/f2fs/segment.c:410     f2fs_write_inode+0x57e/0xe20 fs/f2fs/inode.c:753     write_inode fs/fs-writeback.c:1440 [inline]
    __writeback_single_inode+0xcfc/0x1440 fs/fs-writeback.c:1652     writeback_sb_inodes+0x54d/0xf90 fs/fs-writeback.c:1870     wb_writeback+0x2c5/0xd70 fs/fs-writeback.c:2044     wb_do_writeback fs/fs-writeback.c:2187 [inline]     wb_workfn+0x2dc/0x12f0 fs/fs-writeback.c:2227     process_one_work+0x9bf/0x1710 kernel/workqueue.c:2289     worker_thread+0x665/0x1080 kernel/workqueue.c:2436     kthread+0x2e4/0x3a0 kernel/kthread.c:376     ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306

    The root cause is that we forgot to do sanity check on .i_extra_isize     in below path, result in accessing invalid address later, fix it.
    - gc_data_segment
     - is_alive
      - data_blkaddr
       - offset_in_addr

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 Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - f2fs: fix to do sanity check on i_extra_isize in is_alive() syzbot found a f2fs bug: BUG: KASAN: slab-out-     of-bounds in data_blkaddr fs/f2fs/f2fs.h:2891 [inline] BUG: KASAN: slab-out-of-bounds in is_alive     fs/f2fs/gc.c:1117 [inline] BUG: KASAN: slab-out-of-bounds in gc_data_segment fs/f2fs/gc.c:1520 [inline]     BUG: KASAN: slab-out-of-bounds in do_garbage_collect+0x386a/0x3df0 fs/f2fs/gc.c:1734 Read of size 4 at     addr ffff888076557568 by task kworker/u4:3/52 CPU: 1 PID: 52 Comm: kworker/u4:3 Not tainted     6.1.0-rc4-syzkaller-00362-gfef7fd48922d #0 Hardware name: Google Google Compute Engine/Google Compute     Engine, BIOS Google 10/26/2022 Workqueue: writeback wb_workfn (flush-7:0) Call Trace: <TASK> __dump_stack     lib/dump_stack.c:88 [inline] dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106 print_address_description     mm/kasan/report.c:284 [inline] print_report+0x15e/0x45d mm/kasan/report.c:395 kasan_report+0xbb/0x1f0     mm/kasan/report.c:495 data_blkaddr fs/f2fs/f2fs.h:2891 [inline] is_alive fs/f2fs/gc.c:1117 [inline]     gc_data_segment fs/f2fs/gc.c:1520 [inline] do_garbage_collect+0x386a/0x3df0 fs/f2fs/gc.c:1734     f2fs_gc+0x88c/0x20a0 fs/f2fs/gc.c:1831 f2fs_balance_fs+0x544/0x6b0 fs/f2fs/segment.c:410     f2fs_write_inode+0x57e/0xe20 fs/f2fs/inode.c:753 write_inode fs/fs-writeback.c:1440 [inline]
    __writeback_single_inode+0xcfc/0x1440 fs/fs-writeback.c:1652 writeback_sb_inodes+0x54d/0xf90 fs/fs-     writeback.c:1870 wb_writeback+0x2c5/0xd70 fs/fs-writeback.c:2044 wb_do_writeback fs/fs-writeback.c:2187     [inline] wb_workfn+0x2dc/0x12f0 fs/fs-writeback.c:2227 process_one_work+0x9bf/0x1710     kernel/workqueue.c:2289 worker_thread+0x665/0x1080 kernel/workqueue.c:2436 kthread+0x2e4/0x3a0     kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306 The root cause is that we     forgot to do sanity check on .i_extra_isize in below path, result in accessing invalid address later, fix     it. - gc_data_segment - is_alive - data_blkaddr - offset_in_addr (CVE-2022-49738)

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

ID	Name	Product	Family	Published	Updated	Severity
272896	Unity Linux 20.1070a Security Update: kernel (UTSA-2025-989015)	Nessus	Unity Linux Local Security Checks	11/5/2025	11/5/2025	high
247636	Linux Distros のパッチ未適用の脆弱性: CVE-2022-49738	Nessus	Misc.	8/10/2025	10/28/2025	high
247636	Linux Distros 未修补的漏洞：CVE-2022-49738	Nessus	Misc.	8/10/2025	10/28/2025	high
247636	Linux Distros 未修補的弱點：CVE-2022-49738	Nessus	Misc.	8/10/2025	10/28/2025	high
271069	Unity Linux 20.1070e Security Update: kernel (UTSA-2025-987687)	Nessus	Unity Linux Local Security Checks	10/21/2025	10/21/2025	high
247636	Linux Distros Unpatched Vulnerability : CVE-2022-49738	Nessus	Misc.	8/10/2025	10/28/2025	high

Detections

Analytics

Plugins Search

high

high

high

high

high

high