In the Linux kernel, the following vulnerability has been resolved: erofs: fix memory leak of LZMA global compressed deduplication When stressing microLZMA EROFS images with the new global compressed deduplication feature enabled (`-Ededupe`), I found some short-lived temporary pages weren't properly released, which could slowly cause unexpected OOMs hours later. Let's fix it now (LZ4 and DEFLATE don't have this issue.)

The Rocky Linux 9.6 host has packages installed that are affected by multiple vulnerabilities as referenced in the CIQ ciqsa-2026_1178 advisory.

    This advisory aggregates security fixes for the kernel SRPM in CIQ LTS 9.6. It addresses 449 CVEs:
    CVE-2024-41037, CVE-2024-50189, CVE-2024-50039, CVE-2024-36013, CVE-2024-56605, and 444 more.

Tenable has extracted the preceding description block directly from the CIQ security advisory.

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

An update of the linux package has been released.

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: erofs: fix memory leak of LZMA global     compressed deduplication When stressing microLZMA EROFS images with the new global compressed     deduplication feature enabled (`-Ededupe`), I found some short-lived temporary pages weren't properly     released, which could slowly cause unexpected OOMs hours later. Let's fix it now (LZ4 and DEFLATE don't     have this issue.) (CVE-2023-52526)

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

The remote CentOS Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the kernel-5.14.0-559.el9 build changelog.

  - In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Remove cache tags before     disabling ATS The current implementation removes cache tags after disabling ATS, leading to potential     memory leaks and kernel crashes. Specifically, CACHE_TAG_DEVTLB type cache tags may still remain in the     list even after the domain is freed, causing a use-after-free condition. This issue really shows up when     multiple VFs from different PFs passed through to a single user-space process via vfio-pci. In such cases,     the kernel may crash with kernel messages like: BUG: kernel NULL pointer dereference, address:
    0000000000000014 PGD 19036a067 P4D 1940a3067 PUD 136c9b067 PMD 0 Oops: Oops: 0000 [#1] PREEMPT SMP NOPTI     CPU: 74 UID: 0 PID: 3183 Comm: testCli Not tainted 6.11.9 #2 RIP: 0010:cache_tag_flush_range+0x9b/0x250     Call Trace: <TASK> ? __die+0x1f/0x60 ? page_fault_oops+0x163/0x590 ? exc_page_fault+0x72/0x190 ?     asm_exc_page_fault+0x22/0x30 ? cache_tag_flush_range+0x9b/0x250 ? cache_tag_flush_range+0x5d/0x250     intel_iommu_tlb_sync+0x29/0x40 intel_iommu_unmap_pages+0xfe/0x160 __iommu_unmap+0xd8/0x1a0     vfio_unmap_unpin+0x182/0x340 [vfio_iommu_type1] vfio_remove_dma+0x2a/0xb0 [vfio_iommu_type1]     vfio_iommu_type1_ioctl+0xafa/0x18e0 [vfio_iommu_type1] Move cache_tag_unassign_domain() before     iommu_disable_pci_caps() to fix it. (CVE-2024-56669)

  - In the Linux kernel, the following vulnerability has been resolved: erofs: fix pcluster use-after-free on     UP platforms During stress testing with CONFIG_SMP disabled, KASAN reports as below:
    ================================================================== BUG: KASAN: use-after-free in
    __mutex_lock+0xe5/0xc30 Read of size 8 at addr ffff8881094223f8 by task stress/7789 CPU: 0 PID: 7789 Comm:
    stress Not tainted 6.0.0-rc1-00002-g0d53d2e882f9 #3 Hardware name: Red Hat KVM, BIOS 0.5.1 01/01/2011 Call     Trace: <TASK> .. __mutex_lock+0xe5/0xc30 .. z_erofs_do_read_page+0x8ce/0x1560 ..
    z_erofs_readahead+0x31c/0x580 .. Freed by task 7787 kasan_save_stack+0x1e/0x40 kasan_set_track+0x20/0x30     kasan_set_free_info+0x20/0x40 __kasan_slab_free+0x10c/0x190 kmem_cache_free+0xed/0x380     rcu_core+0x3d5/0xc90 __do_softirq+0x12d/0x389 Last potentially related work creation:
    kasan_save_stack+0x1e/0x40 __kasan_record_aux_stack+0x97/0xb0 call_rcu+0x3d/0x3f0     erofs_shrink_workstation+0x11f/0x210 erofs_shrink_scan+0xdc/0x170 shrink_slab.constprop.0+0x296/0x530     drop_slab+0x1c/0x70 drop_caches_sysctl_handler+0x70/0x80 proc_sys_call_handler+0x20a/0x2f0     vfs_write+0x555/0x6c0 ksys_write+0xbe/0x160 do_syscall_64+0x3b/0x90 The root cause is that     erofs_workgroup_unfreeze() doesn't reset to orig_val thus it causes a race that the pcluster reuses     unexpectedly before freeing. Since UP platforms are quite rare now, such path becomes unnecessary. Let's     drop such specific-designed path directly instead. (CVE-2022-48674)

  - In the Linux kernel, the following vulnerability has been resolved: erofs: fix memory leak of LZMA global     compressed deduplication When stressing microLZMA EROFS images with the new global compressed     deduplication feature enabled (`-Ededupe`), I found some short-lived temporary pages weren't properly     released, which could slowly cause unexpected OOMs hours later. Let's fix it now (LZ4 and DEFLATE don't     have this issue.) (CVE-2023-52526)

  - In the Linux kernel, the following vulnerability has been resolved: iommu/s390: Implement blocking domain     This fixes a crash when surprise hot-unplugging a PCI device. This crash happens because during hot-unplug
    __iommu_group_set_domain_nofail() attaching the default domain fails when the platform no longer     recognizes the device as it has already been removed and we end up with a NULL domain pointer and UAF.
    This is exactly the case referred to in the second comment in __iommu_device_set_domain() and just as     stated there if we can instead attach the blocking domain the UAF is prevented as this can handle the     already removed device. Implement the blocking domain to use this handling. With this change, the crash is     fixed but we still hit a warning attempting to change DMA ownership on a blocked device. (CVE-2024-53232)

  - In the Linux kernel, the following vulnerability has been resolved: i3c: master: Fix miss free     init_dyn_addr at i3c_master_put_i3c_addrs() if (dev->boardinfo && dev->boardinfo->init_dyn_addr) ^^^ here     check init_dyn_addr i3c_bus_set_addr_slot_status(&master->bus, dev->info.dyn_addr, ...) ^^^^ free     dyn_addr Fix copy/paste error dyn_addr by replacing it with init_dyn_addr. (CVE-2024-56562)

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

ID	Name	Product	Family	Type	Severity
354357	Rocky Linux 9.6 [CIQ] Security Update: kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc Multiple Vulnerabilities (ciqsa-2026_1178)	Nessus	Rocky Linux Local Security Checks	Local	critical
332630	Photon OS 5.0: Linux PHSA-2023-5.0-91-0130	Nessus	PhotonOS Local Security Checks	Local	high
247091	Linux Distros Unpatched Vulnerability : CVE-2023-52526	Nessus	Misc.	Local	medium
214888	CentOS 9 : kernel-5.14.0-559.el9	Nessus	CentOS Local Security Checks	Local	high
203657	Photon OS 5.0: Linux PHSA-2023-5.0-0130	Nessus	PhotonOS Local Security Checks	Local	high

Detections

Analytics

CVE-2023-52526

medium

Tenable Plugins

critical

high

medium

high

high