This entry references a vulnerability identified as CVE-2026-98740 related to Microsoft products, specifically versions 3.0 and 4.0. The description provided is a generic Microsoft Support Lifecycle link, offering no direct details about the vulnerability itself. No CVSS score or detailed impact information is available, and no known exploits are reported in the wild. The vulnerability is published but lacks further technical or remediation details.
CVE-2026-76787 is a memory-safety vulnerability in the Zephyr project's UpdateHub firmware-over-the-air client. It arises from improper handling of a missing "sha256sum" string in CoAP probe responses, leading to a null pointer dereference during string length calculation. This flaw allows a remote attacker to cause a denial of service by crashing or halting the system. The vulnerability is exploitable without authentication when DTLS is disabled, allowing on-path or off-path attackers to deliver malformed metadata. The issue is fixed in Zephyr version 4.5.0.
CVE-2026-112267 is a server-side request forgery (SSRF) vulnerability in sglang versions up to 0.5.22. It occurs in the prefill/decode disaggregation mode, allowing unauthenticated attackers to make outbound requests by manipulating bootstrap_host and bootstrap_port fields. Exploiting this flaw, attackers can probe internal network hosts and ports and cause delays by blocking the shared scheduler loop, impacting inference request processing.
The fabtoolkit package on PyPI contains malicious code that executes a payload fetching a remote JSON configuration from an attacker-controlled server with TLS verification disabled. This payload can read arbitrary files, execute arbitrary commands, perform HTTP requests with stolen tokens, probe TCP ports, and establish a reverse shell daemon. It collects sensitive data such as credentials and cloud metadata, packages it, and uploads it to the attacker’s server. The malware enforces single-instance persistence by killing prior instances and is triggered by running 'python -m fabtoolkit' or importing certain functions. The package has no legitimate functionality matching its name.
A vulnerability in the Linux kernel's rtc spear driver was fixed by ensuring the IRQ state is initialized before requesting the alarm IRQ. The issue involved the devm_request_irq() function enabling interrupts before the device probe completed initialization, potentially causing the interrupt handler to run prematurely. The fix initializes the MMIO address and spinlock prior to requesting the alarm IRQ.
A vulnerability in the Linux kernel's vmgenid driver occurs because driver_data is not set before registering notification handlers. This can lead to a NULL pointer dereference and kernel panic when an interrupt or notification triggers the handler before driver_data is assigned. The issue affects both devicetree and ACPI probe paths. The problem has been fixed by assigning driver_data before registering handlers.
CVE-2026-98837 is a use-after-free vulnerability in the ALSA caiaq driver in the Linux kernel. The flaw occurs when the input device is registered during probe but not properly unregistered if subsequent initialization steps fail, leading to a dangling pointer. Accessing the input device's "uevent" attribute after this failure causes a kernel memory read of freed memory, triggering a KASAN slab-use-after-free error.
CVE-2026-98826 is a use-after-free vulnerability in the Linux kernel's rtc ac100 driver that occurs on probe failure. The issue arises because clock providers registered during probe are not device-managed and are only released during device removal, which does not happen if probe fails. This leads to a dangling pointer and potential use of freed memory during later clock lookups. The vulnerability also causes clock leaks that can prevent subsequent device probes. The fix involves registering clocks with device-managed functions to ensure proper cleanup on probe failure.
A vulnerability in the Linux kernel's rtc: mpfs driver was fixed where an error pointer returned by devm_clk_get() was not checked before being passed to clk_get_rate(). This could cause a kernel crash during device probe if the clock provider was not yet registered. The issue was resolved by adding proper error checking with IS_ERR() before calling clk_get_rate().
CVE-2026-98823 is a high-severity vulnerability in the Linux kernel's wifi cfg80211 component. It involves improper handling of hidden-group beacon Information Elements (IEs) during probe-response processing, which can lead to double-free errors and potential memory corruption. The flaw occurs when beacon IEs borrowed from a group's beacon entry are copied to an associated entry, resulting in two owners for the same allocation. This can cause use-after-free or double-free conditions when the group's beacon entry is released. The vulnerability has been resolved by skipping beacon IE replacement for hidden group entries while preserving normal probe-response processing.
A resource leak vulnerability in the Linux kernel's drm/mediatek driver was fixed. The issue involved the OVL adaptor platform device not being unregistered properly during probe failure or driver removal, potentially leading to resource leaks. The flaw was identified via static analysis and manual review. The severity is low.
A NULL pointer dereference vulnerability exists in the Linux kernel's usb: cdns3 driver during the PCI probe process. This occurs when the second function of the Cadence USBSS controller is probed before the first function has set its driver data, leading to a kernel crash. The issue is resolved by deferring the probe until the first function completes its initialization.
CVE-2026-98710 is a low severity vulnerability in the Linux kernel's iwlegacy wifi driver for the 3945 device. The issue involves a memory leak of EEPROM data when the PCI device is removed because the remove path does not free allocated EEPROM memory after a successful probe. This flaw was identified through manual code inspection and affects specific Linux kernel versions.
A vulnerability in the Linux kernel's sun4i-gpadc-iio driver causes improper cleanup when thermal zone registration fails. Specifically, if devm_thermal_of_zone_register() fails, the probe function returns without unregistering the IIO map array or disabling runtime power management, potentially leading to resource leaks.
A vulnerability in the Linux kernel's iio proximity pulsedlight driver caused the iio_device to remain registered after a power management setup failure during device probe. This left sysfs and character device nodes active, pointing to freed memory, potentially leading to use-after-free conditions. The issue has been fixed by ensuring the device is properly unregistered on error paths.
A vulnerability in the Linux kernel's amd_sfh driver allows out-of-bounds memory access due to improper validation of PCI BAR 2 size before mapping. This can cause a page fault during device probe if the BAR size is smaller than expected. The issue has been fixed by ensuring the BAR size is at least 128KB before mapping.
A vulnerability in the Linux kernel's MediaTek Ethernet driver (mtk_eth_soc) causes improper handling of net_device unregistration during probe failure. Specifically, if register_netdev() fails for one of the devices, the error path skips the unregistration step, leading to freeing net_devices still marked as registered, triggering a kernel bug check.