Chromium CVE-2026-87491: Out of bounds write in V8

Chromium: CVE-2026-85046 Type confusion in V8

Android Framework contains an integer overflow vulnerability that allows for code execution that could allow for local privilege escalation.

Chromium: CVE-2026-11645 Out of bounds memory access in V8

Chromium: CVE-2026-3909 Out of bounds write in Skia

Chromium: CVE-2026-3910 Inappropriate implementation in V8

Chromium: CVE-2026-5281 Use after free in Dawn

Chromium: CVE-2026-2441 Use after free in CSS

Accessibility. A privacy issue was addressed by removing sensitive data.

Android Framework contains an unspecified vulnerability that allows for privilege escalation.

Chromium: CVE-2025-13223 Type Confusion in V8

Android Runtime contains a use-after-free vulnerability potentially allowing a chrome sandbox escape leading to local privilege escalation.

In the Linux kernel, the following vulnerability has been resolved:

posix-cpu-timers: fix race between handleposixcputimers() and posixcputimerdel()

If an exiting non-autoreaping task has already passed exitnotify() and calls handleposixcputimers() from IRQ, it can be reaped by its parent or debugger right after unlocktasksighand().

If a concurrent posixcputimerdel() runs at that moment, it won't be able to detect timer->it.cpu.firing != 0: cputimertaskrcu() and/or locktasksighand() will fail.

Add the tsk->exitstate check into runposixcputimers() to fix this.

This fix is not needed if CONFIGPOSIXCPUTIMERSTASKWORK=y, because exittaskwork() is called before exitnotify(). But the check still makes sense, taskworkadd(&tsk->posixcputimerswork.work) will fail anyway in this case.

Accessibility. A logic issue was addressed with improved checks.

Chromium: CVE-2025-6554 Type Confusion in V8

Memory corruption due to unauthorized command execution in GPU micronode while executing specific sequence of commands.

Memory corruption while rendering graphics using Adreno GPU drivers in Chrome.

Chromium: CVE-2025-5419 Out of bounds read and write in V8

Chromium: CVE-2025-5068 Use after free in Blink

Information disclosure when an invalid RTCP packet is received during a VoLTE/VoWiFi IMS call.

Chromium: CVE-2025-2783 Incorrect handle provided in unspecified circumstances in Mojo on Windows

An out of bounds write exists in FreeType versions 2.13.0 and below (newer versions of FreeType are not vulnerable) when attempting to parse font subglyph structures related to TrueType GX and variable font files. The vulnerable code assigns a signed short value to an unsigned long and then adds a static value causing it to wrap around and allocate too small of a heap buffer. The code then writes up to 6 signed long integers out of bounds relative to this buffer. This may result in arbitrary code execution. This vulnerability may have been exploited in the wild.

In the Linux kernel, the following vulnerability has been resolved:

ALSA: usb-audio: Fix potential out-of-bound accesses for Extigy and Mbox devices

A bogus device can provide a bNumConfigurations value that exceeds the initial value used in usbgetconfiguration for allocating dev->config.

This can lead to out-of-bounds accesses later, e.g. in usbdestroyconfiguration.

In the Linux kernel, the following vulnerability has been resolved:

ALSA: usb-audio: Fix out of bounds reads when finding clock sources

The current USB-audio driver code doesn't check bLength of each descriptor at traversing for clock descriptors. That is, when a device provides a bogus descriptor with a shorter bLength, the driver might hit out-of-bounds reads.

For addressing it, this patch adds sanity checks to the validator functions for the clock descriptor traversal. When the descriptor length is shorter than expected, it's skipped in the loop.

For the clock source and clock multiplier descriptors, we can just check bLength against the sizeof() of each descriptor type. OTOH, the clock selector descriptor of UAC2 and UAC3 has an array of bNrInPins elements and two more fields at its tail, hence those have to be checked in addition to the sizeof() check.

Android Framework contains an unspecified vulnerability that allows for privilege escalation.

Memory corruption while maintaining memory maps of HLOS memory.

Chromium: CVE-2024-7965 Inappropriate implementation in V8

There exists a vulnerability in Quick Share/Nearby, where an attacker can bypass the accept file dialog on Quick Share Windows. Normally in Quick Share Windows app we can't send a file without the user accept from the receiving device if the visibility is set to everyone mode or contacts mode. We recommend upgrading to version 1.0.1724.0 of Quick Share or above

Android Pixel contains an unspecified vulnerability in the firmware that allows for privilege escalation.

Android contains an unspecified vulnerability in the kernel that allows for remote code execution. This vulnerability resides in Linux Kernel and could impact other products, including but not limited to Android OS.