In the Linux kernel, the following vulnerability has been resolved: s390/bpf: Fix bpf_plt pointer arithmetic Kui-Feng Lee reported a crash on s390x triggered by the dummy_st_ops/dummy_init_ptr_arg test [1]: [<0000000000000002>] 0x2 [<00000000009d5cde>] bpf_struct_ops_test_run+0x156/0x250 [<000000000033145a>] __sys_bpf+0xa1a/0xd00 [<00000000003319dc>] __s390x_sys_bpf+0x44/0x50 [<0000000000c4382c>] __do_syscall+0x244/0x300 [<0000000000c59a40>] system_call+0x70/0x98 This is caused by GCC moving memcpy() after assignments in bpf_jit_plt(), resulting in NULL pointers being written instead of the return and the target addresses. Looking at the GCC internals, the reordering is allowed because the alias analysis thinks that the memcpy() destination and the assignments' left-hand-sides are based on different objects: new_plt and bpf_plt_ret/bpf_plt_target respectively, and therefore they cannot alias. This is in turn due to a violation of the C standard: When two pointers are subtracted, both shall point to elements of the same array object, or one past the last element of the array object ... From the C's perspective, bpf_plt_ret and bpf_plt are distinct objects and cannot be subtracted. In the practical terms, doing so confuses the GCC's alias analysis. The code was written this way in order to let the C side know a few offsets defined in the assembly. While nice, this is by no means necessary. Fix the noncompliance by hardcoding these offsets. [1] https://lore.kernel.org/bpf/c9923c1d-971d-4022-8dc8-1364e929d34c@gmail.com/

The version of hyperv-daemons installed on the remote Azure Linux 3.0 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the CVE-2024-35917 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: s390/bpf: Fix bpf_plt pointer     arithmetic Kui-Feng Lee reported a crash on s390x triggered by the dummy_st_ops/dummy_init_ptr_arg test     [1]: [<0000000000000002>] 0x2 [<00000000009d5cde>] bpf_struct_ops_test_run+0x156/0x250     [<000000000033145a>] __sys_bpf+0xa1a/0xd00 [<00000000003319dc>] __s390x_sys_bpf+0x44/0x50     [<0000000000c4382c>] __do_syscall+0x244/0x300 [<0000000000c59a40>] system_call+0x70/0x98 This is caused by     GCC moving memcpy() after assignments in bpf_jit_plt(), resulting in NULL pointers being written instead     of the return and the target addresses. Looking at the GCC internals, the reordering is allowed because     the alias analysis thinks that the memcpy() destination and the assignments' left-hand-sides are based on     different objects: new_plt and bpf_plt_ret/bpf_plt_target respectively, and therefore they cannot alias.
    This is in turn due to a violation of the C standard: When two pointers are subtracted, both shall point     to elements of the same array object, or one past the last element of the array object ... From the C's     perspective, bpf_plt_ret and bpf_plt are distinct objects and cannot be subtracted. In the practical     terms, doing so confuses the GCC's alias analysis. The code was written this way in order to let the C     side know a few offsets defined in the assembly. While nice, this is by no means necessary. Fix the     noncompliance by hardcoding these offsets. [1]     https://lore.kernel.org/bpf/c9923c1d-971d-4022-8dc8-1364e929d34c@gmail.com/ (CVE-2024-35917)

Note that Nessus has not tested for this issue 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: s390/bpf: Fix bpf_plt pointer     arithmetic Kui-Feng Lee reported a crash on s390x triggered by the dummy_st_ops/dummy_init_ptr_arg test     [1]: [<0000000000000002>] 0x2 [<00000000009d5cde>] bpf_struct_ops_test_run+0x156/0x250     [<000000000033145a>] __sys_bpf+0xa1a/0xd00 [<00000000003319dc>] __s390x_sys_bpf+0x44/0x50     [<0000000000c4382c>] __do_syscall+0x244/0x300 [<0000000000c59a40>] system_call+0x70/0x98 This is caused by     GCC moving memcpy() after assignments in bpf_jit_plt(), resulting in NULL pointers being written instead     of the return and the target addresses. Looking at the GCC internals, the reordering is allowed because     the alias analysis thinks that the memcpy() destination and the assignments' left-hand-sides are based on     different objects: new_plt and bpf_plt_ret/bpf_plt_target respectively, and therefore they cannot alias.
    This is in turn due to a violation of the C standard: When two pointers are subtracted, both shall point     to elements of the same array object, or one past the last element of the array object ... From the C's     perspective, bpf_plt_ret and bpf_plt are distinct objects and cannot be subtracted. In the practical     terms, doing so confuses the GCC's alias analysis. The code was written this way in order to let the C     side know a few offsets defined in the assembly. While nice, this is by no means necessary. Fix the     noncompliance by hardcoding these offsets. [1]     https://lore.kernel.org/bpf/c9923c1d-971d-4022-8dc8-1364e929d34c@gmail.com/ (CVE-2024-35917)

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

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

    It was discovered that a race condition existed in the Bluetooth subsystem in the Linux kernel when     modifying certain settings values through debugfs. A privileged local attacker could use this to cause a     denial of service.

    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;

    - RISC-V architecture;

    - S390 architecture;

    - x86 architecture;

    - Block layer subsystem;

    - Compute Acceleration Framework;

    - Accessibility subsystem;

    - Android drivers;

    - Drivers core;

    - Bluetooth drivers;

    - Clock framework and drivers;

    - Data acquisition framework and drivers;

    - Cryptographic API;

    - Buffer Sharing and Synchronization framework;

    - GPU drivers;

    - On-Chip Interconnect management framework;

    - IOMMU subsystem;

    - Multiple devices driver;

    - Media drivers;

    - VMware VMCI Driver;

    - Network drivers;

    - Microsoft Azure Network Adapter (MANA) driver;

    - Device tree and open firmware driver;

    - Chrome hardware platform drivers;

    - i.MX PM domains;

    - TI SCI PM domains driver;

    - S/390 drivers;

    - SCSI drivers;

    - SPI subsystem;

    - Thermal drivers;

    - TTY drivers;

    - USB subsystem;

    - Framebuffer layer;

    - BTRFS file system;

    - Network file system server daemon;

    - NILFS2 file system;

    - File systems infrastructure;

    - Pstore file system;

    - SMB network file system;

    - BPF subsystem;

    - Bluetooth subsystem;

    - Netfilter;

    - io_uring subsystem;

    - Core kernel;

    - Extra boot config (XBC);

    - Memory management;

    - Amateur Radio drivers;

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

    - Ethernet bridge;

    - Networking core;

    - IPv4 networking;

    - IPv6 networking;

    - Multipath TCP;

    - NFC subsystem;

    - RDS protocol;

    - Network traffic control;

    - SMC sockets;

    - Sun RPC protocol;

    - TLS protocol;

    - Unix domain sockets;

    - Wireless networking;

    - eXpress Data Path;

    - SELinux security module; (CVE-2024-26988, CVE-2024-36023, CVE-2024-35869, CVE-2024-35938,     CVE-2024-27000, CVE-2024-35880, CVE-2024-35915, CVE-2024-35959, CVE-2024-35883, CVE-2024-35886,     CVE-2024-35976, CVE-2024-35903, CVE-2024-35980, CVE-2024-27020, CVE-2024-35955, CVE-2024-35964,     CVE-2024-26980, CVE-2024-35882, CVE-2024-35927, CVE-2024-35884, CVE-2024-35914, CVE-2024-35905,     CVE-2024-26925, CVE-2024-35885, CVE-2024-26990, CVE-2024-27012, CVE-2024-35969, CVE-2024-35862,     CVE-2024-35956, CVE-2024-35971, CVE-2024-27022, CVE-2024-35935, CVE-2024-26992, CVE-2024-27010,     CVE-2024-35892, CVE-2024-26999, CVE-2024-26989, CVE-2024-35963, CVE-2024-35981, CVE-2024-26997,     CVE-2024-35920, CVE-2024-35918, CVE-2024-35933, CVE-2024-35867, CVE-2024-35904, CVE-2024-35890,     CVE-2024-35968, CVE-2024-35917, CVE-2024-35897, CVE-2024-26922, CVE-2024-36026, CVE-2024-27013,     CVE-2024-26991, CVE-2024-26996, CVE-2024-35873, CVE-2024-26987, CVE-2024-35895, CVE-2024-36027,     CVE-2024-35896, CVE-2024-35894, CVE-2024-26983, CVE-2024-35966, CVE-2024-35967, CVE-2024-35945,     CVE-2024-27003, CVE-2024-35939, CVE-2024-35861, CVE-2024-26985, CVE-2024-27015, CVE-2024-35982,     CVE-2024-35912, CVE-2024-35979, CVE-2024-35879, CVE-2024-26982, CVE-2024-35891, CVE-2024-35925,     CVE-2024-35870, CVE-2024-27021, CVE-2024-35866, CVE-2024-27014, CVE-2024-27001, CVE-2024-27004,     CVE-2024-35953, CVE-2024-36021, CVE-2024-35931, CVE-2024-27007, CVE-2024-35922, CVE-2024-35872,     CVE-2024-35926, CVE-2024-27016, CVE-2024-26984, CVE-2024-35919, CVE-2024-35911, CVE-2024-26923,     CVE-2024-35929, CVE-2024-35887, CVE-2024-35893, CVE-2024-35898, CVE-2024-35930, CVE-2024-35934,     CVE-2024-35916, CVE-2024-35877, CVE-2024-26926, CVE-2024-35974, CVE-2024-36018, CVE-2024-27002,     CVE-2024-35975, CVE-2024-35864, CVE-2024-35958, CVE-2024-35944, CVE-2024-35985, CVE-2024-35940,     CVE-2024-35900, CVE-2024-27018, CVE-2024-26936, CVE-2024-36024, CVE-2024-26998, CVE-2024-35954,     CVE-2024-35878, CVE-2024-26928, CVE-2024-35952, CVE-2024-36020, CVE-2024-26986, CVE-2024-35950,     CVE-2024-35957, CVE-2024-35909, CVE-2024-27005, CVE-2024-35978, CVE-2024-35875, CVE-2024-35943,     CVE-2024-35970, CVE-2024-35863, CVE-2024-26993, CVE-2024-35865, CVE-2024-26995, CVE-2024-35888,     CVE-2024-35899, CVE-2024-35868, CVE-2023-52699, CVE-2024-26994, CVE-2024-26817, CVE-2024-35902,     CVE-2024-35977, CVE-2024-35961, CVE-2024-36025, CVE-2024-35936, CVE-2024-35913, CVE-2024-27017,     CVE-2024-35889, CVE-2024-35972, CVE-2024-35901, CVE-2024-26921, CVE-2024-26924, CVE-2024-35951,     CVE-2024-35860, CVE-2024-35907, CVE-2024-35910, CVE-2024-36022, CVE-2024-27019, CVE-2024-27009,     CVE-2024-26981, CVE-2024-35973, CVE-2024-35965, CVE-2024-36019, CVE-2024-35871, CVE-2024-27008,     CVE-2024-26811, CVE-2024-35908, CVE-2024-35921, CVE-2024-35942, CVE-2024-35946, CVE-2024-35924,     CVE-2024-27011, CVE-2024-35960, CVE-2024-27006, CVE-2024-35937, CVE-2024-35932)

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 host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-6893-3 advisory.

    It was discovered that a race condition existed in the Bluetooth subsystem in the Linux kernel when     modifying certain settings values through debugfs. A privileged local attacker could use this to cause a     denial of service. (CVE-2024-24857, CVE-2024-24858, CVE-2024-24859)

    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;

    - RISC-V architecture;

    - S390 architecture;

    - x86 architecture;

    - Block layer subsystem;

    - Compute Acceleration Framework;

    - Accessibility subsystem;

    - Android drivers;

    - Drivers core;

    - Bluetooth drivers;

    - Clock framework and drivers;

    - Data acquisition framework and drivers;

    - Cryptographic API;

    - Buffer Sharing and Synchronization framework;

    - GPU drivers;

    - On-Chip Interconnect management framework;

    - IOMMU subsystem;

    - Multiple devices driver;

    - Media drivers;

    - VMware VMCI Driver;

    - Network drivers;

    - Microsoft Azure Network Adapter (MANA) driver;

    - Device tree and open firmware driver;

    - Chrome hardware platform drivers;

    - i.MX PM domains;

    - TI SCI PM domains driver;

    - S/390 drivers;

    - SCSI drivers;

    - SPI subsystem;

    - Thermal drivers;

    - TTY drivers;

    - USB subsystem;

    - Framebuffer layer;

    - BTRFS file system;

    - Network file system server daemon;

    - NILFS2 file system;

    - File systems infrastructure;

    - Pstore file system;

    - SMB network file system;

    - BPF subsystem;

    - Bluetooth subsystem;

    - Netfilter;

    - io_uring subsystem;

    - Core kernel;

    - Extra boot config (XBC);

    - Memory management;

    - Amateur Radio drivers;

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

    - Ethernet bridge;

    - Networking core;

    - IPv4 networking;

    - IPv6 networking;

    - Multipath TCP;

    - NFC subsystem;

    - RDS protocol;

    - Network traffic control;

    - SMC sockets;

    - Sun RPC protocol;

    - TLS protocol;

    - Unix domain sockets;

    - Wireless networking;

    - eXpress Data Path;

    - SELinux security module; (CVE-2024-35955, CVE-2024-35921, CVE-2024-35946, CVE-2024-35934,     CVE-2024-26993, CVE-2024-35899, CVE-2024-35952, CVE-2024-35894, CVE-2024-35886, CVE-2024-35872,     CVE-2024-35970, CVE-2024-35936, CVE-2024-35907, CVE-2024-27013, CVE-2024-35910, CVE-2024-27009,     CVE-2024-35875, CVE-2024-36021, CVE-2024-26923, CVE-2024-26997, CVE-2024-35978, CVE-2024-35981,     CVE-2024-27015, CVE-2024-26928, CVE-2024-35963, CVE-2024-35897, CVE-2024-27020, CVE-2024-35922,     CVE-2024-27001, CVE-2024-27011, CVE-2024-35940, CVE-2024-35871, CVE-2024-35900, CVE-2024-35869,     CVE-2024-35905, CVE-2024-35974, CVE-2024-35873, CVE-2024-35882, CVE-2024-35914, CVE-2024-35956,     CVE-2024-35887, CVE-2024-35920, CVE-2024-27018, CVE-2024-35880, CVE-2024-35943, CVE-2024-35912,     CVE-2024-35979, CVE-2024-35862, CVE-2024-36019, CVE-2024-35950, CVE-2024-35977, CVE-2024-35918,     CVE-2024-26992, CVE-2024-35884, CVE-2024-35916, CVE-2024-26817, CVE-2024-35959, CVE-2024-35909,     CVE-2024-35933, CVE-2024-35982, CVE-2024-26996, CVE-2024-35980, CVE-2024-36018, CVE-2024-26925,     CVE-2024-35929, CVE-2024-35971, CVE-2024-26990, CVE-2024-35885, CVE-2024-36025, CVE-2024-26998,     CVE-2024-35930, CVE-2024-26982, CVE-2024-36022, CVE-2024-35895, CVE-2024-35902, CVE-2024-35911,     CVE-2024-27002, CVE-2024-35968, CVE-2024-35861, CVE-2024-35903, CVE-2024-36026, CVE-2024-35896,     CVE-2024-35945, CVE-2024-26936, CVE-2024-35954, CVE-2024-26985, CVE-2024-35908, CVE-2024-35924,     CVE-2024-35938, CVE-2024-26991, CVE-2024-27017, CVE-2024-26922, CVE-2024-35919, CVE-2024-35915,     CVE-2024-35985, CVE-2024-26995, CVE-2024-35870, CVE-2024-27010, CVE-2024-35904, CVE-2024-26999,     CVE-2024-26983, CVE-2024-35939, CVE-2024-35865, CVE-2024-35860, CVE-2024-35944, CVE-2024-27021,     CVE-2024-27016, CVE-2024-27004, CVE-2024-27019, CVE-2024-36027, CVE-2024-35890, CVE-2024-35975,     CVE-2024-35901, CVE-2024-35967, CVE-2024-26986, CVE-2024-35957, CVE-2024-35937, CVE-2024-26988,     CVE-2024-35972, CVE-2024-35926, CVE-2024-26926, CVE-2024-35964, CVE-2024-26994, CVE-2024-35889,     CVE-2024-26981, CVE-2024-36024, CVE-2024-27022, CVE-2024-35935, CVE-2024-26811, CVE-2024-35932,     CVE-2024-35866, CVE-2024-27008, CVE-2024-27012, CVE-2024-36023, CVE-2024-35931, CVE-2024-35888,     CVE-2024-26989, CVE-2024-35868, CVE-2024-35976, CVE-2024-35953, CVE-2024-36020, CVE-2024-35893,     CVE-2024-35961, CVE-2024-35965, CVE-2024-35892, CVE-2024-35942, CVE-2024-35958, CVE-2024-27014,     CVE-2024-35867, CVE-2024-27003, CVE-2024-27007, CVE-2024-35951, CVE-2024-35973, CVE-2024-35863,     CVE-2024-26984, CVE-2024-35898, CVE-2024-35960, CVE-2024-27005, CVE-2024-35917, CVE-2024-35927,     CVE-2024-26980, CVE-2024-35877, CVE-2024-35925, CVE-2024-26921, CVE-2024-35913, CVE-2023-52699,     CVE-2024-26987, CVE-2024-27006, CVE-2024-35878, CVE-2024-35864, CVE-2024-35969, CVE-2024-35883,     CVE-2024-35891, CVE-2024-35879, CVE-2024-27000, CVE-2024-35966)

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 host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-6893-2 advisory.

    It was discovered that a race condition existed in the Bluetooth subsystem in the Linux kernel when     modifying certain settings values through debugfs. A privileged local attacker could use this to cause a     denial of service.

    (CVE-2024-24857, CVE-2024-24858, CVE-2024-24859)

    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;

    - RISC-V architecture;

    - S390 architecture;

    - x86 architecture;

    - Block layer subsystem;

    - Compute Acceleration Framework;

    - Accessibility subsystem;

    - Android drivers;

    - Drivers core;

    - Bluetooth drivers;

    - Clock framework and drivers;

    - Data acquisition framework and drivers;

    - Cryptographic API;

    - Buffer Sharing and Synchronization framework;

    - GPU drivers;

    - On-Chip Interconnect management framework;

    - IOMMU subsystem;

    - Multiple devices driver;

    - Media drivers;

    - VMware VMCI Driver;

    - Network drivers;

    - Microsoft Azure Network Adapter (MANA) driver;

    - Device tree and open firmware driver;

    - Chrome hardware platform drivers;

    - i.MX PM domains;

    - TI SCI PM domains driver;

    - S/390 drivers;

    - SCSI drivers;

    - SPI subsystem;

    - Thermal drivers;

    - TTY drivers;

    - USB subsystem;

    - Framebuffer layer;

    - BTRFS file system;

    - Network file system server daemon;

    - NILFS2 file system;

    - File systems infrastructure;

    - Pstore file system;

    - SMB network file system;

    - BPF subsystem;

    - Bluetooth subsystem;

    - Netfilter;

    - io_uring subsystem;

    - Core kernel;

    - Extra boot config (XBC);

    - Memory management;

    - Amateur Radio drivers;

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

    - Ethernet bridge;

    - Networking core;

    - IPv4 networking;

    - IPv6 networking;

    - Multipath TCP;

    - NFC subsystem;

    - RDS protocol;

    - Network traffic control;

    - SMC sockets;

    - Sun RPC protocol;

    - TLS protocol;

    - Unix domain sockets;

    - Wireless networking;

    - eXpress Data Path;

    - SELinux security module; (CVE-2024-35976, CVE-2024-35873, CVE-2024-35959, CVE-2024-27012,     CVE-2024-36025, CVE-2024-35868, CVE-2024-26995, CVE-2024-35916, CVE-2024-36023, CVE-2024-35964,     CVE-2024-35890, CVE-2024-26980, CVE-2024-35950, CVE-2024-27006, CVE-2024-35955, CVE-2024-35885,     CVE-2024-35960, CVE-2024-35932, CVE-2024-26986, CVE-2024-35884, CVE-2024-35860, CVE-2024-36020,     CVE-2024-35930, CVE-2024-35919, CVE-2024-27020, CVE-2024-26928, CVE-2024-35903, CVE-2024-35907,     CVE-2024-35904, CVE-2024-35972, CVE-2024-35892, CVE-2024-26921, CVE-2024-35869, CVE-2024-35957,     CVE-2024-35967, CVE-2024-35927, CVE-2024-35946, CVE-2024-27000, CVE-2024-35943, CVE-2024-35902,     CVE-2024-27013, CVE-2024-35968, CVE-2024-35970, CVE-2024-35865, CVE-2024-36022, CVE-2024-26993,     CVE-2024-36027, CVE-2024-35895, CVE-2024-35908, CVE-2024-35901, CVE-2024-35872, CVE-2024-26925,     CVE-2024-35917, CVE-2024-35898, CVE-2024-35861, CVE-2024-35900, CVE-2024-26984, CVE-2024-35891,     CVE-2023-52699, CVE-2024-35961, CVE-2024-35951, CVE-2024-36019, CVE-2024-27021, CVE-2024-35939,     CVE-2024-26997, CVE-2024-26999, CVE-2024-35897, CVE-2024-35896, CVE-2024-26817, CVE-2024-35875,     CVE-2024-35935, CVE-2024-27015, CVE-2024-26982, CVE-2024-35958, CVE-2024-26989, CVE-2024-26922,     CVE-2024-26811, CVE-2024-27003, CVE-2024-35920, CVE-2024-27007, CVE-2024-35879, CVE-2024-35979,     CVE-2024-35978, CVE-2024-35914, CVE-2024-35938, CVE-2024-35913, CVE-2024-26985, CVE-2024-35915,     CVE-2024-35974, CVE-2024-27001, CVE-2024-35940, CVE-2024-35867, CVE-2024-26994, CVE-2024-35886,     CVE-2024-35899, CVE-2024-27022, CVE-2024-35910, CVE-2024-35893, CVE-2024-27010, CVE-2024-36024,     CVE-2024-26926, CVE-2024-26923, CVE-2024-26990, CVE-2024-35912, CVE-2024-26987, CVE-2024-35966,     CVE-2024-35977, CVE-2024-35866, CVE-2024-35975, CVE-2024-35965, CVE-2024-35933, CVE-2024-26936,     CVE-2024-35889, CVE-2024-35863, CVE-2024-27002, CVE-2024-27018, CVE-2024-36021, CVE-2024-27019,     CVE-2024-35921, CVE-2024-35870, CVE-2024-35956, CVE-2024-27016, CVE-2024-26996, CVE-2024-35878,     CVE-2024-26988, CVE-2024-35888, CVE-2024-35936, CVE-2024-27014, CVE-2024-35883, CVE-2024-35862,     CVE-2024-35945, CVE-2024-26983, CVE-2024-35982, CVE-2024-35924, CVE-2024-27004, CVE-2024-27008,     CVE-2024-35963, CVE-2024-35909, CVE-2024-35911, CVE-2024-35973, CVE-2024-35887, CVE-2024-27009,     CVE-2024-35980, CVE-2024-36026, CVE-2024-35969, CVE-2024-35954, CVE-2024-35864, CVE-2024-35953,     CVE-2024-26998, CVE-2024-35931, CVE-2024-26981, CVE-2024-35971, CVE-2024-35934, CVE-2024-35929,     CVE-2024-35918, CVE-2024-35937, CVE-2024-36018, CVE-2024-35877, CVE-2024-35925, CVE-2024-35981,     CVE-2024-35985, CVE-2024-35942, CVE-2024-35922, CVE-2024-35952, CVE-2024-27011, CVE-2024-35944,     CVE-2024-35905, CVE-2024-35880, CVE-2024-35882, CVE-2024-27005, CVE-2024-26991, CVE-2024-35871,     CVE-2024-35926, CVE-2024-26992, CVE-2024-35894, CVE-2024-27017)

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 host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-6893-1 advisory.

    It was discovered that a race condition existed in the Bluetooth subsystem in the Linux kernel when     modifying certain settings values through debugfs. A privileged local attacker could use this to cause a     denial of service. (CVE-2024-24857, CVE-2024-24858, CVE-2024-24859)

    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;

    - RISC-V architecture;

    - S390 architecture;

    - x86 architecture;

    - Block layer subsystem;

    - Compute Acceleration Framework;

    - Accessibility subsystem;

    - Android drivers;

    - Drivers core;

    - Bluetooth drivers;

    - Clock framework and drivers;

    - Data acquisition framework and drivers;

    - Cryptographic API;

    - Buffer Sharing and Synchronization framework;

    - GPU drivers;

    - On-Chip Interconnect management framework;

    - IOMMU subsystem;

    - Multiple devices driver;

    - Media drivers;

    - VMware VMCI Driver;

    - Network drivers;

    - Microsoft Azure Network Adapter (MANA) driver;

    - Device tree and open firmware driver;

    - Chrome hardware platform drivers;

    - i.MX PM domains;

    - TI SCI PM domains driver;

    - S/390 drivers;

    - SCSI drivers;

    - SPI subsystem;

    - Thermal drivers;

    - TTY drivers;

    - USB subsystem;

    - Framebuffer layer;

    - BTRFS file system;

    - Network file system server daemon;

    - NILFS2 file system;

    - File systems infrastructure;

    - Pstore file system;

    - SMB network file system;

    - BPF subsystem;

    - Bluetooth subsystem;

    - Netfilter;

    - io_uring subsystem;

    - Core kernel;

    - Extra boot config (XBC);

    - Memory management;

    - Amateur Radio drivers;

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

    - Ethernet bridge;

    - Networking core;

    - IPv4 networking;

    - IPv6 networking;

    - Multipath TCP;

    - NFC subsystem;

    - RDS protocol;

    - Network traffic control;

    - SMC sockets;

    - Sun RPC protocol;

    - TLS protocol;

    - Unix domain sockets;

    - Wireless networking;

    - eXpress Data Path;

    - SELinux security module; (CVE-2024-35967, CVE-2024-35886, CVE-2024-26999, CVE-2024-27008,     CVE-2024-26988, CVE-2024-35980, CVE-2024-26982, CVE-2024-35946, CVE-2024-35918, CVE-2024-27015,     CVE-2024-35900, CVE-2024-35942, CVE-2024-35879, CVE-2024-35961, CVE-2024-35944, CVE-2024-35934,     CVE-2024-35978, CVE-2024-35938, CVE-2024-27003, CVE-2024-35976, CVE-2024-36019, CVE-2024-35880,     CVE-2024-35866, CVE-2024-35929, CVE-2024-35917, CVE-2024-35912, CVE-2024-35896, CVE-2024-26986,     CVE-2024-35951, CVE-2024-35958, CVE-2024-26997, CVE-2024-35965, CVE-2024-35953, CVE-2024-26993,     CVE-2024-26991, CVE-2024-35892, CVE-2024-36026, CVE-2024-35882, CVE-2024-35964, CVE-2024-35865,     CVE-2024-35897, CVE-2024-26981, CVE-2024-35872, CVE-2024-36027, CVE-2024-26983, CVE-2024-35909,     CVE-2024-35985, CVE-2024-35875, CVE-2024-35890, CVE-2024-26922, CVE-2024-26994, CVE-2024-35903,     CVE-2024-35936, CVE-2024-35904, CVE-2024-27013, CVE-2024-36025, CVE-2024-26980, CVE-2024-27006,     CVE-2024-35861, CVE-2024-35864, CVE-2024-27018, CVE-2024-36022, CVE-2024-26990, CVE-2024-35968,     CVE-2024-35860, CVE-2024-36024, CVE-2024-35933, CVE-2024-27019, CVE-2024-35925, CVE-2024-35950,     CVE-2024-35915, CVE-2024-35916, CVE-2024-35956, CVE-2024-36020, CVE-2024-35873, CVE-2024-27002,     CVE-2024-35963, CVE-2024-35959, CVE-2024-35937, CVE-2024-27011, CVE-2024-27020, CVE-2024-35883,     CVE-2024-35913, CVE-2024-35910, CVE-2024-27021, CVE-2024-35921, CVE-2024-35905, CVE-2024-27010,     CVE-2024-35981, CVE-2024-35885, CVE-2024-35955, CVE-2024-35894, CVE-2024-35969, CVE-2024-36018,     CVE-2024-35867, CVE-2024-27007, CVE-2024-35908, CVE-2024-26985, CVE-2024-27016, CVE-2024-35960,     CVE-2024-35935, CVE-2024-35932, CVE-2024-35957, CVE-2024-27001, CVE-2024-35871, CVE-2024-35907,     CVE-2024-35878, CVE-2024-35979, CVE-2024-35972, CVE-2024-35975, CVE-2024-35877, CVE-2024-35926,     CVE-2024-26817, CVE-2024-35899, CVE-2024-27004, CVE-2024-35920, CVE-2024-35924, CVE-2024-35977,     CVE-2024-35930, CVE-2024-35911, CVE-2024-26996, CVE-2024-27005, CVE-2024-35870, CVE-2024-35982,     CVE-2024-35895, CVE-2024-35943, CVE-2024-35902, CVE-2024-35919, CVE-2024-35973, CVE-2024-35931,     CVE-2024-35888, CVE-2024-35914, CVE-2024-35970, CVE-2024-36023, CVE-2024-27012, CVE-2024-35939,     CVE-2024-26984, CVE-2024-35884, CVE-2024-35901, CVE-2024-26811, CVE-2024-35966, CVE-2024-35891,     CVE-2024-35887, CVE-2024-35945, CVE-2024-35971, CVE-2024-35862, CVE-2024-26987, CVE-2024-26921,     CVE-2024-26989, CVE-2024-35952, CVE-2024-27009, CVE-2024-35893, CVE-2024-26995, CVE-2024-26925,     CVE-2024-35868, CVE-2024-35954, CVE-2024-35922, CVE-2024-27000, CVE-2024-36021, CVE-2024-27014,     CVE-2024-35940, CVE-2024-26992, CVE-2024-26926, CVE-2024-35927, CVE-2024-35863, CVE-2024-27022,     CVE-2024-26998, CVE-2024-27017, CVE-2024-26928, CVE-2024-35889, CVE-2024-35898, CVE-2024-35869,     CVE-2024-26936, CVE-2024-26923, CVE-2023-52699, CVE-2024-35974)

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 SUSE Linux SLES15 / SLES_SAP15 / openSUSE 15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2024:2135-1 advisory.

    The SUSE Linux Enterprise 15 SP6 Azure kernel was updated to receive various security bugfixes.

    The following security bugs were fixed:

    - CVE-2024-22099: Fixed a null-pointer-dereference in rfcomm_check_security (bsc#1219170).
    - CVE-2024-26764: Fixed IOCB_AIO_RW check in fs/aio before the struct aio_kiocb conversion (bsc#1222721).
    - CVE-2024-26862: Fixed packet annotate data-races around ignore_outgoing (bsc#1223111).
    - CVE-2024-26673: Fixed netfilter/nft_ct layer 3 and 4 protocol sanitization (bsc#1222368).
    - CVE-2023-0160: Fixed deadlock flaw in BPF that could allow a local user to potentially crash the system     (bsc#1209657).
    - CVE-2024-26993: Fixed fs/sysfs reference leak in sysfs_break_active_protection() (bsc#1223693).
    - CVE-2024-27013: Fixed tun limit printing rate when illegal packet received by tun device (bsc#1223745).
    - CVE-2024-27014: Fixed net/mlx5e to prevent deadlock while disabling aRFS (bsc#1223735).
    - CVE-2024-26948: Fixed drm/amd/display by adding dc_state NULL check in dc_state_release (bsc#1223664).
    - CVE-2024-27056: Fixed wifi/iwlwifi/mvm to ensure offloading TID queue exists (bsc#1223822).
    - CVE-2024-26960: Fixed mm/swap race between free_swap_and_cache() and swapoff() (bsc#1223655).
    - CVE-2023-52652: Fixed NTB for possible name leak in ntb_register_device() (bsc#1223686).
    - CVE-2024-23848: Fixed media/cec for possible use-after-free in cec_queue_msg_fh (bsc#1219104).
    - CVE-2024-26982: Fixed Squashfs inode number check not to be an invalid value of zero (bsc#1223634).
    - CVE-2024-26878: Fixed quota for potential NULL pointer dereference (bsc#1223060).
    - CVE-2024-26901: Fixed do_sys_name_to_handle() to use kzalloc() to prevent kernel-infoleak (bsc#1223198).
    - CVE-2024-26671: Fixed blk-mq IO hang from sbitmap wakeup race (bsc#1222357).
    - CVE-2024-26772: Fixed ext4 to avoid allocating blocks from corrupted group in ext4_mb_find_by_goal()     (bsc#1222613).
    - CVE-2024-26906: Disallowed vsyscall page read for copy_from_kernel_nofault() (bsc#1223202).
    - CVE-2024-26816: Ignore relocations in .notes section when building with CONFIG_XEN_PV=y (bsc#1222624).
    - CVE-2024-26783: Fixed mm/vmscan bug when calling wakeup_kswapd() with a wrong zone index (bsc#1222615).
    - CVE-2024-26883: Fixed bpf stackmap overflow check on 32-bit arches (bsc#1223035).
    - CVE-2024-26884: Fixed bpf hashtab overflow check on 32-bit arches (bsc#1223189).
    - CVE-2024-26885: Fixed bpf DEVMAP_HASH overflow check on 32-bit arches (bsc#1223190).
    - CVE-2024-26882: Fixed net/ip_tunnel to make sure to pull inner header in ip_tunnel_rcv() (bsc#1223034).
    - CVE-2023-52645: Fixed pmdomain/mediatek race conditions with genpd (bsc#1223033).
    - CVE-2024-26836: Fixed platform/x86/think-lmi password opcode ordering for workstations (bsc#1222968).
    - CVE-2024-26601: Fixed ext4 buddy bitmap corruption via fast commit replay (bsc#1220342).
    - CVE-2024-26773: Fixed ext4 block allocation from corrupted group in ext4_mb_try_best_found()     (bsc#1222618).
    - CVE-2024-26807: Fixed spi/cadence-qspi NULL pointer reference in runtime PM hooks (bsc#1222801).
    - CVE-2024-26737: Fixed selftests/bpf racing between bpf_timer_cancel_and_free and bpf_timer_cancel     (bsc#1222557).
    - CVE-2024-26733: Fixed an overflow in arp_req_get() in arp (bsc#1222585).
    - CVE-2024-26684: Fixed net/stmmac/xgmac handling of DPP safety error for DMA channels (bsc#1222445).
    - CVE-2024-26704: Fixed a double-free of blocks due to wrong extents moved_len in ext4 (bsc#1222422).
    - CVE-2023-52591: Fixed a possible reiserfs filesystem corruption via directory renaming (bsc#1221044).
    - CVE-2023-52503: Fixed tee/amdtee use-after-free vulnerability in amdtee_close_session (bsc#1220915).
    - CVE-2024-26642: Fixed the set of anonymous timeout flag in netfilter nf_tables (bsc#1221830).
    - CVE-2024-26614: Fixed the initialization of accept_queue's spinlocks (bsc#1221293).
    - CVE-2024-25739: Fixed possible crash in create_empty_lvol() in drivers/mtd/ubi/vtbl.c (bsc#1219834).
    - CVE-2023-6270: Fixed a use-after-free issue in aoecmd_cfg_pkts (bsc#1218562).
    - CVE-2024-36030: Fix the double free in rvu_npc_freemem() (bsc#1225712)
    - CVE-2023-52698: Fix memory leak in netlbl_calipso_add_pass() (bsc#1224621)
    - CVE-2024-26860: Fix a memory leak when rechecking the data (bsc#1223077).
    - CVE-2023-52772: Fix use-after-free in unix_stream_read_actor() (bsc#1224989).
    - CVE-2024-27431: Zero-initialise xdp_rxq_info struct before running XDP program (bsc#1224718).
    - CVE-2024-35860: Support deferring bpf_link dealloc to after RCU grace period BPF link for some program     types (bsc#1224531).
    - CVE-2024-35964: Fix not validating setsockopt user input Check user input length before copying data     (bsc#1224581).
    - CVE-2023-0160: Prevent lock inversion deadlock in map delete elem  (bsc#1209657).
    - CVE-2024-35903: Fix IP after emitting call depth accounting Adjust the IP passed to `emit_patch` so it     calculates the correct offset for the CALL instruction if `x86_call_depth_emit_accounting` emits code     (bsc#1224493).
    - CVE-2024-35931: Skip do PCI error slot reset during RAS recovery (bsc#1224652).
    - CVE-2024-35877: Fix VM_PAT handling in COW mappings (bsc#1224525).
    - CVE-2024-35969: Fix race condition between ipv6_get_ifaddr and ipv6_del_addr (bsc#1224580)
    - CVE-2024-35852: Fix memory leak when canceling rehash work The rehash delayed work is rescheduled with a     delay if the number of credits at end of the work is not negative as supposedly it means that the     migration ended (bsc#1224502).
    - CVE-2024-36006: Fix incorrect list API usage (bsc#1224541).
    - CVE-2024-36007: Fix warning during rehash (bsc#1224543).
    - CVE-2024-35872: Fix GUP-fast succeeding on secretmem folios (bsc#1224530).
    - CVE-2024-35956: Fix qgroup prealloc rsv leak in subvolume operations (bsc#1224674)
    - CVE-2023-52771: Fix delete_endpoint() vs parent unregistration race  (bsc#1225007).
    - CVE-2024-27408: Add sync read before starting the  DMA transfer in remote setup (bsc#1224430).
    - CVE-2024-35943: Add a null pointer check to the omap_prm_domain_init devm_kasprintf()returns a pointer     to dynamically allocated memory which can be NULL upon failure (bsc#1224649).
    - CVE-2024-35921: Fix oops when HEVC init fails (bsc#1224477).
    - CVE-2023-52860: Use cpuhp_state_remove_instance_nocalls() for hisi_hns3_pmu uninit process     (bsc#1224936).
    - CVE-2024-35991: kABI workaround for struct idxd_evl (bsc#1224553).
    - CVE-2024-35854: Fix possible use-after-free during rehash (bsc#1224636).
    - CVE-2024-27418: Take ownership of skb in mctp_local_output (bsc#1224720)
    - CVE-2024-27417: Fix potential 'struct net' leak in inet6_rtm_getaddr() (bsc#1224721).
    - CVE-2024-35905: Protect against int overflow for stack access size (bsc#1224488).
    - CVE-2024-35917: Fix bpf_plt pointer arithmetic (bsc#1224481).
    - CVE-2023-52674: Add clamp() in scarlett2_mixer_ctl_put() to nsure the value passed to     scarlett2_mixer_ctl_put() is between 0 and SCARLETT2_MIXER_MAX_VALUE so we don't attempt to access outside     scarlett2_mixer_values[] (bsc#1224727).
    - CVE-2023-52680: Add missing error checks to *_ctl_get() because the *_ctl_get() functions which call     scarlett2_update_*() were not checking the return value (bsc#1224608).
    - CVE-2023-52692: Add missing error check to scarlett2_usb_set_config() scarlett2_usb_set_config() calls     scarlett2_usb_get() but was not checking the result (bsc#1224628).
    - CVE-2024-35944: Fix memcpy() run-time warning in dg_dispatch_as_host() Syzkaller hit 'WARNING in     dg_dispatch_as_host' bug (bsc#1224648).
    - CVE-2024-26923: Suppress false-positive lockdep splat for spin_lock()  in __unix_gc() (bsc#1223384).
    - CVE-2023-52659: Ensure input to pfn_to_kaddr() is treated as a 64-bit type (bsc#1224442).
    - CVE-2024-21823: Hardware logic with insecure de-synchronization in Intel(R) DSA and Intel(R) IAA for     some Intel(R) 4th or 5th generation Xeon(R) processors may have allowed an authorized user to potentially     enable denial of service via local access (bsc#1223625).
    - CVE-2024-26828: Fix underflow in parse_server_interfaces() (bsc#1223084).
    - CVE-2024-27395: Fix Use-After-Free in ovs_ct_exit Since kfree_rcu (bsc#1224098).
    - CVE-2023-52483: Perform route lookups under a RCU read-side lock (bsc#1220738).
    - CVE-2024-27396: Fix Use-After-Free in gtp_dellink (bsc#1224096).
    - CVE-2024-26632: Fix iterating over an empty bio with  bio_for_each_folio_all (bsc#1221635).
    - CVE-2024-27401: Ensure that packet_buffer_get respects the user_length provided. (bsc#1224181).
    - CVE-2024-26775: Avoid potential deadlock at set_capacity (bsc#1222627).
    - CVE-2024-26958: Fix UAF in direct writes (bsc#1223653).
    - CVE-2024-26643: Mark set as dead when unbinding anonymous set with timeout While the rhashtable set gc     runs asynchronously, a race allowed it to collect elements from anonymous sets with timeouts while it is     being released from the commit path. (bsc#1221829).
    - CVE-2023-52618: Check for unlikely string overflow (bsc#1221615).
    - CVE-2023-6238: Only privileged user could specify a small meta buffer and let the device perform larger     Direct Memory Access (DMA) into the same buffer, overwriting unrelated kernel memory, causing random     kernel crashes and memory corruption (bsc#1217384).
    - CVE-2024-26946: Use copy_from_kernel_nofault() to read from unsafe address Read from an unsafe address     with copy_from_kernel_nofault() in arch_adjust_kprobe_addr() because this function is used before checking     the address is in text or not (bsc#1223669).
    - CVE-2024-26945: Fix nr_cpus nr_iaa case If nr_cpus nr_iaa, the calculated cpus_per_iaa will be 0, which     causes a divide-by-0 in rebalance_wq_table() (bsc#1223732).
    - CVE-2024-26679: Read sk->sk_family once in inet_recv_error() inet_recv_error() is called without holding     the socket lock. IPv6 socket could mutate to IPv4 with IPV6_ADDRFORM socket option and trigger a KCSAN     warning (bsc#1222385).
    - CVE-2024-26791: Properly validate device names (bsc#1222793)
    - CVE-2023-52641: Add NULL ptr dereference checking at the end of attr_allocate_frame() (bsc#1222303)
    - CVE-2024-26726: Do not drop extent_map for free space inode on write error (bsc#1222532)
    - CVE-2024-27022: Defer linking file vma until vma is fully initialized (bsc#1223774).
    - CVE-2024-26899: Fix deadlock between bd_link_disk_holder and partition scan (bsc#1223045).
    - CVE-2024-26638: Always initialize struct msghdr completely (bsc#1221649).
    - CVE-2024-26909: Fix drm bridge use-after-free A recent DRM series purporting to simplify support     (bsc#1223143).
    - CVE-2024-26674: Revert to _ASM_EXTABLE_UA() for {get,put}_user() fixups (bsc#1222378).
    - CVE-2024-26832: Fix missing folio cleanup in writeback race path (bsc#1223007).
    - CVE-2024-26844: Fix WARNING in _copy_from_iter (bsc#1223015).
    - CVE-2024-26774: Avoid dividing by 0 in mb_update_avg_fragment_size() when block bitmap corrupt     (bsc#1222622).
    - CVE-2024-26815: Properly check TCA_TAPRIO_TC_ENTRY_INDEX (bsc#1222635).
    - cve-2024-267600: Fix bio_put() for error case (bsc#1222596).
    - CVE-2024-26731: Fix NULL pointer dereference in sk_psock_verdict_data_ready() (bsc#1222371).
    - CVE-2024-26740: Use the backlog for mirred ingress (bsc#1222563).
    - CVE-2023-52640: Fix oob in ntfs_listxattr The length of name cannot exceed the space occupied by ea     (bsc#1222301).
    - CVE-2023-52631: Fix a NULL dereference bug (bsc#1222264).
    - CVE-2023-52458: Add check that partition length needs to be aligned  with block size (bsc#1220428).
    - CVE-2023-6270: Fix the potential use-after-free problem in aoecmd_cfg_pkts  (bsc#1218562).
    - CVE-2024-26805: Fix kernel-infoleak-after-free in __skb_datagram_iter (bsc#1222630).
    - CVE-2024-26991: Do not overflow lpage_info when checking attributes (bsc#1223695).

    - CVE-2024-26921: Preserve kabi for sk_buff (bsc#1223138).
    - CVE-2024-26925: Release mutex after nft_gc_seq_end from abort path (bsc#1223390).
    - CVE-2024-26822: Set correct id, uid and cruid for multiuser  automounts (bsc#1223011).
    - CVE-2023-52434: Fixed potential OOBs in smb2_parse_contexts()  (bsc#1220148).
    - CVE-2024-26928: Fixed potential UAF in cifs_debug_files_proc_show() (bsc#1223532).
    - CVE-2024-35999: Fixed missing lock when picking channel (bsc#1224550).
    - CVE-2024-35861: Fixed potential UAF in  cifs_signal_cifsd_for_reconnect() (bsc#1224766).
    - CVE-2024-35862: Fixed potential UAF in smb2_is_network_name_deleted()  (bsc#1224764).
    - CVE-2024-35863: Fixed potential UAF in is_valid_oplock_break() (bsc#1224763).
    - CVE-2024-35865: Fixed potential UAF in smb2_is_valid_oplock_break()  (bsc#1224668).
    - CVE-2024-35864: Fixed potential UAF in smb2_is_valid_lease_break()  (bsc#1224765).
    - CVE-2024-35867: Fixed potential UAF in cifs_stats_proc_show() (bsc#1224664).
    - CVE-2024-35868: Fixed potential UAF in cifs_stats_proc_write() (bsc#1224678).
    - CVE-2024-35866: Fixed potential UAF in cifs_dump_full_key()  (bsc#1224667).
    - CVE-2024-35869: Guarantee refcounted children from parent session  (bsc#1224679).
    - CVE-2024-35870: Fixed UAF in smb2_reconnect_server() (bsc#1224672).
    - CVE-2024-26692: Fixed regression in writes when non-standard maximum write  size negotiated     (bsc#1222464).
    - CVE-2024-27036: Fixed writeback data corruption (bsc#1223810).


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

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	Severity
295492	Azure Linux 3.0 Security Update: hyperv-daemons (CVE-2024-35917)	Nessus	Azure Linux Local Security Checks	medium
252997	Linux Distros Unpatched Vulnerability : CVE-2024-35917	Nessus	Misc.	medium
239342	TencentOS Server 4: kernel (TSSA-2024:0981)	Nessus	Tencent Local Security Checks	high
206008	SUSE SLES15 Security Update : kernel (SUSE-SU-2024:2973-1)	Nessus	SuSE Local Security Checks	high
204795	Ubuntu 24.04 LTS : Linux kernel vulnerabilities (USN-6918-1)	Nessus	Ubuntu Local Security Checks	high
203022	Ubuntu 24.04 LTS : Linux kernel vulnerabilities (USN-6893-3)	Nessus	Ubuntu Local Security Checks	high
202476	Ubuntu 24.04 LTS : Linux kernel vulnerabilities (USN-6893-2)	Nessus	Ubuntu Local Security Checks	high
202230	Ubuntu 24.04 LTS : Linux kernel vulnerabilities (USN-6893-1)	Nessus	Ubuntu Local Security Checks	high
200853	SUSE SLES15 / openSUSE 15 Security Update : kernel (SUSE-SU-2024:2135-1)	Nessus	SuSE Local Security Checks	high

Detections

Analytics

CVE-2024-35917

medium

Tenable Plugins

medium

medium

high

high

high

high

high

high

high