A vulnerability in the Linux kernel's HID subsystem for Wacom devices was resolved. The issue involved the wacom_parse_and_register() function starting hardware before completing input registration and pad LED/remote initialization. Failure in these later steps did not properly stop the HID hardware, potentially leaving it in an inconsistent state. This flaw was identified through static analysis and has been fixed by ensuring hardware is stopped on post-start probe failures.
CVE-2026-68373 is a high-severity vulnerability in the Linux kernel's wifi driver for at76c50x-usb devices. It involves a length underflow in the at76_guess_freq() function when processing truncated beacon or probe response frames. This underflow leads to an out-of-bounds read during scanning, potentially causing denial of service. The issue is fixed in specific Linux kernel commits.
A security flaw has been discovered in Hulupeep mcp-ui-probe up to 0.2.0. Affected is the function get_journey/delete_journey/analyze_journey/usage_stats of the file src/journey/JourneyStorage.ts of the component Journey/Usage. The manipulation of the argument journeyId/filename results in path traversal. The attack requires a local approach. The project was informed of the problem early through an issue report but has not responded yet.
The npm package titan-exchange-shared-permissions version 99.9.9 is a malicious dependency-confusion reconnaissance package. It executes a postinstall script that collects system information including OS username, hostname, current directory, and non-internal IPv4 address, then sends this data to a hardcoded external URL. The package mimics a private internal package to identify build systems that mistakenly resolve private names to the public npm registry. It contains no legitimate functionality and is designed to probe for dependency confusion vulnerabilities.
The npm package @wbnr/frontend-shared versions 99.0.0 and 99.0.1 contains malicious code in its preinstall lifecycle script. This script collects the installer's OS username and hostname, then sends this information to a third-party callback domain via DNS lookup and HTTPS GET requests. This behavior aligns with a dependency-confusion probe, potentially exposing sensitive environment identifiers to an external attacker-controlled domain.
In the Linux kernel, the following vulnerability has been resolved: wifi: brcmfmac: drain bus_reset work on device removal brcmf_fw_crashed() and the debugfs "reset" entry both schedule drvr->bus_reset, whose callback recovers drvr through container_of() and dereferences it. The removal path frees drvr (brcmf_free -> wiphy_free) without draining the work, so a bus_reset callback pending or running during removal can outlive drvr. Cancellation cannot live in brcmf_detach() or brcmf_free(): the work callback reaches teardown through the bus .reset op (PCIe brcmf_pcie_reset -> brcmf_detach; SDIO brcmf_sdio_bus_reset -> brcmf_sdiod_remove -> brcmf_free), so cancelling there would wait for the running work and deadlock. Add a per-bus mutex (bus_reset_lock) and route all arming through brcmf_bus_schedule_reset(), which under the lock skips when the bus is marked removing. Each bus remove entry calls brcmf_bus_cancel_reset_work(), which under the same lock sets removing and cancels the work. Holding the mutex across cancel_work_sync() makes the set-removing + drain step atomic. Every producer reaches the arming path from process context -- the PCIe firmware-halt notification runs in the threaded IRQ handler (brcmf_pcie_isr_thread) and the SDIO hostmail path runs from the data workqueue -- so the mutex is taken only in sleepable contexts. Where applicable the remove entry first stops the firmware-crash producer: on PCIe mask the mailbox and synchronize_irq; on SDIO unregister the bus interrupt and cancel the data worker, which also reports firmware halts through brcmf_fw_crashed(). The mutex is initialized at bus allocation. The SDIO suspend power-off path frees drvr through the same brcmf_sdiod_remove() and takes the same lock; resume re-allows the work only on a successful re-probe. Also guard brcmf_fw_crashed() against a NULL bus_if/drvr: it can fire before brcmf_attach() wires up drvr, and it dereferences drvr (bphy_err/brcmf_dev_coredump) before reaching the arming gate. The bus_reset work is shared across buses, so the drain is applied to every remove path: PCIe (the .reset op introduced by the Fixes commit), SDIO (arms the same work through brcmf_fw_crashed()), and USB (via the debugfs "reset" entry). cancel_work_sync() drains a running or pending bus_reset work item before removal frees drvr, and patch 1/2 makes the scratch-buffer release safe when reset teardown has already released those DMA buffers. This patch fixes the lifetime of the bus_reset work item itself. It does not attempt to address the separate, pre-existing lifetime of the asynchronous firmware completion started by the PCIe reset path. That callback needs its own lifetime/ownership protocol and is being tracked separately. This issue was found by an in-house static analysis tool.
A vulnerability in the Linux kernel's iio: adc: spear driver was fixed by initializing a completion structure before requesting an IRQ. The flaw could cause a kernel panic if an interrupt arrived before the completion was initialized, leading to a wild memory access. This issue has been addressed by reordering the initialization sequence in the probe function.
In the Linux kernel, the following vulnerability has been resolved: HID: hid-lenovo-go: cancel cfg_setup work in hid_go_cfg_remove() hid_go_cfg_probe() initialises drvdata.go_cfg_setup and schedules it to run 2 ms later: INIT_DELAYED_WORK(&drvdata.go_cfg_setup, &cfg_setup); schedule_delayed_work(&drvdata.go_cfg_setup, msecs_to_jiffies(2)); cfg_setup() dereferences drvdata.hdev to issue MCU command requests. hid_go_cfg_remove() tears down sysfs and stops the HID device, but never drains the delayed work. If the device is unbound within the 2 ms scheduling delay (a probe failure rolling back via remove, or a fast rmmod after probe), the work fires after hid_destroy_device() has dropped its reference and released the underlying hdev struct, leaving cfg_setup() with a stale drvdata.hdev pointer. Mirror the sibling driver hid-lenovo-go-s.c, whose hid_gos_cfg_remove() already calls cancel_delayed_work_sync() on its analogous work, and drain go_cfg_setup at the top of hid_go_cfg_remove(). The cancel must come before guard(mutex)(&drvdata.cfg_mutex) because cfg_setup() acquires that mutex; reversing the order would deadlock.
Ghost, a Node.js content management system, contained a server-side request forgery (SSRF) vulnerability in versions from 6.26.0 up to but not including 6.54.1. This flaw allowed unauthenticated users to abuse certain features, such as Webmentions, to make limited HTTP requests to internal network hosts of the Ghost server. Although the attack did not return response data, it could potentially be used to probe internal network resources. The vulnerability is fixed in version 6.54.1.
The sc-font-icons npm package version 9999.0.0 contains malicious code in its preinstall script that automatically runs during installation. This script collects sensitive environment information such as hostname, username, current working directory, npm registry URL, and CI repository identifiers. It then sends this data unencrypted via HTTP GET to a hardcoded external IP address unrelated to legitimate npm infrastructure. This behavior is consistent with a dependency confusion probe designed to leak internal repository and infrastructure details to a third party.
The npm package 'store-locator-widget' version 9999.0.0 is a malicious package that contains no functional code but includes a preinstall script that collects environment information from the installer and sends it to an attacker-controlled IP address. This behavior is consistent with a dependency confusion reconnaissance probe, leaking sensitive build and environment details during installation.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (ecc42778bb54bfdea5784d5dcb68cf43c89def3dbaeddba1d1a6bd2850cb174b)
The package's preinstall script (`node index.js`) auto-executes on `npm install` and collects host identifiers (os.hostname(), os.userInfo().username, home directory, DNS servers) along with the contents of /etc/passwd and /etc/hosts, then POSTs them via HTTPS to a hardcoded Burp Collaborator subdomain at 2ru8qr34u3so6bnti176tzt30u6muci1.oastify.com. The package name mimics an Azure DevOps MATLAB extension but ships no legitimate functionality (empty author, empty description); the package exists only to run the exfil beacon. Consistent with a dependency-confusion / recon probe.
## Source: ghsa-malware (db5089aca87fa4e104e5c3395d2a884191c1ffe1d146bf73b0f255872b59e55e)
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.
A Server-Side Request Forgery (SSRF) vulnerability exists in TryGhost Ghost versions from 0.10.0 up to but not including 6.54.1. This flaw allows any staff-level user to perform blind HTTP GET requests to internal hosts via the Ghost Admin image fetching functionality. Although no response data is returned, the vulnerability could be used to probe internal network ports. The issue is resolved in version 6.54.1.
CTI-Transmute is affected by a server-side request forgery vulnerability in the evaluation report PDF-generation functionality.
User-controlled CTI content, including conversion names, descriptions, and comments, is converted from Markdown to HTML and rendered as a PDF using WeasyPrint. Before the patch, the renderer used WeasyPrint’s default URL-fetching behavior without restricting the protocols or destinations that could be referenced by the generated HTML.
An attacker able to supply content included in an evaluation report could inject crafted resource references using schemes such as http://, https://, or file://. When the report was rendered, CTI-Transmute could fetch these resources using the application server’s network connectivity and filesystem privileges.
Successful exploitation could allow an attacker to:
* access services available only from the CTI-Transmute server or its internal network;
* probe internal hosts and service endpoints;
* retrieve local files readable by the application process; and
* expose fetched content through the generated PDF, depending on the referenced resource type and rendering context.
The vulnerability is corrected by providing WeasyPrint with a restrictive URL fetcher that permits only self-contained data: URIs. The externally hosted Google Fonts stylesheet was also removed so that PDF generation performs no intentional network or filesystem fetches.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (0457a026ab28fbb641d11e4e9ac9d60d026fd77210972f72e6ac931b4b06c59c)
On npm install, postinstall.js executes shell commands that query cloud instance metadata services (AWS IMDS at 169.254.169.254, plus Tencent, Aliyun, GCP, and Azure endpoints) and extracts the AWS IAM role's temporary security credentials. The captured IAM credentials, hostname, and username are appended as query parameters to an HTTP request to the hardcoded out-of-band host pzs5w7ntzhsnepwk564lyfdci3oucl0a.oastify.com (a Burp Collaborator-style domain). The package.json describes the module as a lightweight string formatting helper; the shipped code contains only the credential-harvesting postinstall, with no string-utility functionality present.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (5dc8f9f53c05ecc2642ce82c3841e046025662c206f002b4c6da11ff0cbc763d)
The package's postinstall lifecycle hook runs `node index.js`, which issues an HTTPS GET to a hardcoded Burp Collaborator subdomain at `e0fumpwx24ddfmenzmg0izs2atgk4es3.oastify.com/dependency-confusion` with a User-Agent identifying it as a dependency-confusion probe. On any `npm install` that resolves this scoped name, the request fires automatically and discloses installer identity (source IP, DNS resolver, timing, request metadata) to a third-party out-of-band interaction server controlled by whoever provisioned the Collaborator instance. The package name uses a private-scope pattern (`@heartlandone-private/fontawesome-pro`) that mimics an internal artifact, consistent with a dependency-confusion attempt aimed at organizations whose internal `@heartlandone-private` scope is not reserved on the public registry. Whether the operator's intent is authorized red-team testing or opportunistic exploitation, any consumer whose install pipeline resolves this public package receives install-time code execution and outbound network signalling to an attacker-controlled callback.
## Source: ossf-package-analysis (b5bd52805195c9e3575760b3eaf605a2b9cb0fcbdde2311b7075d2d8095c4900)
The OpenSSF Package Analysis project identified '@heartlandone-private/fontawesome-pro' @ 6.3.3 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
In the Linux kernel, the following vulnerability has been resolved: gpio: rockchip: teardown bugs and resource leaks Address several teardown issues and resource leaks in the driver's remove path and error handling: 1. Debounce clock reference leak: The debounce clock (bank->db_clk) is obtained using of_clk_get() which increments the clock's reference count, but clk_put() is never called. Register a devm action to cleanly release it on unbind. Note that of_clk_get(..., 1) remains necessary over devm_clk_get() because the DT binding does not define clock-names, precluding name-based lookup. 2. Unregistered chained IRQ handler: The chained IRQ handler is not disconnected in remove(). If a stray interrupt fires after the driver is removed, the kernel attempts to execute a stale handler, leading to a panic. Fix this by clearing the handler in remove(). 3. IRQ domain leak: The linear IRQ domain and its generic chips are allocated manually during probe but never removed. Remove the IRQ domain during driver teardown to free the associated generic chips and mappings. [Bartosz: don't emit an error message on devres allocation failure]
In the Linux kernel, the following vulnerability has been resolved: usb: gadget: net2280: Fix double free in probe error path usb_initialize_gadget() installs gadget_release() as the release callback for the embedded gadget device. The struct net2280 instance is therefore released through gadget_release() when the gadget device's last reference is dropped. The probe error path calls net2280_remove(), which tears down the partially initialized device and drops the gadget reference with usb_put_gadget(). Calling kfree(dev) afterwards can free the same object again. Drop the explicit kfree() and let the gadget device release callback handle the final free. This issue was found by a static analysis tool I am developing.
A vulnerability in the Linux kernel's regulator subsystem (tps65219 driver) was fixed by properly assigning irq_data.rdev to avoid undefined behavior during IRQ handling. The issue was caused by removal of a helper function that left irq_data.rdev uninitialized, potentially causing kernel crashes (Oops) when regulator_notifier_call_chain() is invoked. The fix restructures the probe function to assign rdev correctly during regulator and IRQ registration, adding NULL checks for non-regulator IRQs to prevent crashes.
In the Linux kernel, the following vulnerability has been resolved: spi: ti-qspi: fix use-after-free after DMA setup failure The driver falls back to PIO mode if DMA setup fails during probe. Make sure to clear the DMA channel pointer also if buffer allocation fails to avoid passing a pointer to the released channel to the DMA engine (or trying to free the channel a second time on late probe errors or driver unbind). This issue was flagged by Sashiko when reviewing a devres allocation conversion patch.