CVE Vulnerability Catalog

OpenRemote prior to version 1.24.1 allows users with only read:assets privileges to write predicted datapoints via the predicted datapoint write endpoint. Version 1.24.1 fixes the issue.

ArduinoCore-avr versions prior to 1.8.8 allow an attacker to trigger a stack-based buffer overflow when concatenating floating-point values of sufficiently large magnitude onto an Arduino String object. Passing values near the extremes of the float or double range to String::concat(float), String::concat(double), String::operator+=(), or the + operator causes dtostrf() to write beyond the stack buffer, leading to memory corruption and denial of service.

ArduinoBLE versions prior to 2.0.2 contain a missing bounds check in the ATT layer write request handler that allows a remote, unauthenticated BLE client to corrupt memory in the ATTClass global object. Devices running ArduinoBLE with one or more characteristics configured with the BLEEncryption property are affected.

matrix-sdk-ui prior to 0.17.0 is missing a check in the message edit validation logic: when replacing an encrypted event, the replacement event itself is not required to be encrypted. This enables malicious homeserver administrators (or actors with equivalent power) to impersonate or spoof messages as if they were sent by a victim user.

In the Linux kernel, a vulnerability was resolved in drm/amd/display where HDCP configuration was not skipped in the transition state. The transition state does not have a valid dm_stream_ctx, so the HDCP routine should be skipped — it is only valid when a valid stream is created.

A flaw was found in the Linux kernel btrfs subsystem where write-protection of folios during data writeback was lost. A code change replaced folio_clear_dirty_for_io() with a plain folio_test_dirty() check, allowing a process with an mmap-ed file to modify sectors while writeback is in progress. This can cause checksum corruption, lost writes, and data corruption for compressed or inline extents.

In the Linux kernel, a race condition in the ring-buffer during subbuf resize by readers was resolved. trace_buffer subbuf_size is read lockless in ring_buffer_read_page() and ring_buffer_read_start(), while it can simultaneously be resized with ring_buffer_subbuf_order_set(). The fix uses bpage::order instead of trace_buffer::subbuf_size and adds a mutex in ring_buffer_read_start().

In the Linux kernel, a vulnerability was resolved in iomap where a non-existent integrity payload was freed. fs_bio_integrity_alloc might not allocate a bio integrity payload if PI verification is disabled on the block device — the fix checks for that case before calling fs_bio_integrity_free in iomap_bio_read_folio_range_sync to avoid a NULL pointer dereference.

In the Linux kernel, an IRQ leak on the cpuhp_setup_state error path in the nxp-pit clocksource driver was resolved. When cpuhp_setup_state fails after pit_clockevent_per_cpu_init successfully called request_irq, the error handling skips freeing the registered IRQ, leaking the IRQ line and leaving a dangling pointer as the interrupt handler's dev_id, potentially leading to a use-after-free.

A bug was fixed in the Linux kernel in backing_file_open(), which derived the path stored in a new backing file from user_file->f_path. With nested filesystems (e.g. overlayfs on top of overlayfs) this caused an incorrect internal intermediate-layer path to be stored instead of the user-visible path. As a result, files mapped through a nested overlayfs showed the wrong path in /proc/<pid>/maps and in perf/ftrace mmap records.

In the Linux kernel, ovl_create_real() in overlayfs calls end_creating() twice on the casefold-mismatch error path. This causes the parent directory's i_rwsem to be unlocked twice and the dentry reference to be released twice, leading to a deadlock on subsequent creation operations under that parent. The issue is reachable by an unprivileged user.

In the Linux kernel, the PIDFD_GET_*_NAMESPACE ioctls in pidfd_ioctl() perform a ptrace access check based on credentials but, unlike the corresponding procfs paths, do not hold the target task's exec_update_lock. This allows a caller to pass the check against the target's old credentials and then read the namespace after the target has execve()'d a setuid binary and committed new credentials. The fix holds exec_update_lock for reading around the ptrace check and namespace lookup.

In the Linux kernel on native sparc64, struct __kernel_old_timeval contains a four-byte hole after tv_usec because tv_sec is 64-bit while __kernel_suseconds_t is 32-bit. put_itimerval() fills only the named fields in a stack-allocated __kernel_old_itimerval and copies the entire object to userspace, so getitimer() can expose the two padding holes. The fix zero-initializes the aggregate before assigning the fields.

In the Linux kernel's Rust devres layer, a race condition occurs when two paths concurrently revoke a Devres. devres_release_all() calls Revocable::revoke() via the release callback, while Devres::drop() calls revoke_nosync() on another CPU. The revoker that does not claim the is_available swap returns immediately, but the other may still be executing drop_in_place() on the inner data, causing a use-after-free. The fix adds a Completion that Devres::drop() waits on when it loses the is_available swap.

A use-after-free vulnerability exists in the Linux kernel's trusted keys (KEYS: trusted) module due to incorrect TPM teardown ordering. The trusted_tpm_exit() function drops the TPM chip reference and frees the digest array before unregistering the trusted key type, allowing a concurrent key operation to dereference freed memory.

A use-after-free (UAF) vulnerability in the Linux kernel's AppArmor module, related to begin_current_label_crit_section(), has been fixed. The function could directly replace credential pointers (struct cred) during an LSM hook invocation, causing task->cred and task->real_cred to become inconsistent and leading to freed credential memory still being referenced by other tasks.

A fix has been applied in the Linux kernel for an out-of-bounds write in the AppArmor aa_vec_unique() function. When all label components are distinct, the NULL terminator is written to vec[n], but vec_setup() does not reserve space for this extra entry, causing a write one element past the end of the local array or allocation. The vulnerability can be triggered by an unprivileged task writing to /proc/self/attr/apparmor/current or via lsm_set_self_attr(2), and also through the securityfs .access file which is mode 0666.

In the Linux kernel, a bug in swap memory management causes hibernation slots to be freed even when a folio is present in the swap cache. The function swap_free_hibernation_slot() clears the entry under that folio, making it unreachable from the swap table and allowing the offset to be reused by another process. This can trigger silent memory corruption, process crashes, or data instability across unrelated userspace applications, typically when uswsusp is preparing the hibernation image.

In the Linux kernel, a vulnerability was fixed in the kmemleak module where kmemleak_scan() scanned all task stacks under a single RCU read-side critical section with no reschedule point. On hosts with very many threads, this could hog a CPU and trip the soft lockup watchdog. The fix walks tasks one PID at a time using find_ge_pid() and releases the RCU lock between tasks.

A vulnerability exists in the Linux kernel's queue_folios_pmd() function in mm/mempolicy, which fails to skip non-present PMD entries (e.g., device-private) before calling pmd_folio(). This can lead to VM_BUG_ON() on debug kernels, an oops on a bogus vmemmap dereference, or silently isolating an unrelated live folio from LRU. The issue is triggered when an HMM-based GPU driver migrates an anonymous THP folio to device memory and userspace then calls mbind(), migrate_pages(), or set_mempolicy_home_node().