A vulnerability in the Linux kernel's RISC-V architecture handling of BPF JIT execmem addresses was fixed. The issue involved incorrect assumptions about memory writability in the vmalloc area when CONFIG_STRICT_MODULE_RWX is disabled, causing BPF JIT compilation to fail due to page faults. This bug affects configurations where BPF text is read-only regardless of strict module RWX settings and can prevent BPF programs from being JIT-compiled. The fix aligns with similar corrections made on arm64 and involves proper handling of executable memory mappings in patch_map(). The vulnerability does not affect !CONFIG_MMU builds.
A vulnerability in the Linux kernel's memory management subsystem causes a kernel panic during boot when using a boot-time function tracer with a specific filter. The issue arises because deferred kernel page table freeing is scheduled before the workqueue system is initialized, leading to a null pointer dereference and system crash. The flaw was introduced by a commit that allowed collapsing page tables to free kernel page tables prematurely during early boot. The fix prevents scheduling deferred freeing work while the system is still booting, deferring it until the workqueue is available.
A vulnerability in the Linux kernel Bluetooth driver btintel_pcie was fixed by correcting a bounds check on the TX descriptor index. The function btintel_pcie_prepare_tx() previously allowed an index equal to the array size, which is out of bounds, potentially leading to memory access errors.
A vulnerability in the Linux kernel Bluetooth management subsystem caused pending commands flushed on power off to report incorrect success status instead of the actual error status. This could lead to user-space components like bluetoothd misinterpreting the device state, potentially causing crashes.
A vulnerability in the Linux kernel's TEE subsystem allows zero-sized shared memory allocations via tee_dyn_shm_alloc_helper(). This leads to an invalid call to the page allocator, causing allocation failure and potentially a kernel panic during boot on systems with panic_on_warn enabled. The flaw is triggered by TEE_IOC_SHM_ALLOC with a zero size parameter. The issue has been resolved by rejecting zero-sized allocations.
A vulnerability in the Linux kernel's io_uring subsystem allowed disabled rings to bypass task-specific register opcode restrictions. This could enable a task with restricted register opcodes to create a disabled ring, perform any register operation on it, and then enable the ring regardless of the allowed opcode set. The issue has been fixed by ensuring that disabled rings inheriting restrictions from their creating task continue to enforce those restrictions until enabled.
A vulnerability in the Linux kernel's AMDGPU driver involves improper serialization of vblank counter reads against GPU reset operations. During GPU recovery, hardware register reads can occur while a reset semaphore is held for writing, causing lock dependency assertion failures and kernel taint warnings. The fix involves acquiring the reset semaphore for reading before hardware access or returning a cached software count if reset is in progress, preventing unsafe hardware access during reset.
A vulnerability in the Linux kernel's ASoC Samsung i2s driver causes a runtime power management imbalance due to improper clock enablement in the probe function. This leads to a warning during boot related to clock disablement.
Mattermost versions 11.7.x up to 11.7.10 have a vulnerability where outbound internal-connection filtering is not applied to the OpenID discovery endpoint request. This flaw allows a System Administrator to determine if internal addresses and ports are reachable from the server by triggering an unauthenticated login request that initiates the discovery fetch. The issue is classified as low severity with a CVSS score of 2.7.
Mattermost versions 11.7.x through 11.10.x (up to specified patch levels) contain a vulnerability in the WebSocket msgpack decoder where allocation limits are not properly enforced. This flaw allows an authenticated remote attacker to cause excessive server memory allocation by sending a crafted binary WebSocket frame with a large declared Bin32 payload length. The issue leads to a denial-of-service condition due to resource exhaustion.
A vulnerability in the Apache Camel OAuth component allows token caching to serve OAuth 2.0 bearer tokens across profiles sharing the same token endpoint and client ID but differing in scope or client secret. This can cause a profile to use a token issued for another profile's scope or client secret, potentially granting broader access than intended. The issue affects Apache Camel versions from 4.19.0 before 4.22.2. Upgrading to 4.23.0 or 4.22.2 resolves the issue. As a temporary mitigation, token caching can be disabled for affected profiles.
A Linux kernel vulnerability in the Open vSwitch component related to IPv6 address rewriting on IPv6 fragments causes an uninitialized transport header to be accessed, triggering debug warnings under certain configurations. The issue arises because the transport header is not set for non-first IPv6 fragments, but the checksum update function reads the transport header unconditionally. The fix involves early return in the checksum update function to avoid reading uninitialized data for fragment packets.
Mattermost versions 11.9.x up to 11.9.1, 11.8.x up to 11.8.5, 11.7.x up to 11.7.10, and 11.10.x up to 11.10.1 contain a vulnerability where the application fails to properly bind the volume of text extracted from an uploaded PDF. This flaw allows an authenticated user to cause a denial of service by uploading a crafted PDF whose compressed content stream expands into a very large amount of text, exhausting server memory.
CVE-2026-90885 is an XML External Entity (XXE) vulnerability in the Apache Camel Saxon component affecting versions from 4.0.0 before 4.18.5 and from 4.19.0 before 4.22.2. The vulnerability arises because the default Saxon Configuration used by the XQueryBuilder allows DOCTYPE declarations and external entity resolution when the message body is already a javax.xml.transform.Source. This can lead to disclosure of files readable by the Camel process and can cause the process to issue network requests to attacker-controlled hosts. Fixed versions are 4.18.5, 4.22.2, and 4.23.0.
boneIO Black suffers from a Cross-Site Request Forgery (CSRF) vulnerability affecting all state-changing API endpoints due to the absence of CSRF tokens and lack of Origin or Referer header validation. An attacker on the same internal network can exploit this by luring a user to a malicious webpage, causing unauthorized actions such as rebooting the controller or toggling relay circuits. This vulnerability leads to loss of integrity and availability of the device. The issue is resolved in version 1.6.0.
A vulnerability in the Infinispan Operator for Red Hat Data Grid exposes keystore and truststore passwords in plain text as command-line arguments when cross-site TLS is enabled. These passwords are visible in the Pod specification to any user with 'get pods' permission in the namespace, accessible via node-level process command lines, and often recorded in audit logs. This exposure increases the risk of unauthorized access to sensitive credentials.
The boneIO black_debian_images package stores the Mosquitto MQTT broker password file at /etc/mosquitto/passwd with permissions that allow any local user to read it. This exposure enables local users to obtain password hashes for all MQTT accounts and attempt offline dictionary attacks. The vulnerability was fixed in version 1.6.0.
The boneIO Black web interface has a clickjacking vulnerability that allows remote attackers to embed the control panel in an iframe on a malicious website. Authenticated users on the internal network can be tricked into clicking interface elements, causing unauthorized control of physical devices such as relays, gates, or blinds. This vulnerability is compounded by CVE-2026-77053, which disables authentication by default, enabling any internal network user to perform attacker-controlled actions. The issue was fixed in version 1.6.0.
boneIO Black had a vulnerability where several API endpoints were excluded from authentication, allowing unauthenticated remote attackers on the local network to access sensitive information such as system logs, firmware version, serial number, MQTT username, configuration file listings, and API documentation. This information could facilitate reconnaissance and targeted attacks. The issue was fixed in version 1.6.0 by requiring authentication for all API routes, disabling interactive API documentation, and withholding the serial number from anonymous users.
Mattermost versions 11.7.x up to 11.7.10 contain a vulnerability where reserved system post types are not properly validated during scheduled post creation and publication. This flaw allows an authenticated channel member to publish messages that appear as trusted system events via the scheduled post endpoint. The vulnerability has a low severity rating and does not impact confidentiality or availability.