PULSE
FEED
ransomakira reclama a Ligne Roset · FR · Retail & E-Commerceransomakira reclama a Houston Machine and Thread · US · Manufacturingransomdirewolf reclama a Algonomy · US · Technologyransomobsoft reclama a Company #6ransomakira reclama a Hudson & Hudson SignProducts · US · Manufacturingransomshiba reclama a Istituto Borgo · IT · Otherransomakira reclama a Boyle, Pecharich, Cline, Whittington andStallings · Professional Servicesransomn0n reclama a Dompé Farmaceutici S.p.A. · IT · Healthcareransomn0n reclama a Cogent Biosciences, Inc. · US · Healthcareransomn0n reclama a Chartboost LLC · US · Technologyransomn0n reclama a Centrepoint · SA · Energy & Utilitiesransomn0n reclama a Resource Consultants · US · Professional Servicesransomqilin reclama a Rotstein & Shiffman · IL · Professional Servicesransomn0n reclama a Max Fashion · AE · Retail & E-Commerceransomakira reclama a Ligne Roset · FR · Retail & E-Commerceransomakira reclama a Houston Machine and Thread · US · Manufacturingransomdirewolf reclama a Algonomy · US · Technologyransomobsoft reclama a Company #6ransomakira reclama a Hudson & Hudson SignProducts · US · Manufacturingransomshiba reclama a Istituto Borgo · IT · Otherransomakira reclama a Boyle, Pecharich, Cline, Whittington andStallings · Professional Servicesransomn0n reclama a Dompé Farmaceutici S.p.A. · IT · Healthcareransomn0n reclama a Cogent Biosciences, Inc. · US · Healthcareransomn0n reclama a Chartboost LLC · US · Technologyransomn0n reclama a Centrepoint · SA · Energy & Utilitiesransomn0n reclama a Resource Consultants · US · Professional Servicesransomqilin reclama a Rotstein & Shiffman · IL · Professional Servicesransomn0n reclama a Max Fashion · AE · Retail & E-Commerce
← Todos os CVEs
CVE Watch4 de nov. de 2026

CVE-2026-87038

The user-mode verification handler for the i3c_transfer() system call, z_vrfy_i3c_transfer() in drivers/i3c/i3c_handlers.c, validated the ca

CVSS

7.0

Alta

EPSS

0.1%

p0

KEV

—

Exploit Today

0

0-100

Publicado: 4 de nov. de 2026 · Última mod.: 4 de nov. de 2026 · CWE-367

EPSS · 30d
0.1%EPSS · 30 dias0.1%
2026-11-042026-11-05
Descrição técnica

The user-mode verification handler for the i3c_transfer() system call, z_vrfy_i3c_transfer() in drivers/i3c/i3c_handlers.c, validated the caller-supplied struct i3c_device_desc in place instead of snapshotting it. It confirmed only that the descriptor was readable by the calling thread (K_SYSCALL_MEMORY_READ()), read target->bus once to check it with K_SYSCALL_OBJ(), and then passed the caller's live pointer down. The implementation z_impl_i3c_transfer() re-reads target->bus from that user memory and dispatches through it as DEVICE_API_GET(i3c, target->bus)->i3c_xfers(...), so the bus that was validated is not necessarily the bus that is used. DEVICE_API_GET() performs no runtime type check outside CONFIG_DEVICE_API_ASSERT builds. On a build with CONFIG_USERSPACE and an I3C controller driver, a user thread that has been granted an I3C device object can exploit this with a second thread in the same memory domain: one thread calls i3c_transfer() while the other rewrites the bus field of the descriptor. The window between the check and the use spans the num_msgs validation, the message-array access check, a stack VLA allocation and a memcpy() of up to 32 struct i3c_msg, so the race is repeatable and can simply be retried until it lands. When the substitution succeeds, the kernel dereferences an attacker-chosen pointer as a struct device, loads a function pointer from the attacker-controlled api table and calls it in supervisor mode with attacker-influenced arguments. This yields kernel-mode code execution from an unprivileged user thread — a complete escape of the userspace memory-protection sandbox; lesser outcomes are an arbitrary two-level kernel read or a kernel fault. Builds without CONFIG_USERSPACE, or without an I3C driver, are unaffected. The fix copies the descriptor into a kernel-stack local with k_usermode_from_copy(), validates the bus in that copy, and dispatches on the copy, so the validated value is provably the value used.

Referências oficiais
CVEs relacionados
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2026-1129133.3 BAI
—
———filelock is a platform-independent file lock for Python. From 3.20.4 until 4.2.1, ReadWriteLock and AsyncReadWriteLock on Windows use _connect to attach SQLite to the lock database by pathname, allowing another local account that can create adjacent names to place a database-wal or database-journal side file before acquisition. An undeletable WAL file makes each read or write acquisition fail immediately with sqlite3.OperationalError regardless of timeout. Separately, when the database contains at least one table, a hot journal that grants the lock account modify rights can cause SQLite recovery to delete a file named by that journal only when the lock account has permission to delete the target. The issue requires a directory writable by another account, such as a shared Windows temporary directory, and does not affect private directories. This issue is fixed in version 4.2.1.22h
CVE-2026-1232073.1 BAI
—
——0LibreTV before v2.21.2 contains a server-side request forgery vulnerability that allows authenticated users to bypass checkUpstreamAllowed() by exploiting unpinned DNS resolution in fetchWithSafeRedirects(). Attackers controlling authoritative DNS can return public addresses during validation and internal addresses at connection time via /api/source/test, /api/proxy, /api/search or /api/detail to reach loopback services, private hosts or cloud metadata endpoints.1d
CVE-2026-1121106.3 MÉD
—
——0A time-of-check to time-of-use race condition in the SafeNet Authentication Client (SAC) SACSrv log-cleanup function can allow an authenticated, non-administrator local user to redirect a privileged file deletion operation outside the intended log directory.  This issue affects SAC releases up to and including 10.9 R3 GA (build 10.9.7449).1d
CVE-2026-119345—
—
——0Cocos AI is a confidential computing system for AI. Prior to 0.9.0, Cocos AI performs attestation only once when an attested TLS connection is established. An attacker who can modify the attester's workload code, memory-backed state, configuration, or attached devices after that check can keep the existing connection open while the peer continues trusting stale initial Evidence. This gap is especially significant for long-lived connections because the verifier has no mechanism to detect the changed state. This issue is fixed in version 0.9.0.23h
CVE-2026-123119—
—
——0The Symfony HttpClient component NoPrivateNetworkHttpClient does not pin the checked IP address of cached hosts, allowing for DNS rebinding to bypass private network restrictions, resulting in enumeration of internal hosts and ports in Symfony versions prior to 5.4.56, 6.x prior to 6.4.50, 7.x prior to 7.4.23, and 8.x prior to 8.1.11. NoPrivateNetworkHttpClient resolves the host of each request and checks the IP before connecting. It caches the result per host, and passes the IP to the decorated client through the resolve option so that the client connects to the exact IP that was checked. The issue is that resolve was only passed on the first lookup of a host: on subsequent requests, the decorated client resolved the host again on its own. An attacker who controls a host's DNS can exploit this with DNS rebinding by answering the first lookup with a public IP, and subsequent lookups with a private IP, so when an application sends several requests to that host through the same client, the later requests connect to the private IP. This happens, for example, when an application fetches several URLs of a repository provided by a user. The check of the primary_ip in the on_progress callback still aborts the request before anything is sent, but the connection is made, and the error differs depending on whether the port is open or closed. This allows enumerating internal hosts and ports, as in CVE-2024-50342.1d
CVE-2026-1223219.1 CRÍ
13.6%
——4Kyverno 1.18.0 before 1.19.2 contains a signature verification bypass in verifyImages because cached verification results are keyed by the image reference string (such as a tag) rather than bound to the verified digest, so cache hits skip signature and attestation checks. An attacker who can submit workloads and move a registry tag can warm the cache with a signed image, repoint the tag, and have Kyverno admit the workload and use mutateDigest to pin the unverified digest.1d