In the Linux kernel, the following vulnerability has been resolved: Revert "libfs: fix infinite directory reads for offset dir" The current directory offset allocator (based on mtree_alloc_cyclic) stores the next offset value to return in octx->next_offset. This mechanism typically returns values that increase monotonically over time. Eventually, though, the newly allocated offset value wraps back to a low number (say, 2) which is smaller than other already- allocated offset values. Yu Kuai <yukuai3@huawei.com> reports that, after commit 64a7ce76fb90 ("libfs: fix infinite directory reads for offset dir"), if a directory's offset allocator wraps, existing entries are no longer visible via readdir/getdents because offset_readdir() stops listing entries once an entry's offset is larger than octx->next_offset. These entries vanish persistently -- they can be looked up, but will never again appear in readdir(3) output. The reason for this is that the commit treats directory offsets as monotonically increasing integer values rather than opaque cookies, and introduces this comparison: if (dentry2offset(dentry) >= last_index) { On 64-bit platforms, the directory offset value upper bound is 2^63 - 1. Directory offsets will monotonically increase for millions of years without wrapping. On 32-bit platforms, however, LONG_MAX is 2^31 - 1. The allocator can wrap after only a few weeks (at worst). Revert commit 64a7ce76fb90 ("libfs: fix infinite directory reads for offset dir") to prepare for a fix that can work properly on 32-bit systems and might apply to recent LTS kernels where shmem employs the simple_offset mechanism.

The remote Ubuntu 24.04 LTS / 24.10 host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-7448-1 advisory.

    It was discovered that the CIFS network file system implementation in the Linux kernel did not properly     verify the target namespace when handling upcalls. An attacker could use this to expose sensitive     information. (CVE-2025-2312)

    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:

    - GPIO subsystem;

    - GPU drivers;

    - IRQ chip drivers;

    - Network drivers;

    - Mellanox network drivers;

    - x86 platform drivers;

    - i.MX PM domains;

    - SCSI subsystem;

    - USB Serial drivers;

    - AFS file system;

    - GFS2 file system;

    - File systems infrastructure;

    - Proc file system;

    - SMB network file system;

    - Timer subsystem;

    - Kernel CPU control infrastructure;

    - Memory management;

    - Networking core;

    - Ethtool driver;

    - IEEE 802.15.4 subsystem;

    - Open vSwitch;

    - Network traffic control;

    - VMware vSockets driver; (CVE-2025-21694, CVE-2025-21993, CVE-2025-21684, CVE-2025-21681, CVE-2025-21675,     CVE-2025-21672, CVE-2025-21696, CVE-2025-21691, CVE-2025-21683, CVE-2025-21666, CVE-2025-21682,     CVE-2025-21697, CVE-2025-21668, CVE-2025-21701, CVE-2025-21670, CVE-2025-21676, CVE-2025-21695,     CVE-2025-21692, CVE-2025-21674, CVE-2025-21699, CVE-2024-57948, CVE-2025-21677, CVE-2024-57951,     CVE-2025-21702, CVE-2025-21700, CVE-2024-57949, CVE-2025-21669, CVE-2025-21703, CVE-2025-21756,     CVE-2025-21667, CVE-2024-57952, CVE-2024-57950, CVE-2025-21685, CVE-2025-21693, CVE-2025-21678,     CVE-2025-21665, CVE-2025-21680, CVE-2025-21689, CVE-2025-21690, CVE-2025-21673)

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 24.04 LTS / 24.10 host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-7445-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:

    - GPIO subsystem;

    - GPU drivers;

    - IRQ chip drivers;

    - Network drivers;

    - Mellanox network drivers;

    - x86 platform drivers;

    - i.MX PM domains;

    - SCSI subsystem;

    - USB Serial drivers;

    - AFS file system;

    - GFS2 file system;

    - File systems infrastructure;

    - Proc file system;

    - SMB network file system;

    - Timer subsystem;

    - Kernel CPU control infrastructure;

    - Memory management;

    - Networking core;

    - Ethtool driver;

    - IEEE 802.15.4 subsystem;

    - Open vSwitch;

    - Network traffic control;

    - VMware vSockets driver; (CVE-2025-21685, CVE-2025-21684, CVE-2025-21756, CVE-2025-21670, CVE-2024-57949,     CVE-2025-21677, CVE-2025-21680, CVE-2025-21703, CVE-2024-57952, CVE-2025-21674, CVE-2025-21701,     CVE-2025-21691, CVE-2025-21689, CVE-2025-21668, CVE-2025-21665, CVE-2025-21683, CVE-2025-21675,     CVE-2025-21672, CVE-2024-57948, CVE-2025-21669, CVE-2025-21673, CVE-2025-21692, CVE-2025-21699,     CVE-2025-21702, CVE-2025-21682, CVE-2025-21690, CVE-2025-21681, CVE-2025-21695, CVE-2025-21696,     CVE-2025-21700, CVE-2025-21678, CVE-2025-21676, CVE-2024-57950, CVE-2025-21666, CVE-2025-21694,     CVE-2025-21693, CVE-2025-21993, CVE-2024-57951, CVE-2025-21697, CVE-2025-21667)

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 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: Revert libfs: fix infinite directory     reads for offset dir The current directory offset allocator (based on mtree_alloc_cyclic) stores the next     offset value to return in octx->next_offset. This mechanism typically returns values that increase     monotonically over time. Eventually, though, the newly allocated offset value wraps back to a low number     (say, 2) which is smaller than other already- allocated offset values. Yu Kuai <yukuai3@huawei.com>     reports that, after commit 64a7ce76fb90 (libfs: fix infinite directory reads for offset dir), if a     directory's offset allocator wraps, existing entries are no longer visible via readdir/getdents because     offset_readdir() stops listing entries once an entry's offset is larger than octx->next_offset. These     entries vanish persistently -- they can be looked up, but will never again appear in readdir(3) output.
    The reason for this is that the commit treats directory offsets as monotonically increasing integer values     rather than opaque cookies, and introduces this comparison: if (dentry2offset(dentry) >= last_index) { On     64-bit platforms, the directory offset value upper bound is 2^63 - 1. Directory offsets will monotonically     increase for millions of years without wrapping. On 32-bit platforms, however, LONG_MAX is 2^31 - 1. The     allocator can wrap after only a few weeks (at worst). Revert commit 64a7ce76fb90 (libfs: fix infinite     directory reads for offset dir) to prepare for a fix that can work properly on 32-bit systems and might     apply to recent LTS kernels where shmem employs the simple_offset mechanism. (CVE-2024-57952)

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

ID	Name	Product	Family	Severity
234778	Ubuntu 24.04 LTS / 24.10 : Linux kernel vulnerabilities (USN-7448-1)	Nessus	Ubuntu Local Security Checks	high
234757	Ubuntu 24.04 LTS / 24.10 : Linux kernel vulnerabilities (USN-7445-1)	Nessus	Ubuntu Local Security Checks	high
230423	Linux Distros Unpatched Vulnerability : CVE-2024-57952	Nessus	Misc.	medium

Detections

Analytics

CVE-2024-57952

medium

Tenable Plugins

high

high

medium