In the Linux kernel, the following vulnerability has been resolved: nilfs2: do not force clear folio if buffer is referenced Patch series "nilfs2: protect busy buffer heads from being force-cleared". This series fixes the buffer head state inconsistency issues reported by syzbot that occurs when the filesystem is corrupted and falls back to read-only, and the associated buffer head use-after-free issue. This patch (of 2): Syzbot has reported that after nilfs2 detects filesystem corruption and falls back to read-only, inconsistencies in the buffer state may occur. One of the inconsistencies is that when nilfs2 calls mark_buffer_dirty() to set a data or metadata buffer as dirty, but it detects that the buffer is not in the uptodate state: WARNING: CPU: 0 PID: 6049 at fs/buffer.c:1177 mark_buffer_dirty+0x2e5/0x520 fs/buffer.c:1177 ... Call Trace: <TASK> nilfs_palloc_commit_alloc_entry+0x4b/0x160 fs/nilfs2/alloc.c:598 nilfs_ifile_create_inode+0x1dd/0x3a0 fs/nilfs2/ifile.c:73 nilfs_new_inode+0x254/0x830 fs/nilfs2/inode.c:344 nilfs_mkdir+0x10d/0x340 fs/nilfs2/namei.c:218 vfs_mkdir+0x2f9/0x4f0 fs/namei.c:4257 do_mkdirat+0x264/0x3a0 fs/namei.c:4280 __do_sys_mkdirat fs/namei.c:4295 [inline] __se_sys_mkdirat fs/namei.c:4293 [inline] __x64_sys_mkdirat+0x87/0xa0 fs/namei.c:4293 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f The other is when nilfs_btree_propagate(), which propagates the dirty state to the ancestor nodes of a b-tree that point to a dirty buffer, detects that the origin buffer is not dirty, even though it should be: WARNING: CPU: 0 PID: 5245 at fs/nilfs2/btree.c:2089 nilfs_btree_propagate+0xc79/0xdf0 fs/nilfs2/btree.c:2089 ... Call Trace: <TASK> nilfs_bmap_propagate+0x75/0x120 fs/nilfs2/bmap.c:345 nilfs_collect_file_data+0x4d/0xd0 fs/nilfs2/segment.c:587 nilfs_segctor_apply_buffers+0x184/0x340 fs/nilfs2/segment.c:1006 nilfs_segctor_scan_file+0x28c/0xa50 fs/nilfs2/segment.c:1045 nilfs_segctor_collect_blocks fs/nilfs2/segment.c:1216 [inline] nilfs_segctor_collect fs/nilfs2/segment.c:1540 [inline] nilfs_segctor_do_construct+0x1c28/0x6b90 fs/nilfs2/segment.c:2115 nilfs_segctor_construct+0x181/0x6b0 fs/nilfs2/segment.c:2479 nilfs_segctor_thread_construct fs/nilfs2/segment.c:2587 [inline] nilfs_segctor_thread+0x69e/0xe80 fs/nilfs2/segment.c:2701 kthread+0x2f0/0x390 kernel/kthread.c:389 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 </TASK> Both of these issues are caused by the callbacks that handle the page/folio write requests, forcibly clear various states, including the working state of the buffers they hold, at unexpected times when they detect read-only fallback. Fix these issues by checking if the buffer is referenced before clearing the page/folio state, and skipping the clear if it is.

The remote Ubuntu Pro FIPS-updates 20.04 LTS host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-7518-1 advisory.

    Several security issues were discovered in the Linux kernel. An attacker could possibly use these to     compromise the system. This update corrects flaws in the following subsystems:

    - ARM64 architecture;

    - PowerPC architecture;

    - Block layer subsystem;

    - Drivers core;

    - Network block device driver;

    - Character device driver;

    - GPU drivers;

    - HID subsystem;

    - InfiniBand drivers;

    - Media drivers;

    - Network drivers;

    - PPS (Pulse Per Second) driver;

    - PTP clock framework;

    - RapidIO drivers;

    - Real Time Clock drivers;

    - SCSI subsystem;

    - SLIMbus drivers;

    - QCOM SoC drivers;

    - Trusted Execution Environment drivers;

    - USB DSL drivers;

    - USB Device Class drivers;

    - USB core drivers;

    - USB Gadget drivers;

    - USB Host Controller drivers;

    - Renesas USBHS Controller drivers;

    - File systems infrastructure;

    - BTRFS file system;

    - Ceph distributed file system;

    - NILFS2 file system;

    - UBI file system;

    - KVM subsystem;

    - L3 Master device support module;

    - Netfilter;

    - Process Accounting mechanism;

    - printk logging mechanism;

    - Scheduler infrastructure;

    - Tracing infrastructure;

    - Memory management;

    - 802.1Q VLAN protocol;

    - B.A.T.M.A.N. meshing protocol;

    - Bluetooth subsystem;

    - Networking core;

    - IPv4 networking;

    - IPv6 networking;

    - Logical Link layer;

    - NFC subsystem;

    - Open vSwitch;

    - Rose network layer;

    - Network traffic control;

    - Wireless networking;

    - Tomoyo security module; (CVE-2025-21760, CVE-2025-21928, CVE-2025-21877, CVE-2024-58069, CVE-2025-21909,     CVE-2025-21926, CVE-2025-21731, CVE-2025-21718, CVE-2025-21763, CVE-2025-21866, CVE-2024-58009,     CVE-2025-21971, CVE-2025-21787, CVE-2025-21721, CVE-2024-58072, CVE-2025-21791, CVE-2021-47191,     CVE-2025-21865, CVE-2025-21762, CVE-2024-58063, CVE-2025-21910, CVE-2025-21823, CVE-2025-21905,     CVE-2025-21708, CVE-2024-58090, CVE-2025-21917, CVE-2024-58051, CVE-2025-21781, CVE-2025-21898,     CVE-2025-21922, CVE-2024-58002, CVE-2024-58017, CVE-2024-57986, CVE-2024-58052, CVE-2024-26982,     CVE-2025-21848, CVE-2025-21835, CVE-2025-21749, CVE-2024-58014, CVE-2024-58007, CVE-2024-57980,     CVE-2025-21715, CVE-2025-21858, CVE-2025-21916, CVE-2025-21811, CVE-2025-21765, CVE-2025-21736,     CVE-2025-21647, CVE-2025-21934, CVE-2025-21776, CVE-2025-21761, CVE-2025-21904, CVE-2024-57979,     CVE-2024-58020, CVE-2025-21935, CVE-2025-21871, CVE-2025-21704, CVE-2024-57977, CVE-2024-58083,     CVE-2025-21764, CVE-2025-21814, CVE-2025-21772, CVE-2025-21719, CVE-2024-58055, CVE-2023-52664,     CVE-2024-56599, CVE-2024-58001, CVE-2025-21744, CVE-2024-58085, CVE-2025-21753, CVE-2025-21846,     CVE-2024-58010, CVE-2024-26996, CVE-2023-52927, CVE-2024-50055, CVE-2025-21925, CVE-2025-21782,     CVE-2024-57973, CVE-2024-58071, CVE-2025-21785, CVE-2025-21859, CVE-2025-21920, CVE-2024-26689,     CVE-2023-52741, CVE-2025-21806, CVE-2024-58058, CVE-2025-21722, CVE-2025-21728, CVE-2024-57981,     CVE-2025-21948, CVE-2025-21914, CVE-2025-21862, CVE-2025-21735)

Tenable has extracted the preceding description block directly from the Ubuntu 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 remote Ubuntu 20.04 LTS / 22.04 LTS host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-7510-1 advisory.

    Several security issues were discovered in the Linux kernel. An attacker could possibly use these to     compromise the system. This update corrects flaws in the following subsystems:

    - ARM64 architecture;

    - PowerPC architecture;

    - x86 architecture;

    - Block layer subsystem;

    - Network block device driver;

    - Bus devices;

    - Character device driver;

    - TPM device driver;

    - Clock framework and drivers;

    - GPIO subsystem;

    - GPU drivers;

    - HID subsystem;

    - I2C subsystem;

    - InfiniBand drivers;

    - Media drivers;

    - NVIDIA Tegra memory controller driver;

    - Network drivers;

    - PCI subsystem;

    - PPS (Pulse Per Second) driver;

    - PTP clock framework;

    - RapidIO drivers;

    - Real Time Clock drivers;

    - SLIMbus drivers;

    - QCOM SoC drivers;

    - Trusted Execution Environment drivers;

    - TTY drivers;

    - USB DSL drivers;

    - USB Device Class drivers;

    - USB core drivers;

    - USB Gadget drivers;

    - USB Host Controller drivers;

    - Renesas USBHS Controller drivers;

    - ACRN Hypervisor Service Module driver;

    - File systems infrastructure;

    - BTRFS file system;

    - F2FS file system;

    - Network file system (NFS) server daemon;

    - NILFS2 file system;

    - Overlay file system;

    - SMB network file system;

    - UBI file system;

    - KVM subsystem;

    - L3 Master device support module;

    - Process Accounting mechanism;

    - Padata parallel execution mechanism;

    - printk logging mechanism;

    - Scheduler infrastructure;

    - Timer subsystem;

    - Tracing infrastructure;

    - Memory management;

    - 802.1Q VLAN protocol;

    - B.A.T.M.A.N. meshing protocol;

    - Networking core;

    - IPv4 networking;

    - IPv6 networking;

    - Logical Link layer;

    - Multipath TCP;

    - Netfilter;

    - NFC subsystem;

    - Open vSwitch;

    - Rose network layer;

    - Network traffic control;

    - Wireless networking;

    - Landlock security;

    - Linux Security Modules (LSM) Framework;

    - Tomoyo security module; (CVE-2025-21731, CVE-2025-21926, CVE-2025-21830, CVE-2024-58010, CVE-2025-21745,     CVE-2025-21871, CVE-2024-57980, CVE-2025-21916, CVE-2025-21735, CVE-2025-21763, CVE-2025-21799,     CVE-2025-21811, CVE-2025-21814, CVE-2024-58083, CVE-2025-21922, CVE-2025-21802, CVE-2024-58034,     CVE-2025-21758, CVE-2024-58069, CVE-2025-21905, CVE-2024-57986, CVE-2025-21718, CVE-2024-58020,     CVE-2025-21858, CVE-2025-21749, CVE-2025-21928, CVE-2024-58085, CVE-2025-21795, CVE-2025-21744,     CVE-2025-21776, CVE-2025-21804, CVE-2024-57973, CVE-2025-21848, CVE-2025-21844, CVE-2024-56721,     CVE-2024-58079, CVE-2025-21781, CVE-2025-21866, CVE-2024-58052, CVE-2024-58017, CVE-2024-58071,     CVE-2025-21791, CVE-2024-26982, CVE-2025-21787, CVE-2024-58090, CVE-2025-21951, CVE-2025-21846,     CVE-2025-21722, CVE-2024-58001, CVE-2025-21715, CVE-2025-21919, CVE-2025-21904, CVE-2024-57977,     CVE-2025-21785, CVE-2025-21950, CVE-2025-21924, CVE-2024-57979, CVE-2025-21711, CVE-2024-47726,     CVE-2024-58002, CVE-2025-21914, CVE-2024-58086, CVE-2024-58005, CVE-2025-21835, CVE-2024-58051,     CVE-2025-21761, CVE-2025-21760, CVE-2025-21767, CVE-2025-21766, CVE-2025-21726, CVE-2025-21865,     CVE-2024-58014, CVE-2025-21878, CVE-2025-21934, CVE-2024-58007, CVE-2025-21898, CVE-2025-21806,     CVE-2024-58058, CVE-2025-21779, CVE-2024-58063, CVE-2025-21708, CVE-2025-21684, CVE-2024-57834,     CVE-2025-21971, CVE-2025-21762, CVE-2025-21728, CVE-2024-58076, CVE-2025-21704, CVE-2025-21719,     CVE-2025-21948, CVE-2025-21707, CVE-2025-21917, CVE-2025-21782, CVE-2025-21943, CVE-2025-21765,     CVE-2025-21721, CVE-2024-58016, CVE-2025-21859, CVE-2025-21909, CVE-2025-21748, CVE-2025-21912,     CVE-2025-21736, CVE-2025-21862, CVE-2024-57978, CVE-2025-21826, CVE-2025-21920, CVE-2025-21772,     CVE-2025-21877, CVE-2025-21935, CVE-2024-56599, CVE-2025-21820, CVE-2025-21764, CVE-2025-21796,     CVE-2025-21887, CVE-2025-21753, CVE-2025-21910, CVE-2024-57981, CVE-2025-21727, CVE-2025-21875,     CVE-2024-58072, CVE-2024-58055, CVE-2025-21925, CVE-2025-21823, CVE-2025-21647)

Tenable has extracted the preceding description block directly from the Ubuntu 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 remote Ubuntu 20.04 LTS host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-7512-1 advisory.

    Several security issues were discovered in the Linux kernel. An attacker could possibly use these to     compromise the system. This update corrects flaws in the following subsystems:

    - ARM64 architecture;

    - PowerPC architecture;

    - x86 architecture;

    - Block layer subsystem;

    - Network block device driver;

    - Bus devices;

    - Character device driver;

    - TPM device driver;

    - Clock framework and drivers;

    - GPIO subsystem;

    - GPU drivers;

    - HID subsystem;

    - I2C subsystem;

    - InfiniBand drivers;

    - Media drivers;

    - NVIDIA Tegra memory controller driver;

    - Network drivers;

    - PCI subsystem;

    - PPS (Pulse Per Second) driver;

    - PTP clock framework;

    - RapidIO drivers;

    - Real Time Clock drivers;

    - SLIMbus drivers;

    - QCOM SoC drivers;

    - Trusted Execution Environment drivers;

    - TTY drivers;

    - USB DSL drivers;

    - USB Device Class drivers;

    - USB core drivers;

    - USB Gadget drivers;

    - USB Host Controller drivers;

    - Renesas USBHS Controller drivers;

    - ACRN Hypervisor Service Module driver;

    - File systems infrastructure;

    - BTRFS file system;

    - F2FS file system;

    - Network file system (NFS) server daemon;

    - NILFS2 file system;

    - Overlay file system;

    - SMB network file system;

    - UBI file system;

    - KVM subsystem;

    - L3 Master device support module;

    - Netfilter;

    - Process Accounting mechanism;

    - Padata parallel execution mechanism;

    - printk logging mechanism;

    - Scheduler infrastructure;

    - Timer subsystem;

    - Tracing infrastructure;

    - Memory management;

    - 802.1Q VLAN protocol;

    - B.A.T.M.A.N. meshing protocol;

    - Networking core;

    - IPv4 networking;

    - IPv6 networking;

    - Logical Link layer;

    - Multipath TCP;

    - NFC subsystem;

    - Open vSwitch;

    - Rose network layer;

    - Network traffic control;

    - Wireless networking;

    - Landlock security;

    - Linux Security Modules (LSM) Framework;

    - Tomoyo security module; (CVE-2025-21914, CVE-2024-58090, CVE-2024-58017, CVE-2024-58069, CVE-2025-21920,     CVE-2025-21935, CVE-2024-57977, CVE-2025-21763, CVE-2025-21684, CVE-2025-21721, CVE-2025-21736,     CVE-2024-58020, CVE-2025-21799, CVE-2025-21904, CVE-2025-21934, CVE-2025-21719, CVE-2025-21811,     CVE-2025-21727, CVE-2024-58071, CVE-2025-21905, CVE-2024-26982, CVE-2025-21820, CVE-2024-58052,     CVE-2025-21925, CVE-2025-21796, CVE-2025-21779, CVE-2025-21823, CVE-2024-58063, CVE-2025-21772,     CVE-2025-21924, CVE-2025-21765, CVE-2024-56721, CVE-2025-21859, CVE-2025-21760, CVE-2025-21753,     CVE-2025-21835, CVE-2025-21887, CVE-2024-58002, CVE-2024-58086, CVE-2025-21744, CVE-2025-21848,     CVE-2024-57986, CVE-2025-21865, CVE-2025-21766, CVE-2025-21715, CVE-2023-52664, CVE-2025-21764,     CVE-2024-58085, CVE-2025-21704, CVE-2024-58072, CVE-2024-58079, CVE-2025-21846, CVE-2025-21647,     CVE-2025-21726, CVE-2024-58034, CVE-2025-21943, CVE-2025-21875, CVE-2025-21871, CVE-2025-21898,     CVE-2024-58083, CVE-2025-21748, CVE-2024-57834, CVE-2024-58051, CVE-2025-21862, CVE-2025-21722,     CVE-2025-21912, CVE-2025-21950, CVE-2025-21917, CVE-2024-57973, CVE-2024-56599, CVE-2025-21922,     CVE-2025-21787, CVE-2025-21919, CVE-2025-21971, CVE-2024-57979, CVE-2024-35889, CVE-2025-21804,     CVE-2025-21782, CVE-2025-21910, CVE-2025-21909, CVE-2025-21708, CVE-2025-21830, CVE-2025-21791,     CVE-2024-58016, CVE-2025-21711, CVE-2025-21928, CVE-2024-58007, CVE-2024-58005, CVE-2023-52927,     CVE-2025-21802, CVE-2024-58010, CVE-2024-58001, CVE-2024-47726, CVE-2024-57978, CVE-2024-58055,     CVE-2025-21735, CVE-2025-21795, CVE-2025-21745, CVE-2025-21878, CVE-2025-21877, CVE-2025-21826,     CVE-2024-58076, CVE-2025-21806, CVE-2025-21858, CVE-2025-21866, CVE-2025-21776, CVE-2025-21785,     CVE-2025-21758, CVE-2024-57980, CVE-2025-21728, CVE-2024-58014, CVE-2025-21814, CVE-2025-21762,     CVE-2025-21951, CVE-2025-21767, CVE-2025-21844, CVE-2025-21781, CVE-2024-58058, CVE-2025-21761,     CVE-2025-21707, CVE-2025-21731, CVE-2024-44964, CVE-2025-21749, CVE-2024-57981, CVE-2025-21948,     CVE-2025-21926, CVE-2025-21916, CVE-2025-21718)

Tenable has extracted the preceding description block directly from the Ubuntu 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 remote Ubuntu 18.04 LTS / 20.04 LTS host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-7516-1 advisory.

    Several security issues were discovered in the Linux kernel. An attacker could possibly use these to     compromise the system. This update corrects flaws in the following subsystems:

    - ARM64 architecture;

    - PowerPC architecture;

    - Block layer subsystem;

    - Drivers core;

    - Network block device driver;

    - Character device driver;

    - GPU drivers;

    - HID subsystem;

    - InfiniBand drivers;

    - Media drivers;

    - Network drivers;

    - PPS (Pulse Per Second) driver;

    - PTP clock framework;

    - RapidIO drivers;

    - Real Time Clock drivers;

    - SCSI subsystem;

    - SLIMbus drivers;

    - QCOM SoC drivers;

    - Trusted Execution Environment drivers;

    - USB DSL drivers;

    - USB Device Class drivers;

    - USB core drivers;

    - USB Gadget drivers;

    - USB Host Controller drivers;

    - Renesas USBHS Controller drivers;

    - File systems infrastructure;

    - BTRFS file system;

    - NILFS2 file system;

    - UBI file system;

    - KVM subsystem;

    - L3 Master device support module;

    - Process Accounting mechanism;

    - printk logging mechanism;

    - Scheduler infrastructure;

    - Tracing infrastructure;

    - Memory management;

    - 802.1Q VLAN protocol;

    - B.A.T.M.A.N. meshing protocol;

    - Bluetooth subsystem;

    - Networking core;

    - IPv4 networking;

    - IPv6 networking;

    - Logical Link layer;

    - NFC subsystem;

    - Open vSwitch;

    - Rose network layer;

    - Network traffic control;

    - Wireless networking;

    - Tomoyo security module; (CVE-2025-21866, CVE-2025-21846, CVE-2025-21971, CVE-2025-21909, CVE-2024-58083,     CVE-2025-21811, CVE-2025-21776, CVE-2024-58051, CVE-2025-21917, CVE-2025-21935, CVE-2025-21785,     CVE-2021-47191, CVE-2025-21765, CVE-2025-21704, CVE-2025-21647, CVE-2024-58069, CVE-2025-21877,     CVE-2025-21948, CVE-2024-58007, CVE-2024-58001, CVE-2025-21871, CVE-2024-58055, CVE-2025-21848,     CVE-2025-21925, CVE-2024-58058, CVE-2025-21814, CVE-2025-21905, CVE-2025-21898, CVE-2025-21926,     CVE-2025-21760, CVE-2024-57973, CVE-2025-21806, CVE-2024-58071, CVE-2025-21761, CVE-2025-21762,     CVE-2024-57986, CVE-2025-21708, CVE-2025-21744, CVE-2024-26996, CVE-2024-50055, CVE-2024-58020,     CVE-2025-21858, CVE-2025-21715, CVE-2025-21904, CVE-2025-21920, CVE-2024-56599, CVE-2025-21781,     CVE-2025-21764, CVE-2025-21865, CVE-2025-21772, CVE-2024-58072, CVE-2025-21928, CVE-2025-21859,     CVE-2025-21721, CVE-2025-21719, CVE-2025-21914, CVE-2025-21753, CVE-2024-58009, CVE-2024-57981,     CVE-2024-58063, CVE-2024-58052, CVE-2025-21722, CVE-2024-57977, CVE-2025-21736, CVE-2025-21922,     CVE-2024-26982, CVE-2025-21718, CVE-2025-21916, CVE-2025-21749, CVE-2025-21787, CVE-2024-58085,     CVE-2024-58010, CVE-2024-57979, CVE-2024-57980, CVE-2025-21782, CVE-2025-21791, CVE-2025-21728,     CVE-2023-52741, CVE-2025-21934, CVE-2024-58002, CVE-2025-21735, CVE-2025-21910, CVE-2025-21823,     CVE-2024-58090, CVE-2025-21862, CVE-2025-21731, CVE-2025-21835, CVE-2024-58017, CVE-2024-58014,     CVE-2025-21763)

Tenable has extracted the preceding description block directly from the Ubuntu 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 remote Ubuntu 20.04 LTS host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-7517-1 advisory.

    Several security issues were discovered in the Linux kernel. An attacker could possibly use these to     compromise the system. This update corrects flaws in the following subsystems:

    - ARM64 architecture;

    - PowerPC architecture;

    - Block layer subsystem;

    - Drivers core;

    - Network block device driver;

    - Character device driver;

    - GPU drivers;

    - HID subsystem;

    - InfiniBand drivers;

    - Media drivers;

    - Network drivers;

    - PPS (Pulse Per Second) driver;

    - PTP clock framework;

    - RapidIO drivers;

    - Real Time Clock drivers;

    - SCSI subsystem;

    - SLIMbus drivers;

    - QCOM SoC drivers;

    - Trusted Execution Environment drivers;

    - USB DSL drivers;

    - USB Device Class drivers;

    - USB core drivers;

    - USB Gadget drivers;

    - USB Host Controller drivers;

    - Renesas USBHS Controller drivers;

    - File systems infrastructure;

    - BTRFS file system;

    - Ceph distributed file system;

    - NILFS2 file system;

    - UBI file system;

    - KVM subsystem;

    - L3 Master device support module;

    - Netfilter;

    - Process Accounting mechanism;

    - printk logging mechanism;

    - Scheduler infrastructure;

    - Tracing infrastructure;

    - Memory management;

    - 802.1Q VLAN protocol;

    - B.A.T.M.A.N. meshing protocol;

    - Bluetooth subsystem;

    - Networking core;

    - IPv4 networking;

    - IPv6 networking;

    - Logical Link layer;

    - NFC subsystem;

    - Open vSwitch;

    - Rose network layer;

    - Network traffic control;

    - Wireless networking;

    - Tomoyo security module; (CVE-2024-58051, CVE-2025-21731, CVE-2025-21782, CVE-2025-21785, CVE-2025-21917,     CVE-2025-21914, CVE-2025-21744, CVE-2025-21948, CVE-2025-21708, CVE-2024-58072, CVE-2024-57977,     CVE-2024-26996, CVE-2025-21787, CVE-2025-21859, CVE-2024-58007, CVE-2023-52664, CVE-2025-21722,     CVE-2025-21971, CVE-2025-21928, CVE-2025-21791, CVE-2024-58090, CVE-2024-57981, CVE-2025-21865,     CVE-2024-58001, CVE-2025-21926, CVE-2024-58071, CVE-2025-21721, CVE-2025-21772, CVE-2025-21764,     CVE-2024-58017, CVE-2024-57973, CVE-2025-21761, CVE-2025-21866, CVE-2025-21920, CVE-2025-21704,     CVE-2024-58055, CVE-2024-56599, CVE-2025-21935, CVE-2023-52927, CVE-2025-21811, CVE-2024-50055,     CVE-2025-21781, CVE-2025-21760, CVE-2025-21922, CVE-2024-58009, CVE-2024-58069, CVE-2025-21877,     CVE-2024-58058, CVE-2024-57980, CVE-2025-21905, CVE-2024-26982, CVE-2025-21916, CVE-2024-58020,     CVE-2025-21835, CVE-2025-21719, CVE-2025-21858, CVE-2024-58085, CVE-2025-21814, CVE-2025-21762,     CVE-2025-21862, CVE-2024-58014, CVE-2025-21898, CVE-2025-21904, CVE-2025-21736, CVE-2025-21765,     CVE-2025-21647, CVE-2024-58010, CVE-2025-21763, CVE-2025-21718, CVE-2021-47191, CVE-2024-58052,     CVE-2025-21846, CVE-2024-58063, CVE-2024-26689, CVE-2025-21806, CVE-2025-21753, CVE-2025-21910,     CVE-2025-21848, CVE-2025-21749, CVE-2025-21871, CVE-2024-57979, CVE-2025-21728, CVE-2025-21925,     CVE-2024-58002, CVE-2025-21909, CVE-2025-21715, CVE-2024-58083, CVE-2025-21735, CVE-2025-21776,     CVE-2025-21823, CVE-2025-21934, CVE-2023-52741, CVE-2024-57986)

Tenable has extracted the preceding description block directly from the Ubuntu 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 remote Ubuntu 22.04 LTS host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-7511-1 advisory.

    Several security issues were discovered in the Linux kernel. An attacker could possibly use these to     compromise the system. This update corrects flaws in the following subsystems:

    - ARM64 architecture;

    - PowerPC architecture;

    - x86 architecture;

    - Block layer subsystem;

    - Network block device driver;

    - Bus devices;

    - Character device driver;

    - TPM device driver;

    - Clock framework and drivers;

    - GPIO subsystem;

    - GPU drivers;

    - HID subsystem;

    - I2C subsystem;

    - InfiniBand drivers;

    - Media drivers;

    - NVIDIA Tegra memory controller driver;

    - Network drivers;

    - PCI subsystem;

    - PPS (Pulse Per Second) driver;

    - PTP clock framework;

    - RapidIO drivers;

    - Real Time Clock drivers;

    - SLIMbus drivers;

    - QCOM SoC drivers;

    - Trusted Execution Environment drivers;

    - TTY drivers;

    - USB DSL drivers;

    - USB Device Class drivers;

    - USB core drivers;

    - USB Gadget drivers;

    - USB Host Controller drivers;

    - Renesas USBHS Controller drivers;

    - ACRN Hypervisor Service Module driver;

    - File systems infrastructure;

    - BTRFS file system;

    - F2FS file system;

    - Network file system (NFS) server daemon;

    - NILFS2 file system;

    - Overlay file system;

    - SMB network file system;

    - UBI file system;

    - KVM subsystem;

    - L3 Master device support module;

    - Process Accounting mechanism;

    - Padata parallel execution mechanism;

    - printk logging mechanism;

    - Scheduler infrastructure;

    - Timer subsystem;

    - Tracing infrastructure;

    - Memory management;

    - 802.1Q VLAN protocol;

    - B.A.T.M.A.N. meshing protocol;

    - Networking core;

    - IPv4 networking;

    - IPv6 networking;

    - Logical Link layer;

    - Multipath TCP;

    - Netfilter;

    - NFC subsystem;

    - Open vSwitch;

    - Rose network layer;

    - Network traffic control;

    - Wireless networking;

    - Landlock security;

    - Linux Security Modules (LSM) Framework;

    - Tomoyo security module; (CVE-2024-58063, CVE-2025-21802, CVE-2025-21910, CVE-2025-21718, CVE-2025-21707,     CVE-2025-21781, CVE-2025-21726, CVE-2024-56599, CVE-2025-21735, CVE-2025-21859, CVE-2025-21924,     CVE-2024-57980, CVE-2024-58002, CVE-2024-58090, CVE-2025-21728, CVE-2024-58055, CVE-2024-57978,     CVE-2025-21704, CVE-2025-21820, CVE-2025-21776, CVE-2025-21919, CVE-2025-21765, CVE-2025-21935,     CVE-2025-21647, CVE-2025-21804, CVE-2024-58072, CVE-2025-21865, CVE-2025-21887, CVE-2024-58079,     CVE-2024-58020, CVE-2024-35889, CVE-2024-58017, CVE-2024-58005, CVE-2025-21862, CVE-2025-21875,     CVE-2025-21925, CVE-2025-21951, CVE-2025-21866, CVE-2025-21871, CVE-2025-21914, CVE-2025-21948,     CVE-2025-21715, CVE-2025-21848, CVE-2025-21905, CVE-2025-21830, CVE-2024-58051, CVE-2025-21909,     CVE-2025-21711, CVE-2025-21684, CVE-2025-21844, CVE-2025-21904, CVE-2025-21898, CVE-2025-21767,     CVE-2024-58069, CVE-2024-57834, CVE-2025-21934, CVE-2025-21926, CVE-2025-21708, CVE-2025-21736,     CVE-2024-58085, CVE-2024-26982, CVE-2024-58083, CVE-2025-21920, CVE-2025-21764, CVE-2025-21753,     CVE-2025-21799, CVE-2025-21846, CVE-2024-57979, CVE-2025-21785, CVE-2024-58010, CVE-2024-57986,     CVE-2025-21762, CVE-2025-21912, CVE-2025-21744, CVE-2025-21787, CVE-2025-21761, CVE-2025-21971,     CVE-2025-21943, CVE-2024-47726, CVE-2025-21721, CVE-2025-21748, CVE-2025-21791, CVE-2025-21796,     CVE-2025-21806, CVE-2025-21779, CVE-2024-58001, CVE-2025-21745, CVE-2025-21814, CVE-2025-21719,     CVE-2025-21950, CVE-2025-21858, CVE-2025-21823, CVE-2025-21758, CVE-2024-57981, CVE-2024-58058,     CVE-2024-56721, CVE-2025-21811, CVE-2024-58086, CVE-2025-21722, CVE-2025-21727, CVE-2025-21760,     CVE-2024-58076, CVE-2025-21916, CVE-2025-21826, CVE-2024-57973, CVE-2025-21795, CVE-2025-21763,     CVE-2024-58014, CVE-2025-21917, CVE-2024-57977, CVE-2024-44964, CVE-2024-58016, CVE-2024-58007,     CVE-2025-21928, CVE-2024-58052, CVE-2025-21749, CVE-2025-21772, CVE-2025-21877, CVE-2025-21782,     CVE-2025-21922, CVE-2025-21766, CVE-2024-58034, CVE-2025-21835, CVE-2025-21878, CVE-2025-21731,     CVE-2024-58071)

Tenable has extracted the preceding description block directly from the Ubuntu 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 version of kernel installed on the remote CBL Mariner 2.0 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the CVE-2025-21722 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: nilfs2: do not force clear folio if     buffer is referenced Patch series nilfs2: protect busy buffer heads from being force-cleared. This     series fixes the buffer head state inconsistency issues reported by syzbot that occurs when the filesystem     is corrupted and falls back to read-only, and the associated buffer head use-after-free issue. This patch     (of 2): Syzbot has reported that after nilfs2 detects filesystem corruption and falls back to read-only,     inconsistencies in the buffer state May occur. One of the inconsistencies is that when nilfs2 calls     mark_buffer_dirty() to set a data or metadata buffer as dirty, but it detects that the buffer is not in     the uptodate state: WARNING: CPU: 0 PID: 6049 at fs/buffer.c:1177 mark_buffer_dirty+0x2e5/0x520     fs/buffer.c:1177 ... Call Trace: <TASK> nilfs_palloc_commit_alloc_entry+0x4b/0x160 fs/nilfs2/alloc.c:598     nilfs_ifile_create_inode+0x1dd/0x3a0 fs/nilfs2/ifile.c:73 nilfs_new_inode+0x254/0x830     fs/nilfs2/inode.c:344 nilfs_mkdir+0x10d/0x340 fs/nilfs2/namei.c:218 vfs_mkdir+0x2f9/0x4f0 fs/namei.c:4257     do_mkdirat+0x264/0x3a0 fs/namei.c:4280 __do_sys_mkdirat fs/namei.c:4295 [inline] __se_sys_mkdirat     fs/namei.c:4293 [inline] __x64_sys_mkdirat+0x87/0xa0 fs/namei.c:4293 do_syscall_x64     arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83     entry_SYSCALL_64_after_hwframe+0x77/0x7f The other is when nilfs_btree_propagate(), which propagates the     dirty state to the ancestor nodes of a b-tree that point to a dirty buffer, detects that the origin buffer     is not dirty, even though it should be: WARNING: CPU: 0 PID: 5245 at fs/nilfs2/btree.c:2089     nilfs_btree_propagate+0xc79/0xdf0 fs/nilfs2/btree.c:2089 ... Call Trace: <TASK>     nilfs_bmap_propagate+0x75/0x120 fs/nilfs2/bmap.c:345 nilfs_collect_file_data+0x4d/0xd0     fs/nilfs2/segment.c:587 nilfs_segctor_apply_buffers+0x184/0x340 fs/nilfs2/segment.c:1006     nilfs_segctor_scan_file+0x28c/0xa50 fs/nilfs2/segment.c:1045 nilfs_segctor_collect_blocks     fs/nilfs2/segment.c:1216 [inline] nilfs_segctor_collect fs/nilfs2/segment.c:1540 [inline]     nilfs_segctor_do_construct+0x1c28/0x6b90 fs/nilfs2/segment.c:2115 nilfs_segctor_construct+0x181/0x6b0     fs/nilfs2/segment.c:2479 nilfs_segctor_thread_construct fs/nilfs2/segment.c:2587 [inline]     nilfs_segctor_thread+0x69e/0xe80 fs/nilfs2/segment.c:2701 kthread+0x2f0/0x390 kernel/kthread.c:389     ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30     arch/x86/entry/entry_64.S:244 </TASK> Both of these issues are caused by the callbacks that handle the     page/folio write requests, forcibly clear various states, including the working state of the buffers they     hold, at unexpected times when they detect read-only fallback. Fix these issues by checking if the buffer     is referenced before clearing the page/folio state, and skipping the clear if it is. (CVE-2025-21722)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The version of kernel installed on the remote host is prior to 5.10.235-227.919. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.10-2025-088 advisory.

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

    macsec: fix UAF bug for real_dev (CVE-2022-49390)

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

    Squashfs: check the inode number is not the invalid value of zero (CVE-2024-26982)

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

    smb: client: fix UAF in smb2_reconnect_server() (CVE-2024-35870)

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

    rdma/cxgb4: Prevent potential integer overflow on 32bit (CVE-2024-57973)

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

    memcg: fix soft lockup in the OOM process (CVE-2024-57977)

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

    pps: Fix a use-after-free (CVE-2024-57979)

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

    rtc: pcf85063: fix potential OOB write in PCF85063 NVMEM read (CVE-2024-58069)

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

    KVM: Explicitly verify target vCPU is online in kvm_get_vcpu() (CVE-2024-58083)

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

    net: sched: Disallow replacing of child qdisc from one parent to another (CVE-2025-21700)

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

    ipmr: do not call mr_mfc_uses_dev() for unres entries (CVE-2025-21719)

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

    nilfs2: handle errors that nilfs_prepare_chunk() may return (CVE-2025-21721)

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

    nilfs2: do not force clear folio if buffer is referenced (CVE-2025-21722)

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

    padata: avoid UAF for reorder_work (CVE-2025-21726)

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

    padata: fix UAF in padata_reorder (CVE-2025-21727)

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

    bpf: Send signals asynchronously if !preemptible (CVE-2025-21728)

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

    nbd: don't allow reconnect after disconnect (CVE-2025-21731)

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

    btrfs: fix use-after-free when attempting to join an aborted transaction (CVE-2025-21753)

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

    vsock: Keep the binding until socket destruction (CVE-2025-21756)

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

    ndisc: extend RCU protection in ndisc_send_skb() (CVE-2025-21760)

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

    openvswitch: use RCU protection in ovs_vport_cmd_fill_info() (CVE-2025-21761)

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

    arp: use RCU protection in arp_xmit() (CVE-2025-21762)

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

    neighbour: use RCU protection in __neigh_notify() (CVE-2025-21763)

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

    ndisc: use RCU protection in ndisc_alloc_skb() (CVE-2025-21764)

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

    clocksource: Use migrate_disable() to avoid calling get_random_u32() in atomic context (CVE-2025-21767)

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

    arm64: cacheinfo: Avoid out-of-bounds write to cacheinfo array (CVE-2025-21785)

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

    team: better TEAM_OPTION_TYPE_STRING validation (CVE-2025-21787)

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

    vrf: use RCU protection in l3mdev_l3_out() (CVE-2025-21791)

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

    NFSD: fix hang in nfsd4_shutdown_callback (CVE-2025-21795)

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

    nfsd: clear acl_access/acl_default after releasing them (CVE-2025-21796)

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

    nilfs2: protect access to buffers with no active references (CVE-2025-21811)

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

    geneve: Fix use-after-free in geneve_find_dev(). (CVE-2025-21858)

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

    vlan: enforce underlying device type (CVE-2025-21920)

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

    net: gso: fix ownership in __udp_gso_segment (CVE-2025-21926)

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

    HID: intel-ish-hid: Fix use-after-free issue in ishtp_hid_remove() (CVE-2025-21928)

Tenable has extracted the preceding description block directly from the tested product 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 version of kernel installed on the remote host is prior to 5.4.291-206.400. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.4-2025-097 advisory.

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

    Squashfs: check the inode number is not the invalid value of zero (CVE-2024-26982)

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

    smb: client: fix UAF in smb2_reconnect_server() (CVE-2024-35870)

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

    pps: Fix a use-after-free (CVE-2024-57979)

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

    rtc: pcf85063: fix potential OOB write in PCF85063 NVMEM read (CVE-2024-58069)

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

    KVM: Explicitly verify target vCPU is online in kvm_get_vcpu() (CVE-2024-58083)

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

    sched: sch_cake: add bounds checks to host bulk flow fairness counts (CVE-2025-21647)

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

    net: sched: Disallow replacing of child qdisc from one parent to another (CVE-2025-21700)

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

    pfifo_tail_enqueue: Drop new packet when sch->limit == 0 (CVE-2025-21702)

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

    nilfs2: do not force clear folio if buffer is referenced (CVE-2025-21722)

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

    nbd: don't allow reconnect after disconnect (CVE-2025-21731)

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

    btrfs: fix use-after-free when attempting to join an aborted transaction (CVE-2025-21753)

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

    ndisc: extend RCU protection in ndisc_send_skb() (CVE-2025-21760)

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

    openvswitch: use RCU protection in ovs_vport_cmd_fill_info() (CVE-2025-21761)

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

    arp: use RCU protection in arp_xmit() (CVE-2025-21762)

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

    neighbour: use RCU protection in __neigh_notify() (CVE-2025-21763)

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

    ndisc: use RCU protection in ndisc_alloc_skb() (CVE-2025-21764)

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

    arm64: cacheinfo: Avoid out-of-bounds write to cacheinfo array (CVE-2025-21785)

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

    vrf: use RCU protection in l3mdev_l3_out() (CVE-2025-21791)

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

    nilfs2: protect access to buffers with no active references (CVE-2025-21811)

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

    geneve: Fix use-after-free in geneve_find_dev(). (CVE-2025-21858)

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

    vlan: enforce underlying device type (CVE-2025-21920)

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

    HID: intel-ish-hid: Fix use-after-free issue in ishtp_hid_remove() (CVE-2025-21928)

Tenable has extracted the preceding description block directly from the tested product 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 remote Debian 11 host has packages installed that are affected by multiple vulnerabilities as referenced in the dla-4102 advisory.

    -------------------------------------------------------------------------     Debian LTS Advisory DLA-4102-1                debian-lts@lists.debian.org     https://www.debian.org/lts/security/                        Ben Hutchings     March 31, 2025                                https://wiki.debian.org/LTS
    -------------------------------------------------------------------------

    Package        : linux-6.1     Version        : 6.1.129-1~deb11u1     CVE ID         : CVE-2024-26596 CVE-2024-40945 CVE-2024-42069 CVE-2024-42122                      CVE-2024-45001 CVE-2024-47726 CVE-2024-49989 CVE-2024-50061                      CVE-2024-54458 CVE-2024-56549 CVE-2024-57834 CVE-2024-57973                      CVE-2024-57978 CVE-2024-57979 CVE-2024-57980 CVE-2024-57981                      CVE-2024-57986 CVE-2024-57993 CVE-2024-57996 CVE-2024-57997                      CVE-2024-57998 CVE-2024-58001 CVE-2024-58007 CVE-2024-58009                      CVE-2024-58010 CVE-2024-58011 CVE-2024-58013 CVE-2024-58014                      CVE-2024-58016 CVE-2024-58017 CVE-2024-58020 CVE-2024-58034                      CVE-2024-58051 CVE-2024-58052 CVE-2024-58054 CVE-2024-58055                      CVE-2024-58056 CVE-2024-58058 CVE-2024-58061 CVE-2024-58063                      CVE-2024-58068 CVE-2024-58069 CVE-2024-58071 CVE-2024-58072                      CVE-2024-58076 CVE-2024-58077 CVE-2024-58080 CVE-2024-58083                      CVE-2024-58085 CVE-2024-58086 CVE-2025-21684 CVE-2025-21700                      CVE-2025-21701 CVE-2025-21703 CVE-2025-21704 CVE-2025-21705                      CVE-2025-21706 CVE-2025-21707 CVE-2025-21708 CVE-2025-21711                      CVE-2025-21715 CVE-2025-21716 CVE-2025-21718 CVE-2025-21719                      CVE-2025-21722 CVE-2025-21724 CVE-2025-21725 CVE-2025-21726                      CVE-2025-21727 CVE-2025-21728 CVE-2025-21731 CVE-2025-21734                      CVE-2025-21735 CVE-2025-21736 CVE-2025-21738 CVE-2025-21744                      CVE-2025-21745 CVE-2025-21748 CVE-2025-21749 CVE-2025-21750                      CVE-2025-21753 CVE-2025-21758 CVE-2025-21760 CVE-2025-21761                      CVE-2025-21762 CVE-2025-21763 CVE-2025-21764 CVE-2025-21765                      CVE-2025-21766 CVE-2025-21767 CVE-2025-21772 CVE-2025-21775                      CVE-2025-21776 CVE-2025-21779 CVE-2025-21780 CVE-2025-21781                      CVE-2025-21782 CVE-2025-21785 CVE-2025-21787 CVE-2025-21790                      CVE-2025-21791 CVE-2025-21792 CVE-2025-21794 CVE-2025-21795                      CVE-2025-21796 CVE-2025-21799 CVE-2025-21802 CVE-2025-21804                      CVE-2025-21806 CVE-2025-21811 CVE-2025-21812 CVE-2025-21814                      CVE-2025-21819 CVE-2025-21820 CVE-2025-21821 CVE-2025-21823                      CVE-2025-21826 CVE-2025-21829 CVE-2025-21830 CVE-2025-21832                      CVE-2025-21835     Debian Bug     : 1071562 1087807 1088159 1091517 1091858 1093371 1095435                      1095745 1095764 1098250 1098354 1099138

    Several vulnerabilities have been discovered in the Linux kernel that     may lead to a privilege escalation, denial of service or information     leaks.

    For Debian 11 bullseye, these problems have been fixed in version     6.1.129-1~deb11u1.  This additionally includes many more bug fixes     from stable update 6.1.129, and a fix for a regression affecting some     Rockchip SoCs.

    We recommend that you upgrade your linux-6.1 packages.

    For the detailed security status of linux-6.1 please refer to     its security tracker page at:
    https://security-tracker.debian.org/tracker/linux-6.1

    Further information about Debian LTS security advisories, how to apply     these updates to your system and frequently asked questions can be     found at: https://wiki.debian.org/LTS     Attachment:
    signature.asc     Description: PGP signature

Tenable has extracted the preceding description block directly from the Debian 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 Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - In the Linux kernel, the following vulnerability has been resolved: nilfs2: do not force clear folio if     buffer is referenced Patch series nilfs2: protect busy buffer heads from being force-cleared. This     series fixes the buffer head state inconsistency issues reported by syzbot that occurs when the filesystem     is corrupted and falls back to read-only, and the associated buffer head use-after-free issue. This patch     (of 2): Syzbot has reported that after nilfs2 detects filesystem corruption and falls back to read-only,     inconsistencies in the buffer state may occur. One of the inconsistencies is that when nilfs2 calls     mark_buffer_dirty() to set a data or metadata buffer as dirty, but it detects that the buffer is not in     the uptodate state: WARNING: CPU: 0 PID: 6049 at fs/buffer.c:1177 mark_buffer_dirty+0x2e5/0x520     fs/buffer.c:1177 ... Call Trace: <TASK> nilfs_palloc_commit_alloc_entry+0x4b/0x160 fs/nilfs2/alloc.c:598     nilfs_ifile_create_inode+0x1dd/0x3a0 fs/nilfs2/ifile.c:73 nilfs_new_inode+0x254/0x830     fs/nilfs2/inode.c:344 nilfs_mkdir+0x10d/0x340 fs/nilfs2/namei.c:218 vfs_mkdir+0x2f9/0x4f0 fs/namei.c:4257     do_mkdirat+0x264/0x3a0 fs/namei.c:4280 __do_sys_mkdirat fs/namei.c:4295 [inline] __se_sys_mkdirat     fs/namei.c:4293 [inline] __x64_sys_mkdirat+0x87/0xa0 fs/namei.c:4293 do_syscall_x64     arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83     entry_SYSCALL_64_after_hwframe+0x77/0x7f The other is when nilfs_btree_propagate(), which propagates the     dirty state to the ancestor nodes of a b-tree that point to a dirty buffer, detects that the origin buffer     is not dirty, even though it should be: WARNING: CPU: 0 PID: 5245 at fs/nilfs2/btree.c:2089     nilfs_btree_propagate+0xc79/0xdf0 fs/nilfs2/btree.c:2089 ... Call Trace: <TASK>     nilfs_bmap_propagate+0x75/0x120 fs/nilfs2/bmap.c:345 nilfs_collect_file_data+0x4d/0xd0     fs/nilfs2/segment.c:587 nilfs_segctor_apply_buffers+0x184/0x340 fs/nilfs2/segment.c:1006     nilfs_segctor_scan_file+0x28c/0xa50 fs/nilfs2/segment.c:1045 nilfs_segctor_collect_blocks     fs/nilfs2/segment.c:1216 [inline] nilfs_segctor_collect fs/nilfs2/segment.c:1540 [inline]     nilfs_segctor_do_construct+0x1c28/0x6b90 fs/nilfs2/segment.c:2115 nilfs_segctor_construct+0x181/0x6b0     fs/nilfs2/segment.c:2479 nilfs_segctor_thread_construct fs/nilfs2/segment.c:2587 [inline]     nilfs_segctor_thread+0x69e/0xe80 fs/nilfs2/segment.c:2701 kthread+0x2f0/0x390 kernel/kthread.c:389     ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30     arch/x86/entry/entry_64.S:244 </TASK> Both of these issues are caused by the callbacks that handle the     page/folio write requests, forcibly clear various states, including the working state of the buffers they     hold, at unexpected times when they detect read-only fallback. Fix these issues by checking if the buffer     is referenced before clearing the page/folio state, and skipping the clear if it is. (CVE-2025-21722)

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

ID	Name	Product	Family	Severity
236963	Ubuntu Pro FIPS-updates 20.04 LTS : Linux kernel (Azure FIPS) vulnerabilities (USN-7518-1)	Nessus	Ubuntu Local Security Checks	high
236880	Ubuntu 20.04 LTS / 22.04 LTS : Linux kernel vulnerabilities (USN-7510-1)	Nessus	Ubuntu Local Security Checks	high
236879	Ubuntu 20.04 LTS : Linux kernel (GCP) vulnerabilities (USN-7512-1)	Nessus	Ubuntu Local Security Checks	high
236878	Ubuntu 18.04 LTS / 20.04 LTS : Linux kernel vulnerabilities (USN-7516-1)	Nessus	Ubuntu Local Security Checks	high
236877	Ubuntu 20.04 LTS : Linux kernel (Xilinx ZynqMP) vulnerabilities (USN-7517-1)	Nessus	Ubuntu Local Security Checks	high
236875	Ubuntu 22.04 LTS : Linux kernel (GCP) vulnerabilities (USN-7511-1)	Nessus	Ubuntu Local Security Checks	high
235246	CBL Mariner 2.0 Security Update: kernel (CVE-2025-21722)	Nessus	MarinerOS Local Security Checks	high
234528	Amazon Linux 2 : kernel (ALASKERNEL-5.10-2025-088)	Nessus	Amazon Linux Local Security Checks	high
233712	Amazon Linux 2 : kernel (ALASKERNEL-5.4-2025-097)	Nessus	Amazon Linux Local Security Checks	high
233595	Debian dla-4102 : linux-config-6.1 - security update	Nessus	Debian Local Security Checks	high
231046	Linux Distros Unpatched Vulnerability : CVE-2025-21722	Nessus	Misc.	high

Detections

Analytics

CVE-2025-21722

high

Tenable Plugins

high

high

high

high

high

high

high

high

high

high

high