SiYuan note-taking software versions before 3.8.1 have a vulnerability where invisible-tier content is not properly filtered in certain listing mechanisms during publish mode. This allows anonymous readers to enumerate content that was intended to be unlisted by the administrator. The issue affects SQL embed blocks, attribute-view keys, and attribute-view backlinks.
A use-after-free vulnerability in the tlclk driver of the Linux kernel was fixed by improving the module cleanup process. The flaw involved missing the .owner field in the file_operations structure, allowing module unloading while the device was in use, and improper cleanup in tlclk_cleanup() that could lead to use-after-free and race conditions. The patch sets the .owner field to THIS_MODULE and updates cleanup to wake blocked readers, release hardware I/O regions, and safely delete timers before freeing memory.
In the Linux kernel, the following vulnerability has been resolved: ovpn: defer key slot crypto freeing to workqueue Key slots are released through a kref and the existing release path frees the AEAD transforms from an RCU callback. That is not safe for all crypto implementations: crypto_free_aead can sleep, for example when an async or hardware implementation has teardown work to complete. Use queue_rcu_work for key-slot release. This keeps the RCU grace period needed by lockless key-slot readers, but runs the actual crypto teardown from workqueue context where sleeping is allowed. Once the rcu_work callback runs, pre-existing RCU readers are gone, and the final kref put already proves that no transform user remains, so the worker can release the AEAD transforms and free the slot directly. The previous patch drains ovpn_wq during module exit, so queued key-slot teardown work cannot outlive module text.
Ech0 versions before 4.7.3 have a stored cross-site scripting (XSS) vulnerability in the public RSS feed. This flaw allows attackers with admin privileges to inject malicious tag names or raw HTML into echo content, which is rendered without proper HTML escaping. As a result, JavaScript can execute in RSS readers that render HTML summaries, potentially impacting anonymous subscribers and other users.
SiYuan before version 3.7.4 has a vulnerability in 17 block metadata and content endpoints within kernel/api/block.go. These endpoints lack proper authorization checks and publish-access filtering, allowing anonymous users to access private block content and metadata without authentication. This issue affects handlers such as getRefText, checkBlockExist, and getBlockBreadcrumb.
In the Linux kernel, the following vulnerability has been resolved: net: openvswitch: fix potential UAF on meter attach failure While attaching a newly created meter attach_meter() function makes the new meter visible to other CPUs but can still fail afterwards. On failure, it detaches the meter back and returns an error. However, this is an unexpected behavior for the ovs_meter_cmd_set() that uses a plain kfree(meter) on attach failure without waiting for RCU readers to stop using it, assuming it was never visible. This is never a problem for ovs-vswitchd as it always creates meters before creating any flows that use them. But the UAF can be triggered with a custom application using uAPI: BUG: KASAN: slab-use-after-free in ovs_meter_execute (net/openvswitch/meter.c:653) Read of size 8 at addr ffff88810d152650 by task meter/2508 Call Trace: ovs_meter_execute (net/openvswitch/meter.c:653) do_execute_actions (net/openvswitch/actions.c:1407) ovs_execute_actions (net/openvswitch/actions.c:1584) ovs_packet_cmd_execute (net/openvswitch/datapath.c:703) ... netlink_sendmsg (af_netlink.c:1900) Allocated by task 2519: __kasan_kmalloc (mm/kasan/common.c:398 mm/kasan/common.c:415) ovs_meter_cmd_set (net/openvswitch/meter.c:422) ... netlink_sendmsg (af_netlink.c:1900) Freed by task 2519: kfree (mm/slub.c:2705 mm/slub.c:6405 mm/slub.c:6720) ovs_meter_cmd_set (net/openvswitch/meter.c:479) ... netlink_sendmsg (af_netlink.c:1900) Fix that by making sure attach_meter() doesn't make the meter visible until all the checks are done and the function can't fail anymore. This also makes sure the "hash" value is calculated after the potential re-sizing of the table. Reported by Trend Micro's Zero Day Initiative as ZDI-CAN-31642.
In the Linux kernel, the following vulnerability has been resolved: fou: Fix use-after-free in fou_create() fou_create() publishes struct fou through sk_user_data before adding the new FOU port to the per-netns list. If fou_add_to_port_list() fails, the error path frees fou while it is still reachable through sk_user_data. A concurrent receive can then dereference the freed object in fou_from_sock(). This ordering issue was previously noted in the linked discussion. The failure is reachable when local port 0 is requested. Each socket binds to a different ephemeral port, but fou_cfg_cmp() compares the requested port 0 and reports -EALREADY once an entry already exists. Release the tunnel socket before freeing fou so sk_user_data is cleared first, and defer reclamation with kfree_rcu() to protect concurrent RCU readers. This matches the lifetime handling in fou_release().
In the Linux kernel, the following vulnerability has been resolved: audit: fix potential use-after-free in audit_del_rule() `audit_del_rule()` destroys `e->rule.exe` via `audit_remove_mark_rule()` before unlinking the rule from RCU-visible filter lists and waiting for a grace period. Concurrent readers in `audit_filter()` and `audit_filter_rules()` still dereference `e->rule.exe`, while the fsnotify mark can be freed on an independent lifetime path. This creates a use-after-free window during rule deletion. Fix this by unlinking the rule from the RCU-visible lists and invoking `synchronize_rcu()` before calling `audit_remove_mark_rule()` (and other rule removal helpers). This ensures that all existing RCU readers have exited the critical section before any underlying resources are destroyed.
A use-after-free (UAF) vulnerability in the Linux kernel's TIPC UDP media bearer cleanup function (cleanup_bearer) was fixed. The issue arises because dst_cache_destroy() is called prematurely, freeing per-CPU cache memory without proper synchronization, which can lead to crashes or warnings when concurrent transmitters access freed memory. The fix defers destruction of cache entries and memory freeing until after ensuring no concurrent readers remain, using RCU callbacks and proper synchronization.
A race condition in the Linux kernel's mlx5e network driver caused a potential NULL pointer dereference on weakly-ordered architectures such as ARM, PowerPC, and RISC-V. This occurred because the publication of new channel statistics entries and the increment of the stats counter lacked proper memory barriers, allowing readers to observe inconsistent state. The issue was observed on BlueField-3 DPUs during NIC bringup, leading to kernel crashes. The vulnerability has been fixed by adding memory barrier helpers to ensure proper ordering of updates and visibility of channel statistics entries.
A use-after-free vulnerability in the Linux kernel's mt76 wireless driver was fixed by changing the memory free method from kfree() to kfree_rcu() in the mt76_put_vif_phy_link function. The issue arises because the offchannel link is freed immediately after being set to NULL with rcu_assign_pointer, which does not wait for ongoing readers to finish accessing the pointer. This can lead to dereferencing freed memory during TX datapath operations. The vulnerability is addressed in Linux kernel versions 7.0.0 and later.
CVE-2026-74255 is a critical use-after-free vulnerability in the Linux kernel's TIPC subsystem, specifically in the tipc_l2_send_msg() function. The flaw arises from improper synchronization when clearing a device pointer, allowing concurrent readers to access a freed device pointer. This vulnerability has been fixed by clearing the pointer before synchronization to prevent use-after-free conditions.
A critical vulnerability in the Linux kernel's netfilter ipset subsystem involves improper use of the test_bit() function in lockless RCU readers for hash types. The issue arises because test_bit() is a relaxed atomic operation without memory barrier guarantees, which can lead to race conditions. The vulnerability has been fixed by replacing test_bit() with test_bit_acquire() in affected code paths. Multiple Linux kernel versions, including specific linux-aws builds, are affected. The flaw has a CVSS score of 9.8, indicating high severity with potential for complete system compromise. Official patches are available in several fixed kernel versions.