In the Linux kernel, the following vulnerability has been resolved: ocfs2: remove entry once instead of null-ptr-dereference in ocfs2_xa_remove() Syzkaller is able to provoke null-ptr-dereference in ocfs2_xa_remove(): [ 57.319872] (a.out,1161,7):ocfs2_xa_remove:2028 ERROR: status = -12 [ 57.320420] (a.out,1161,7):ocfs2_xa_cleanup_value_truncate:1999 ERROR: Partial truncate while removing xattr overlay.upper. Leaking 1 clusters and removing the entry [ 57.321727] BUG: kernel NULL pointer dereference, address: 0000000000000004 [...] [ 57.325727] RIP: 0010:ocfs2_xa_block_wipe_namevalue+0x2a/0xc0 [...] [ 57.331328] Call Trace: [ 57.331477] <TASK> [...] [ 57.333511] ? do_user_addr_fault+0x3e5/0x740 [ 57.333778] ? exc_page_fault+0x70/0x170 [ 57.334016] ? asm_exc_page_fault+0x2b/0x30 [ 57.334263] ? __pfx_ocfs2_xa_block_wipe_namevalue+0x10/0x10 [ 57.334596] ? ocfs2_xa_block_wipe_namevalue+0x2a/0xc0 [ 57.334913] ocfs2_xa_remove_entry+0x23/0xc0 [ 57.335164] ocfs2_xa_set+0x704/0xcf0 [ 57.335381] ? _raw_spin_unlock+0x1a/0x40 [ 57.335620] ? ocfs2_inode_cache_unlock+0x16/0x20 [ 57.335915] ? trace_preempt_on+0x1e/0x70 [ 57.336153] ? start_this_handle+0x16c/0x500 [ 57.336410] ? preempt_count_sub+0x50/0x80 [ 57.336656] ? _raw_read_unlock+0x20/0x40 [ 57.336906] ? start_this_handle+0x16c/0x500 [ 57.337162] ocfs2_xattr_block_set+0xa6/0x1e0 [ 57.337424] __ocfs2_xattr_set_handle+0x1fd/0x5d0 [ 57.337706] ? ocfs2_start_trans+0x13d/0x290 [ 57.337971] ocfs2_xattr_set+0xb13/0xfb0 [ 57.338207] ? dput+0x46/0x1c0 [ 57.338393] ocfs2_xattr_trusted_set+0x28/0x30 [ 57.338665] ? ocfs2_xattr_trusted_set+0x28/0x30 [ 57.338948] __vfs_removexattr+0x92/0xc0 [ 57.339182] __vfs_removexattr_locked+0xd5/0x190 [ 57.339456] ? preempt_count_sub+0x50/0x80 [ 57.339705] vfs_removexattr+0x5f/0x100 [...] Reproducer uses faultinject facility to fail ocfs2_xa_remove() -> ocfs2_xa_value_truncate() with -ENOMEM. In this case the comment mentions that we can return 0 if ocfs2_xa_cleanup_value_truncate() is going to wipe the entry anyway. But the following 'rc' check is wrong and execution flow do 'ocfs2_xa_remove_entry(loc);' twice: * 1st: in ocfs2_xa_cleanup_value_truncate(); * 2nd: returning back to ocfs2_xa_remove() instead of going to 'out'. Fix this by skipping the 2nd removal of the same entry and making syzkaller repro happy.

The remote Debian 12 host has packages installed that are affected by multiple vulnerabilities as referenced in the dsa-5818 advisory.

    - -------------------------------------------------------------------------     Debian Security Advisory DSA-5818-1                   security@debian.org     https://www.debian.org/security/                     Salvatore Bonaccorso     November 24, 2024                     https://www.debian.org/security/faq
    - -------------------------------------------------------------------------

    Package        : linux     CVE ID         : CVE-2022-45888 CVE-2023-52812 CVE-2024-26952 CVE-2024-26954                      CVE-2024-35964 CVE-2024-36244 CVE-2024-36478 CVE-2024-36914                      CVE-2024-36915 CVE-2024-36923 CVE-2024-38540 CVE-2024-38553                      CVE-2024-41080 CVE-2024-42322 CVE-2024-43868 CVE-2024-43904                      CVE-2024-43911 CVE-2024-44949 CVE-2024-49950 CVE-2024-49960                      CVE-2024-49974 CVE-2024-49986 CVE-2024-49991 CVE-2024-50012                      CVE-2024-50036 CVE-2024-50067 CVE-2024-50072 CVE-2024-50126                      CVE-2024-50215 CVE-2024-50218 CVE-2024-50228 CVE-2024-50229                      CVE-2024-50230 CVE-2024-50232 CVE-2024-50233 CVE-2024-50234                      CVE-2024-50235 CVE-2024-50236 CVE-2024-50237 CVE-2024-50242                      CVE-2024-50243 CVE-2024-50244 CVE-2024-50245 CVE-2024-50247                      CVE-2024-50249 CVE-2024-50250 CVE-2024-50251 CVE-2024-50252                      CVE-2024-50255 CVE-2024-50256 CVE-2024-50257 CVE-2024-50259                      CVE-2024-50261 CVE-2024-50262 CVE-2024-50264 CVE-2024-50265                      CVE-2024-50267 CVE-2024-50268 CVE-2024-50269 CVE-2024-50271                      CVE-2024-50272 CVE-2024-50273 CVE-2024-50276 CVE-2024-50278                      CVE-2024-50279 CVE-2024-50280 CVE-2024-50282 CVE-2024-50283                      CVE-2024-50284 CVE-2024-50286 CVE-2024-50287 CVE-2024-50290                      CVE-2024-50292 CVE-2024-50295 CVE-2024-50296 CVE-2024-50299                      CVE-2024-50301 CVE-2024-50302 CVE-2024-53042 CVE-2024-53043                      CVE-2024-53052 CVE-2024-53054 CVE-2024-53055 CVE-2024-53057                      CVE-2024-53058 CVE-2024-53059 CVE-2024-53060 CVE-2024-53061                      CVE-2024-53063 CVE-2024-53066 CVE-2024-53070 CVE-2024-53072                      CVE-2024-53081 CVE-2024-53082 CVE-2024-53088 CVE-2024-53093

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

    For the stable distribution (bookworm), these problems have been fixed in     version 6.1.119-1.

    We recommend that you upgrade your linux packages.

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

    Further information about Debian Security Advisories, how to apply     these updates to your system and frequently asked questions can be     found at: https://www.debian.org/security/

    Mailing list: debian-security-announce@lists.debian.org

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.

Detections

Analytics

CVE-2024-50265

high

Tenable Plugins

high