This Red Hat security advisory addresses multiple vulnerabilities in the kernel live patch module for kernel version 4.18.0-553.72.1.el8_10. The vulnerabilities include double free errors in RDMA components (rxe and vmw_pvrdma), improper validation of rx_hash_key_len in RDMA/mana, and a use-after-free in the IPv6 networking code. These issues could lead to memory corruption or crashes. The advisory provides updated kpatch modules to fix these flaws.
Unsloth Zoo versions from 2025.9.9 up to but not including 2026.8.14 contain a code injection vulnerability in the model-loading compile path. The vulnerability arises because the get_transformers_model_type() function does not enforce a character allowlist on model_type values, allowing malicious input to inject arbitrary Python code. This can lead to remote code execution when a malicious model is loaded for training or inference.
Flowise through 3.1.4 (Enterprise/platform mode with SSO enabled) contains an authentication bypass in the SSO login path. When an SSO callback arrives with an email matching a user whose status is INVITED, verifyAndLogin (SSOBase.ts:80-94) copies the user record from the database — including the server-stored single-use invitation tempToken — into the data passed to AccountService.register(). The register handler's token lookup, email match, and expiry checks therefore pass trivially against the server's own token instead of a caller-supplied one, and the account and its organization membership are flipped to ACTIVE. As a result, anyone able to authenticate at any configured SSO provider using a pending invitee's email address as the email claim can take over that invitation and obtain the invited user's access to the organization without ever possessing the emailed invitation token, for as long as the invitation is valid (24 hours by default). At the time of the advisory no patched version was available.
ClawHub (openclaw/clawhub) application/backend contains a server-side request forgery vulnerability in the public profile preview's image fetching. The preview accepts a user-supplied image URL and checks the textual hostname against private-address patterns, but does not validate or pin the resolved network destination, so a public-looking hostname can resolve to an internal address or change resolution between validation and connection (DNS rebinding). A maintainer-run local harness demonstrated an outbound connection to an owner-controlled loopback listener; access to production internal services, credential disclosure, and code execution were not demonstrated. The issue was confirmed at revision cbfee7343ddc867316dd9b3de6fa8856730f9f41; the complete historical affected range was not established. Fixed by PR #3683, included in revision 8c2de6c506bb4efabe3f0c2ffb8370b9e23d4650, which was deployed to clawhub.ai on 2026-09-11; self-hosted deployments should update to that revision or a later descendant. The npm CLI and OpenClaw runtime are separate products and are not affected.
The MCP Server for WordPress plugin versions before 1.8.2 contains a vulnerability in the verification of the WordPress REST API nonce for cookie-authenticated requests. This flaw allows unauthenticated attackers to perform actions restricted to administrators by tricking a logged-in administrator into visiting a maliciously crafted page. Such actions include creating new administrator accounts. The vulnerability is classified under CWE-352 (Cross-Site Request Forgery).
Cotonti through 1.0.0 contains a reflected cross-site scripting vulnerability in message.php where the lng parameter is not properly escaped before output in the confirmation dialog. Unauthenticated attackers can craft malicious links with script payloads in the lng parameter to execute arbitrary JavaScript in victim browser sessions.
Ghidra versions up to 12.1.4 have a heap use-after-free vulnerability in the decompiler's Funcdata::opInsertAfter function. This flaw is caused by stale INDIRECT effect-op references. An attacker can craft a malicious x86-64 binary that triggers a crash in the decompile helper process, resulting in denial of service for analysts and automated pipelines.
GNU libextractor versions before 1.16 contain an untrusted search path vulnerability. The software loads plugins from a directory specified by the LIBEXTRACTOR_PREFIX environment variable without proper privilege checks. A local attacker can exploit this by setting LIBEXTRACTOR_PREFIX to a directory containing a malicious plugin, which may execute arbitrary code with elevated privileges when loaded by a setuid or setgid program.
In the Linux kernel, the following vulnerability has been resolved: net: hsr: free learned nodes on device setup failure hsr_dev_finalize() can fail after a lower-device RX handler has already been registered (slave A is added before the failable slave B and interlink adds). RX handlers run in softirq regardless of the master's state, so frames received in that window can learn dynamic nodes into node_db, and the error unwind never releases them. Free both owned dynamic databases in the unwind, mirroring hsr_dellink(). proxy_node_db is provably empty on every current error exit (only interlink RX feeds it, and the interlink add is the last failable step) and is freed for symmetry. The order is safe: hsr_del_port() unregisters each RX handler with synchronize_net() before hsr_del_nodes() runs, which removes remaining entries with list_del_rcu() and defers their release with call_rcu() for readers already under RCU.
A vulnerability in the Linux kernel's XFS filesystem code could cause a memory leak when the rhashtable insertion fails during quota accounting. Specifically, the function xqcheck_mod_live_ino_dqtrx does not free a newly allocated dqa object if the insertion into the rhashtable fails, leading to resource leakage. This issue has been resolved in certain Linux kernel versions.
A vulnerability in the Linux kernel's multipath TCP (mptcp) syncookies implementation was resolved by properly handling the request backup flag. The issue involved using an uninitialized bit in the subflow_ulp_clone() function, which has been corrected by using a single bit from the mptcp_subflow_request_sock structure instead of extending the join_entry structure.
A vulnerability in the Linux kernel's bnxt_en driver caused crashes due to out-of-bounds access when handling TPA IDs. The firmware supports up to 1024 concurrent TPAs, but some NICs advertise fewer, leading to invalid indexing and kernel crashes. This issue has been fixed by properly bounding the software TPA IDs and allocating the rx_tpa array accordingly.
A vulnerability in the Linux kernel's bnxt_en driver was resolved involving improper error propagation during RX ring initialization. The function bnxt_init_nic() ignored errors from bnxt_init_rx_rings(), potentially enabling TPA over partially zeroed RX ring entries, which could lead to zeroed DMA addresses being used. This issue was fixed by ensuring error propagation out of bnxt_init_nic(), allowing callers to properly handle failures and clean up resources.
A vulnerability in the Linux kernel's bnxt_en driver was resolved that involved improper handling of buffer allocation failures in the bnxt_rx_ring_reset() function. The function failed to properly propagate allocation errors, leading to potential use of uninitialized DMA addresses when re-enabling TPA (TCP Packet Aggregation). This could cause severe impacts including confidentiality, integrity, and availability issues. The vulnerability affects specific linux-hwe-edge versions and has a CVSS score of 8.1.
A use-after-free vulnerability in the Linux kernel's mac802154 subsystem was fixed. The issue involved unsafe handling of queued RX frames leading to potential use-after-free conditions when interfaces were removed while frames were still queued. The flaw was addressed by adding locking around list accesses, pinning interfaces during frame processing, and dropping frames for interfaces being unregistered. This vulnerability has a CVSS score of 7.5 and affects specific versions of the linux-hwe-edge kernel.
A use-after-free vulnerability was resolved in the Linux kernel's idpf driver. The issue occurs because the driver does not properly drain Tx/Rx Dynamic Interrupt Moderation (DIM) work before freeing the associated q_vectors memory, leading to potential execution of work on freed memory. This race condition can cause invalid memory access during network interrupt handling. The vulnerability affects specific versions of the linux-hwe-edge kernel. No configuration is required to trigger the issue, and it is a timing-dependent race rather than deterministic. The severity is assessed as medium.
A vulnerability in the Linux kernel's MANA network driver was resolved by reserving an extra completion queue (CQ) slot for the fence completion CQE. Previously, the RX completion queue was sized to hold exactly one CQE per posted RX WQE, but the hardware posts an additional CQE_RX_OBJECT_FENCE which was not accounted for, potentially causing the fence completion CQE to be dropped. This could lead to the driver waiting while holding the RTNL lock for the duration of a timeout. The fix involves rounding up the CQ size to accommodate the extra CQE slot.
A vulnerability in the Linux kernel's mana network driver was resolved that involved improper handling of the XDP program pointer when pre-allocation of RX buffers fails. The issue occurs because the new XDP program pointer is published before buffer allocation, and if allocation fails, the previous pointer is not restored. This can lead to use of freed memory when the system attempts to add a reference to the freed BPF program. The vulnerability is triggered by a standard command to set an XDP program on a network device when RX buffer pre-allocation cannot be satisfied.
A buffer overflow vulnerability in the Linux kernel's hinic network driver was resolved. The issue arises because the check_mbox_seq_id_and_seg_len() function allows the last mailbox segment to carry a payload that overflows the receive buffer by 16 bytes. This can lead to a heap buffer overflow. The hinic3 driver already implements a fix by rejecting oversized last segments, and this fix was applied to the hinic driver as well.