Heap out-of-bounds read in gfs2-utils enables memory disclosure and potential crashes when parsing crafted GFS2 filesystem images. The `ea_num_ptrs` field embedded in on-disk extended attribute metadata is consumed without validating it against the available buffer boundary, allowing an attacker who controls a filesystem image to trigger a heap over-read. Affected across Red Hat Enterprise Linux 7, 8, and 9; no public exploit is identified at time of analysis, and the local, user-interaction-dependent attack vector substantially limits practical exploitation.
Cross-site request forgery in AVideo's removePoster.php endpoint allows network-accessible attackers to permanently delete an authenticated victim's live poster and thumbnail files by tricking them into loading a crafted page. The endpoint accepts state-changing file-deletion operations over HTTP GET while performing neither POST-method enforcement (forbidIfNotPost) nor CSRF token validation (forbidIfInvalidToken), making the attack trivially embeddable in an HTML image tag. No active exploitation or public exploit code has been identified at time of analysis.
Missing authorization in the Unlimited Elements For Elementor WordPress plugin (versions through 2.0.17) exposes restricted functionality to unauthenticated remote callers, resulting in limited confidentiality impact. The CVSS vector AV:N/AC:L/PR:N/UI:N confirms no credentials or user interaction are needed, meaning any internet-accessible WordPress installation running the affected plugin version is reachable. No active exploitation has been identified at time of analysis, and no public exploit code is known.
Sensitive data exposure in the KP Agent Ready WordPress plugin (all versions before 1.2.08) causes the plugin to embed sensitive information - likely API keys or credentials for an external agent/chat service - in HTTP responses or frontend JavaScript assets delivered to site visitors. The CVSS 5.3 vector AV:N/AC:L/PR:N/UI:N confirms unauthenticated, low-complexity exploitation accessible to any visitor. No public exploit or active exploitation is identified at time of analysis; vendor-released patch version 1.2.08 is available.
WP EasyPay WordPress plugin versions up to and including 4.5.3 allow unauthenticated remote attackers to bypass access controls by manipulating web parameters the plugin treats as server-authoritative and immutable. The flaw (CWE-472) results in a low-level integrity impact - attackers can alter application state without credentials - but carries no confidentiality or availability consequence. No public exploit code and no CISA KEV listing have been identified at time of analysis, consistent with its Medium CVSS score of 5.3.
Insecure Direct Object Reference (IDOR) in CRMEB through 6.0.0 allows any authenticated user to modify arbitrary system inbox messages belonging to other users via the `edit_message` endpoint in `MessageSystemController.php`. The handler accepts user-controlled message IDs without validating that the requesting user owns the targeted message, enabling silent manipulation of victim notifications - including soft-deletion (`is_del`), marking as read (`look`), or reassigning ownership (`uid`). A proof-of-concept is publicly documented in the project's GitHub issue tracker; no vendor-released patch has been identified at time of analysis.
Unrestricted file upload via ZIP extraction in ILIAS MediaPool allows authenticated low-privilege users to bypass extension controls through the subtitle bulk-upload endpoint (`uploadMultipleSubtitleFileObject` backed by `ZipAdapter`), placing arbitrary file types - including PHP scripts - into server directories. Versions 9.x through 9.21, 10.x through 10.9, and 11.x through 11.2 across all active release branches are affected. No public exploit has been identified at time of analysis, but the CWE-434 primitive in a PHP application is a well-understood RCE precursor if extracted files land in a web-executable path.
Uncontrolled resource consumption in NousResearch hermes-agent 0.18.0 allows a remote attacker, with passive user interaction, to trigger excessive memory or resource allocation through the Electron main process via the `resourceBufferFromUrl` function. The impact is limited to low availability degradation (DoS) with no confidentiality or integrity exposure. Critically, the description acknowledges the vulnerable `copyImageFromUrl()` entry point was removed by v2026.8.19, making this effectively self-patched in current builds; the vulnerability is specific to the v2026.8.3 codebase window. No public exploit or active exploitation is identified.
Reflected XSS and open-redirect flaws in J2Store, a Joomla e-commerce extension by j2commerce.com, allow unauthenticated network attackers to inject malicious scripts into victim browsers via the `filter_tag`, `pricefrom`, and `priceto` parameters across all 3.x releases through 3.3.21 and all 4.x releases through 4.1.6. Four task handlers additionally accept base64-encoded redirect URLs without destination-host validation, enabling phishing attacks that abuse the shop's trusted domain to mislead customers into visiting attacker-controlled sites. No public exploit has been identified at time of analysis, and the vulnerability is not listed in CISA KEV.
Stack corruption with potential code execution in MOOS core-moos through version 10.4.0 arises from an off-by-one error in CMOOSSerialPort::GetTelegram(), where a NUL terminator is written one byte past the end of a fixed-size stack buffer. An attacker who controls the serial communication line connected to a MOOS-enabled platform can send a full-length telegram to trigger the overwrite, corrupting adjacent stack memory and potentially redirecting execution. A vendor patch is available via GitHub PR #73 and commit befb04df; no public exploit has been identified at time of analysis.
Stored cross-site scripting in pfSense Plus before 26.07 and CE before 2.9.0 allows an authenticated attacker holding the Firewall: Schedules: Edit privilege to inject arbitrary JavaScript via the schedule description field in /firewall_schedule_edit.php. The description is written to backend storage without HTML sanitization, and when rendered in /firewall_rules.php only single-quote escaping is applied - insufficient to prevent double-quote-based breakout from an HTML attribute context. Any pfSense administrator with the Firewall: Rules privilege who views the rules list while the malicious schedule is attached will silently execute the attacker's payload, enabling session token theft or in-browser privilege escalation within the firewall management interface.
Stored cross-site scripting in pfSense Plus and pfSense CE allows an authenticated attacker holding the 'Firewall: Rules: Edit' privilege to inject arbitrary JavaScript via the `descr` parameter in `/firewall_rules_edit.php`. The injected payload is written to the pfSense XML configuration with only backslash-escaping applied and no HTML sanitization, then rendered unencoded in the firewall log table at `/status_logs_filter.php`, executing in the browser of any administrator holding the 'Status: Logs: Firewall' privilege who views the affected entries. Patches are available in pfSense Plus 26.07 and pfSense CE 2.9.0; no public exploit or CISA KEV listing has been identified at time of analysis.
Stored XSS in pfSense Plus before 26.07 and pfSense CE before 2.9.0 allows an authenticated user holding only the Status: Monitoring privilege to inject arbitrary JavaScript via unsanitized graph configuration POST parameters in /status_monitoring.php. The payload is persisted in the global pfSense XML configuration file and rendered unsanitized into a JavaScript string context, meaning it executes automatically in the browser of every subsequent visitor to the Status: Monitoring page - including full administrators. Vendor-released patches exist in pfSense Plus 26.07 and CE 2.9.0; no public exploit code has been identified at time of analysis.
Command injection in the MongoDB extension for Visual Studio Code allows a remote attacker, via social engineering, to inject arbitrary shell characters into a terminal command composed by the extension when a developer opens its integrated shell feature against an attacker-controlled connection target. The extension fails to neutralize special characters from user-supplied MongoDB connection strings before embedding them in the command line, and the confirmation dialog shown to the developer does not render the injected payload, preventing visual detection. No public exploit has been identified at time of analysis, and the vulnerability is not listed in CISA KEV, but the multi-step social-engineering requirement is the primary barrier to exploitation.
Stored cross-site scripting in LearnPress WordPress Plugin before 4.4.6 allows authenticated Instructor-role users to inject persistent JavaScript through quiz question answer title fields, with payloads executing in the browsers of any user who views the affected quiz - including administrators. The unescaped HTML sink means stored payloads persist until patched, making every quiz viewer a potential victim regardless of their privilege level. No public exploit or active exploitation (CISA KEV) is confirmed at time of analysis, but the admin-targeting capability meaningfully elevates practical impact beyond the medium CVSS score.
Command injection in Dell SmartFabric OS10 Software (versions prior to 10.5.6.14) allows a remote authenticated administrator to execute arbitrary OS commands on the underlying network operating system. Classified under CWE-77, the flaw requires high privilege and high attack complexity, yielding a vendor-assigned CVSS score of 5.0 - reflecting a substantially elevated bar for exploitation compared to typical network-reachable command injection. No public exploit code or active exploitation has been identified at time of analysis; Dell has released a patched version.
Command injection in Dell SmartFabric OS10 Software (versions prior to 10.5.6.14) allows a remotely-authenticated, high-privileged attacker to execute arbitrary OS commands via the network-accessible management interface. Dell disclosed and patched the issue through advisory DSA-2026-322, with version 10.5.6.14 as the confirmed fix. No public exploit code or active exploitation has been identified; the high-privilege and high-complexity prerequisites substantially constrain the realistic threat surface.
Stack exhaustion in gfs2-utils's metawalk.c metadata walk code allows a local attacker to cause denial of service by supplying a crafted GFS2 filesystem image containing a maliciously large inode height value that drives unbounded alloca() calls. Affected systems include Red Hat Enterprise Linux 7, 8, and 9 with gfs2-utils installed; the CVSS 4.7 medium rating reflects a local, high-complexity, user-interaction-required attack path with no confidentiality or integrity impact. No public exploit code or active exploitation has been identified at time of analysis.
Stack exhaustion in gfs2-utils allows an attacker who can deliver a crafted GFS2 filesystem image to crash fsck.gfs2, gfs2_edit, or savemeta on Red Hat Enterprise Linux 7, 8, and 9. The root cause is unbounded use of alloca() in metawalk.c's hash table traversal, where the allocation size is derived exponentially from the on-disk di_depth field with no upper-bound check, so a sufficiently large di_depth value causes the process stack to be fully consumed. The impact is limited to denial of service of the affected utility; no public exploit has been identified at time of analysis, and EPSS data is not available in the provided intelligence.
CSV injection (CWE-1236) in Hitachi Energy MicroSCADA SYS600 allows attackers who can write arbitrary entries to the Notify service log to embed malicious spreadsheet formulas that execute when a Windows operator exports and opens the log as a CSV file. Impact ranges from cell data manipulation and link insertion to conditional code execution on the operator's workstation, contingent on the target's spreadsheet application security configuration. No active exploitation or public proof-of-concept has been identified; Hitachi Energy has published a security advisory documenting the issue.
Out-of-bounds read in Samsung's rlottie animation library (not Escargot as the CVE metadata incorrectly states) exposes consumers of the library - including Samsung TV appliances - to information disclosure and potential parser crashes when processing specially crafted JPEG images. The root cause is the absence of fractional-ratio validation in stb_image.h's JPEG frame header processor: when h_max is not evenly divisible by a color component's sampling factor, the resampler accesses memory beyond the intended buffer boundary. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in CISA KEV.
Incorrect Authorization (CWE-863) in Kibana allows a low-privileged authenticated user to exploit misconfigured access control levels, resulting in partial denial of service against the Kibana instance. Affected across Kibana 8.x and 9.x branches, with fixes released in versions 8.19.21, 9.4.6, and 9.5.3 per Elastic advisory ESA-2026-174. No public exploit code or active exploitation has been identified at time of analysis.
Log injection in IBM Netezza Software 11.3.0.3 through Interim Fix 002 allows unauthenticated remote attackers to insert arbitrary content into log files by supplying input containing special characters - such as CRLF sequences - that is written to logs without proper neutralization. The vulnerability (CWE-117) enables falsification of audit trails, potential SIEM-alert manipulation, and degradation of forensic fidelity. No public exploit code or active exploitation has been identified; a vendor patch is available via IBM Support.
Template injection in Kibana's Cribl integration allows a low-privileged authenticated user holding Fleet management rights to write Elasticsearch ingest pipelines exceeding their authorized Elasticsearch permissions. The flaw stems from insufficient validation of a configuration field that is rendered server-side as a script template, giving the attacker a code injection foothold (CWE-94) into the pipeline generation path. No public exploit has been identified at time of analysis, and the CVSS score of 4.3 (PR:L/I:L) reflects the constrained privilege requirement and limited integrity impact.
Cross-space agent data exposure in the Kibana Fleet feature allows authenticated low-privileged users to read agent metadata and diagnostic content outside their authorized Kibana space. An attacker holding read-level Fleet agent privileges in any one Kibana space can enumerate agents enrolled in other spaces - bypassing the space-based access boundary that Elastic uses for multi-tenancy isolation. No public exploit or active exploitation has been identified; CVSS 4.3 with PR:L aligns with the real-world impact: meaningful tenant boundary breach, but limited to read-only metadata disclosure.
Privilege abuse in Kibana allows an authenticated user holding Security read-level access in a single Kibana space to trigger Entity Analytics migration operations that perform write actions across all Kibana spaces, violating the platform's space-isolation access control model. The vulnerability stems from CWE-862 (Missing Authorization): the migration API endpoint executes privileged writes without verifying whether the caller's authorization scope covers the target spaces. No public exploit has been identified at time of analysis; a vendor patch is available per ESA-2026-154.
Server-Side Request Forgery in Dell PowerProtect Data Manager's REST API (versions 20.2.0.0 and below) allows high-privileged remote attackers to induce the server to issue unauthorized outbound HTTP requests to internal or adjacent network resources. The CVSS scope-change metric (S:C) signals that successful exploitation can reach infrastructure beyond the PowerProtect instance itself, enabling partial internal-network reconnaissance even from a single compromised admin session. No public exploit code exists and no active exploitation has been confirmed; Dell has issued multi-vulnerability advisory DSA-2026-368 addressing this flaw.
Out-of-bounds memory read in Google Chrome's CrashReporting component (all versions prior to 152.0.7977.82) allows an attacker who has already compromised the renderer process to read memory beyond sandbox boundaries via a crafted HTML page, leaking limited cross-process memory contents. The exploitation chain is constrained by a hard prerequisite - renderer compromise must precede this step - placing the flaw in a post-exploitation context rather than as a standalone initial access vector. The vendor patch is available in stable channel 152.0.7977.82, and SSVC assessment confirms no known active exploitation at time of analysis.
Stack-based buffer overflow in OpenVPN's Windows service component (openvpnserv) affects versions 2.5.0 through 2.7.6, requiring high attack complexity and passive user interaction to trigger. The flaw produces limited integrity and availability impact on the vulnerable Windows system and marginally on downstream systems in the VPN path. Fixed in v2.7.7, released on GitHub and announced via the OpenVPN community security page, alongside several other Windows-specific CVEs addressed in the same release cycle. No public exploit or active exploitation has been identified at time of analysis.
Unrestricted file upload in itsourcecode Online Medicine Delivery System 1.0 allows an authenticated customer to upload arbitrary file types through the photo parameter of the Customer Controller endpoint (/customer/controller.php?action=photos), targeting the doupdateimage function. The absence of server-side file-type validation means a low-privileged customer account can upload PHP webshells or other malicious files, enabling remote code execution on the server. A public exploit writeup is available on GitHub demonstrating the RCE chain, making this immediately actionable by opportunistic attackers.
Divide-by-zero crash in Xpdf 4.06 and earlier is triggered when the PDF rendering engine encounters a Type 3 font glyph whose declared height is zero, causing an abnormal application termination. The CVSS 4.0 score of 2.1, with all confidentiality and integrity metrics at N and only VA:L, confirms this is a pure availability impact - no memory disclosure or code execution is achievable through this path. No public exploit code has been identified and the vulnerability has not been added to the CISA KEV catalog at time of analysis.
OpenVPN on Windows (versions 2.0.0-2.6.22 and 2.7_alpha1-2.7.6) creates the --service exit event and netsh.exe guard semaphore with a NULL Discretionary Access Control List, granting any local process unrestricted access to these named synchronization objects. A low-privileged local user can acquire and hold the world-accessible semaphore indefinitely or signal the exit event, disrupting or terminating all other users' OpenVPN sessions on the same Windows host. The issue is Windows-only, affects only deployments not using the Interactive Service (iservice), and has been resolved in v2.7.7; no public exploit code has been identified.
In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables_offload: suppress WARN_ON_ONCE for ENOMEM in abort path In nft_flow_rule_offload_abort(), WARN_ON_ONCE(err) is triggered on every error during rollback, including -ENOMEM. Memory allocation failures are expected under low-memory conditions and do not indicate a kernel bug. Trace for example: nft_flow_offload_chain() // FLOW_BLOCK_BIND nft_flow_block_chain() nft_chain_offload_cmd() nft_block_offload_cmd() ->ndo_setup_tc() nsim_setup_tc() flow_block_cb_setup_simple() flow_block_cb_alloc() // fails to -ENOMEM The warning was reproduced on the 5.10 stable kernel under memory pressure via fault injection, but the underlying bug exists in mainline as well, as demonstrated by the ENOMEM trace above. The following splat was triggered during nf_tables transaction processing: WARNING: CPU: 0 PID: 8567 at net/netfilter/nf_tables_offload.c:532 nft_flow_rule_offload_abort net/netfilter/nf_tables_offload.c:532 [inline] WARNING: CPU: 0 PID: 8567 at net/netfilter/nf_tables_offload.c:532 nft_flow_rule_offload_commit+0x971/0xcd0 net/netfilter/nf_tables_offload.c:591 Modules linked in: CPU: 0 PID: 8567 Comm: syz-executor.0 Not tainted 5.10.260-syzkaller #0 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014 RIP: 0010:nft_flow_rule_offload_abort net/netfilter/nf_tables_offload.c:532 [inline] RIP: 0010:nft_flow_rule_offload_commit+0x971/0xcd0 net/netfilter/nf_tables_offload.c:591 Call Trace: nf_tables_commit+0x3bd/0x4bd0 net/netfilter/nf_tables_api.c:8604 nfnetlink_rcv_batch+0xb1e/0x1f20 net/netfilter/nfnetlink.c:509 nfnetlink_rcv_skb_batch net/netfilter/nfnetlink.c:579 [inline] nfnetlink_rcv+0x3b3/0x420 net/netfilter/nfnetlink.c:597 netlink_unicast_kernel net/netlink/af_netlink.c:1314 [inline] netlink_unicast+0x6cd/0xa00 net/netfilter/af_netlink.c:1340 netlink_sendmsg+0x906/0xe10 net/netfilter/af_netlink.c:1919 sock_sendmsg_nosec net/socket.c:651 [inline] __sock_sendmsg+0x155/0x190 net/socket.c:663 ____sys_sendmsg+0x705/0x870 net/socket.c:2379 ___sys_sendmsg+0x100/0x170 net/socket.c:2433 __sys_sendmsg+0xe9/0x1c0 net/socket.c:2462 do_syscall_64+0x33/0x40 arch/x86/entry/common.c:46 entry_SYSCALL_64_after_hwframe+0x67/0xd1 Change the condition to WARN_ON_ONCE(err && err != -ENOMEM) so that warnings are only emitted for unexpected errors. This aligns with the common kernel practice of not warning on -ENOMEM. Found by Linux Verification Center (linuxtesting.org) with Syzkaller.
In the Linux kernel, the following vulnerability has been resolved: selinux: reject a class permission count below its inherited common security_get_permissions() maps an inherited common's permissions into an array sized by the class's own permissions.nprim, but class_read() takes that nprim verbatim from the policy image and never checks that it covers the common. A class that inherits a common of N permissions while declaring a smaller nprim is accepted, and on load the common's permissions are written past the class-sized array -- an out-of-bounds heap write. Reject a class whose permission count is below its inherited common's. Well-formed policies, where the class count already includes the inherited permissions, are unaffected.
In the Linux kernel, the following vulnerability has been resolved: selinux: do not cancel a policy conversion that never started sel_write_load() calls selinux_policy_cancel() when sel_make_policy_nodes() fails, and that helper dereferences the outgoing policy to cancel its sidtab conversion. On the first policy load there is no outgoing policy: security_load_policy() returns early for that case, before it converts anything, and state->policy is still NULL. A first load that fails while building the selinuxfs tree therefore takes a NULL dereference in selinux_policy_cancel(), reached from a write(2) to /sys/fs/selinux/load. Skip the cancel when there is no old policy, mirroring the check security_load_policy() already makes before it converts.
In the Linux kernel, the following vulnerability has been resolved: ASoC: xilinx: formatter_pcm: pass aud_drv_data to irq handlers The irq handlers take a struct device pointer and call dev_get_drvdata() to obtain the driver data. However, the driver data is only set at the end of probe, after devm_request_irq(), so an interrupt taken in between causes the handlers to pass a NULL pointer to readl() and crash. Pass the private data directly as the devm_request_irq() argument instead of the device pointer, matching what the handlers expect.
In the Linux kernel, the following vulnerability has been resolved: af_packet: Don't send zero-byte data in tpacket_snd(). syzbot reported a WARNING in __dev_queue_xmit() triggered via tpacket_snd(): skb_assert_len WARNING: at include/linux/skbuff.h:2753 skb_assert_len WARNING: at __dev_queue_xmit+0x21bc/0x4970 net/core/dev.c:4781 Call Trace: <TASK> dev_queue_xmit include/linux/netdevice.h:3448 [inline] packet_xmit+0x243/0x310 net/packet/af_packet.c:276 tpacket_snd net/packet/af_packet.c:2907 [inline] packet_sendmsg+0x28d6/0x4eb0 net/packet/af_packet.c:3134 When sending 0-byte packets via TPACKET ring buffer on devices with no hard header (e.g. dev->hard_header_len == 0), tpacket_fill_skb() populates an skb with skb->len == 0 and returns 0. tpacket_snd() then forwards this empty skb to packet_xmit(), causing __dev_queue_xmit() to hit skb_assert_len(skb). Similar checks exist in packet_snd() via commit dc633700f00f ("net/af_packet: check len when min_header_len equals to 0") and in packet_sendmsg_spkt() via commit 6a341729fb31 ("af_packet: Don't send zero-byte data in packet_sendmsg_spkt()."). Return -EINVAL in tpacket_fill_skb() when skb->len is zero to reject zero-length packets in tpacket_snd().
In the Linux kernel, the following vulnerability has been resolved: net: remove WARN_ON_ONCE() from sk_mc_loop() sk_mc_loop() can be called for sockets that are neither AF_INET nor AF_INET6 (e.g. AF_PACKET sockets when sending packets via raw/packet socket over virtual devices such as VRF or ipvlan). In such cases, sk_family is not AF_INET/AF_INET6 and sk_mc_loop() falls through the switch statement and triggers WARN_ON_ONCE(1). Non-INET sockets do not support IP_MULTICAST_LOOP or IPV6_MULTICAST_LOOP options, so loopback should default to true without generating a warning.
In the Linux kernel, the following vulnerability has been resolved: Revert "drm/amdgpu: fix aperture mapping leak" devres teardown is LIFO. The aperture devres node was registered after the DRM device node, so devres_release_all() unmaps the aperture before the DRM device release callback fires amdgpu_device_fini_sw(). IP sw_fini callbacks (e.g. vcn_v4_0_sw_fini) write to fw_shared through a pointer derived from aper_base_kaddr, causing a kernel page fault on probe failure / rollback: BUG: unable to handle page fault ... PMD 0 RIP: vcn_v4_0_sw_fini+0x7b/0x170 [amdgpu] Call Trace: amdgpu_device_fini_sw amdgpu_driver_release_kms devm_drm_dev_init_release devres_release_all This reverts commit d871e99879cb5fd1fa798b006b4888887e63a17a. (cherry picked from commit 336e0cd576817ac64a4b394ca2b3680029f3e37f)
In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Fix crash passing ERR_PTR to kthread_stop() In test_ringbuffer()'s out_free cleanup loop, the check `!rb_threads[cpu]` only catches NULL entries and misses entries that hold an ERR_PTR. rb_threads[] is static, so unassigned slots are NULL. But when kthread_run_on_cpu() fails for a cpu, it stores ERR_PTR(-ENOMEM) (or -EINTR) in rb_threads[cpu] before the creation loop jumps to out_free. That entry is non-NULL, so the old `!ptr` check does not break, and the cleanup proceeds to call kthread_stop() on the ERR_PTR. kthread_stop() then dereferences the bogus pointer, crashing the kernel during the late_initcall self-test. crash logs: BUG: kernel NULL pointer dereference, address: 000000000000001c Oops: 0002 [#1] SMP NOPTI CPU: 1 PID: 1 Comm: swapper/0 Not tainted 7.2.0-rc6-dirty #7 PREEMPT(lazy) RIP: 0010:kthread_stop+0x2e/0x220 RBX: fffffffffffffff4 CR2: 000000000000001c Call Trace: <TASK> test_ringbuffer+0x1ec/0x650 do_one_initcall+0x6c/0x2c0 kernel_init_freeable+0x21d/0x420 kernel_init+0x15/0x1c0 ret_from_fork+0x21b/0x320 </TASK> Kernel panic - not syncing: Fatal exception
In the Linux kernel, the following vulnerability has been resolved: selinux: reject a permission value exceeding the class permission count perm_read() bounds a permission value by SEL_VEC_MAX but never by the nprim of the owning class or common, which is taken verbatim from the policy image. security_get_permissions() then writes perms[value - 1] into an nprim-sized kcalloc() array, so a class declaring fewer permissions than its largest permission value drives an out-of-bounds heap write. The top-level symbol tables are validated this way; the nested per-class permission table is not. Reject a permission whose value exceeds nprim, which is already set when perm_read() runs. Well-formed policies are unaffected. [PM: tweak comment for line length]
Server-side request forgery in OpenStack Glance 16.0.0 through 32.0.0 allows authenticated tenant users to make the image service fetch arbitrary internal URLs, including cloud metadata endpoints at 169.254.169.254, turning the image import pipeline into a full-read SSRF channel. Three related flaws (CVE-2026-71196, CVE-2026-71197, CVE-2026-71198) stem from insecure default host filtering in the web-download import method, a DNS rebinding bypass that evades the validator, and absent host filtering in the HTTP image location API respectively. Because Glance stores fetched bytes as downloadable image data, none of these are blind SSRF - the full response body is directly retrievable by the attacker. No public exploit has been identified, but the cloud-credential-theft impact warrants urgent remediation in any multi-tenant or internet-facing OpenStack deployment.
DNS rebinding bypass in OpenStack Glance's web-download URI validator allows authenticated tenant users to circumvent host-filter restrictions and force the image service to fetch arbitrary internal URLs, enabling full-read SSRF exfiltration via the image download API. The validator evaluates host filters against the raw pre-resolution hostname, creating a TOCTOU window: an attacker's domain passes the check resolving to a legitimate external IP, then DNS rebinding redirects the actual fetch to internal targets such as the cloud instance metadata service at 169.254.169.254. Glance versions 16.0.0 through 30.2.0, 31.0.0 through 31.1.0, and 32.0.0 are affected; no public exploit has been identified at time of analysis.
In the Linux kernel, the following vulnerability has been resolved: clk: qcom: dispcc-eliza: Fix disp_cc_mdss_mdp_clk_src RCG stall on Eliza EVK Eliza EVK (eliza-cqs-evk.dts) does not have display enabled, however its Display Clock Controller is enabled and references parent clocks from DSI PHYs, which causes clock reparenting issues during probe (init) and warning on Eliza EVK: disp_cc_mdss_mdp_clk_src: rcg didn't update its configuration. WARNING: drivers/clk/qcom/clk-rcg2.c:136 at update_config+0xd4/0xe4, CPU#1: udevd/273 ... update_config (drivers/clk/qcom/clk-rcg2.c:136 (discriminator 2)) (P) clk_rcg2_shared_disable (drivers/clk/qcom/clk-rcg2.c:1471) clk_rcg2_shared_init (drivers/clk/qcom/clk-rcg2.c:1540) __clk_register (drivers/clk/clk.c:3959 drivers/clk/clk.c:4368) devm_clk_hw_register (drivers/clk/clk.c:4448 (discriminator 1) drivers/clk/clk.c:4672 (discriminator 1)) devm_clk_register_regmap (drivers/clk/qcom/clk-regmap.c:104) qcom_cc_really_probe (drivers/clk/qcom/common.c:418) qcom_cc_probe (drivers/clk/qcom/common.c:445) disp_cc_eliza_probe (dispcc-eliza.c:?) dispcc_eliza platform_probe (drivers/base/platform.c:1432)
In the Linux kernel, the following vulnerability has been resolved: drm/log: Fix infinite loop when scale is too large for display When scale is large enough that scaled_font exceeds the display dimensions, rows or columns become 0. A columns value of 0 causes an infinite loop in drm_log_draw_kmsg_record() because the loop never decrements len. Check for zero rows/columns in drm_log_setup_modeset() and return an error, cleaning up the already allocated buffer to avoid a leak.
In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: TC, Check if flow is PEER before acquiring devcom lock In case __mlx5e_add_fdb_flow() fails in lower levels, the flow is deleted via mlx5e_tc_del_flow(), and mlx5e_tc_del_flow() is acquiring ESW devcom lock without condition. In addition, in case of peer_flow, __mlx5e_add_fdb_flow() is called while holding ESW devcom comp lock. This results in an AA deadlock. To fix this, introduce a new PEER flag that is set on flows created as peer flows (the duplicate flows on peer devices), and check it in mlx5e_tc_del_flow() before acquiring ESW devcom lock. Lockdep splat: ============================================ WARNING: possible recursive locking detected ============================================ Possible unsafe locking scenario: CPU0 ---- lock(&comp->lock_key#2); lock(&comp->lock_key#2); *** DEADLOCK *** Call Trace: <TASK> dump_stack_lvl+0x69/0xa0 print_deadlock_bug.cold+0xbd/0xca __lock_acquire+0x1671/0x2ec0 lock_acquire+0x10e/0x2e0 down_read+0x95/0x430 mlx5_devcom_for_each_peer_begin+0x4e/0xe0 [mlx5_core] mlx5e_tc_del_flow+0x11d/0xa70 [mlx5_core] mlx5e_flow_put+0x99/0x100 [mlx5_core] __mlx5e_add_fdb_flow+0x409/0xf00 [mlx5_core] mlx5e_configure_flower+0x2a86/0x4100 [mlx5_core] mlx5e_rep_setup_tc_cls_flower+0x12f/0x1b0 [mlx5_core] mlx5e_rep_setup_tc_cb+0x153/0x750 [mlx5_core] tc_setup_cb_add+0x1dc/0x470 fl_change+0x2f4d/0x626d [cls_flower] tc_new_tfilter+0x79b/0x2310 rtnetlink_rcv_msg+0x778/0xad0 do_syscall_64+0x70/0x960 entry_SYSCALL_64_after_hwframe+0x4b/0x53 </TASK>
In the Linux kernel, the following vulnerability has been resolved: mm/huge_memory: initialise workingset state before folio split xas_try_split() adds __GFP_ACCOUNT for page-cache xa_nodes, but __folio_split() leaves the xa_state's xa_lru unset. That lets a live, memcg-charged xa_node exist without being linked into the mapping's shadow_nodes list_lru; when reclaim later walks the list_lru it trips VM_WARN_ON(!css_is_dying()). Use mapping_set_update() to install both the workingset update callback and the shadow_nodes list_lru on the xa_state.
In the Linux kernel, the following vulnerability has been resolved: x86/mce: Set up the polling timer before CMCI discovery I hit the following on one of my machines: mce: CPU0 BANK15 CMCI inherited storm ------------[ cut here ]------------ ODEBUG: assert_init not available (active state 0) object: (____ptrval____) object type: timer_list hint: 0x0 WARNING: lib/debugobjects.c:632 at debug_object_assert_init+0x178/0x230, CPU#0: swapper/0/0 CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 7.2.0-rc5 #3 PREEMPTLAZY RIP: 0010:debug_object_assert_init+0x18f/0x230 Call Trace: <TASK> __mod_timer mce_timer_kick cmci_discover intel_init_cmci mce_intel_feature_init mcheck_cpu_init identify_cpu identify_boot_cpu arch_cpu_finalize_init start_kernel A second splat follows right after, from timer_setup() finding that same timer already queued: ODEBUG: init active (active state 0) object: (____ptrval____) object type: timer_list hint: stub_timer+0x0/0x10 This is happening because CMCI storm detection is trying to modify the timer before latter was properly set up. Set up the timer first. __mcheck_cpu_setup_timer() only calls timer_setup(), and depends on neither the generic nor the vendor init. [ bp: Massage commit message. ]
Multiple unsafe database operations and query-construction flaws in slurmdbd, the SLURM Workload Manager's accounting database daemon, allow authenticated cluster users or malicious slurmctld nodes to send crafted requests that result in unvalidated or improperly sanitized queries against the underlying database. The precise impact - whether SQL injection, privilege escalation within Slurm accounting, or data corruption - is not fully disclosed in available sources. No CVSS score, CWE classification, or KEV listing is present at time of analysis; the vulnerability is known only through an Ubuntu vendor disclosure.
Stack-based buffer overflow in slurmstepd, the SLURM job step daemon, can be triggered by an authenticated cluster user who submits a job containing an oversized SPANK (SLURM Plug-in Architecture for Node and job Control) option variable in the job environment. Because slurmstepd typically executes with elevated privileges on compute nodes, successful exploitation could allow a regular SLURM user to achieve privilege escalation or arbitrary code execution on cluster nodes. No public exploit or CISA KEV listing has been identified at time of analysis; this report originates from Ubuntu's vendor security tracking.