There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - In the Linux kernel, the following vulnerability has been resolved: btrfs: do not ASSERT() when the fs
    flips RO inside btrfs_repair_io_failure() [BUG] There is a bug report that when btrfs hits ENOSPC error in
    a critical path, btrfs flips RO (this part is expected, although the ENOSPC bug still needs to be
    addressed). The problem is after the RO flip, if there is a read repair pending, we can hit the ASSERT()
    inside btrfs_repair_io_failure() like the following: BTRFS info (device vdc): relocating block group
    30408704 flags metadata|raid1 ------------[ cut here ]------------ BTRFS: Transaction aborted (error -28)
    WARNING: fs/btrfs/extent-tree.c:3235 at __btrfs_free_extent.isra.0+0x453/0xfd0, CPU#1: btrfs/383844
    Modules linked in: kvm_intel kvm irqbypass [...] ---[ end trace 0000000000000000 ]--- BTRFS info (device
    vdc state EA): 2 enospc errors during balance BTRFS info (device vdc state EA): balance: ended with
    status: -30 BTRFS error (device vdc state EA): parent transid verify failed on logical 30556160 mirror 2
    wanted 8 found 6 BTRFS error (device vdc state EA): bdev /dev/nvme0n1 errs: wr 0, rd 0, flush 0, corrupt
    10, gen 0 [...] assertion failed: !(fs_info->sb->s_flags & SB_RDONLY) :: 0, in fs/btrfs/bio.c:938
    ------------[ cut here ]------------ assertion failed: !(fs_info->sb->s_flags & SB_RDONLY) :: 0, in
    fs/btrfs/bio.c:938 kernel BUG at fs/btrfs/bio.c:938! Oops: invalid opcode: 0000 [#1] SMP NOPTI CPU: 0 UID:
    0 PID: 868 Comm: kworker/u8:13 Tainted: G W N 6.19.0-rc6+ #4788 PREEMPT(full) Tainted: [W]=WARN, [N]=TEST
    Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.17.0-0-gb52ca86e094d-prebuilt.qemu.org
    04/01/2014 Workqueue: btrfs-endio simple_end_io_work RIP: 0010:btrfs_repair_io_failure.cold+0xb2/0x120
    RSP: 0000:ffffc90001d2bcf0 EFLAGS: 00010246 RAX: 0000000000000051 RBX: 0000000000001000 RCX:
    0000000000000000 RDX: 0000000000000000 RSI: ffffffff8305cf42 RDI: 00000000ffffffff RBP: 0000000000000002
    R08: 00000000fffeffff R09: ffffffff837fa988 R10: ffffffff8327a9e0 R11: 6f69747265737361 R12:
    ffff88813018d310 R13: ffff888168b8a000 R14: ffffc90001d2bd90 R15: ffff88810a169000 FS:
    0000000000000000(0000) GS:ffff8885e752c000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0:
    0000000080050033 ------------[ cut here ]------------ [CAUSE] The cause of -ENOSPC error during the test
    case btrfs/124 is still unknown, although it's known that we still have cases where metadata can be over-
    committed but can not be fulfilled correctly, thus if we hit such ENOSPC error inside a critical path, we
    have no choice but abort the current transaction. This will mark the fs read-only. The problem is inside
    the btrfs_repair_io_failure() path that we require the fs not to be mount read-only. This is normally
    fine, but if we are doing a read-repair meanwhile the fs flips RO due to a critical error, we can enter
    btrfs_repair_io_failure() with super block set to read-only, thus triggering the above crash. [FIX] Just
    replace the ASSERT() with a proper return if the fs is already read-only. (CVE-2026-43299)

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

  - btrfs：當 fs 翻轉 btrfs_repair_io_failure（） 內的 RO 時，不要 ASSERT（） [錯誤] 有一個錯誤報告，當 btrfs 在關鍵路徑中遇到 ENOSPC 錯誤時，btrfs 會翻轉 RO （這部分是預期的，儘管 ENOSPC 錯誤仍需要解決）。問題是 RO 翻轉後，如果有待處理的讀取修復，我們可以按 btrfs_repair_io_failure（） 內的 ASSERT（），如下所示： BTRFS 資訊 （裝置 vdc）：重新定位區塊群組 30408704 旗標 metadata|raid1 ------------[ 切到這裡 ]------------ BTRFS：
    交易中止 （錯誤 -28） 警告：fs/btrfs/extent-tree.c：3235
    __btrfs_free_extent.isra.0+0x453/0xfd0， CPU#1： btrfs/383844 連結的模組：kvm_intel kvm irqbypass [...] ---[ 結束追蹤 00000000000000000000 ]--- BTRFS 資訊（裝置 vdc 狀態 EA）：平衡期間發生 2 個 enospc 錯誤 BTRFS 資訊（裝置 vdc 狀態 EA）：餘額：以狀態結束：-30 BTRFS 錯誤（裝置 vdc 狀態 EA）：邏輯 30556160 鏡像上的父 transid 驗證失敗 2 想要 8 找到 6 BTRFS 錯誤（裝置 vdc 狀態 EA）： bdev /dev/nvme0n1 錯誤：WR 0、RD 0、排清 0、損毀 10、gen 0 [...] 宣告失敗：
    !（fs_info->sb->s_flags &; SB_RDONLY） ：： 0， in fs/btrfs/bio.c：938 ------------[ 切到這裡 ]------------斷言失敗： ！（fs_info->sb->s_flags &; SB_RDONLY） ：： 0，在 fs/btrfs/bio.c：938 中，fs/btrfs/bio.c：938 的核心錯誤！哎呀：無效的操作碼：0000 [#1] SMP NOPTI CPU：0 UID：0 PID：868 通訊：kworker/u8：13 污染：G W N 6.19.0-rc6+ #4788 搶佔（完整） 污染：[W]=WARN，[N]=TEST 硬體名稱：QEMU 標準電腦 （Q35 + ICH9,2009），BIOS rel-1.17.0-0-gb52ca86e094d-prebuilt.qemu.org 2014 年 4 月 1 日 工作佇列：btrfs-endio simple_end_io_work RIP：0010：btrfs_repair_io_failure.cold+0xb2/0x120 RSP：0000：ffffc90001d2bcf0 EFLAGS：
    00010246 RAX：0000000000000051 RBX：0000000000001000 RCX：0000000000000000000 RDX：000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    ffffffff8305cf42 RDI： 00000000ffffffff RBP： 0000000000000002 ： 00000000fffeffff R09： ffffffff837fa988 R10： ffffffff8327a9e0 R11： 6f69747265737361 R12： ffff88813018d310 R13： ffff888168b8a000 R14：R08
    ffffc90001d2bd90 R15： ffff88810a169000 FS： 000000000000000000（0000） GS：ffff8885e752c000（0000） knlGS：000000000000000000 CS：0010 DS：0000 ES：0000 CR0：0000000080050033 ------------[ 切到這裡]------------ [原因] 測試用例 btrfs/124 期間 -ENOSPC 錯誤的原因仍然未知，儘管已知我們仍然存在元數據可能被過度提交但無法正確滿足的情況，因此，如果我們在關鍵路徑中遇到此類 ENOSPC 錯誤， 我們別無選擇，只能中止當前的交易。這會將 fs 標記為唯讀。問題出在 btrfs_repair_io_failure（） 路徑內部，我們要求 fs 不是掛載唯讀。這通常沒問題，但如果我們在進行讀取修復的同時，fs 由於嚴重錯誤而翻轉 RO，我們可以輸入 btrfs_repair_io_failure（），並將超級區塊設定為唯讀，從而觸發上述崩潰。[修復]如果 fs 已經是唯讀的，只需將 ASSERT（） 替換為適當的傳回符即可。（CVE-2026-43299）

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

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

  - btrfs：当 fs 翻转 btrfs_repair_io_failure（） 中的 RO 时，不 ASSERT（） [缺陷] 有缺陷报告指出，当 btrfs 在关键路径中发生 ENOSPC 错误时，btrfs 会翻转 RO（这部分是预期的，尽管仍需要解决 ENOSPC 缺陷）。问题在于在 RO 翻转之后，如果存在待定的读取修复，我们可以点击 btrfs_repair_io_failure（） 中的 ASSERT（），如下所示： BTRFS 信息 （设备 vdc）：重新定位块群组 30408704 标记元数据|raid1 ------------[ 切中 ]------------ BTRFS：
    事务已中止（错误 -28） 警告：fs/btrfs/extent-tree.c：3235 at
    __btrfs_free_extent.isra.0+0x453/0xfd0， CPU#1： btrfs/383844 模块链接于： kvm_intel kvm irqbypass [...] ---[ end trace 00000000000000000 ]--- BTRFS 信息（设备 vdc 状态 EA）：平衡期间出现 2 个 enospc 错误 BTRFS 信息（设备 vdc 状态 EA）：平衡：以状态结束： -30 BTRFS 错误（设备 vdc 状态 EA）：逻辑 30556160 镜像上的父 transid 验证失败 2 想要 8 发现 6 BTRFS 错误（设备 vdc 状态 EA）： bdev /dev/nvme0n1 错误：WR 0、RD 0、刷新 0、损坏 10、gen 0 [...] 断言失败：
    !（fs_info->sb->s_flags &; SB_RDONLY） ：： 0， in fs/btrfs/bio.c：938 ------------[ cut here ]------------断言失败： ！（fs_info->sb->s_flags &; SB_RDONLY） ：： 0，fs/btrfs/bio.c：938 中的内核缺陷 fs/btrfs/bio.c：938！Oops： invalid opcode： 0000 [#1] SMP NOPTI CPU： 0 UID： 0 PID： 868 Comm： kworker/u8：13 受感染： G W N 6.19.0-rc6+ #4788 PREEMPT（full） 受感染： [W]=WARN， [N]=TEST 硬件名称： QEMU Standard PC （Q35 + ICH9， 2009）， BIOS rel-1.17.0-0-gb52ca86e094d-prebuilt.qemu.org 04/01/2014 工作队列： btrfs-endio simple_end_io_work RIP： 0010：btrfs_repair_io_failure.cold+0xb2/0x120 RSP： 0000：ffffc90001d2bcf0 EFLAGS：
    00010246 RAX：0000000000000051 RBX：0000000000001000 RCX：0000000000000000 RDX：00000000000000000 RSI：
    ffffffff8305cf42 RDI： 000000000ffffffff RBP： 0000000000000002 ： 000000000fffeffff R09： ffffffff837fa988 R10： ffffffff8327a9e0 R11： 6f69747265737361 R12： ffff88813018d310 R13： ffff888168b8a000R14：R08
    ffffc90001d2bd90 R15：ffff88810a169000 FS：0000000000000000（0000） GS：ffff8885e752c000（0000） knlGS：000000000000000 CS：0010 DS：0000 ES：0000 CR0：0000000080050033 ------------[ cut here]------------ [CAUSE] 测试用例 btrfs/124 期间发生 -ENOSPC 错误的原因仍然未知，不过众所周知，仍有元数据可过度使用但无法正确履行的情况，因此，如果在关键路径中遇到此类 ENOSPC 错误， 我们别无选择，只能中止当前的交易。这会将 fs 标记为只读。问题出在 btrfs_repair_io_failure（） 路径内部，我们要求 fs 不得挂载为只读。这通常没问题，但如果我们在进行读取-修复的同时，fs 由于严重错误而翻转 RO，我们可以输入 btrfs_repair_io_failure（），并将超级块设置为只读，从而触发上述崩溃。[修复]如果 fs 已经是只读，只需将 ASSERT（） 替换为正确的返回函数即可。（CVE-2026-43299）

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

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

  - btrfs:fs が btrfs_repair_io_failure() 内の RO を反転させるときに ASSERT() しません [バグ] btrfs がクリティカルパスで ENOSPC エラーにヒットすると、btrfs が RO を反転させるというバグレポートがあります(この部分は想定事項ですが、ENOSPC バグにはまだ対処する必要があります)。問題は、ROフリップ後、保留中の読み取り修復がある場合、次のようにbtrfs_repair_io_failure()内のASSERT()をヒットする可能性があります。BTRFS情報(デバイスvdc):ブロックグループ30408704フラグメタデータの再配置|raid1------------[切り取り]------------ BTRFS:
    トランザクション中止(エラー -28)警告:fs/btrfs/extent-tree.c:3235
    __btrfs_free_extent.isra.0+0x453/0xfd0、 CPU#1:btrfs/383844 リンクされているモジュール:kvm_intel kvm irqbypass [...] ---[ エンドトレース 000000000000000000 ]--- BTRFS 情報(デバイス vdc 状態 EA):バランス中の 2 enospc エラー BTRFS 情報(デバイス vdc 状態 EA):バランス:ステータスで終了:-30 BTRFS エラー(デバイス vdc 状態 EA):論理 30556160 ミラー 2 で親 transid 検証が失敗しました 8 が 6 BTRFS エラー(デバイス vdc 状態 EA): bdev /dev/nvme0n1 エラー:WR 0、RD 0、フラッシュ 0、破損 10、Gen 0 [...] アサーションが失敗しました:
    !(fs_info->sb->s_flags &; SB_RDONLY) :: 0、in fs/btrfs/bio.c:938 ------------[ cut here ]------------ アサーションが失敗しました: !(fs_info->sb->s_flags &; SB_RDONLY) :: 0、fs/btrfs/bio.c:938 のカーネルバグ at fs/btrfs/bio.c:938! Oops:無効な opcode:0000 [#1] SMP NOPTI CPU:0 UID:0 PID:868 Comm:kworker/u8:13 汚染:G W N 6.19.0-rc6+ #4788 PREEMPT(full) 汚染:[W]=WARN、[N]=TEST ハードウェア名:QEMU Standard PC(Q35 + ICH9、2009)、BIOS rel-1.17.0-0-gb52ca86e094d-prebuilt.qemu.org 04/01/2014 Workqueue:btrfs-endio simple_end_io_work RIP:0010:btrfs_repair_io_failure.cold+0xb2/0x120 RSP:0000:ffffc90001d2bcf0 EFLAGS:
    00010246 RAX: 0000000000000051 RBX: 0000000000001000 RCX: 000000000000000000 RDX: 0000000000000000000 RSI:
    ffffffff8305cf42 RDI: 000000000ffffffff RBP: 0000000000000002 R08: 000000000fffeffffff R09: ffffffff837fa988 R10: ffffffff8327a9e0 R11: 6f69747265737361 R12: ffff88813018d310 R13: ffff888168b8a000 R14:
    ffffc90001d2bd90 R15: ffff88810a169000 FS: 00000000000000000(0000) GS:ffff8885e752c000(0000) knlGS:0000000000000000 CS:0010 DS:0000 ES: 0000 CR0: 0000000080050033 ------------[ cut here]------------ [原因] テストケース btrfs/124 中の -ENOSPC エラーの原因はまだ不明ですが、メタデータがオーバーコミットされる可能性があるが、正しく履行できない場合が依然としてあることが知られています。このため、クリティカルパス内でそのような ENOSPC エラーに遭遇すると、 現在の取引を中止するしかありません。これにより、fs が読み取り専用としてマークされます。問題は btrfs_repair_io_failure() パスの内部にあるため、fs は読み取り専用マウントでないようにする必要があります。これは通常問題ありませんが、重大なエラーにより fs が RO を反転する間に読み取りリペアを行っている場合、スーパーブロックを読み取り専用に設定して btrfs_repair_io_failure() と入力し、上記のクラッシュを発生させる可能性があります。[修正]fs が既に読み取り専用の場合は、ASSERT() を適切な戻り値に置き換えてください。(CVE-2026-43299)

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

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

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

    btrfs: do not ASSERT() when the fs flips RO inside btrfs_repair_io_failure()

    [BUG]     There is a bug report that when btrfs hits ENOSPC error in a critical     path, btrfs flips RO (this part is expected, although the ENOSPC bug     still needs to be addressed).

    The problem is after the RO flip, if there is a read repair pending, we     can hit the ASSERT() inside btrfs_repair_io_failure() like the following:

      BTRFS info (device vdc): relocating block group 30408704 flags metadata|raid1
      ------------[ cut here ]------------       BTRFS: Transaction aborted (error -28)       WARNING: fs/btrfs/extent-tree.c:3235 at __btrfs_free_extent.isra.0+0x453/0xfd0, CPU#1: btrfs/383844       Modules linked in: kvm_intel kvm irqbypass       [...]
      ---[ end trace 0000000000000000 ]---       BTRFS info (device vdc state EA): 2 enospc errors during balance       BTRFS info (device vdc state EA): balance: ended with status: -30       BTRFS error (device vdc state EA): parent transid verify failed on logical 30556160 mirror 2 wanted 8     found 6       BTRFS error (device vdc state EA): bdev /dev/nvme0n1 errs: wr 0, rd 0, flush 0, corrupt 10, gen 0       [...]       assertion failed: !(fs_info->sb->s_flags & SB_RDONLY) :: 0, in fs/btrfs/bio.c:938
      ------------[ cut here ]------------       assertion failed: !(fs_info->sb->s_flags & SB_RDONLY) :: 0, in fs/btrfs/bio.c:938       kernel BUG at fs/btrfs/bio.c:938!       Oops: invalid opcode: 0000 [#1] SMP NOPTI       CPU: 0 UID: 0 PID: 868 Comm: kworker/u8:13 Tainted: G        W        N  6.19.0-rc6+ #4788 PREEMPT(full)       Tainted: [W]=WARN, [N]=TEST       Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.17.0-0-gb52ca86e094d-prebuilt.qemu.org     04/01/2014       Workqueue: btrfs-endio simple_end_io_work       RIP: 0010:btrfs_repair_io_failure.cold+0xb2/0x120       RSP: 0000:ffffc90001d2bcf0 EFLAGS: 00010246       RAX: 0000000000000051 RBX: 0000000000001000 RCX: 0000000000000000       RDX: 0000000000000000 RSI: ffffffff8305cf42 RDI: 00000000ffffffff       RBP: 0000000000000002 R08: 00000000fffeffff R09: ffffffff837fa988       R10: ffffffff8327a9e0 R11: 6f69747265737361 R12: ffff88813018d310       R13: ffff888168b8a000 R14: ffffc90001d2bd90 R15: ffff88810a169000       FS:  0000000000000000(0000) GS:ffff8885e752c000(0000) knlGS:0000000000000000       CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
      ------------[ cut here ]------------

    [CAUSE]     The cause of -ENOSPC error during the test case btrfs/124 is still     unknown, although it's known that we still have cases where metadata can     be over-committed but can not be fulfilled correctly, thus if we hit     such ENOSPC error inside a critical path, we have no choice but abort     the current transaction.

    This will mark the fs read-only.

    The problem is inside the btrfs_repair_io_failure() path that we require     the fs not to be mount read-only. This is normally fine, but if we are     doing a read-repair meanwhile the fs flips RO due to a critical error,     we can enter btrfs_repair_io_failure() with super block set to     read-only, thus triggering the above crash.

    [FIX]     Just replace the ASSERT() with a proper return if the fs is already     read-only.

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.

  - btrfs: do not ASSERT() when the fs flips RO inside btrfs_repair_io_failure() [BUG] There is a bug report     that when btrfs hits ENOSPC error in a critical path, btrfs flips RO (this part is expected, although the     ENOSPC bug still needs to be addressed). The problem is after the RO flip, if there is a read repair     pending, we can hit the ASSERT() inside btrfs_repair_io_failure() like the following: BTRFS info (device     vdc): relocating block group 30408704 flags metadata|raid1 ------------[ cut here ]------------ BTRFS:
    Transaction aborted (error -28) WARNING: fs/btrfs/extent-tree.c:3235 at
    __btrfs_free_extent.isra.0+0x453/0xfd0, CPU#1: btrfs/383844 Modules linked in: kvm_intel kvm irqbypass     [...] ---[ end trace 0000000000000000 ]--- BTRFS info (device vdc state EA): 2 enospc errors during     balance BTRFS info (device vdc state EA): balance: ended with status: -30 BTRFS error (device vdc state     EA): parent transid verify failed on logical 30556160 mirror 2 wanted 8 found 6 BTRFS error (device vdc     state EA): bdev /dev/nvme0n1 errs: wr 0, rd 0, flush 0, corrupt 10, gen 0 [...] assertion failed:
    !(fs_info->sb->s_flags & SB_RDONLY) :: 0, in fs/btrfs/bio.c:938 ------------[ cut here ]------------     assertion failed: !(fs_info->sb->s_flags & SB_RDONLY) :: 0, in fs/btrfs/bio.c:938 kernel BUG at     fs/btrfs/bio.c:938! Oops: invalid opcode: 0000 [#1] SMP NOPTI CPU: 0 UID: 0 PID: 868 Comm: kworker/u8:13     Tainted: G W N 6.19.0-rc6+ #4788 PREEMPT(full) Tainted: [W]=WARN, [N]=TEST Hardware name: QEMU Standard PC     (Q35 + ICH9, 2009), BIOS rel-1.17.0-0-gb52ca86e094d-prebuilt.qemu.org 04/01/2014 Workqueue: btrfs-endio     simple_end_io_work RIP: 0010:btrfs_repair_io_failure.cold+0xb2/0x120 RSP: 0000:ffffc90001d2bcf0 EFLAGS:
    00010246 RAX: 0000000000000051 RBX: 0000000000001000 RCX: 0000000000000000 RDX: 0000000000000000 RSI:
    ffffffff8305cf42 RDI: 00000000ffffffff RBP: 0000000000000002 R08: 00000000fffeffff R09: ffffffff837fa988     R10: ffffffff8327a9e0 R11: 6f69747265737361 R12: ffff88813018d310 R13: ffff888168b8a000 R14:
    ffffc90001d2bd90 R15: ffff88810a169000 FS: 0000000000000000(0000) GS:ffff8885e752c000(0000)     knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 ------------[ cut here     ]------------ [CAUSE] The cause of -ENOSPC error during the test case btrfs/124 is still unknown, although     it's known that we still have cases where metadata can be over-committed but can not be fulfilled     correctly, thus if we hit such ENOSPC error inside a critical path, we have no choice but abort the     current transaction. This will mark the fs read-only. The problem is inside the btrfs_repair_io_failure()     path that we require the fs not to be mount read-only. This is normally fine, but if we are doing a read-     repair meanwhile the fs flips RO due to a critical error, we can enter btrfs_repair_io_failure() with     super block set to read-only, thus triggering the above crash. [FIX] Just replace the ASSERT() with a     proper return if the fs is already read-only. (CVE-2026-43299)

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

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

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

    btrfs: do not ASSERT() when the fs flips RO inside btrfs_repair_io_failure()

    [BUG]     There is a bug report that when btrfs hits ENOSPC error in a critical     path, btrfs flips RO (this part is expected, although the ENOSPC bug     still needs to be addressed).

    The problem is after the RO flip, if there is a read repair pending, we     can hit the ASSERT() inside btrfs_repair_io_failure() like the following:

      BTRFS info (device vdc): relocating block group 30408704 flags metadata|raid1
      ------------[ cut here ]------------       BTRFS: Transaction aborted (error -28)       WARNING: fs/btrfs/extent-tree.c:3235 at __btrfs_free_extent.isra.0+0x453/0xfd0, CPU#1: btrfs/383844       Modules linked in: kvm_intel kvm irqbypass       [...]
      ---[ end trace 0000000000000000 ]---       BTRFS info (device vdc state EA): 2 enospc errors during balance       BTRFS info (device vdc state EA): balance: ended with status: -30       BTRFS error (device vdc state EA): parent transid verify failed on logical 30556160 mirror 2 wanted 8     found 6       BTRFS error (device vdc state EA): bdev /dev/nvme0n1 errs: wr 0, rd 0, flush 0, corrupt 10, gen 0       [...]       assertion failed: !(fs_info->sb->s_flags & SB_RDONLY) :: 0, in fs/btrfs/bio.c:938
      ------------[ cut here ]------------       assertion failed: !(fs_info->sb->s_flags & SB_RDONLY) :: 0, in fs/btrfs/bio.c:938       kernel BUG at fs/btrfs/bio.c:938!       Oops: invalid opcode: 0000 [#1] SMP NOPTI       CPU: 0 UID: 0 PID: 868 Comm: kworker/u8:13 Tainted: G        W        N  6.19.0-rc6+ #4788 PREEMPT(full)       Tainted: [W]=WARN, [N]=TEST       Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.17.0-0-gb52ca86e094d-prebuilt.qemu.org     04/01/2014       Workqueue: btrfs-endio simple_end_io_work       RIP: 0010:btrfs_repair_io_failure.cold+0xb2/0x120       RSP: 0000:ffffc90001d2bcf0 EFLAGS: 00010246       RAX: 0000000000000051 RBX: 0000000000001000 RCX: 0000000000000000       RDX: 0000000000000000 RSI: ffffffff8305cf42 RDI: 00000000ffffffff       RBP: 0000000000000002 R08: 00000000fffeffff R09: ffffffff837fa988       R10: ffffffff8327a9e0 R11: 6f69747265737361 R12: ffff88813018d310       R13: ffff888168b8a000 R14: ffffc90001d2bd90 R15: ffff88810a169000       FS:  0000000000000000(0000) GS:ffff8885e752c000(0000) knlGS:0000000000000000       CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
      ------------[ cut here ]------------

    [CAUSE]     The cause of -ENOSPC error during the test case btrfs/124 is still     unknown, although it's known that we still have cases where metadata can     be over-committed but can not be fulfilled correctly, thus if we hit     such ENOSPC error inside a critical path, we have no choice but abort     the current transaction.

    This will mark the fs read-only.

    The problem is inside the btrfs_repair_io_failure() path that we require     the fs not to be mount read-only. This is normally fine, but if we are     doing a read-repair meanwhile the fs flips RO due to a critical error,     we can enter btrfs_repair_io_failure() with super block set to     read-only, thus triggering the above crash.

    [FIX]     Just replace the ASSERT() with a proper return if the fs is already     read-only.

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.

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
472554	Chainguard: linux-qemu-melange: security update to 6.18.49-r2	Tenable Cloud Security	Chainguard Local Security Checks	2026/10/3	2026/10/22	medium
472554	Chainguard: linux-qemu-melange: security update to 6.18.49-r2	Tenable Self-Hosted Container Security	Chainguard Local Security Checks	2026/10/3	2026/10/22	medium
313384	Linux Distros 未修補的弱點：CVE-2026-43299	Nessus	Misc.	2026/5/8	2026/10/12	medium
313384	Linux Distros 未修补的漏洞：CVE-2026-43299	Nessus	Misc.	2026/5/8	2026/10/12	medium
350138	openSUSE 16:cluster-md-kmp-64kb / cluster-md-kmp-azure / cluster-md-kmp-default / etc (openSUSE-SU-2026:21910-1)	Nessus	SuSE Local Security Checks	2026/9/25	2026/9/28	high
313384	Linux Distros のパッチ未適用の脆弱性: CVE-2026-43299	Nessus	Misc.	2026/5/8	2026/10/12	medium
340429	Unity Linux 20.1050a Security Update: kernel (UTSA-2026-098805)	Nessus	Unity Linux Local Security Checks	2026/8/26	2026/8/28	medium
350138	openSUSE 16: cluster-md-kmp-64kb / cluster-md-kmp-azure / cluster-md-kmp-default / etc (openSUSE-SU-2026:21910-1)	Nessus	SuSE Local Security Checks	2026/9/25	2026/9/28	high
313384	Linux Distros Unpatched Vulnerability : CVE-2026-43299	Nessus	Misc.	2026/5/8	2026/10/12	medium
337325	Unity Linux 20.1050e Security Update: kernel (UTSA-2026-102111)	Nessus	Unity Linux Local Security Checks	2026/8/18	2026/8/18	medium

检测

插件搜索

medium

medium

medium

medium

high

medium

medium

high

medium

medium