A vulnerability identified as CVE-2026-74386 affects Microsoft product version 3.0, involving a page fragment cache leak in an error path within the nvmet-tcp component. The issue was published on September 23, 2026. No CVSS score or detailed impact information is provided, and there is no indication of known exploitation in the wild.
This vulnerability involves the CIFS component where the function pagecache_isize_extended() should be called within cifs_setsize() when extending file sizes. The advisory does not provide detailed technical or impact information.
A vulnerability in the Linux kernel's Open vSwitch (openvswitch) component was resolved that involved improper handling of packet skb flags during error processing. The issue caused the stripping of the SKBFL_SHARED_FRAG flag on a live socket buffer (skb) that was still being forwarded, leading to an unprivileged write to page-cache memory. This was due to skb_tx_error() being called on a packet that was not yet dropped, affecting in-place decryption of ESP-in-UDP packets and enabling a local page-cache write primitive. The fix moves the skb_tx_error() call to the appropriate flow-miss drop path to prevent this unsafe modification.
CVE-2026-69329 is an out-of-bounds read vulnerability in the BranchCache component of Microsoft Windows 10 Version 1607 and other versions. This flaw allows an unauthorized attacker to cause a denial of service (DoS) over a network. The vulnerability has been assigned a high severity with a CVSS score of 7.5. Official fixes have been released by Microsoft for affected versions.
This advisory addresses multiple bug fixes and enhancements for the virtio-win package, which provides paravirtualized network drivers for Microsoft Windows guests running on Red Hat Enterprise Linux virtualization hosts. The fixes include resolution validation to prevent framebuffer overflow, improved debug message handling, guest cache mode configuration, packet transmission corrections, socket driver compliance, and crash prevention when setting invalid display resolutions. These updates improve stability and correctness of the virtio-win drivers in Red Hat Enterprise Linux 9.6 Extended Update Support.
URI versions before 5.36 for Perl encode non-NFC host names to non-standard punycode labels via missing normalization in nameprep.
nameprep lowercases each host label but performs no Unicode normalization. IDNA requires a label to be normalized to Form C before it is encoded (RFC 5891), so a label that is not already in NFC is encoded to a different A-label than its normalized form. A label built from the precomposed Devanagari sequence U+0958 U+093E encodes to xn--72b5c without normalization but to xn--11b2fg after NFC normalization, and xn--72b5c does not round-trip back to the original label.
Any caller that reads host() from a URI built from untrusted input and uses it for a security decision (an allow or deny list, an SSRF filter, deduplication, a cache key) sees the non-standard label, while a client that fetches the same URL resolves the NFC form, so the check and the fetch can disagree about the host.
CVE-2026-82327 is a vulnerability in libsolv, a library used by RPM-based package managers like dnf, yum, and zypper on Red Hat Enterprise Linux 10. The flaw involves improper validation of directory-id values read from compressed .solv repository cache files, which can lead to an out-of-bounds memory write. This memory corruption causes the affected package management tools to crash, resulting in a denial of service. The out-of-bounds write stores a fixed, non-attacker-controlled value, so arbitrary code execution is not expected. No mitigation is currently available that meets Red Hat's standards, and no fix has been released yet.
CVE-2026-72329 is a published vulnerability related to the net/liquidio component, specifically involving the dropping of cached VF pci_dev LUT. The advisory references Microsoft's support lifecycle but provides no further technical details or impact information.
CVE-2026-72404 is a use-after-free (UAF) vulnerability in the tipc component related to premature destruction of dst_cache in the cleanup_bearer() function. This flaw could lead to memory corruption issues. The vulnerability affects Microsoft product version 3.0. No CVSS score or detailed impact information is provided.
This vulnerability involves the vhost component where the vring metadata cache is not properly reset during vring reconfiguration. It affects specific Microsoft software versions and has been addressed in later fixed versions. No CVSS score or detailed impact description is provided.
A use-after-free vulnerability in the Linux kernel SCTP implementation was resolved. The issue involves improper handling of a cached ASCONF chunk pointer during peer restart and timer expiry, leading to potential double free and null pointer dereference. This flaw could allow an attacker to cause system compromise. Multiple specific Linux kernel versions are affected. A patch is available to fix the issue.
A use-after-free vulnerability in the Linux kernel SCTP implementation was resolved. The issue occurs because the SCTP heartbeat acknowledgment chunk caches a transport pointer without proper reference counting. If the peer transport is removed while the chunk is queued, the chunk retains a dangling pointer, leading to a use-after-free when transmitted. This flaw can cause system compromise. A patch is available to clear the cached transport pointer when removing the transport.
In the Linux kernel, the following vulnerability has been resolved: hwmon: (adt7470) Fix divide-by-zero TOCTOU crash in fan speed read If the fan data becomes 0 between the FAN_DATA_VALID() check and the FAN_PERIOD_TO_RPM() conversion, it will result in a divide-by-zero crash due to a race with a concurrent update of the cached fan value. Fix a TOCTOU issue by reading fan data once.
This vulnerability, identified as CVE-2026-68233, relates to the drm/vc4 component and involves shutting down the BO cache timer before teardown. The provided information is minimal and does not describe the specific impact or exploitation details. The affected product is Microsoft software version 3.0. No CVSS score or detailed technical impact is provided.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (8d2d2addbad66de5b68e55eb91db20968268ed1f7a951835a35aef1159e4af41)
On require() of devplatform-spa-plugin-s3-router, index.js loads _helpers.js which runs a bootstrap routine at module load. The code assembles Cloudflare Workers hostnames (oob-worker.cf10-0-416.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev) via string-splitting and.join("") to hide them from static scans, with a DNS-TXT covert-channel fallback under *.dl.wel1.ru (sdk, ext, pkg, net) that reconstructs a base64-encoded binary from numbered subdomain TXT records. The retrieved binary is written to /tmp or the Windows temp directory under a disguised name mimicking Microsoft dotnet diagnostics (dotnet_diag_<hex>.exe or.cache_<hex>), chmod 0755'd, and spawned detached via /bin/sh -c or cmd /c start. A.analytics_state file rate-limits re-execution. A sibling lib/telemetry.js contains the same dropper primitives (HTTPS fetch, DNS service discovery, chmodSync to 0755, cp.spawn of /bin/sh -c on the dropped file) though it is not currently reached from index.js. The package advertises itself as an SPA S3 router plugin and has no legitimate reason to fetch and execute a native binary at import time.
## Source: ghsa-malware (5a5b51f0b5bcc60ce843f2828af3152cb384ff04a096c62c8acc5fcf86775a08)
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
In the Linux kernel, the following vulnerability has been resolved: wifi: p54: validate RX frame length in p54_rx_eeprom_readback() p54_rx_eeprom_readback() copies the requested EEPROM slice out of a device-supplied readback frame without checking that the skb actually holds that many bytes. Commit da1b9a55ff11 ("wifi: p54: prevent buffer-overflow in p54_rx_eeprom_readback()") closed the destination overflow by copying a fixed priv->eeprom_slice_size (and rejecting a mismatched advertised len), but the source side is still unbounded: nothing verifies the frame is long enough to supply that many bytes. A malicious USB device can send a short frame whose advertised len matches priv->eeprom_slice_size while the payload is truncated. The equality check passes and memcpy() reads past the end of the skb, leaking adjacent heap: BUG: KASAN: slab-out-of-bounds in p54_rx (drivers/net/wireless/intersil/p54/txrx.c:507) Read of size 1016 at addr ffff88800f077114 by task swapper/0/0 Call Trace: <IRQ> ... __asan_memcpy (mm/kasan/shadow.c:105) p54_rx (drivers/net/wireless/intersil/p54/txrx.c:507) p54u_rx_cb (drivers/net/wireless/intersil/p54/p54usb.c:163) __usb_hcd_giveback_urb (drivers/usb/core/hcd.c:1657) dummy_timer (drivers/usb/gadget/udc/dummy_hcd.c:2005) ... </IRQ> The buggy address belongs to the object at ffff88800f0770c0 which belongs to the cache skbuff_small_head of size 704 The buggy address is located 84 bytes inside of allocated 704-byte region [ffff88800f0770c0, ffff88800f077380) Check that the slice fits in the skb before copying.
In this article Attack chain overview Mitigation and protection guidance Indicators of compromise (IOC) Microsoft Defender XDR detections Advanced hunting queries Learn more Microsoft Threat Intelligence identified a large-scale npm supply chain attack affecting more than 400 packages across multiple unrelated publishers, including packages associated with major enterprise software ecosystems such as keyv, flat-cache, cache-manager, and others. The malicious releases contain a Mini Shai-Hulud variant, a self-propagating credential-stealing worm delivered through a large, heavily obfuscated Bun-based JavaScript payload. The malware typically executes automatically through an npm preinstall lifecycle hook before package installation completes. Once executed, the malware searches developer workstations and continuous integration and continuous delivery (CI/CD) environments for npm, GitHub, cloud, and infrastructure credentials. It uses recovered identities to authenticate to npm, GitHub, Amazon Web Services (AWS), Kubernetes, and HashiCorp Vault, enabling it to enumerate packages, repositories, workflow secrets, cloud parameters, and secret-store values. Collected data is encrypted and transmitted through an attacker-controlled HTTPS endpoint, with GitHub repositories serving as a fallback exfiltration channel. The payload’s most significant capability is automated propagation. After obtaining an npm publishing token, it enumerates packages available to the compromised identity, downloads their latest tarballs, inserts the malware and setup loader, adds a preinstall hook, increments the patch version, and republishes the modified packages. The malware can also use stolen GitHub credentials to inject Claude and Visual Studio Code configuration files into repositories, establishing persistence and creating an additional developer-to-developer infection path. In this blog, we’re sharing our analysis of this supply chain attack, along with protection, detection, amd hunting guidance. Organizations that installed an affected package with lifecycle scripts enabled should treat the associated developer workstation or build runner as potentially compromised. Investigations should prioritize credentials accessible to the affected identity, unauthorized npm releases, unexpected repository or workflow modifications, suspicious cloud and secret-store access, and artifacts produced by affected build systems. Organizations should revoke and rotate exposed credentials from a known-clean environment and rebuild affected systems and downstream artifacts from trusted sources. Attack chain overview The campaign appeared as a rapid sequence of unauthorized patch releases across more than 400 npm packages maintained by otherwise unrelated publishers. Many malicious versions had no corresponding source-code commit, pull request, tag, or legitimate release, indicating that the attackers modified and published package tarballs directly rather than compromising each public source repository. Affected releases typically added a preinstall lifecycle script that launched a malicious file, setup.mjs, contained within the package, which launched the large, obfuscated Bun JavaScript bundle included in the package. Because npm runs preinstall scripts before installation completes, the payload could execute on developer workstations and build runners before application tests or conventional security checks began. After execution, the malware performs the following actions: Determines whether it is running on a developer workstation or in a CI/CD environment. On workstations, it detaches itself to continue after installation; on CI/CD systems, it remains in the active job to access workflow secrets, runner credentials, and OpenID Connect (OIDC) publishing permissions. Both paths could support further package or repository propagation when suitable credentials are found. Collects credentials from local files, environment variables, command-line tools, and GitHub A…