A vulnerability in the Linux kernel's KVM arm64 nested virtualization implementation was resolved by fixing the lifecycle management of the nested_mmus array. This array holds shadow page tables used during nested guest execution. Previously, if a VCPU_INIT event occurred while a virtual CPU was running a nested context and the nested_mmus array needed relocation, the vCPU could continue using a pointer to a freed structure, leading to use-after-free conditions. The fix changes the nested_mmus array to an array of pointers allocated at VM creation to avoid reallocations and clarifies object lifecycles.
A vulnerability in the Linux kernel's Rust IRQ handling was resolved by changing how RegistrationInner is passed as a cookie to request_irq. The issue involved accessing uninitialized memory in the IRQ callback due to the IRQ being enabled before RegistrationInner was fully initialized. This flaw was fixed by ensuring RegistrationInner's fields are initialized before passing it as the IRQ cookie. The vulnerability does not affect mainline Linux kernels where a related commit removed the problematic pattern.
A vulnerability in the Linux kernel USB hub driver related to USB3 root hubs has been resolved by reducing the post-resume hold time from 200ms to 120ms. The previous 200ms hold time could trigger an issue on AMD platforms, causing crashes when Android adb repeatedly polls and wakes the USB subsystem. The fix optimizes the hold time for USB3 root hubs without affecting external hubs, improving stability and preventing crashes.
A vulnerability in the Linux kernel related to x86 memory management was resolved by removing an unnecessary PMD page copy during page freeing. The issue caused a possible deadlock on systems with discrete GPUs due to a circular locking dependency involving mmap locks and memory reclaim operations. The fix detaches the original PMD page earlier and frees page tables without additional allocations, eliminating the locking cycle.
A vulnerability in the Linux kernel ext4 filesystem allows a crash due to a NULL pointer dereference when large folios are enabled on encrypted inodes. This occurs because enabling the encrypt feature on a mounted filesystem bypasses a check that disables large folios, leading to a kernel crash during encrypted data writes. The issue affects Linux kernel versions from 6.19 up to but not including 7.3, where the code was refactored to prevent this. The vulnerability has been resolved by disabling large folios on encrypted inodes, similar to the handling of inodes using data journaling.
A vulnerability in the Linux kernel arm64 io subsystem related to ioremap_prot() was resolved. The issue involved improper handling of non-user protection flags in memory mappings, causing spurious warnings when reading process cmdline via /proc. The fix ensures ioremap_prot() rejects protection values without PTE_USER, preventing invalid warnings and cleanly failing access for PROT_NONE and execute-only mappings.
A vulnerability in the Linux kernel's KVM module for arm64 architecture related to the handling of the Scalable Vector Extension (SVE) feature bit at EL2 has been resolved. The issue involved inconsistent derivation and use of the GUEST_HAS_SVE flag, which could lead to a virtual CPU (vCPU) having a NULL SVE state. This inconsistency arose because the flag was taken separately from the host, but the actual feature bit was tested differently, potentially causing improper SVE state loading in guests. The fix derives the GUEST_HAS_SVE flag directly from the SVE feature bit and removes redundant code related to protected VMs, which do not allow SVE.
A vulnerability in the Linux kernel's emac network driver caused a kernel crash due to a NULL pointer dereference during driver initialization. The issue was triggered because netdev_ops were not set before calling of_phy_connect(), leading to a crash on certain PowerPC platforms. The fix involved moving the setting of netdev_ops earlier in the initialization sequence to prevent the crash. This bug appeared starting with kernel version 7.3-rc1 and was resolved by adjusting the initialization order in the emac driver code.
A vulnerability in the Linux kernel's DAMON subsystem was resolved involving the use of an unaligned address in damon_ptep_mkold(). This caused an out-of-bounds write during page table walks on arm64 architectures, potentially corrupting adjacent memory or causing kernel crashes. The issue was triggered by the kernel selftest suite and could lead to kernel faults or silent memory corruption depending on the memory page permissions. The fix ensures a page-aligned address is used in the affected function, preventing the out-of-bounds access.
A use-after-free (UAF) vulnerability in the Linux kernel's overlay filesystem (ovl) was fixed in the ovl_do_mkdir() function. The issue occurs because ovl_do_mkdir() prints the input dentry after calling vfs_mkdir(), which may free or replace the dentry, leading to a UAF when CONFIG_OVERLAY_FS_DEBUG is enabled. The fix involves printing the dentry before the call and only printing the result afterward.
A vulnerability in the Linux kernel's netfs subsystem related to missing allocation tagging of direct mempool allocations has been resolved. The issue caused warnings and missing allocation tags when CONFIG_MEM_ALLOC_PROFILING_DEBUG was enabled, affecting memory allocation tracking during CIFS mount operations. The fix involves wrapping direct allocation calls with proper allocation tagging hooks to ensure correct profiling and avoid warnings.
A vulnerability in the Linux kernel's drm/xe component related to the adjust_idledly() function has been resolved. The function had multiple issues including a divide-by-zero error when an unrecognized crystal clock caused a zero timestamp base, and integer overflow problems in tick-to-nanosecond conversions. These issues could cause kernel panics or repeated warnings during initialization. The fix involves early returns to avoid divide-by-zero, using 64-bit arithmetic to prevent overflow, and careful clamping of delay values to avoid invalid programming of hardware registers.
The kestreljob package on PyPI version 0.1.0 is part of a malicious campaign involving loader packages that execute code from remote URLs. These packages do not contain the malicious payload themselves but are designed to download and run remote malicious scripts. This campaign is coordinated and aims to provide multiple deceptive methods to load malicious code.
Hugging Face Datasets versions up to 5.1.0 contain a deserialization vulnerability in the deprecated pandas packaged builder. This flaw allows attackers to execute arbitrary Python code by supplying a malicious pickle file that is loaded without validation. When a victim loads such a dataset using datasets.load_dataset("pandas", data_files=...), the embedded payload executes with the victim process's privileges.
Kitodo.Production versions prior to 3.9.2 contain an XML External Entity (XXE) vulnerability due to insecure XML parser configurations that allow processing of external entities. Authenticated users uploading crafted EAD/XML files can exploit this to perform local file disclosure and server-side request forgery (SSRF). The issue is fixed in version 3.9.2.
Uni-CLI gives people and agents one command interface for websites, browsers, desktop applications, local tools, and MCP. Prior to version 0.225.2, Uni-CLI exposed the legacy JSON-RPC-over-HTTP MCP transport on loopback without validating browser Origin headers before routing requests. A malicious web page could send a CORS simple POST request, such as text/plain, to the local /mcp endpoint and deliver a JSON-RPC body to the dispatcher. If the user had started the local MCP HTTP transport, that page could drive tools/call requests against the user's local Uni-CLI server. The Streamable HTTP transport already enforced this browser-to-localhost boundary. The legacy stateless HTTP path did not, so the two HTTP transports had drifted. This issue is about the browser-to-localhost boundary; it does not change Uni-CLI's local-code-execution trust model. This issue has been patched in version 0.225.2.
CVE-2026-102786 is a high-severity authenticated stored cross-site scripting (XSS) vulnerability in the Phoca Gallery extension for Joomla versions 4.5.0 through 6.1.5. The flaw arises from improper neutralization of input during web page generation, specifically through HTML attribute injection. This vulnerability allows an authenticated attacker to inject malicious scripts that can execute with high confidentiality and integrity impact on affected systems.
This content describes a technology used by Kaspersky to detect and block email spam domains generated by domain generation algorithms (DGAs). Spammers use DGAs to create many similar domain names automatically, making it difficult to block spam by individual domain names. Kaspersky's solution clusters similar domains and creates rules to block entire batches of these generated domains, improving spam filtering efficiency. The technology is part of Kaspersky's corporate email security solutions and helps reduce spam, phishing, and malware emails.
Isar is an integration system for automated root filesystem generation. In versions 0.11 and newer, /etc/apt/trusted.gpg.d is created manually during bootstrap setup to be able to deploy local keys. By that, the directory is owned by the calling user (the one that executes Isar) instead of root. If the calling user's id is identical to one of an unprivileged user inside the image, this user is able to alter existing keys and deploy new ones, silently breaking the apt repo integrity protection. The issue is has no impact on those images that use an immutable rootfs, or if apt is never invoked. Changing only the keys does not trigger an exploit, it's just one step in a chain. An attacker would also have to manipulate a remote repo or intercept non-secure communication with it. This issue has been patched via commit 29e84ed.
Conda Organization Infrastructure is a centralized location for infrastructure codes. Prior to commit 9c0f238, a GitHub Actions Pwn Request vulnerability appears to remain present in conda/conda. The affected workflow is .github/workflows/update.yml. It is triggered by issue_comment events containing @conda-bot render or @conda-bot recreate. For the render path, the workflow obtains the pull request head repository and branch from the PR API, checks out that PR-controlled repository/ref using secrets.SYNC_TOKEN, and then runs conda/actions/template-files@7f6830b1428a9bd47f0b068892c77eae95207037. The external template-files action reads its default configuration and templates from the checked-out working directory. In the confirmed finding, that action uses an unsandboxed Jinja2 environment to render attacker-controlled template content. This creates a Pwn Request chain in which an untrusted PR/comment path can reach template rendering in a privileged token context. This issue has been patched via commit 9c0f238.