2026-09-16
A mismatched DMA unmap size in the nouveau DRM driver's device-private memory (dmem) migration path causes the kernel to unmap only PAGE_SIZE instead of the full compound-folio mapping size when device-private transparent huge pages (THP) are migrated. On affected systems running the open-source nouveau driver with dmem THP migration in use, an authenticated local attacker able to drive GPU device-memory migration workloads can repeatedly trigger the nouveau_dmem_migrate_to_ram() success path or the nouveau_dmem_migrate_copy_one() copy-error path, gradually leaking residual IOMMU/IOVA mappings for order>0 folios. No public exploit code exists and the issue is not confirmed as actively exploited (not in CISA KEV); EPSS and KEV signals are absent, and our independent assessment scores this as a low-impact, local-only mapping leak (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L) rather than the 8.8 vendor vector, which overstates confidentiality, integrity, and scope impact.
Command injection in Pepperl+Fuchs ICE2/ICE3 and Phoenix Contact IOL MA8 series IO-Link Master devices allows a low-privileged remote attacker to execute arbitrary OS commands with root privileges by sending a crafted GET request to the /api/status/data REST endpoint. Three separate CERTVDE coordinated advisories (VDE-2026-014, VDE-2026-027, VDE-2026-028) indicate the same vulnerable firmware stack is shared across multiple industrial automation vendors, broadening the effective attack surface beyond any single manufacturer. No public exploit code or active exploitation has been identified at time of analysis.
Command injection via a PHP web management endpoint on Pepperl+Fuchs ICE2/ICE3 series IO-Link Masters and Phoenix Contact IOL_MA8_PN_DI8 allows an authenticated operator-level attacker to execute arbitrary OS commands with root privileges on the device. The vulnerable endpoint, `/index.php/attached_devices_tab/ajax_remove_uploaded_iodd_files`, passes user-supplied filenames to an underlying OS command without sanitization, enabling full device compromise. No public exploit code or KEV listing has been identified at time of analysis, but the low attack complexity and network accessibility make this a serious risk in OT/ICS environments.
Remote code execution is achievable on Pepperl+Fuchs ICE2/ICE3-series IO-Link Master devices and the Phoenix Contact IOL MA8 via a local file inclusion flaw in the `/index.php/ajax/save_iodd_parameters` AJAX endpoint. An authenticated attacker holding a valid operator-level session cookie can supply a crafted filename parameter that causes the PHP runtime to include and execute an attacker-controlled file, yielding full device compromise. No public exploit code and no CISA KEV listing have been identified at time of analysis; exploitation requires prior acquisition of operator credentials.
Remote code execution via PHP local file inclusion on Pepperl+Fuchs ICE2/ICE3 series IO-Link Master devices and OEM equivalents (Phoenix Contact, Indu-Sol variants) allows a low-privileged authenticated attacker to execute arbitrary PHP code by supplying a crafted parameter to the /index.php/ajax/get_iodd_port_info endpoint. The vulnerability requires only a valid user session cookie, making it accessible to any account holder on these industrial automation gateways. Three separate CERT VDE advisories (VDE-2026-014, VDE-2026-027, VDE-2026-028) indicate the same vulnerable firmware is shipped under at least three different vendor brands, broadening the affected fleet across OT environments. No public exploit code or active exploitation has been identified at time of analysis.
Command injection via the PHP-based IODD parameter save endpoint on Pepperl+Fuchs ICE2/ICE3 series IO-Link masters and OEM-equivalent devices allows an authenticated operator-level attacker to execute arbitrary OS commands with root privileges on the device. Affected hardware includes multiple ICE2 and ICE3 form-factor variants from Pepperl+Fuchs and the Phoenix Contact IOL MA8 PN DI8, with additional OEM-labeled variants covered under three separate CERTVDE advisories (VDE-2026-014, VDE-2026-027, VDE-2026-028). No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis.
Command injection in Pepperl+Fuchs ICE2/ICE3 IO-Link Master devices (and OEM variants from Phoenix Contact and others) allows a low-privileged authenticated remote attacker to execute arbitrary OS commands with root privileges via the PHP-based /index.php/ajax/parameterManage endpoint. The flaw is tracked across three CERTVDE advisories (VDE-2026-014, VDE-2026-027, VDE-2026-028), indicating the vulnerable firmware is shared across multiple vendor rebrand families. No public exploit has been identified and the vulnerability is not listed in CISA KEV at time of analysis.
Command injection via the Field_Shadow_Password class in Pepperl+Fuchs ICE2/ICE3 IO-Link master devices and Phoenix Contact IOL_MA8_PN_DI8 allows a network-authenticated attacker holding only operator-level credentials to inject OS commands that execute with root privileges on the device. The vulnerability (CWE-78) is exploitable without user interaction against a low-privileged account, resulting in full confidentiality, integrity, and availability compromise of the affected industrial device. No public exploit code or CISA KEV listing has been identified at time of analysis; three coordinated CERTVDE advisories (VDE-2026-014, VDE-2026-027, VDE-2026-028) cover multiple vendor families sharing the same underlying platform.
Command injection in Pepperl+Fuchs ICE2/ICE3 series and Phoenix Contact IOL_MA8 IO-Link master devices enables an authenticated low-privileged attacker to execute arbitrary OS commands as root via the /index.php/attached_devices_tab/do_upload web management endpoint. The vulnerability (CWE-78) is exploitable remotely without user interaction using only operator-level credentials, yielding full device compromise including confidentiality, integrity, and availability of the industrial gateway. No public exploit code or CISA KEV listing has been identified at time of analysis, though three separate CERTVDE advisories (VDE-2026-014, VDE-2026-027, VDE-2026-028) indicate coordinated multi-vendor disclosure.
Command injection in Pepperl+Fuchs ICE2/ICE3 IO-Link Master devices and OEM equivalents allows a low-privileged authenticated attacker to execute arbitrary OS commands as root via the /index.php/ajax/get_iodd_port_info PHP endpoint. Affected hardware spans multiple ICE2 and ICE3 form factors (G65L, K45P, K45S housings) as well as Phoenix Contact IOL MA8 and additional OEM-branded variants sharing the same firmware. No public exploit code has been identified at time of analysis, but the low attack complexity and high impact make this a credible priority in any industrial network where these devices are reachable.
Arbitrary file overwrite in the Contest Gallery WordPress plugin (Upload & Vote Photos, Media, Sell with PayPal & Stripe) affects all versions up to and including 32.0.1, where the 'baseUrlForFacebook' parameter is passed to a file-writing routine without adequate path validation. Exploitation requires at least a subscriber-level account on the target WordPress site, but then allows overwriting known files on the server, which can escalate to remote code execution when the overwritten path is a PHP file that the web server later executes. No public exploit code or CISA KEV listing was provided in the source data for this CVE, so active exploitation is unconfirmed at time of analysis.
Authenticated remote code execution in Arista EOS allows a malicious client with valid gRPC Network Management Interface (gNMI) access to execute arbitrary code with root privileges on the switch by sending a single specially crafted request. Only switches where gNMI has been explicitly enabled are exposed - gNMI is a non-default management API - and the attacker must already hold working gNMI credentials, which limits practical exposure to insiders or adversaries who have already compromised network-automation or management accounts, but grants them full root control of the device with low attack complexity and no user interaction. No public exploit code has been identified at time of analysis and the vulnerability is not confirmed as actively exploited (no CISA KEV listing); no EPSS score was provided. The vendor has published security advisory SA-0166 at https://www.arista.com/en/support/advisories-notices/security-advisory/24722-security-advisory-0166.
Improper output encoding in the RabbitMQ amqp091-go Go client before 1.13.0 lets an attacker who can influence a TLS asset path value (CertFile, KeyFile, CACertFile, or ServerName) inject or overwrite AMQPS connection options whenever an application serializes a URI with URI.String() and later reparses it with ParseURI(). Because the values are concatenated into the query string without url.Values encoding, embedded '&' and '=' delimiters split into extra parameters that can redirect the client to different - but still pre-existing - local certificate, key, or CA files, corrupting connection configuration. There is no confirmed active exploitation (not in CISA KEV) and no public exploit code identified at time of analysis; the vendor fix is version 1.13.0, and the practical risk is well below the headline 8.7 CVSS 4.0 score because exploitation needs a specific serialize-then-reparse code path plus attacker-influenceable path data.
Passive interception of the cleartext edgserver management protocol on Advantech EKI-1242EIMS and EKI-1242IEIMS devices running firmware V1.06.01 allows any observer positioned on the same network segment to recover sensitive device identity and network metadata as it traverses the wire. The vulnerability is unauthenticated and requires no user interaction (CVSS 4.0 vector AV:A/AC:L/AT:N/PR:N/UI:N), but our independent assessment scopes the real-world impact to confidentiality only (CVSS 3.1 AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) because a purely passive observer cannot alter or disrupt device behavior - the CVSS 4.0 base score of 8.7 reflects the vector's asserted high integrity and availability impact, which is not supported by the exploitation conditions. No public exploit code and no CISA KEV listing were identified at time of analysis, and the primary limiting factor is the requirement for network adjacency (the protocol is not remotely routable).
Authenticated non-guest users of Curiosity Workspace can escalate their privileges to administrator within an existing access group without an invitation or approval, as reported in CVE-2026-88817. The vendor rates this as high severity (CVSS 4.0 score 8.7), and our independent assessment confirms the impact is limited to the targeted access group-it does not grant application-wide administrator rights or root access to the host. No public exploit has been identified at the time of analysis, and a vendor advisory is available with potential remediation guidance.
Authentication bypass in the WNC T-Mobile 5G Box IDU router lets an attacker on the adjacent network reach the portal.cgi administration interface and log in without credentials by setting the sessionid cookie to a directory entry such as '.' or '..' that always exists under /tmp/login_user. The flaw affects firmware versions before 1.1.0.651412 and requires no authentication, no user interaction, and no non-default configuration - only network adjacency to the device (LAN or Wi-Fi side), since the assessed vector is AV:A. Impact is total: full read/write/execute control of the administrative panel, which is why the score is high (CVSS 4.0 8.7; assessed CVSS 3.1 8.7, C:H/I:H/A:H); no public exploit code and no confirmed active exploitation were identified at time of analysis, and vendor firmware 1.1.0.651412 resolves the issue.
Unauthenticated elevated command execution is possible on Arista VeloCloud Edge appliances whenever High Availability is enabled, because the HA peer functions perform no caller verification (CWE-306). An attacker positioned on the private HA interconnect can invoke sensitive peer operations and obtain full confidentiality, integrity and availability impact on the Edge unit, reflected by a CVSS 4.0 base score of 8.7 (AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H). No public exploit code has been identified at time of analysis, and the exploitable surface is adjacent-only - it is the HA interconnect segment rather than the routed internet, and units without HA configured are not affected.
Command injection in the gRPC Network Security Interface (gNSI) Credentialz service of Arista EOS allows an authenticated, low-privileged attacker with access to the gRPC management endpoint to send a crafted request that modifies a target account's properties, potentially granting that account elevated privileges or broader access than an administrator intended (CVSS 4.0 base 8.6; assessed CVSS 3.1 8.6, AV:N/AC:L/PR:L/UI:N/C:H/I:H/A:N). Exposure is conditional: the device must be running an affected EOS maintenance train (4.30.0F through 4.36.0.1F) with gNSI Credentialz configured, a non-default management feature, and the attacker must already hold authenticated access to that endpoint, making this a privilege-escalation-from-foothold rather than an anonymous remote compromise. A vendor patch is available per the Arista advisory; no public exploit code and no confirmed active exploitation were identified at time of analysis, and the issue is narrower in practice than the raw score suggests because of the configuration prerequisite.
Authenticated administrators with network reachability to the web management interface of Advantech EKI-1242EIMS and EKI-1242IEIMS devices running firmware V1.06.01 can upload firmware images that the device accepts without any cryptographic signature or certificate verification, resulting in full, persistent compromise of the platform (CWE-345; CVSS 4.0 base 8.6). The risk is genuine but access-gated: the attacker must already hold administrator-level credentials for the management interface (PR:H), so this CVE does not by itself provide a pre-authentication or privilege-escalation path, but the resulting ability to replace device firmware gives durable control over an industrial edge device that may sit on an OT/IT boundary. No public exploit code or confirmed active exploitation was identified at time of analysis.
Authenticated OS command injection in the web management interface of Advantech EKI-1242IEIMS and EKI-1242EIMS industrial gateways (reported in firmware V1.06.01) allows an attacker holding high-privilege management credentials to run arbitrary operating-system commands as root through crafted request parameters. Exploitation requires network reachability to the device's management plane plus valid privileged authentication (CVSS PR:H), after which a single low-complexity, no-interaction request yields full confidentiality, integrity, and availability impact on the appliance (assessed CVSS 3.1 base 8.8; vendor-published CVSS 4.0 score 8.6). Intelligence sources show no CISA KEV listing and no public exploit identified at time of analysis; the practical gate is that these OT edge devices are normally deployed on segmented industrial networks rather than internet-exposed, making management-plane reachability the limiting factor.
An authenticated file-overwrite vulnerability in the backup-restore workflow of Advantech EKI-1242EIMS (and EKI-1242IEIMS) firmware V1.06.01 allows an attacker who already holds administrative credentials on the device's web management interface to upload a crafted backup archive whose internal file names/paths are not validated, causing arbitrary files on the device filesystem to be overwritten. The result is complete loss of confidentiality, integrity and availability for the device itself (CVSS 4.0 base 8.6; independent assessment CVSS 3.1 AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H), making it a genuine but authentication-gated risk in a niche OT/industrial networking device rather than a pre-auth compromise path. Because exploitation requires both network reachability to the management plane and high-privilege authentication (PR:H), realistic exposure is driven by default, weak or reused admin credentials, internet- or flat-network-exposed management interfaces, and any credential compromise on the management VLAN; no public exploit code has been identified and there is no CISA KEV entry for this CVE at time of analysis.
Arbitrary Lua code execution is possible on Advantech EKI-1242EIMS and EKI-1242IEIMS industrial Modbus gateways running firmware V1.06.01, because the Modbus CSV import workflow fails to neutralize code embedded in an uploaded configuration file (CWE-94). Exploitation requires an attacker to already hold a high-privilege authenticated session on the device web management interface and to be able to reach that interface over the network, which materially limits exposure in properly segmented OT environments; no user interaction on the part of a legitimate operator is needed, only the attacker's own crafted upload. Successful exploitation yields full loss of confidentiality, integrity, and availability of the device, but no public exploit code has been identified at time of analysis, and there is no confirmation of active exploitation (not listed in CISA KEV); the vulnerability was identified by Nozomi Networks Labs and a vendor security advisory has been published.
OS command injection in the web management interface of the Advantech EKI-1242IEIMS and EKI-1242EIMS industrial gateways (firmware V1.06.01) lets an attacker who already holds high-privilege administrative credentials send a crafted HTTP request whose unsanitized parameters are passed into an OS command executed as root, yielding full compromise of confidentiality, integrity, and availability of the device. The attack is remote and low-complexity with no user interaction required, but it is access-gated: the CVSS 4.0 vector carries PR:H, so exploitation presupposes valid admin access to the management UI - no public exploit code has been identified at time of analysis and there is no confirmed active exploitation (CISA KEV). Risk is materially amplified when the web interface is reachable from untrusted networks and protected only by default or weak credentials, a common condition for field-deployed industrial gateways.
Code injection in the web management interface of Advantech EKI-1242IEIMS (and the closely related EKI-1242EIMS) industrial gateways on firmware V1.06.01 lets a remote attacker who already holds high-privilege web UI credentials execute arbitrary code on the device, including OS commands running as root. Exploitation is low-complexity once the attacker is authenticated, but the admin credential requirement (CVSS PR:H) is a hard gate that limits exposure to devices whose management interfaces are reachable and whose admin accounts have been compromised, reused, or left at weak/default values. No public exploit code has been identified at time of analysis and the flaw is not confirmed as actively exploited (no CISA KEV listing); Advantech has published a security advisory for the issue, with Nozomi Networks Labs credited for the discovery. Risk framing: this is a genuine but access-gated risk concentrated on internet- or flat-network-exposed management interfaces rather than on segmented OT deployments.
OS command injection in the web management interface of Advantech EKI-1242IEIMS and EKI-1242EIMS industrial devices running firmware V1.06.01 lets a remote attacker who already holds a valid authenticated session on the management UI execute arbitrary operating system commands with root privileges through crafted request parameters. The vulnerability (CWE-78), reported by Nozomi Networks Labs, is rated 8.6 under CVSS 4.0 (our independent assessment maps it to 8.8 under CVSS 3.1, AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H), and the high PR:H value means the attacker must first authenticate - typically at administrator level - before the injection is reachable. There is no CISA KEV listing and no public exploit identified at time of analysis, so the practical risk is driven less by exploit popularity than by how broadly the device's management plane is exposed to untrusted networks.
Authenticated high-privileged users of Advantech EKI-1242IEIMS and EKI-1242EIMS industrial gateways running firmware V1.06.01 can execute arbitrary operating system commands as root through the device's web management interface, because crafted request parameters reach an OS command without proper neutralization (CWE-78, OS Command Injection). The vendor-assigned CVSS 4.0 score is 8.6 (AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H), reflecting network reachability and complete compromise of the device's confidentiality, integrity and availability with no user interaction, but exploitation deliberately depends on the attacker first holding valid administrative credentials on the management UI. Reported by Nozomi Networks Labs; no public exploit code and no confirmed active exploitation were identified at time of analysis, so the realistic risk is driven by whether the web interface is exposed and how tightly administrative access is controlled.
OS command injection in the web management interface of Advantech EKI-1242IEIMS industrial gateways (firmware V1.06.01) lets a remote authenticated attacker with high privileges execute arbitrary OS commands as root. Exploitation requires a valid high-privilege session (CVSS 4.0 PR:H) and network reachability to the management interface, but then yields full device compromise (VC:H/VI:H/VA:H). No public exploit or active exploitation has been identified at time of analysis.
Cross-site request forgery in the LuCI administrative web interface of Advantech EKI-1242IEIMS running firmware V1.06.01 allows a remote, unauthenticated attacker to make an authenticated administrator's browser issue unauthorized state-changing requests, reaching privileged device management functions with high integrity and availability impact (vendor CVSS 4.0 base 8.6; independent 3.1 assessment AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H). Exploitation is conditional and social-engineering dependent: the administrator must hold an active LuCI session and be lured into visiting attacker-controlled content, so the technique fails against logged-out or idle-session administrators and reliability is constrained by the required user interaction. No public exploit code or confirmed active exploitation was identified at time of analysis.
Heap-based memory corruption in NLnet Labs Unbound up to and including 1.26.0 lets a remote, unauthenticated attacker who controls or spoofs the upstream DNS response (PR:N/UI:N) gradually overwrite heap memory, with the reliable outcome being a crash and remote code execution possible only on certain systems and compilation options that lack hardening. The flaw is scored CVSS 8.4 (CVSS:4.0) and by the independent assessment as CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, with the high attack complexity reflecting heavy dependence on heap layout and non-deterministic results. No public exploit code and no confirmed active exploitation were identified at time of analysis, and no KEV listing or EPSS signal is present, so this is a genuine but not-yet-urgent priority for internet-facing recursive resolvers.
Mounting a crafted NTFS filesystem image can corrupt Linux kernel memory through the in-kernel fs/ntfs3 driver, where an integer truncation in restart-table growth (a u32 'used + add' cast to the u16 __le16 count of struct RESTART_TABLE) produces an undersized allocation that is subsequently written past its bounds during $LogFile replay. The issue is local and requires an attacker-supplied image to actually be mounted: on default configurations this needs mount privileges (CAP_SYS_ADMIN/root), while the unprivileged path depends on a USB-automount daemon plus physical insertion of the media, so it is not remotely reachable. Kernels carrying the vulnerable ntfs3 log-replay code before the listed stable fixes are affected; vendor patches are available (Linux 5.15.221, 6.1.188, 6.6.157, 6.12.110, 6.18.52 and 7.2.6, plus 7.3-rc1 in mainline), no public exploit was identified at time of analysis, and EPSS is low at 0.21% (11th percentile).
Mounting a crafted NTFS image on a Linux system with the ntfs3 driver loaded triggers an out-of-bounds read in read_log_rec_buf(), causing a kernel crash and possible disclosure of adjacent slab memory into the log replay buffer. This is a local-only issue that requires the attacker to get the malicious volume mounted, either through physical media with an active automount daemon or a process/user holding mount privileges such as CAP_SYS_ADMIN, and no public exploit was identified at the time of analysis. Vendor patches are available in stable releases 5.15.221, 6.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.6, and 7.3-rc1, and the independent assessment (AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:H) is lower than the provided 8.4 vector because impact is limited to crash and potential disclosure rather than code execution.
Sandbox escape in RestrictedPython versions prior to 8.4 lets code executing inside the restricted context reach host-level primitives - function globals, builtins, file access, and code-execution gadgets - whenever the host exposes the standard-library string module, the string.Formatter class, a Formatter instance, or a Formatter subclass to that restricted code. The prerequisite is non-default: stock RestrictedPython does not surface these objects, so a custom import policy or specially crafted globals must be in place, and the attacker must also be able to submit restricted Python code (typically an authenticated user of the hosting application). A vendor patch is available in 8.4; no public exploit was identified at time of analysis.
Cross-site request forgery in the WNC T-Mobile 5G Box IDU router (portal.cgi) lets a remote attacker drive privileged actions through an already-authenticated administrator's browser, because the anti-CSRF check accepts any value supplied in the csrf_token_value parameter. The flaw affects firmware versions below 1.1.0.651412, is rated 8.4 under CVSS 4.0 (AV:A/PR:N/UI:A, high confidentiality and integrity impact, low availability impact), and requires the victim to be logged into the router portal while being lured to an attacker-controlled page reachable over the adjacent network. There is no confirmed active exploitation (not listed in CISA KEV) and no public exploit code identified at time of analysis; the vendor has released a fixed firmware build, so risk is real but conditional rather than an emergency patch-now scenario.
Improper freeing of a kernel heap buffer in the Linux kernel's cpuidle device-tree idle power-domain support (dt_idle_genpd) can crash affected systems when a device-tree idle power domain is torn down. Kernels built with CONFIG_DT_IDLE_GENPD and instantiated DT idle power domains - introduced by commit 9d976d6721df (present since Linux 5.18) and fixed in stable releases 6.1.188, 6.6.157, 6.12.110, 6.18.51 and 7.2.5/7.3-rc2 - are affected, which in practice means ARM/embedded PSCI-style platforms whose firmware provides cpuidle power-domain nodes. Triggering requires local privileged or boot-time influence over device-tree content or the ability to force genpd teardown/probe failure, so this is not remotely reachable and no public exploit has been identified at time of analysis; the practical impact is a kernel crash rather than code execution or data disclosure, despite the 8.4 base score reported by NVD-style scoring (our own assessment is AV:L/AC:H/PR:H with C:N/I:N/A:H).
Uninitialized spinlock use in the Linux kernel's ALSA 'harmony' driver (HP PA-RISC CS4215 sound hardware) can crash the system during driver initialization, because snd_harmony_create() calls request_irq() before h->lock and h->mixer_lock are initialized and a pending interrupt can fire the handler against garbage lock state. Only systems with this legacy driver present and probing on real or emulated PA-RISC hardware are exposed, and triggering it requires a narrow hardware timing window during boot or root-privileged module load, so there is no public exploit identified at time of analysis and independent assessment rates real-world risk as low despite the vendor's 8.4 (HIGH) score - the assessed impact is availability-only (local denial of service/crash) under a privileged, high-complexity precondition. Vendor patches have been published as upstream commits and are shipped in the stable releases listed below.
A missing error check in the Linux kernel's Loongson ASoC sound-card ACPI probe path (loongson_card_parse_acpi) leaves the pointer returned by device_property_read_string() for the 'codec-dai-name' property uninitialized when that property is absent or invalid, and the stale pointer is dereferenced later during driver binding. Only LoongArch/Loongson platforms whose ACPI firmware omits or malforms codec-dai-name are affected, and reaching the bug requires the ability to supply or modify that firmware description - it is not reachable over the network and not triggerable by an unprivileged local user on a default, correctly-described platform. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV; the vendor's CVSS 8.4 rating substantially overstates the assessed risk (CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:H), and the vendor vector is also internally inconsistent because it computes to 7.8 rather than 8.4.
LoongArch Linux kernels overflow the fixed-size acpi_package_ids[] array while parsing the ACPI PPTT table, so a system whose firmware or hypervisor advertises more CPU packages (sockets) than the array can hold crashes during topology setup - the concrete case in the description being a LoongArch virt VM configured with one core per socket for up to 256 sockets. Affected builds are those before the fixed 6.12.110, 6.18.51, 7.2.5 and 7.3-rc1 kernels; the flaw is reachable only on LoongArch, and the assessed precondition (per our independent analysis: AV:L/AC:H/PR:H, C:N/I:L/A:H) is control over the guest's ACPI topology rather than an ordinary unprivileged runtime action, with the practical outcome being a boot-time crash and memory corruption rather than remote code execution. No public exploit code was identified at the time of analysis and there is no CISA KEV record, so this is not confirmed as actively exploited; the vendor has released patches and the relevant upstream commits are public.
Double-decrementing the SCP device reference in the Linux kernel's MediaTek MDP3 (mtk-mdp3) media platform driver can free or unbalance a device object that the driver still uses, producing driver instability and potentially a use-after-free on systems that take the fallback SCP lookup path. The flaw is only reachable when scp_get() fails during mdp_probe() so that __get_pdev_by_id() runs; the reference taken by that fallback is dropped immediately, yet scp_put() is later called unconditionally from the probe error path and from mdp_video_device_release(). Exposure is confined to local presence on embedded MediaTek SoC hardware running the affected driver, the triggering scp_get() failure is a non-default condition rather than an attacker-controlled input path, and no public exploit code has been identified at time of analysis. Although NVD scores this 8.4, our independent assessment rates it CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H - high severity but low realistic risk.
The Linux kernel's saa7164 media driver can leave a freed device structure dangling on the global saa7164_devlist when PCI BAR memory-region allocation fails during probe, because saa7164_dev_setup() adds the device to the list before calling get_resources() and never removes it on that error path; the probe cleanup then frees the device while the global list still points at it. Affected systems are those running the saa7164 driver against an SAA7164-based (NXP/Philips) TV capture card such as a Hauppauge HVR-22xx, and effectively any kernel built with CONFIG_VIDEO_SAA7164; the flaw was introduced with commit 443c1228d50518f3c550e1fef490a2c9d9246ce7 and is fixed in Linux 6.1.188, 6.6.157, 6.12.110, 6.18.51 and 7.2.5 (mainline 7.3-rc1). No public exploit has been identified at time of analysis (no CISA KEV entry, no published POC, no EPSS signal in the supplied data), and the vendor's CVSS 8.4 is not supported by our independent assessment, which rates the issue CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L and concludes real-world risk is LOW: the trigger is a hardware/probe-time resource failure rather than an attacker-controlled input, there is no remote vector, and no default configuration is affected.
Memory corruption and kernel crashes in the Linux kernel's qla2xxx QLogic Fibre Channel HBA driver arise from an integer truncation when the driver derives its request/response queue counts from the adapter's advertised MSI-X vector count. Affected systems are those running the CONFIG_SCSI_QLA_FC driver and bound to a QLogic FC HBA that reports a boundary MSI-X count (257 vectors, which truncates to zero in the u8 queue-count fields, or exactly 1), after which qla2x00_alloc_queues() obtains ZERO_SIZE_PTR from kzalloc_objs(struct req_que *, 0) and then dereferences it via ha->req_q_map[0]; target-mode configurations can additionally underflow max_req_queues from 0 to 255. Exploitation requires physical or firmware-level control of a PCI/FC device (per our independent assessment of CVSS:3.1/AV:P/AC:H/PR:N/UI:N, C:N/I:L/A:H) rather than any network or unprivileged-user input, and there is no public exploit identified at time of analysis. Vendor patches are available in the referenced stable tree commits.
Signed integer overflow in the Linux kernel ofdrm (Open Firmware framebuffer) driver allows the framebuffer size computation fb_size = linebytes * height to wrap when both geometry values are large, resulting in an undersized framebuffer allocation and subsequent out-of-bounds memory handling inside the drm/sysfb subsystem. Exposure is confined to systems that actually bind the ofdrm driver, effectively Open Firmware/PowerPC-class platforms whose linebytes and height come from firmware or the boot device tree rather than from runtime user input, and the assessed vector (CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:H) reflects that a privileged actor able to influence platform firmware or the device tree is required, which is considerably more restrictive than the published 8.4/PR:N rating. No public exploit code and no CISA KEV entry were identified at time of analysis, and no EPSS score was supplied.
Slot reset on IBM Z (s390) Linux kernel systems can hit the wrong PCI function, and the associated slot bookkeeping leaks memory, because the PCI core assigns a single shared pci_slot object to all functions of a multifunction device. Only s390 hosts running under a machine-level hypervisor with PCI pass-through are affected, and only when multifunction devices are exposed grouped into a shared PCI domain (the topology added by commit 44510d6fa0c0); the issue is local and requires a low-privileged authenticated actor able to drive the hotplug reset path (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H, base 8.4), with no confidentiality impact and no applicability to non-s390 architectures or s390 setups that still expose virtual functions as separate PCI domains. Vendor-released patches are available in the stable and mainline trees, and no public exploit code has been identified at time of analysis.
Improper authorization on the IODD file upload endpoint of multiple Pepperl+Fuchs ICE2 and ICE3 IO-Link master devices, as well as Phoenix Contact IOL MA8 PN DI8 units, permits any low-privileged authenticated remote user to upload IO-Link Device Description (IODD) files without the privilege level required for that operation. Successful exploitation can silently alter how connected IO-Link sensors and actuators are configured or interpreted by the master, or crash the device entirely by supplying malformed IODD content. No public exploit code and no CISA KEV listing have been identified at time of analysis.
Local privilege escalation in Dell Update Package (DUP) Framework versions prior to 26.07.03 lets a low-privileged local user obtain elevated privileges when a Dell Update Package is executed through the affected framework. Exploitation is not autonomous: per the assessed vector (CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H) it requires an already-authenticated low-privileged local account plus user interaction to trigger the vulnerable code path, and the impact crosses a security boundary (S:C) with high confidentiality, integrity and availability consequences. There is no public exploit identified at time of analysis and no indication of confirmed active exploitation; the issue is rated 8.2 High, making it a credible but not urgent local escalation risk that is fully closed by upgrading to 26.07.03 or later.
OAuth access-token theft in the rmcp Rust SDK (the official Rust SDK for the Model Context Protocol) before 2.0.0 allows a malicious MCP server to harvest a victim's legitimate bearer token by publishing RFC 9728 protected-resource metadata that names a different, legitimate MCP resource together with that resource's authorization server. The OAuth client transport never verifies that the returned `resource` identifier matches the MCP server URL it was actually configured to contact, so a victim who connects and completes the normal authorization/consent flow receives a genuine access token and then sends it to the attacker's endpoint, letting the attacker replay it against the legitimate MCP resource within the granted scopes. Exploitation requires the user to be induced to connect to the attacker-controlled server and to complete consent (UI:R; CVSS 3.1 vector AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N, SSVC Automatable=no), publicly available exploit code exists per the SSVC exploitation signal, and there is no CISA KEV entry confirming active exploitation.
Denial of service in the RabbitMQ amqp091-go Go AMQP 0.9.1 client affects all releases prior to 1.13.0: the library's frame-dispatch path synchronously pushes publisher confirms, flow-control events, consumer cancellations, returned messages and connection-block notifications into application-registered listener channels, so an unbuffered, undersized or not-promptly-drained listener channel permanently blocks the connection's sole reader goroutine. Once that goroutine stalls, the client stops processing incoming frames, acknowledgments, deliveries and heartbeats, which leads to connection stalls, missed heartbeats, deadlocks and eventual broker-initiated disconnection; exploitation requires a broker-driven burst of the corresponding events against an application that registered an affected listener, rather than any attacker-supplied payload. Unauthenticated remote triggering is possible per the published PR:N vector, but only applications built on versions below 1.13.0 that back a notification listener with a small or undrained channel are exposed, and no public exploit code has been identified at time of analysis. The issue is fixed in v1.13.0, where each notification send is bounded by a 5-second timeout and slow deliveries are dropped instead of blocking the reader.
Memory exhaustion in the RabbitMQ amqp091-go Go AMQP 0.9.1 client library prior to 1.13.0 lets unauthenticated remote attackers who can influence an application's Qos settings make the client request an absurdly large prefetch limit and then buffer enough broker-delivered messages to exhaust host memory. Channel.Qos performs no bounds validation, so a negative prefetchCount or prefetchSize is cast straight into the uint16/uint32 fields of the basic.qos method and wraps to 65535 or 4294967295 instead of being rejected. The vendor CVSS 4.0 score of 8.2 (High) is availability-only and materially gated by the attack requirement that the embedding application accept untrusted Qos values; default usage with hard-coded, non-negative values is unaffected, and no public exploit code was identified at time of analysis. The defect is repaired in 1.13.0 via a new validateQos check.
Heap memory corruption in the userspace SMB daemon of MikroTik RouterOS before 7.24 lets remote, unauthenticated attackers crash or destabilize the service by sending a crafted SMB1 SessionSetupAndX request whose uniPwdLen field triggers an integer underflow and an oversized copy into a smaller heap buffer (CWE-122). The independently assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) rates this as an availability-only impact - adjacent heap corruption in a userspace daemon, not a confirmed path to code execution - and the primary limiting factor is that the SMB service is not enabled by default on RouterOS. No public exploit code has been identified at time of analysis, and exploitation requires the SMB service to be enabled and network-reachable with legacy SMB1 dialect handling active; a vendor fix shipped in RouterOS 7.24.
An out-of-bounds write in Arista VeloCloud Edge and VeloCloud Gateway affects the VCMP tunnel protocol when it processes tunneled IP fragments, causing the affected process to crash and restart and briefly disrupting traffic on the affected SD-WAN node. Exploitation requires the attacker to already be an authenticated overlay neighbor with an established VCMP peer relationship to the target (assessed CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H) - internet hosts that are unauthenticated and cannot form an overlay peer relationship cannot reach the vulnerable logic. No public exploit code has been identified at time of analysis; the impact is bounded to a temporary availability loss, with no code execution or data compromise demonstrated.
Denial of service in the Linux kernel's NVMe-over-TCP (nvme-tcp) host driver, where nvme_tcp_handle_c2h_data() accepts a controller-to-host data PDU for a command that did not request a read; the receive path then hits WARN_ON_ONCE(i->data_source) inside _copy_to_iter(), returns -EFAULT, and resets the controller. The impacted component is the initiator side of the NVMe-oF TCP transport, so hosts are only at risk when they attach to a malicious or compromised NVMe-oF TCP target that can dictate PDU sequencing; there is no public exploit identified at time of analysis, and the practical severity is modest because the trigger requires control of the storage controller the host talks to (inverted trust model). Impact is normally limited to a failed command plus a controller reset, but on hosts booted with panic_on_warn the same warning becomes an immediate kernel panic and full system outage, which is the key amplifying condition behind the assigned A:H rating.