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

  - btrfs: skip reserved bytes warning on unmount after log cleanup failure After the recent changes made by     commit c2e39305299f01 (btrfs: clear extent buffer uptodate when we fail to write it) and its followup     fix, commit 651740a5024117 (btrfs: check WRITE_ERR when trying to read an extent buffer), we can now end     up not cleaning up space reservations of log tree extent buffers after a transaction abort happens, as     well as not cleaning up still dirty extent buffers. This happens because if writeback for a log tree     extent buffer failed, then we have cleared the bit EXTENT_BUFFER_UPTODATE from the extent buffer and we     have also set the bit EXTENT_BUFFER_WRITE_ERR on it. Later on, when trying to free the log tree with     free_log_tree(), which iterates over the tree, we can end up getting an -EIO error when trying to read a     node or a leaf, since read_extent_buffer_pages() returns -EIO if an extent buffer does not have     EXTENT_BUFFER_UPTODATE set and has the EXTENT_BUFFER_WRITE_ERR bit set. Getting that -EIO means that we     return immediately as we can not iterate over the entire tree. In that case we never update the reserved     space for an extent buffer in the respective block group and space_info object. When this happens we get     the following traces when unmounting the fs: [174957.284509] BTRFS: error (device dm-0) in     cleanup_transaction:1913: errno=-5 IO failure [174957.286497] BTRFS: error (device dm-0) in     free_log_tree:3420: errno=-5 IO failure [174957.399379] ------------[ cut here ]------------     [174957.402497] WARNING: CPU: 2 PID: 3206883 at fs/btrfs/block-group.c:127 btrfs_put_block_group+0x77/0xb0     [btrfs] [174957.407523] Modules linked in: btrfs overlay dm_zero (...) [174957.424917] CPU: 2 PID: 3206883     Comm: umount Tainted: G W 5.16.0-rc5-btrfs-next-109 #1 [174957.426689] Hardware name: QEMU Standard PC     (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014 [174957.428716] RIP:
    0010:btrfs_put_block_group+0x77/0xb0 [btrfs] [174957.429717] Code: 21 48 8b bd (...) [174957.432867] RSP:
    0018:ffffb70d41cffdd0 EFLAGS: 00010206 [174957.433632] RAX: 0000000000000001 RBX: ffff8b09c3848000 RCX:
    ffff8b0758edd1c8 [174957.434689] RDX: 0000000000000001 RSI: ffffffffc0b467e7 RDI: ffff8b0758edd000     [174957.436068] RBP: ffff8b0758edd000 R08: 0000000000000000 R09: 0000000000000000 [174957.437114] R10:
    0000000000000246 R11: 0000000000000000 R12: ffff8b09c3848148 [174957.438140] R13: ffff8b09c3848198 R14:
    ffff8b0758edd188 R15: dead000000000100 [174957.439317] FS: 00007f328fb82800(0000)     GS:ffff8b0a2d200000(0000) knlGS:0000000000000000 [174957.440402] CS: 0010 DS: 0000 ES: 0000 CR0:
    0000000080050033 [174957.441164] CR2: 00007fff13563e98 CR3: 0000000404f4e005 CR4: 0000000000370ee0     [174957.442117] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [174957.443076] DR3:
    0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [174957.443948] Call Trace: [174957.444264]     <TASK> [174957.444538] btrfs_free_block_groups+0x255/0x3c0 [btrfs] [174957.445238] close_ctree+0x301/0x357     [btrfs] [174957.445803] ? call_rcu+0x16c/0x290 [174957.446250] generic_shutdown_super+0x74/0x120     [174957.446832] kill_anon_super+0x14/0x30 [174957.447305] btrfs_kill_super+0x12/0x20 [btrfs]     [174957.447890] deactivate_locked_super+0x31/0xa0 [174957.448440] cleanup_mnt+0x147/0x1c0 [174957.448888]     task_work_run+0x5c/0xa0 [174957.449336] exit_to_user_mode_prepare+0x1e5/0x1f0 [174957.449934]     syscall_exit_to_user_mode+0x16/0x40 [174957.450512] do_syscall_64+0x48/0xc0 [174957.450980]     entry_SYSCALL_64_after_hwframe+0x44/0xae [174957.451605] RIP: 0033:0x7f328fdc4a97 [174957.452059] Code: 03     0c 00 f7 (...) [174957.454320] RSP: 002b:00007fff13564ec8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6     [174957.455262] RAX: 0000000000000000 RBX: 00007f328feea264 RCX: 00007f328fdc4a97 [174957.456131] RDX:
    0000000000000000 RSI: 00000000000000 ---truncated--- (CVE-2022-48833)

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

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

  - btrfsログクリーンアップ失敗後のアンマウントで、予約されたバイトの警告をスキップします。コミット c2e39305299f01btrfs書き込みに失敗した場合はエクステントバッファの更新をクリアしますとそのフォローアップ修正により、コミット 651740a5024117btrfs書き込みを行う際に WRITE_ERR をチェックしますエクステントバッファの読み取り) を引き起こした場合、トランザクション中止の発生後に、ログツリーエクステントバッファのスペース予約をクリーンアップせず、またダーティなエクステントバッファをクリーンアップしないままになる可能性があります。これは、ログツリーエクステントバッファへの書き戻しが失敗した場合に、エクステントバッファからビット EXTENT_BUFFER_UPTODATE がクリアされ、さらにビット EXTENT_BUFFER_WRITE_ERR がそれに設定されるために発生します。後に、ツリー上で反復する free_log_tree() でログツリーを解放しようとすると、read_extent_buffer_pages() が -EIO を返すため、ノードまたはリーフを読み取ろうとしたときに -EIO エラーが発生する可能性があります。これは、read_extent_buffer_pages() が -EIO を返すためです。バッファには EXTENT_BUFFER_UPTODATE が設定されておらず、EXTENT_BUFFER_WRITE_ERR ビットが設定されています。-EIO の取得は、ツリー全体を反復できないため、すぐに返すことを意味します。その場合、それぞれのブロックグループおよび space_info オブジェクト内のエクステントバッファ用に予約されたスペースが更新されることはありません。この状況が発生すると、fs をアンマウントするときに次のトレースが生じます [174957.284509] BTRFSエラーデバイス dm-0cleanup_transaction:1913 における errno=-5 IO エラー [174957.286497] BTRFSエラーデバイス dm-0 free_log_tree:3420errno=-5 IO エラー [174957.399379] ------------[ ] ここで挿入 ]----------------------- [174957.402497] 警告CPU 2 PID3206883 at fs/btrfs/block-group.c:127 btrfs_put_block_group+0x77/0xb0 [btrfs] [174957.407523] リンクされているモジュールbtrfs overlay dm_zero...[174957.424917] CPU2 PID 3206883 通信umount汚染GW 5.16.0-rc5-btrfs-next-109 #1174957.426689ハードウェア名QEMU Standard PCi440FX + PIIX、1996、BIOS rel-1.14.0-0-g155821a1990b-prebuilt .qemu.org 04/01/2014 [174957.428716] RIP
    0010:btrfs_put_block_group+0x77/0xb0 [btrfs] [174957.429717] コード21 48 8b bd...[174957.432867] RSP
    0018:ffffb70d41cffdd0 EFLAGS: 00010206 [174957.433632] RAX: 000000000000000 RBX: ffff8b09c3848000 RCX:
    ffff8b0758edd1c8 [174957.434689] RDX: 0000000000000001 RSI: ffffffffc0b467e7 RDI: R10ffff8b0758edd000 [174957.436068] RBP: ffff8b0758edd000174957.437114R08R0900000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    000000000000246 R110000000000000000 R12ffff8b09c3848148 [174957.438140] R13ffff8b09c3848198 R14
    ffff8b0758edd188 R15ded00000000100 [174957.439317] FS:00007f328fb82800(0000) GS:ffff8b0a2d200000174957.440402( 0000)knlGS:000000000000000000000000000000000000000000000000000000
    0000000080050033 [174957.441164] CR2: 00007fff13563e98 CR3: 0000000404f4e005 CR4: 0000000000370ee0 [174957.442117] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [174957.443076] DR3:
    0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [174957.443948] Call Trace: [174957.444264] <TASK> [174957.444538] btrfs_free_block_groups+0x255/0x3c0 [btrfs] [174957.445238] close_ctree+0x301/0x357 [btrfs] [174957.445803] ? call_rcu+0x16c/0x290 [174957.446250] generic_shutdown_super+0x74/0x120 [174957.446832 ] kill_anon_super+0x14/0x30 [174957.447305] btrfs_kill_super+0x12/0x20 [btrfs] [174957.447890[ ] deactivate_locked_super+0x31/0xa0174957.448440] cleanup_mnt+ 0x147/0x1c0174957.448888] task_work_run+0x5c/0xa0 [174957.449336] exit_to_user_mode_prepare+0x1e5/0x1f0 [174957.449934] syscall_exit_to_user_mode+0x16/0x40174957.450512[ ] do_syscall_64+174957.4516050x48 /0xc0174957.450980entry_SYALL_64_after_x164_after_x164_after_x164_after_x864  ] RIP: 0033:0x7f328fdc4a97 [174957.452059] Code: 03 0c 00 f7 (...) [174957.454320] RSP: 002b:00007fff13564ec8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6 [174957.455262] RAX: 0000000000000000 RBX: 00007f328feea264 RCX: 00007f328fdc4a97 [174957.456131] RDX
    000000000000000 RSI: 00000000000000 ---truncated---CVE-2022-48833

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

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

  - btrfs略過在記錄清理失敗後對卸載提出的保留位元組警告在認可 c2e39305299f01 進行的最近變更之後 (btrfs 當我們無法寫入時清除範圍緩衝區 uptodate) 及其後續修正認可後 651740a5024117 (btrfs嘗試在讀取範圍緩衝區)時，我們現在可以在交易中止發生後，最終不清理記錄樹狀結構範圍緩衝區的空間保留，以及不清理靜止的已變更範圍緩衝區。會發生這種情況是因為如果記錄樹狀結構範圍緩衝區回寫失敗是因為我們已清除範圍緩衝區中的 EXTENT_BUFFER_UPTODATE 位元而且我們也已在其上設定 EXTENT_BUFFER_WRITE_ERR 位元。之後當嘗試使用 free_log_tree() 反覆使用樹狀結構來釋放記錄樹狀結構時我們最終可能會在嘗試讀取節點或分葉時遇到 -EIO 錯誤因為 read_extent_buffer_pages() 會在範圍緩衝區未設定 EXTENT_BUFFER_UPTODATE但已設定 EXTENT_BUFFER_WRITE_ERR 位元。取得 -EIO 表示我們會立即傳回因為我們無法逐一查看整個樹狀結構。在此情況下我們絕不會更新個別區塊群組與 space_info 物件中範圍緩衝區的保留空間。若發生此情況我們在卸載 fs 時會收到下列追踪[174957.284509] BTRFScleanup_transaction:1913 中的錯誤 (dm-0)errno=-5 IO 失敗 [174957.286497] ] BTRFS錯誤 (裝置 dm-0)在 free_log_tree:3420 中errno=-5 IO 失敗 [174957.399379] ------------[cut here ]------------ [174957.402497] 警告CPU 2 PID: 3206883@fs/btrfs/block-group.c:127 btrfs_put_block_group+0x77/0xb0 [btrfs] [174957.407523] 連結的模組btrfs overlay dm_zero (...) [174957.424917] CPU2 PID 3206883 Commumount 污染GW 5.16.0-rc5-btrfs-next-109 #1 [174957.426689] 硬體名稱QEMU Standard PC (i440FX + PIIX, 1996)BIOS rel-1.14.0-0-g155821a1990b-prebuilt .qemu.org 04/01/2014 [174957.428716] RIP
    0010:btrfs_put_block_group+0x77/0xb0 [btrfs] [174957.429717] 代碼21 48 8bd (...) [174957.432867] RSP
    0018:ffffb70d41cffdd0 EFLAGS00010206 [174957.433632] RAX0000000000000001 RBXffff8b09c3848000 RCX
    ffff8b0758edd1c8 [174957.434689] RDX 0000000000000001 RSIffffffffc0b467e7 RDI ffff8b0758edd000 [174957.436068] RBP ffff8b0758edd000 R080000000000000000 R090 [000000000174957.437114] 00000 R10[00000]
    0000000000000246 R110000000000000000 R12ffff8b09c3848148 [174957.438140] R13ffff8b09c3848198 R14
    ffff8b0758edd188 R15dead000000000100 [174957.439317] FS00007f328fb82800(0000) GS:ffff8b0a2d200000(0000) knlGS:000000000000000 [174957.440402] CS0010 000000CR:000000000000000000000000000000000000000000000000000000
    0000000080050033 [174957.441164] CR2: 00007fff13563e98 CR3: 0000000404f4e005 CR4: 0000000000370ee0 [174957.442117] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [174957.443076] DR3:
    0000000000000000 DR600000000fffe0ff0 DR7: 0000000000000400 [174957.443948] 呼叫追踪[174957.444264] <TASK> [174957.444538] btrfs_free_block_groups+0x255/0x3c0 [btrfs] [174957.445238] close_ctree+0x301/0x357? [btrfsfs] [174957.445803] call_rcu+0x16c/0x290 [174957.446250] generic_shutdown_super+0x74/0x120 [174957.446832] kill_anon_super+0x14/0x30 [174957.447305] btrfs_kill_super+0x12/0x20 [btrfs] [174957.447890] deactivate_locked_super+0x31/0xa0 [174957.448440] cleanup_mnt+ 0x147/0x1c0 [174957.448888] task_work_run+0x5c/0xa0 [174957.449336] exit_to_user_mode_prepare+0x1e5/0x1f0 [174957.449934] syscall_exit_to_user_mode+0x16/0x40 [174957.450512] ] do_syscall_64+174957.4516050x48 /0xc0 [174957.450980] entry_sysCALL_64_xae_ [wframe_SYSCALL_64_after_[hframe]  ] RIP: 0033:0x7f328fdc4a97 [174957.452059] Code: 03 0c 00 f7 (...) [174957.454320] RSP: 002b:00007fff13564ec8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6 [174957.455262] RAX: 0000000000000000 RBX: 00007f328feea264 RCX: 00007f328fdc4a97 [174957.456131] RDX
    0000000000000000 RSI 00000000000000 ---truncated--- (CVE-2022-48833)

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

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

  - btrfs日志清理失败后跳过卸载上的保留字节警告在接受 c2e39305299f01 提交 c2e39305299f01 写入失败时清除最新的盘区缓冲区之后进行最近的更改及其后续修复请提交 651740a5024117btrfs尝试写入时检查 WRITE_ERR读取范围缓冲区现在可以在事务中止发生后不清除日志树范围缓冲区的空间预留并且不清除仍然脏的范围缓冲区。发生这种情况的原因是如果日志树范围缓冲区的回写失败那么我们已从范围缓冲区中清除了 EXTENT_BUFFER_UPTODATE 并且在其上设置了 EXTENT_BUFFER_WRITE_ERR 位。稍后当我们尝试使用 free_log_tree() 在树上迭代时释放日志树时尝试读取节点或叶时会发生 -EIO 错误因为如果盘区的 read_extent_buffer_pages() 返回 -EIO缓冲区未设置 EXTENT_BUFFER_UPTODATE 而是设置了 EXTENT_BUFFER_WRITE_ERR 位。获取 -EIO 意味着我们立即返回因为无法迭代整个树。在这种情况下我们绝不会更新各自的块组和 space_info 对象中为盘区缓冲区保留的空间。如果发生这种情况我们在卸载 fs 时会得到以下跟踪[174957.284509] BTRFScleanup_transaction:1913: errno=-5 IO 中存在错误 (设备 dm-0) IO 失败 [174957.286497] BTRFS: 错误 (设备 dm-0) free_log_tree:3420 中的 errno=-5 IO 故障 [174957.399379] ------------[ 在此处切换 ]------------ [174957.402497] 警告CPU 2 PID3206883 at fs/btrfs/block-group.c:127 btrfs_put_block_group+0x77/0xb0 [btrfs] [174957.407523] 链接的模块btrfs overlay dm_zero (...) [174957.424917] CPU2 PID 3206883 Comm: umount Tainted: GW 5.16.0-rc5-btrfs-next-109 #1 [174957.426689] 硬件名称QEMU Standard PC (i440FX + PIIX,1996)、BIOS rel-1.14.0-0-g155821a1990b-prebuilt .qemu.org 2014 年 04 月 1 日 [174957.428716] RIP
    0010btrfs_put_block_group+0x77/0xb0 [btrfs] [174957.429717] Code21 48 8b bd (...) [174957.432867] RSP
    0018ffffb70d41cffdd0 EFLAGS00010206 [174957.433632] RAX: 0000000000000001 RBX: ffff8b09c3848000 RCX
    ffff8b0758edd1c8 [174957.434689] RDX: 0000000000000001 RSI: ffffffffc0b467e7 RDI: ffff8b0758edd000 [174957.436068] RBP: ffff8b0758edd000 R08: 0000000000000000 R09: 0000000000 [000000174957.437114R10[000000]
    0000000000000246 R110000000000000000 R12ffff8b09c3848148 [174957.438140] R13ffff8b09c3848198 R14
    ffff8b0758edd188 R15dead000000000100 [174957.439317] FS: 00007f328fb82800(0000) GS:ffff8b0a2d200000(0000) knlGS:0000000000000000 [174957.440402] CS: 0010 DS: 0000 CR0 ES:
    0000000080050033 [174957.441164] CR2: 00007fff13563e98 CR3: 0000000404f4e005 CR4: 0000000000370ee0 [174957.442117] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [174957.443076] DR3:
    0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [174957.443948] 调用跟踪[174957.444264] <TASK> [174957.444538] btrfs_free_block_groups+0x255/0x3c0 [btrfs] [174957.445238] close_ctree+0x301/0x35s] [?] [trfs174957.4458037 call_rcu+0x16c/0x290 [174957.446250] generic_shutdown_super+0x74/0x120 [174957.446832] kill_anon_super+0x14/0x30 [174957.447305] btrfs_kill_super+0x12/0x20 [btrfs] [174957.447890] deactivate_locked_super+0x31/0xa0 [174957.448440] cleanup_mnt+ 0x147/0x1c0 [174957.448888] task_work_run+0x5c/0xa0 [174957.449336] exit_to_user_mode_prepare+0x1e5/0x1f0 [174957.449934] syscall_exit_to_user_mode+0x16/0x40 [174957.450512[] ] do_syscall_64+0x48/0xc0 [  ] entry_SYSCALL_64_after_hw [/0x147/0x1c0] do_syscall_64+0x48/0xc0174957.450980[  ] entry_SYSCALL_64_after_hw [174957.451605/ 0x147/0x1c0  ] RIP: 0033:0x7f328fdc4a97 [174957.452059] Code: 03 0c 00 f7 (...) [174957.454320] RSP: 002b:00007fff13564ec8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6 [174957.455262] RAX: 0000000000000000 RBX: 00007f328feea264 RCX: 00007f328fdc4a97 [174957.456131] RDX
    0000000000000000 RSI00000000000000 ---truncated--- (CVE-2022-48833)

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

ID	Name	Product	Family	Published	Updated	Severity
225616	Linux Distros Unpatched Vulnerability : CVE-2022-48833	Nessus	Misc.	3/5/2025	8/12/2025	medium
225616	Linux Distros のパッチ未適用の脆弱性: CVE-2022-48833	Nessus	Misc.	3/5/2025	8/12/2025	medium
225616	Linux Distros 未修補的弱點：CVE-2022-48833	Nessus	Misc.	3/5/2025	8/12/2025	medium
225616	Linux Distros 未修补的漏洞：CVE-2022-48833	Nessus	Misc.	3/5/2025	8/12/2025	medium

Detections

Analytics

Plugins Search

medium

medium

medium

medium