A vulnerability in the Linux kernel's openvswitch component caused a soft lockup during netlink flow dumps, leading to system panics on nodes with many datapath flows. The issue arises from improper handling of softirq processing during flow statistics retrieval, causing the dumping thread to monopolize CPU softirq handling and preventing rescheduling. The fix involves holding bottom halves off across the entire callback to prevent nested softirq draining and ensure proper CPU scheduling.
An AI-powered espionage campaign, tracked as CL-UNK-1211, targeted government and state-affiliated Linux infrastructure from October 2025 to April 2026. The attackers used AI-generated payloads, custom malware, web shells, and credential harvesting techniques to maintain persistent access and conduct reconnaissance. They deployed multiple web shells, modified PHP configurations for persistence, and used advanced anti-forensics methods including disabling endpoint protections and tampering with system logs. Credential theft was achieved through hijacked .bashrc files and PHP login page modifications. The campaign aimed to dump sensitive databases and exfiltrate government mailboxes to access social media accounts. The attackers combined open-source tools with custom cross-platform backdoors and employed AI to streamline payload creation. No specific patch or fix is mentioned.
A missing authorization check in Brocade Fabric OS versions before 10.0.1 REST API interface of affected platform releases allows an authenticated user, regardless of their assigned role or administrative scope, to retrieve complete Monitoring and Alerting Policy Suite (MAPS) violation data across all logical switches. An attacker with low-privilege API access can leverage this endpoint to dump chassis-wide system health metrics, port performance violations, and configuration data without appropriate privileges.
A race condition vulnerability in the Linux kernel's IPv6 routing exception handling was resolved by using a safe RCU iterator. The function rt6_nh_dump_exceptions() previously used an unsafe iteration method over RCU-protected exception lists, leading to a data race when concurrent modifications occurred. This issue was detected by the Kernel Concurrency Sanitizer and fixed by switching to hlist_for_each_entry_rcu() for safe iteration.
Multiple security vulnerabilities have been identified and fixed in the GNU tar program as distributed with Red Hat Enterprise Linux 8. These include path traversal, hidden file injection via crafted archives, a time-of-check to time-of-use (TOCTOU) race condition in incremental dump directory rename handling, and arbitrary file overwrite via hardlink targets not confined to the top-level directory. The update also includes bug fixes and enhancements related to the --one-top-level option. The security impact is rated as moderate by Red Hat.
A use-after-free vulnerability in the Linux kernel's qla2xxx SCSI driver was fixed. The issue occurred during firmware dump operations where a DMA buffer could be freed while still being accessed, due to improper locking. This could lead to a use-after-free condition. The fix ensures the DMA buffer is unpublished under a hardware lock before being freed, preventing concurrent access to freed memory.
A threat actor exploited CVE-2026-15409, a critical unauthenticated server-side request forgery vulnerability in SonicWall SMA1000 appliances, to gain command execution and steal credentials. The attacker used a modified public proof-of-concept exploit to access internal Erlang services on the appliance, enabling remote code execution. This allowed extraction of LDAP configurations, Active Directory credentials, and deployment of tools to dump secrets from internal Windows systems. The campaign targeted at least 250 SonicWall SMA1000 devices across multiple countries and sectors, with confirmed credential theft in France, India, Italy, and the US. The attack leveraged compromised appliances as pivots into internal networks, exposing sensitive Active Directory data and enabling DCSync attacks against domain controllers. The targeting was opportunistic and technology-driven rather than sector-specific. The campaign was uncovered through an open directory left exposed by the attacker, providing a comprehensive view of the operation.
Red Hat OpenShift Data Foundation 4.22.3 includes a security, enhancement, and bug fix update addressing multiple issues including upgrade failures, incorrect status reporting, and operator errors. The update fixes bugs related to database dump capturing, DR application validation, UI status inaccuracies, and resource handling. This advisory does not report active exploitation in the wild. The update is important for maintaining stability and security in OpenShift Data Foundation deployments.
PassMark PerformanceTest before 11.1 build 1012, BurnInTest before 11.1 build 1000, and OSForensics before 11.1 build 1016 contain an information disclosure vulnerability in DirectIo64.sys that allows unauthenticated local attackers to dump complete physical memory contents by supplying a caller-controlled file path to an exposed IOCTL. Attackers can issue a single IOCTL call to trigger the driver to iterate all physical memory ranges via MmGetPhysicalMemoryRanges and map each page through ZwMapViewOfSection on the PhysicalMemory section object, writing a full RAM image to an attacker-specified path in the SYSTEM context, bypassing user-mode ACLs and exposing LSASS working set, process memory, and cryptographic material from all running processes.
PassMark PerformanceTest before 11.1 build 1012, BurnInTest before 11.1 build 1000, and OSForensics before 11.1 build 1016 contain an unauthenticated physical memory disclosure in DirectIo64.sys, reachable by unprivileged local users through a single IOCTL with no caller-identity check. The handler writes a crash-dump-format (PAGEDU64) image of all physical memory to a caller-supplied file path in the SYSTEM context, allowing a standard user to create files in locations they cannot otherwise write and to recover memory belonging to processes of other users. The image is preceded by a header that exposes the kernel loaded-module list, active-process list and PFN database pointers, defeating KASLR. The same handler also dereferences the return value of an internal kernel-structure locator without a NULL check; that locator returns NULL on three distinct failure paths, and a kernel crash results on builds where any of those paths is taken.
Multiple security vulnerabilities have been identified in the GNU tar program used in Red Hat Enterprise Linux 9. These include hidden file injection via crafted archives, a time-of-check to time-of-use (TOCTOU) flaw in incremental dump directory rename handling that allows path escape during restore, and an issue where hardlink targets with the --one-top-level option are not confined to the top-level directory, enabling arbitrary file overwrite. Red Hat has issued an update addressing these vulnerabilities along with bug fixes and enhancements.
A vulnerability in the Linux kernel's mlx5 network driver was resolved where the fw_tracer creation function could return either NULL or ERR_PTR on failure. The code incorrectly treated these return values the same, leading to a NULL pointer dereference and a kernel crash during core dump logic. This flaw could cause a denial of service via system crash. The issue affects specific Linux kernel versions and has been patched.
In the Linux kernel, the following vulnerability has been resolved: sctp: prevent peer transport count overflow sctp_assoc_add_peer() increments the association's 16-bit transport_count for every new unique peer. Adding the 65,536th transport wraps the count to zero. SCTP sock_diag uses transport_count to reserve the INET_DIAG_PEERS payload, then copies one sockaddr_storage for every entry in transport_addr_list. After the wrap, a diagnostic dump reserves an empty payload and writes 8 MiB of peer addresses past the skb tail. Reject a new unique peer when transport_count has reached U16_MAX. Perform the check after the existing-peer lookup so a duplicate address continues to return its existing transport at the limit.
A memory leak vulnerability exists in UltraJSON's ujson.dump() function, which fails to release allocated memory when an error occurs during writing to a file-like object. This flaw can lead to resource exhaustion and a denial of service (DoS) condition. The issue affects applications using ujson.dump() with attacker-controlled input or file-like objects. Deployments using only ujson.dumps() or JSON decoding functions are not affected. Red Hat has identified this as a moderate severity issue but currently does not provide a fix that meets their criteria for ease of use and deployment.
In the Linux kernel, the following vulnerability has been resolved: mpls: fix NULL deref in mpls_valid_fib_dump_req() on CONFIG_INET=n On CONFIG_INET=n builds, mpls_valid_fib_dump_req() walks the parsed attribute table itself instead of calling ip_valid_fib_dump_req(). The RTA_OIF arm passes tb[RTA_OIF] to nla_get_u32() without checking it is present, so an RTM_GETROUTE dump for AF_MPLS with strict checking and no RTA_OIF hits a NULL dereference. RTM_GETROUTE is RTNL_KIND_GET, which rtnetlink_rcv_msg() permits without CAP_NET_ADMIN, so an unprivileged user can trigger it. Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] SMP KASAN NOPTI KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] RIP: 0010:mpls_valid_fib_dump_req (net/mpls/af_mpls.c:2189) Call Trace: mpls_dump_routes (net/mpls/af_mpls.c:2236) netlink_dump (net/netlink/af_netlink.c:2331) __netlink_dump_start (net/netlink/af_netlink.c:2446) rtnetlink_rcv_msg (net/core/rtnetlink.c:7033) netlink_rcv_skb (net/netlink/af_netlink.c:2556) netlink_unicast (net/netlink/af_netlink.c:1345) netlink_sendmsg (net/netlink/af_netlink.c:1900) __sock_sendmsg (net/socket.c:790) ____sys_sendmsg (net/socket.c:2684) ___sys_sendmsg (net/socket.c:2738) __sys_sendmsg (net/socket.c:2770) do_syscall_64 (arch/x86/entry/syscall_64.c:94) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121) Skip unset attributes, as ip_valid_fib_dump_req() does.
The Automatic Bug Reporting Tool (ABRT) recognizes defects in applications and creates bug reports that help maintainers fix the defects. ABRT uses a plug-in system to extend its functionality.
Security Fix(es):
* abrt: TOCTOU race condition in abrt-dbus SetElement allows arbitrary file writes to dump directories (CVE-2026-54228)
* abrt: ChownProblemDir succeeds during active post-create event processing due to inadequate locking (CVE-2026-54229)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
pgAdmin 4's Import/Export Data tool builds a psql \copy (...) command line by interpolating a user-supplied SQL query into a Jinja template and passing the rendered line to psql via --command. To stop an attacker from breaking out of the (...) wrapper, create_import_export_job() (route POST /import_export/job/<sid>, gated only by the ordinary, commonly-granted tools_import_export_data permission) validated the query with a hand-written parenthesis-balance checker, _is_query_parens_balanced(). That checker always treated a backslash before a single quote (\') as escaping the quote, i.e. as if standard_conforming_strings were off. PostgreSQL has defaulted standard_conforming_strings to on since 9.1 (2010), the default on every PostgreSQL version pgAdmin 4 currently supports (13-18); under that default psql's own \copy tokenizer treats \ as an ordinary character, so a single quote immediately after it closes the string literal. A query such as SELECT 'a\') TO PROGRAM 'echo pwned' x' was therefore accepted as "balanced" by pgAdmin's checker (which believed the ) was still inside the string), while psql, run through the actual rendered command line, closes the string at that point and treats the following ) as the end of the wrapping \copy (...) subquery, exposing an attacker-chosen TO PROGRAM '<command>' clause that psql executes via popen() -- independent of a subsequent syntax error later on the same line. This is the same class of bug as CVE-2025-12762/CVE-2025-13780 (RCE via psql meta-command/COPY injection during PLAIN-format dump restore), reached through an independently written defense in a different module (Import/Export Data rather than Restore) that had its own, different logic bug (inverted backslash-escape semantics rather than a BOM-defeated regex anchor).
The fix rejects any backslash inside a single-quoted string in the query outright, rather than picking one of the two possible psql interpretations. This is intentionally conservative: because the correct interpretation of \ depends on the target server's standard_conforming_strings setting, which the checker cannot reliably know at validation time, refusing the query is safer than guessing.
This issue affects pgAdmin 4: from the introduction of _is_query_parens_balanced() before 9.18.
garminconnect is a Python 3 API wrapper for Garmin Connect that retrieves statistics and manages activities. Prior to 0.3.5, garminconnect/client.py Client.dump creates the OAuth token directory and garmin_tokens.json without explicit owner-only modes, so a permissive umask such as 022 can leave the directory mode at 0755 and the token file mode at 0644. garmin_tokens.json contains di_refresh_token, and another unprivileged user on a shared Linux or macOS host can read the token and obtain persistent access to the victim's Garmin Connect account, including health, fitness, activity, and device data. The Garmin.login tokenstore path is affected, and a pre-existing loosely permissioned token file remains exposed until rewritten or manually restricted. This issue is fixed in version 0.3.5.
