A use-after-free and double-free vulnerability exists in the Linux kernel's AMD KFD driver (drm/amdkfd) in the function kfd_criu_resume_svm. The flaw occurs because the code frees list entries without removing them from the linked list, leading to list corruption and potential memory errors when the same operation is re-entered. This vulnerability is exploitable by an unprivileged user with render-group access via /dev/kfd without requiring additional capabilities. The issue has been fixed by properly unlinking list entries before freeing them.
A vulnerability in the Linux kernel's mlx5e network driver related to traffic control (TC) handling can cause bad memory access and kernel crashes when the peer device sequence is unavailable during Link Aggregation Group (LAG) operations. The issue arises because mlx5_lag_get_dev_seq() returns an error if the peer is not part of the LAG or no device is marked as master, leading to improper cleanup attempts. This flaw affects multiple specific Linux kernel versions and has a high severity rating with a CVSS score of 7.8.
CVE-2026-72321 is a medium severity vulnerability in the Linux kernel's IPv4 IGMP implementation. It involves potential memory leaks in the igmp_mod_timer() and igmp_stop_timer() functions due to improper reference count handling when timers are deleted or stopped. The flaw occurs when these functions are called from the RCU reader path and the multicast group entry's reference count is decremented incorrectly, causing a memory leak. This issue has been fixed by replacing refcount_dec() with ip_ma_put() to properly free the object after releasing the spinlock.
A double-free vulnerability in the Linux kernel's resource control (resctrl) subsystem was fixed. The issue occurs because a pseudo-locked group's RMID is freed twice: once when created and again unconditionally on unmount, leading to a double addition to the free list. This flaw can cause memory corruption within the kernel. The vulnerability affects specific versions of the linux-hwe-edge kernel. A patch is available to correct this behavior.
A use-after-free vulnerability in the Linux kernel's resctrl filesystem was resolved. The flaw occurs during unmount or failure teardown when monitoring event file private data structures are freed but a flag indicating deletion is not set for the default resource group. This can lead to a concurrent reader accessing freed memory, causing potential system compromise. The issue affects specific Linux kernel versions and has been assigned CVE-2026-72080 with a CVSS score of 7.8. A patch is available to set the deletion flag unconditionally and prevent new mounts if waiters exist on the default group from a previous mount.
This vulnerability in the Linux kernel affects the creation of temporary files using O_TMPFILE on idmapped mounts. It allows temporary files to be created with invalid ownership if the caller's fsuid or fsgid is not mapped into the filesystem. The issue was fixed by adding a check to refuse O_TMPFILE creation when the fsuid or fsgid is unmapped, preventing files from having invalid user or group IDs.
The vulnerability, if exploited, could allow an authenticated miscreant
with "DNA Authority - Operator" privilege to tamper with serialized
data, potentially resulting in code execution during deserialization
under the privilege of Enterprise SCADA security group "DNA Apps".
A privilege escalation vulnerability exists in Tenable Security Center that allows a user with "Security Manager" role and "manage user" permission on a single group to modify users belonging to other groups. This bypasses the intended access control restrictions and enables unauthorized cross-group user management.
**CVE:** This vulnerability corresponds to [CVE-2026-72812](https://nvd.nist.gov/vuln/detail/CVE-2026-72812).
### Summary
The `/api/ref/refreshBacklink` endpoint is gated by `CheckAuth` only. Unlike its mutating siblings, it carries no `CheckAdminRole`, no `CheckReadonly`, and no inline reader-role guard so it falls through all three authorization mechanisms the codebase uses to protect write operations. A publish `RoleReader` or the anonymous account when `Publish.Auth.Enable` is `false` can invoke it, forcing the server to flush its pending write-transaction queue, scan all references globally, load and parse referencing trees from disk, and enqueue database writes. This violates the read-only invariant (it writes even in a globally read-only workspace), provides an unauthenticated resource-amplification/DoS primitive, and applies no per-object access check to the caller-supplied ID.
### Details
**Route / auth tier.** `router.go`: `Handle("POST", "/api/ref/refreshBacklink", model.CheckAuth, refreshBacklink)`, `CheckAuth` only. `CheckAuth` admits `RoleReader`; the publish proxy forwards port-6808 traffic with a Reader JWT (anonymous account when publish auth is disabled). Anonymous/reader reachable.
**Guard fall-through.** SiYuan protects write handlers with one of three mechanisms: route-level `CheckAdminRole` (AV/riff/repo/sync/setting/snippet/notebook mutations), route-level `CheckReadonly` (filetree/block/attr/tag mutations), or an inline `IsReadOnlyRoleContext` check (e.g. `updateEmbedBlock`, `updateRecentDoc*Time`). `refreshBacklink` has none of the three.
**Write path reached.** `refreshBacklink` calls `model.RefreshBacklink(id)`:
- `FlushTxQueue()` — forces the pending write-transaction queue to disk.
- `refreshRefsByDefID(defID)` → `QueryRefsByDefID(defID)` (global scan with encrypted-box fallback loop) → `filesys.LoadTrees(rootIDs)` (disk read and Lute parse of every referencing tree) → `sql.UpdateRefsTreeQueue(tree)` (enqueues DB writes) → ref-count task update.
The handler also does not consult `util.ReadOnly`, so it executes its writes even when the workspace is configured globally read-only.
**No per-object authorization.** `defID` is attacker-controlled and receives no publish-access or ownership check, so a reader can force a reference reindex of any document, including publish-forbidden/unpublished ones (cross-scope).
### Proof of Concept
Reproduced on a local instance (SiYuan running locally, publish mode enabled on port 6808, publish Basic Auth disabled), as an anonymous reader (no token):
**Target endpoint executes the full write path:**
```
POST http://127.0.0.1:6808/api/ref/refreshBacklink
{"id":"<any block id>"}
```
Returns `{"code":0,"msg":"","data":null}` HTTP 200 the handler ran to completion, flushing the transaction queue and enqueuing ref writes.
**Controls: the guarded mutating siblings correctly reject the same anonymous session:**
```
POST http://127.0.0.1:6808/api/tag/renameTag → 403 (CheckAdminRole and CheckReadonly)
POST http://127.0.0.1:6808/api/block/foldBlock → 403
POST http://127.0.0.1:6808/api/block/updateEmbedBlock → code 0 no-op (inline IsReadOnlyRoleContext blocks the write)
```
The 200-vs-403 contrast confirms `refreshBacklink` is reachable and executes where its siblings are blocked.
### Impact
An anonymous reader (publish mode with auth disabled) or any publish `RoleReader` can:
- **Bypass the read-only invariant:** trigger persistent server-side writes (transaction-queue flush and reference reindex), including in a workspace configured globally read-only.
- **Amplify resource use without authentication:** each call forces a transaction flush, a global reference scan, and disk read and parse of every referencing tree, with an attacker-controlled `id` and no rate limiting, a DoS primitive.
- **Act cross-scope:** `defID` receives no publish-access check, so a reader can force reindexing of documents outside their publish scope. This is an integrity-invariant violation and a resource-amplification vector, not data corruption or injection, the caller cannot control the content of the writes, only trigger them. Impact is integrity-low and availability-low; no confidentiality impact and no attacker-controlled data reaches storage.
### Suggested fix
Apply the same guard its mutating siblings use, add `CheckReadonly` (and `CheckAdminRole` if reference refresh is intended to be an authenticated operation) to the route, or an inline `IsReadOnlyRoleContext` check consistent with `updateEmbedBlock`. The endpoint should also honor `util.ReadOnly` and apply a publish-access check to `defID` so a reader cannot force cross-scope reindexing. More broadly, the three-way guard strategy (route middleware vs. inline check vs. none) is what allowed this handler to receive no gate at all; a structural backstop, a role-scoped route group for the mutation surface would prevent recurrence.
The Flex Objects plugin (through 1.4.6, tested with Grav 2.0.11) contains an incorrect authorization vulnerability in its Flex Objects API. FlexApiController::update() checks only the general Flex directory permission and does not apply the additional target/field/super-admin checks enforced by the dedicated Users and Groups API controllers. An authenticated account with api.access, admin.login, and users.update permissions (but without api.users.write or admin.super) can use the generic /api/v1/flex-objects/user-accounts endpoint to change a super administrator's password, or the /api/v1/flex-objects/user-groups endpoint to grant its group admin.super, resulting in full site takeover. Fixed in Flex Objects 1.4.7.
The Grav API plugin (getgrav/grav-plugin-api) before 1.0.13 contains an API-key scope-cap bypass in UsersController's create() and update() methods. These methods enforce the scope cap only for api.users.write, but gate super-privilege grants on a bare isSuperAdmin() check that reads access.api.super directly without consulting the key's scopes. As a result, an api.users.write-scoped key minted on a super account can set access.api.super or assign a super-granting group to mint or promote a full super account, then authenticate as that account for uncapped administrative privileges.
HoneyMyte APT group (also known as Mustang Panda) has significantly upgraded its CoolClient backdoor with kernel-level rootkit capabilities. The latest variant deploys a signed kernel-mode driver (msagent.sys) as a Windows service, enabling advanced stealth features including process hiding, file and registry protection, and network traffic filtering. The multi-stage malware uses DLL sideloading through a legitimate Sangfor application, establishes persistence via scheduled tasks and AutoRun entries, and implements UAC bypass techniques. CoolClient now injects into synchost.exe and communicates with the kernel driver through IOCTL requests. The driver hooks Nsiproxy to filter C2 addresses from network information. Victims have been identified in Myanmar, Mongolia, Pakistan, and Russia, with PlugX serving as the initial infection vector before CoolClient deployment.
In May 2026, a cyber-espionage campaign by the Armored Likho group (also known as Eagle Werewolf) targeted private individuals and organizations across Russia, including major corporations, public sector entities, IT companies, and educational institutions. The attackers employed fake donation service applications as initial infection vectors. The campaign introduced the Still Toolkit, comprising two Rust-based components: Still Sync, which steals Telegram session data and leverages the Telegram API to extract chat logs and media files, and Still Audio, an implant that conducts covert audio surveillance by detecting speech patterns and recording conversations. The toolkit demonstrates sophisticated capabilities including Dead Drop Resolver techniques, RMS-based voice activity detection, and gRPC-based C2 communications. The campaign shows significant code overlap with previous Armored Likho operations, particularly from February 2026, including identical dropper architecture, encryption algorithms, and inf...
OpenWrt LuCI contains an overly permissive ACL definition in luci-mod-system-mounts that grants write access to /etc/crontabs/root to users intended only for mount configuration. Authenticated users with only the mount-configuration ACL group can append arbitrary cron entries via ubus file.write, which the default busybox crond daemon executes as root within one minute.
OpenClaw CLI versions up to 2026.2.25 have an authorization inconsistency where BlueBubbles group allowlist checks may incorrectly accept DM pairing-store identities as group members when configured with dmPolicy=pairing and groupPolicy=allowlist. This flaw allows DM-authorized identities to bypass explicit group membership checks for message and reaction ingress. The issue does not escalate privileges beyond existing DM authorization or bypass sandbox or gateway controls. A fix is planned for version 2026.2.26.
A vulnerability in openclaw-cli versions up to 2026.3.24 allows authorization bypass in Google Chat due to reliance on mutable space display names for group policy binding. This flaw permits rebinding of group policies when display names change or collide. The issue is fixed in version 2026.3.25 by enforcing stable group IDs for access decisions.