An update of the linux package has been released.

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-7654-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:

    - PA-RISC architecture;

    - PowerPC architecture;

    - x86 architecture;

    - Block layer subsystem;

    - Cryptographic API;

    - Serial ATA and Parallel ATA drivers;

    - Bluetooth drivers;

    - Bus devices;

    - CPU frequency scaling framework;

    - Buffer Sharing and Synchronization framework;

    - DMA engine subsystem;

    - ARM SCMI message protocol;

    - GPU drivers;

    - HID subsystem;

    - HSI subsystem;

    - I2C subsystem;

    - I3C subsystem;

    - IIO subsystem;

    - InfiniBand drivers;

    - IOMMU subsystem;

    - IRQ chip drivers;

    - MCB driver;

    - Multiple devices driver;

    - Media drivers;

    - Multifunction device drivers;

    - PCI Endpoint Test driver;

    - MTD block device drivers;

    - Network drivers;

    - Device tree and open firmware driver;

    - PCI subsystem;

    - TI SCI PM domains driver;

    - PWM drivers;

    - S/390 drivers;

    - SCSI subsystem;

    - Samsung SoC drivers;

    - TCM subsystem;

    - UFS subsystem;

    - Cadence USB3 driver;

    - ChipIdea USB driver;

    - USB Device Class drivers;

    - DesignWare USB3 driver;

    - USB Gadget drivers;

    - USB Type-C support driver;

    - USB Type-C Connector System Software Interface driver;

    - Backlight driver;

    - Framebuffer layer;

    - Xen hypervisor drivers;

    - BTRFS file system;

    - Ext4 file system;

    - F2FS file system;

    - File systems infrastructure;

    - JFS file system;

    - Network file system (NFS) client;

    - Network file system (NFS) server daemon;

    - Proc file system;

    - SMB network file system;

    - Kernel stack handling interfaces;

    - Bluetooth subsystem;

    - Network traffic control;

    - SCTP protocol;

    - BPF subsystem;

    - Kernel command line parsing driver;

    - Tracing infrastructure;

    - Memory management;

    - 802.1Q VLAN protocol;

    - Networking core;

    - IPv6 networking;

    - MAC80211 subsystem;

    - Management Component Transport Protocol (MCTP);

    - Multipath TCP;

    - Netfilter;

    - Open vSwitch;

    - Phonet protocol;

    - TIPC protocol;

    - TLS protocol;

    - Virtio sound driver;

    - CPU Power monitoring subsystem; (CVE-2025-37790, CVE-2025-37871, CVE-2025-23147, CVE-2025-37803,     CVE-2025-37909, CVE-2025-37840, CVE-2025-37989, CVE-2025-37927, CVE-2024-50280, CVE-2024-50272,     CVE-2025-37850, CVE-2024-35866, CVE-2025-22027, CVE-2025-37812, CVE-2025-21853, CVE-2025-37810,     CVE-2025-37766, CVE-2024-54458, CVE-2022-21546, CVE-2025-37757, CVE-2025-37839, CVE-2024-38540,     CVE-2025-37990, CVE-2025-37794, CVE-2024-53203, CVE-2025-37964, CVE-2025-37819, CVE-2024-50125,     CVE-2024-53128, CVE-2022-48893, CVE-2023-52572, CVE-2024-42322, CVE-2024-35943, CVE-2025-37740,     CVE-2025-37739, CVE-2025-37838, CVE-2025-37995, CVE-2025-37789, CVE-2024-50258, CVE-2025-37970,     CVE-2025-38024, CVE-2025-23146, CVE-2025-37780, CVE-2022-49168, CVE-2025-23145, CVE-2024-46774,     CVE-2022-49063, CVE-2025-37742, CVE-2025-37940, CVE-2025-37781, CVE-2025-37796, CVE-2025-23159,     CVE-2025-23144, CVE-2025-37875, CVE-2024-49989, CVE-2025-37867, CVE-2025-37892, CVE-2025-37913,     CVE-2024-38541, CVE-2025-37983, CVE-2025-37923, CVE-2025-37836, CVE-2025-23151, CVE-2025-37765,     CVE-2025-37817, CVE-2025-37991, CVE-2025-38009, CVE-2025-37858, CVE-2025-37841, CVE-2025-37771,     CVE-2025-22062, CVE-2025-37912, CVE-2025-23156, CVE-2022-49535, CVE-2025-37829, CVE-2025-37851,     CVE-2024-46816, CVE-2025-37998, CVE-2025-38023, CVE-2024-56751, CVE-2025-37844, CVE-2025-37967,     CVE-2025-37930, CVE-2025-37994, CVE-2025-37805, CVE-2024-46742, CVE-2025-37883, CVE-2025-21839,     CVE-2025-37823, CVE-2025-23157, CVE-2025-37787, CVE-2025-38094, CVE-2024-26686, CVE-2024-26739,     CVE-2025-23142, CVE-2025-23163, CVE-2025-37915, CVE-2025-37885, CVE-2024-27402, CVE-2025-37749,     CVE-2025-37738, CVE-2025-37905, CVE-2025-37773, CVE-2025-23140, CVE-2025-37792, CVE-2025-37808,     CVE-2024-49960, CVE-2025-37857, CVE-2025-23158, CVE-2025-37824, CVE-2023-52757, CVE-2025-37767,     CVE-2025-37758, CVE-2025-37914, CVE-2025-23161, CVE-2025-37741, CVE-2024-35867, CVE-2025-37911,     CVE-2025-37859, CVE-2025-37830, CVE-2025-37982, CVE-2024-46751, CVE-2025-37985, CVE-2025-37756,     CVE-2025-37768, CVE-2025-37811, CVE-2025-37992, CVE-2025-37862, CVE-2025-38005, CVE-2024-36908,     CVE-2025-23150, CVE-2025-37949, CVE-2025-37788, CVE-2025-37881, CVE-2025-37770, CVE-2025-37797,     CVE-2025-23148, CVE-2024-35790, CVE-2025-37969)

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 SLED15 / SLED_SAP15 / SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2025:02307-1 advisory.

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


    The following security bugs were fixed:

    - CVE-2023-52888: media: mediatek: vcodec: Only free buffer VA that is not NULL (bsc#1228557).
    - CVE-2024-49568: net/smc: check v2_ext_offset/eid_cnt/ism_gid_cnt when receiving proposal msg     (bsc#1235728).
    - CVE-2024-57982: xfrm: state: fix out-of-bounds read during lookup (bsc#1237913).
    - CVE-2024-57995: wifi: ath12k: fix read pointer after free in ath12k_mac_assign_vif_to_vdev()     (bsc#1237895).
    - CVE-2024-58053: rxrpc: Fix handling of received connection abort (bsc#1238982).
    - CVE-2025-21720: xfrm: delete intermediate secpath entry in packet offload mode (bsc#1238859).
    - CVE-2025-21868: kABI workaround for adding an header (bsc#1240180).
    - CVE-2025-21898: ftrace: Avoid potential division by zero in function_stat_show() (bsc#1240610).
    - CVE-2025-21899: tracing: Fix bad hist from corrupting named_triggers list (bsc#1240577).
    - CVE-2025-21920: vlan: enforce underlying device type (bsc#1240686).
    - CVE-2025-21938: mptcp: fix 'scheduling while atomic' in mptcp_pm_nl_append_new_local_addr (bsc#1240723).
    - CVE-2025-21959: netfilter: nf_conncount: Fully initialize struct nf_conncount_tuple in insert_tree()     (bsc#1240814).
    - CVE-2025-21997: xsk: fix an integer overflow in xp_create_and_assign_umem() (bsc#1240823).
    - CVE-2025-22035: tracing: Fix use-after-free in print_graph_function_flags during tracer switching     (bsc#1241544).
    - CVE-2025-22111: kABI fix for net: Remove RTNL dance for SIOCBRADDIF and SIOCBRDELIF (bsc#1241572).
    - CVE-2025-22113: ext4: define ext4_journal_destroy wrapper (bsc#1241617).
    - CVE-2025-23155: net: stmmac: Fix accessing freed irq affinity_hint (bsc#1242573).
    - CVE-2025-37738: ext4: ignore xattrs past end (bsc#1242846).
    - CVE-2025-37743: wifi: ath12k: Avoid memory leak while enabling statistics (bsc#1242163).
    - CVE-2025-37752: net_sched: sch_sfq: move the limit validation (bsc#1242504).
    - CVE-2025-37756: net: tls: explicitly disallow disconnect (bsc#1242515).
    - CVE-2025-37757: tipc: fix memory leak in tipc_link_xmit (bsc#1242521).
    - CVE-2025-37786: net: dsa: free routing table on probe failure (bsc#1242725).
    - CVE-2025-37800: driver core: fix potential NULL pointer dereference in dev_uevent() (bsc#1242849).
    - CVE-2025-37801: spi: spi-imx: Add check for spi_imx_setupxfer() (bsc#1242850).
    - CVE-2025-37811: usb: chipidea: ci_hdrc_imx: fix usbmisc handling (bsc#1242907).
    - CVE-2025-37837: iommu/tegra241-cmdqv: Fix warnings due to dmam_free_coherent() (bsc#1242952).
    - CVE-2025-37844: cifs: avoid NULL pointer dereference in dbg call (bsc#1242946).
    - CVE-2025-37859: page_pool: avoid infinite loop to schedule delayed worker (bsc#1243051).
    - CVE-2025-37862: HID: pidff: Fix null pointer dereference in pidff_find_fields (bsc#1242982).
    - CVE-2025-37865: net: dsa: mv88e6xxx: fix -ENOENT when deleting VLANs and MST is unsupported     (bsc#1242954).
    - CVE-2025-37874: net: ngbe: fix memory leak in ngbe_probe() error path (bsc#1242940).
    - CVE-2025-37884: bpf: Fix deadlock between rcu_tasks_trace and event_mutex (bsc#1243060).
    - CVE-2025-37909: net: lan743x: Fix memleak issue when GSO enabled (bsc#1243467).
    - CVE-2025-37917: net: ethernet: mtk-star-emac: fix spinlock recursion issues on rx/tx poll (bsc#1243475).
    - CVE-2025-37921: vxlan: vnifilter: Fix unlocked deletion of default FDB entry (bsc#1243480).
    - CVE-2025-37923: tracing: Fix oob write in trace_seq_to_buffer() (bsc#1243551).
    - CVE-2025-37927: iommu/amd: Fix potential buffer overflow in parse_ivrs_acpihid (bsc#1243620).
    - CVE-2025-37933: octeon_ep: Fix host hang issue during device reboot (bsc#1243628).
    - CVE-2025-37936: perf/x86/intel: KVM: Mask PEBS_ENABLE loaded for guest with vCPU's value (bsc#1243537).
    - CVE-2025-37938: tracing: Verify event formats that have '%*p..' (bsc#1243544).
    - CVE-2025-37945: net: phy: allow MDIO bus PM ops to start/stop state machine for phylink-controlled PHY     (bsc#1243538).
    - CVE-2025-37954: smb: client: Avoid race in open_cached_dir with lease breaks (bsc#1243664).
    - CVE-2025-37961: ipvs: fix uninit-value for saddr in do_output_route4 (bsc#1243523).
    - CVE-2025-37967: usb: typec: ucsi: displayport: Fix deadlock (bsc#1243572).
    - CVE-2025-37968: iio: light: opt3001: fix deadlock due to concurrent flag access (bsc#1243571).
    - CVE-2025-37987: pds_core: Prevent possible adminq overflow/stuck condition (bsc#1243542).
    - CVE-2025-37992: net_sched: Flush gso_skb list too during ->change() (bsc#1243698).
    - CVE-2025-37995: module: ensure that kobject_put() is safe for module type kobjects (bsc#1243827).
    - CVE-2025-37997: netfilter: ipset: fix region locking in hash types (bsc#1243832).
    - CVE-2025-37998: openvswitch: Fix unsafe attribute parsing in output_userspace() (bsc#1243836).
    - CVE-2025-38000: sch_hfsc: Fix qlen accounting bug when using peek in hfsc_enqueue() (bsc#1244277).
    - CVE-2025-38001: net_sched: hfsc: Address reentrant enqueue adding class to eltree twice (bsc#1244234).
    - CVE-2025-38011: drm/amdgpu: csa unmap use uninterruptible lock (bsc#1244729).
    - CVE-2025-38018: net/tls: fix kernel panic when alloc_page failed (bsc#1244999).
    - CVE-2025-38053: idpf: fix null-ptr-deref in idpf_features_check (bsc#1244746).
    - CVE-2025-38055: perf/x86/intel: Fix segfault with PEBS-via-PT with sample_freq (bsc#1244747).
    - CVE-2025-38057: espintcp: fix skb leaks (bsc#1244862).
    - CVE-2025-38060: bpf: abort verification if env->cur_state->loop_entry != NULL (bsc#1245155).
    - CVE-2025-38072: libnvdimm/labels: Fix divide error in nd_label_data_init() (bsc#1244743).


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.

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

    Michael Randrianantenaina discovered that the Bluetooth driver in the Linux Kernel contained an improper     access control vulnerability. A nearby attacker could use this to connect a rougue device and possibly     execute arbitrary code. (CVE-2024-8805)

    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:

    - PA-RISC architecture;

    - PowerPC architecture;

    - x86 architecture;

    - Block layer subsystem;

    - Cryptographic API;

    - ACPI drivers;

    - Serial ATA and Parallel ATA drivers;

    - Bluetooth drivers;

    - Bus devices;

    - Clock framework and drivers;

    - CPU frequency scaling framework;

    - Buffer Sharing and Synchronization framework;

    - DMA engine subsystem;

    - ARM SCMI message protocol;

    - GPU drivers;

    - HID subsystem;

    - HSI subsystem;

    - I2C subsystem;

    - I3C subsystem;

    - IIO subsystem;

    - InfiniBand drivers;

    - IOMMU subsystem;

    - IRQ chip drivers;

    - MCB driver;

    - Multiple devices driver;

    - Media drivers;

    - MemoryStick subsystem;

    - Multifunction device drivers;

    - PCI Endpoint Test driver;

    - MTD block device drivers;

    - Network drivers;

    - Mellanox network drivers;

    - NTB driver;

    - Device tree and open firmware driver;

    - PCI subsystem;

    - TI SCI PM domains driver;

    - PWM drivers;

    - Voltage and Current Regulator drivers;

    - Remote Processor subsystem;

    - S/390 drivers;

    - SCSI subsystem;

    - QCOM SoC drivers;

    - Samsung SoC drivers;

    - TCM subsystem;

    - Thermal drivers;

    - UFS subsystem;

    - Cadence USB3 driver;

    - ChipIdea USB driver;

    - USB Device Class drivers;

    - DesignWare USB3 driver;

    - USB Gadget drivers;

    - USB Type-C support driver;

    - USB Type-C Connector System Software Interface driver;

    - Backlight driver;

    - Framebuffer layer;

    - Xen hypervisor drivers;

    - BTRFS file system;

    - Ext4 file system;

    - F2FS file system;

    - File systems infrastructure;

    - JFS file system;

    - Network file system (NFS) client;

    - Network file system (NFS) server daemon;

    - NTFS3 file system;

    - Proc file system;

    - SMB network file system;

    - Kernel stack handling interfaces;

    - Bluetooth subsystem;

    - IPv6 networking;

    - Network traffic control;

    - SCTP protocol;

    - RDMA verbs API;

    - SoC audio core drivers;

    - BPF subsystem;

    - Kernel command line parsing driver;

    - Tracing infrastructure;

    - Watch queue notification mechanism;

    - Memory management;

    - 802.1Q VLAN protocol;

    - Asynchronous Transfer Mode (ATM) subsystem;

    - Networking core;

    - IPv4 networking;

    - MAC80211 subsystem;

    - Management Component Transport Protocol (MCTP);

    - Multipath TCP;

    - Netfilter;

    - Open vSwitch;

    - Phonet protocol;

    - SMC sockets;

    - Sun RPC protocol;

    - TIPC protocol;

    - TLS protocol;

    - SoC Audio for Freescale CPUs drivers;

    - Virtio sound driver;

    - CPU Power monitoring subsystem; (CVE-2025-37989, CVE-2025-22071, CVE-2025-37808, CVE-2025-37983,     CVE-2025-38001, CVE-2024-46816, CVE-2024-50125, CVE-2025-38575, CVE-2025-37766, CVE-2022-49168,     CVE-2025-22025, CVE-2025-22035, CVE-2025-37923, CVE-2024-49989, CVE-2025-23148, CVE-2024-53051,     CVE-2025-39728, CVE-2025-21956, CVE-2025-37741, CVE-2025-37970, CVE-2025-37798, CVE-2025-23157,     CVE-2025-38177, CVE-2022-49535, CVE-2025-22027, CVE-2025-37756, CVE-2025-38023, CVE-2025-22066,     CVE-2025-37780, CVE-2025-37995, CVE-2025-37739, CVE-2025-37932, CVE-2025-37982, CVE-2025-37812,     CVE-2025-23156, CVE-2025-38005, CVE-2025-21839, CVE-2025-37892, CVE-2025-22073, CVE-2024-35866,     CVE-2023-52757, CVE-2025-37785, CVE-2025-23150, CVE-2024-58093, CVE-2025-21992, CVE-2025-37905,     CVE-2025-37836, CVE-2025-21964, CVE-2025-23140, CVE-2025-22056, CVE-2025-37915, CVE-2025-22054,     CVE-2025-37859, CVE-2025-22050, CVE-2025-37811, CVE-2024-38540, CVE-2025-37794, CVE-2025-37839,     CVE-2022-21546, CVE-2025-22089, CVE-2025-22079, CVE-2024-56751, CVE-2025-37789, CVE-2025-37790,     CVE-2025-23159, CVE-2025-22097, CVE-2025-37883, CVE-2025-37829, CVE-2023-52572, CVE-2025-21962,     CVE-2025-37823, CVE-2024-53203, CVE-2025-38000, CVE-2025-38152, CVE-2025-37771, CVE-2025-39735,     CVE-2025-37992, CVE-2025-37937, CVE-2025-22081, CVE-2024-35943, CVE-2025-37803, CVE-2025-37940,     CVE-2025-22005, CVE-2025-22014, CVE-2025-37742, CVE-2022-49063, CVE-2025-37890, CVE-2025-37969,     CVE-2025-37788, CVE-2022-48893, CVE-2025-23161, CVE-2024-46753, CVE-2025-21853, CVE-2025-37817,     CVE-2022-49636, CVE-2025-37985, CVE-2025-37787, CVE-2025-37810, CVE-2025-22008, CVE-2025-37824,     CVE-2025-37765, CVE-2025-23145, CVE-2025-37830, CVE-2025-37913, CVE-2025-37881, CVE-2025-37967,     CVE-2025-37912, CVE-2024-42230, CVE-2024-46821, CVE-2024-56608, CVE-2025-37805, CVE-2025-37838,     CVE-2025-38637, CVE-2025-38024, CVE-2025-23138, CVE-2025-37949, CVE-2024-46751, CVE-2025-22007,     CVE-2025-37844, CVE-2024-46812, CVE-2025-37889, CVE-2023-53034, CVE-2025-37927, CVE-2025-37998,     CVE-2024-42322, CVE-2024-50280, CVE-2025-22086, CVE-2025-21963, CVE-2024-50272, CVE-2024-54458,     CVE-2024-36908, CVE-2025-22062, CVE-2025-37994, CVE-2025-22044, CVE-2025-22018, CVE-2025-22010,     CVE-2024-49960, CVE-2025-37768, CVE-2025-37911, CVE-2025-22060, CVE-2025-37781, CVE-2024-26686,     CVE-2024-50047, CVE-2025-37850, CVE-2024-46742, CVE-2025-37797, CVE-2025-37767, CVE-2025-23136,     CVE-2025-23158, CVE-2025-37792, CVE-2025-37749, CVE-2025-38009, CVE-2024-35867, CVE-2025-37885,     CVE-2025-37914, CVE-2024-46774, CVE-2025-38094, CVE-2025-23163, CVE-2024-38541, CVE-2025-37819,     CVE-2025-22020, CVE-2025-37857, CVE-2025-21975, CVE-2024-53144, CVE-2025-21991, CVE-2025-37867,     CVE-2025-37930, CVE-2025-37796, CVE-2025-21968, CVE-2025-22075, CVE-2025-37997, CVE-2025-22063,     CVE-2025-37840, CVE-2025-37909, CVE-2025-22045, CVE-2024-46787, CVE-2025-37738, CVE-2025-22055,     CVE-2025-37862, CVE-2024-56664, CVE-2025-21959, CVE-2025-22004, CVE-2024-50258, CVE-2025-23146,     CVE-2025-22021, CVE-2025-21994, CVE-2025-21957, CVE-2025-37758, CVE-2024-26739, CVE-2025-37858,     CVE-2025-37757, CVE-2025-23142, CVE-2025-23151, CVE-2025-21996, CVE-2025-21970, CVE-2025-37770,     CVE-2024-35790, CVE-2025-37773, CVE-2025-37990, CVE-2025-21941, CVE-2025-21999, CVE-2024-53128,     CVE-2025-37851, CVE-2025-23147, CVE-2025-37964, CVE-2025-37841, CVE-2025-37875, CVE-2024-53168,     CVE-2022-49728, CVE-2025-23144, CVE-2025-37991, CVE-2024-56551, CVE-2025-21981, CVE-2024-27402,     CVE-2025-37740, CVE-2024-36945)

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 AlmaLinux 9.2 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.2:CLSA-2026:1783791447 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: phy: mdio: fix memory leak Syzbot     reported memory leak in MDIO bus interface, the problem was in wrong state logic. MDIOBUS_ALLOCATED     indicates 2 states: 1. Bus is only allocated 2. Bus allocated and __mdiobus_register() fails, but     device_register() was called In case of device_register() has been called we should call put_device() to     correctly free the memory allocated for this device, but mdiobus_free() calls just kfree(dev) in case of     MDIOBUS_ALLOCATED state To avoid this behaviour we need to set bus->state to MDIOBUS_UNREGISTERED _before_     calling device_register(), because put_device() should be called even in case of device_register()     failure. (CVE-2021-47416)

  - An out-of-bounds read flaw was found in the Linux kernel's TeleTYpe subsystem. The issue occurs in how a     user triggers a race condition using ioctls TIOCSPTLCK and TIOCGPTPEER and TIOCSTI and TCXONC with leakage     of memory in the flush_to_ldisc function. This flaw allows a local user to crash the system or read     unauthorized random data from memory. (CVE-2022-1462)

  - In the Linux kernel, the following vulnerability has been resolved: can: isotp: sanitize CAN ID checks in     isotp_bind() Syzbot created an environment that lead to a state machine status that can not be reached     with a compliant CAN ID address configuration. The provided address information consisted of CAN ID     0x6000001 and 0xC28001 which both boil down to 11 bit CAN IDs 0x001 in sending and receiving. Sanitize the     SFF/EFF CAN ID values before performing the address checks. (CVE-2022-49269)

  - In the Linux kernel, the following vulnerability has been resolved: tty: fix deadlock caused by calling     printk() under tty_port->lock pty_write() invokes kmalloc() which may invoke a normal printk() to print     failure message. This can cause a deadlock in the scenario reported by syz-bot below: CPU0 CPU1 CPU2 ----
    ---- ---- lock(console_owner); lock(&port_lock_key); lock(&port->lock); lock(&port_lock_key);
    lock(&port->lock); lock(console_owner); As commit dbdda842fe96 (printk: Add console owner and waiter     logic to load balance console writes) said, such deadlock can be prevented by using printk_deferred() in     kmalloc() (which is invoked in the section guarded by the port->lock). But there are too many printk() on     the kmalloc() path, and kmalloc() can be called from anywhere, so changing printk() to printk_deferred()     is too complicated and inelegant. Therefore, this patch chooses to specify __GFP_NOWARN to kmalloc(), so     that printk() will not be called, and this deadlock problem can be avoided. Syzbot reported the following     lockdep error: ====================================================== WARNING: possible circular locking     dependency detected 5.4.143-00237-g08ccc19a-dirty #10 Not tainted
    ------------------------------------------------------ syz-executor.4/29420 is trying to acquire lock:
    ffffffff8aedb2a0 (console_owner){....}-{0:0}, at: console_trylock_spinning kernel/printk/printk.c:1752     [inline] ffffffff8aedb2a0 (console_owner){....}-{0:0}, at: vprintk_emit+0x2ca/0x470     kernel/printk/printk.c:2023 but task is already holding lock: ffff8880119c9158 (&port->lock){-.-.}-{2:2},     at: pty_write+0xf4/0x1f0 drivers/tty/pty.c:120 which lock already depends on the new lock. the existing     dependency chain (in reverse order) is: -> #2 (&port->lock){-.-.}-{2:2}: __raw_spin_lock_irqsave     include/linux/spinlock_api_smp.h:110 [inline] _raw_spin_lock_irqsave+0x35/0x50     kernel/locking/spinlock.c:159 tty_port_tty_get drivers/tty/tty_port.c:288 [inline] <-- lock(&port->lock);
    tty_port_default_wakeup+0x1d/0xb0 drivers/tty/tty_port.c:47 serial8250_tx_chars+0x530/0xa80     drivers/tty/serial/8250/8250_port.c:1767 serial8250_handle_irq.part.0+0x31f/0x3d0     drivers/tty/serial/8250/8250_port.c:1854 serial8250_handle_irq drivers/tty/serial/8250/8250_port.c:1827     [inline] <-- lock(&port_lock_key); serial8250_default_handle_irq+0xb2/0x220     drivers/tty/serial/8250/8250_port.c:1870 serial8250_interrupt+0xfd/0x200     drivers/tty/serial/8250/8250_core.c:126 __handle_irq_event_percpu+0x109/0xa50 kernel/irq/handle.c:156     [...] -> #1 (&port_lock_key){-.-.}-{2:2}: __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110     [inline] _raw_spin_lock_irqsave+0x35/0x50 kernel/locking/spinlock.c:159     serial8250_console_write+0x184/0xa40 drivers/tty/serial/8250/8250_port.c:3198 <-- lock(&port_lock_key);
    call_console_drivers kernel/printk/printk.c:1819 [inline] console_unlock+0x8cb/0xd00     kernel/printk/printk.c:2504 vprintk_emit+0x1b5/0x470 kernel/printk/printk.c:2024 <-- lock(console_owner);
    vprintk_func+0x8d/0x250 kernel/printk/printk_safe.c:394 printk+0xba/0xed kernel/printk/printk.c:2084     register_console+0x8b3/0xc10 kernel/printk/printk.c:2829 univ8250_console_init+0x3a/0x46     drivers/tty/serial/8250/8250_core.c:681 console_init+0x49d/0x6d3 kernel/printk/printk.c:2915     start_kernel+0x5e9/0x879 init/main.c:713 secondary_startup_64+0xa4/0xb0 arch/x86/kernel/head_64.S:241 ->     #0 (console_owner){....}-{0:0}: [...] lock_acquire+0x127/0x340 kernel/locking/lockdep.c:4734     console_trylock_spinning kernel/printk/printk.c:1773 ---truncated--- (CVE-2022-49441)

  - In the Linux kernel, the following vulnerability has been resolved: list: fix a data-race around     ep->rdllist ep_poll() first calls ep_events_available() with no lock held and checks if ep->rdllist is     empty by list_empty_careful(), which reads rdllist->prev. Thus all accesses to it need some protection to     avoid store/load-tearing. Note INIT_LIST_HEAD_RCU() already has the annotation for both prev and next.
    Commit bf3b9f6372c4 (epoll: Add busy poll support to epoll with socket fds.) added the first lockless     ep_events_available(), and commit c5a282e9635e (fs/epoll: reduce the scope of wq lock in epoll_wait())     made some ep_events_available() calls lockless and added single call under a lock, finally commit     e59d3c64cba6 (epoll: eliminate unnecessary lock for zero timeout) made the last ep_events_available()     lockless. BUG: KCSAN: data-race in do_epoll_wait / do_epoll_wait write to 0xffff88810480c7d8 of 8 bytes by     task 1802 on cpu 0: INIT_LIST_HEAD include/linux/list.h:38 [inline] list_splice_init     include/linux/list.h:492 [inline] ep_start_scan fs/eventpoll.c:622 [inline] ep_send_events     fs/eventpoll.c:1656 [inline] ep_poll fs/eventpoll.c:1806 [inline] do_epoll_wait+0x4eb/0xf40     fs/eventpoll.c:2234 do_epoll_pwait fs/eventpoll.c:2268 [inline] __do_sys_epoll_pwait fs/eventpoll.c:2281     [inline] __se_sys_epoll_pwait+0x12b/0x240 fs/eventpoll.c:2275 __x64_sys_epoll_pwait+0x74/0x80     fs/eventpoll.c:2275 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x44/0xd0     arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae read to 0xffff88810480c7d8 of 8 bytes     by task 1799 on cpu 1: list_empty_careful include/linux/list.h:329 [inline] ep_events_available     fs/eventpoll.c:381 [inline] ep_poll fs/eventpoll.c:1797 [inline] do_epoll_wait+0x279/0xf40     fs/eventpoll.c:2234 do_epoll_pwait fs/eventpoll.c:2268 [inline] __do_sys_epoll_pwait fs/eventpoll.c:2281     [inline] __se_sys_epoll_pwait+0x12b/0x240 fs/eventpoll.c:2275 __x64_sys_epoll_pwait+0x74/0x80     fs/eventpoll.c:2275 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x44/0xd0     arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae value changed: 0xffff88810480c7d0 ->     0xffff888103c15098 Reported by Kernel Concurrency Sanitizer on: CPU: 1 PID: 1799 Comm: syz-fuzzer Tainted:
    G W 5.17.0-rc7-syzkaller-dirty #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS     Google 01/01/2011 (CVE-2022-49443)

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

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
236949	Photon OS 5.0: Linux PHSA-2025-5.0-0521	Nessus	PhotonOS Local Security Checks	2025/5/19	2026/10/14	high
333653	Photon OS 5.0: Linux PHSA-2025-5.0-91-0521	Nessus	PhotonOS Local Security Checks	2026/8/10	2026/8/10	high
242343	Ubuntu 20.04 LTS / 22.04 LTS : Linux kernel vulnerabilities (USN-7654-1)	Nessus	Ubuntu Local Security Checks	2025/7/18	2026/10/6	high
242099	SUSE SLED15 / SLES15 : Security update for the Linux Kernel (SUSE-SU-2025:02307-1)	Nessus	SuSE Local Security Checks	2025/7/15	2026/9/29	high
242345	Ubuntu 20.04 LTS : Linux kernel (Intel IoTG) vulnerabilities (USN-7655-1)	Nessus	Ubuntu Local Security Checks	2025/7/18	2025/7/18	high
352871	AlmaLinux 9.2 [TuxCare] Security Update: bpftool / kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2026:1783791447)	Nessus	Alma Linux Local Security Checks	2026/9/30	2026/10/22	low

检测

插件搜索

high

high

high

high

high

low