Quote:Mozilla’s Firefox Relay free email masking service now offers 50 disposable email addresses, representing a 10x increase from the previous five-mask limit.
Firefox Relay offers a free tier and a $12 per year paid tier, but since its general launch in November 2021, the free plan was limited to just five email masks. Not bad to get a taste of it, but otherwise not broadly helpful. In late May, Mozilla quietly gave us freeloaders a massive boost—a 10x increase to 50 email masks.
This upgrade should apply to all users, though the Relay extension for Firefox hasn’t quite gotten the memo yet. (At least, not on my install of Firefox.) If you’re encountering this issue, you can still create up to 50 email masks through the main interface.
- Notifications: always rendered in-app so elevated processes receive callbacks correctly
- Added Indonesian and Korean languages
- Lazy notification stack initialization for a faster app launch
- Updated to core 8.10.2
* Service start hardening: defer COM/Debug heavy init to OnRun, skip IsInstalled on the hot path
* Service: prefetch privilege LUIDs before kernel callbacks fire (eliminates first-event latency)
* Scheduled real-time-protection task: refresh VarEnv2 alongside VarEnv
* UCheck: fall back to PE FileVersion when DisplayVersion is malformed
* UCheck: match installed app by MSI ProductCode and validate downloaded file format
* ScanDigisig: collect all hits before deciding (better multi-signer file handling)
* MalPE AI: catch OOM when converting model buffer to string
* Win11: fixed AdliceDisabled folder opening an Explorer window
* Browser data: use move semantics when storing Chrome / Edge preferences
* Telemetry: include machine_id in payload
- Updated Utils libraries
* Service start hardening: defer heavy init + recover from non-crash exits
* Crash hardening: privileges cache, NTFS bounds checks, monitor dump filter
* GetFormattedSize: avoid locale leak when size == 0
- Themes: constrain checkbox / tree / table indicators to 16x16px
- Translations: Ukrainian installer string prefix fix, Hungarian style cleanup
This Android Security Bulletin contains details of security vulnerabilities that affect Android devices. Security patch levels of 2026-06-05 or later address all of these issues. To learn how to check a device's security patch level, see Check and update your Android version.
Within 48 hours after the initial publication of this bulletin, we will release the corresponding source code patches to the Android Open Source Project (AOSP) repository. We will then revise this bulletin with the AOSP links.
The most severe of these issues is a critical security vulnerability in the Framework component that could lead to remote escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. The severity assessment is based on the effect that exploiting the vulnerability would possibly have on an affected device, assuming the platform and service mitigations are turned off for development purposes or if successfully bypassed.
For more details on the Android security platform protections and Google Play Protect, which improve the security of the Android platform, refer to the Android and Google Play Protect mitigations section.
We notify our Android partners of all issues at least a month before publishing the bulletin.
Android and Google service mitigations
This is a summary of the mitigations provided by the Android security platform and service protections such as Google Play Protect. These capabilities reduce the likelihood that security vulnerabilities could be successfully exploited on Android.
Exploitation for many issues on Android is made more difficult by enhancements in newer versions of the Android platform. We encourage all users to update to the latest version of Android where possible.
The Android security team actively monitors for abuse through Google Play Protect and warns users about Potentially Harmful Applications. Google Play Protect is enabled by default on devices with Google Mobile Services, and is especially important for users who install apps from outside of Google Play.
Note: There are indications that CVE-2025-48595 may be under limited, targeted exploitation.
Quote:Microsoft has fixed the known issue that caused installation failures and 0x800f0922 errors when deploying the May 26, 2026, Windows 11 security update KB5089549.
The solution is included in the KB5089573 preview cumulative update released on May 26 and will be available to all users through the June Patch Tuesday updates later this month.
The failures were due to insufficient free space on the EFI System Partition (ESP), which led the update to roll back automatically on affected devices.
What Was Causing KB5089549 Install Failures and How to Fix Them
Microsoft confirmed two weeks ago that the problem affected devices with limited free space on the EFI System Partition, especially those with 10MB or less available. On these systems, the installation process would begin normally but fail during the reboot phase at around 35 to 36 percent completion.
Affected users saw a message stating, "Something didn't go as planned. Undoing changes," when the update rolled back. Logs from impacted systems included entries like "SpaceCheck" and "ServicingBootFiles failed," which pointed to insufficient free space on the EFI System Partition.
The GPU architecture roadmap shown at Computex 2026 also lists Xe3P under “Next Gen PC.” This is separate from Panther Lake, which already uses Xe3 graphics in the Core Ultra 300 series.
What Xe3p is
Intel confirmed Xe3p powers Crescent Island data-center GPU, which was today confirmed to support up to 480GB memory. This is not the game card though. Meanwhile, the new slide mentions PC.
What the wording does not confirm are discrete Xe3P graphics cards for gamers. It more likely refers to future client processors, perhaps Nova Lake variants with Xe3P-based graphics. Intel has confirmed Xe3P for Crescent Island, but it has not announced a gaming graphics card based on this architecture.
Quote:NVIDIA confirms RTX Spark PCs with Blackwell GPU, 20-core Grace CPU and DLSS support
NVIDIA is turning RTX Spark into a Windows PC platform
NVIDIA has officially announced RTX Spark, a new Windows PC platform built around a Grace Blackwell superchip. The announcement confirms that NVIDIA is entering the consumer PC processor segment with a full system-on-chip design, not just a discrete GPU.
The chip was announced with Microsoft at GTC Taipei. NVIDIA says RTX Spark is designed for AI agents, content creation and gaming. The platform will appear in slim Windows laptops and compact desktop PCs this fall.
RTX Spark uses a Blackwell RTX GPU with 6144 CUDA cores and fifth-generation Tensor Cores with FP4 support. NVIDIA lists up to 1 petaFLOP of FP4 AI performance. The GPU is connected through NVLink-C2C to a 20-core Grace CPU, which NVIDIA says was custom-built with MediaTek.
Quote:Apple released today iOS 26.5.1 to address charging issues on the iPhone Air and iPhone 17 models. The company also issued macOS Tahoe 26.5.1 (What's new in the updates for macOS Tahoe 26 - Apple Support), which includes a fix for an unexpected shutdown issue affecting enterprise users with M5 Mac models.
iOS 26.5.1 comes three weeks after the release of iOS 26.5, which added support for end-to-end encrypted RCS messaging and suggested places in Apple Maps. In the release notes for iOS 26.5.1, Apple explained that “this update addresses an issue for a small number of users that may prevent wired charging on iPhone Air and iPhone 17 models when the battery is nearly drained.”
For Mac users, macOS 26.5.1 “addresses an issue for enterprise users where Mac computers with an M5 chip could unexpectedly shut down when using certain content-filtering network extensions.” Apple refreshed its entire MacBook lineup with M5 chips between fall and spring, but the Mac Mini and Mac Studio have yet to be updated with the latest silicon.
![[Image: INTEL-XE3P-NEXTGEN-PC-1200x634.jpg]](https://cdn.videocardz.com/1/2026/06/INTEL-XE3P-NEXTGEN-PC-1200x634.jpg)
![[Image: NVIDIA-N1-HERO-1200x626.jpg]](https://cdn.videocardz.com/1/2026/06/NVIDIA-N1-HERO-1200x626.jpg)
![[-]](https://www.geeks.fyi/images/collapse.png "[-]")
