The iOS 26.6.1, iPadOS 26.6.1, and macOS Tahoe 26.6.2 updates Apple released today fix almost 30 security vulnerabilities, according to Apple's security support document. This is Apple's third security release in three weeks as AI surfaces bugs faster than the company's typical release schedule can absorb.


Apple says the software includes security fixes that were previously added to the iOS 27, iPadOS 27, and macOS Golden Gate betas.

There are fixes for an audio vulnerability that could allow an app to leak sensitive user information, an image vulnerability that could allow for arbitrary code execution, a trio of kernel vulnerabilities, and several WebKit bugs that could cause memory corruption or Safari crashes. Of the 29 CVEs outlined in the document, 21 are WebKit-related, and nine are credited to OpenAI Codex Security.

On iOS, Apple also fixed a telephony bug that could allow an attacker in a privileged network position to bypass IPSec authentication and intercept network traffic.

None of the vulnerabilities are known to have been actively exploited, but Apple always recommends updating to new versions of iOS, iPadOS, and macOS as soon as possible. Now that the vulnerabilities have been made public, attackers could target devices still running earlier versions of the software.

Apple also released iOS 18.7.10 and iPadOS 18.7.10 for devices unable to run iOS 26 and iPadOS 26. Apple did not ship macOS Sequoia or macOS Sonoma updates for Macs unable to run ‌macOS Tahoe‌.

The updates can be installed by opening up the Settings app, tapping into the General section, and selecting Software Update.
This article, "iOS 26.6.1 and macOS Tahoe 26.6.2 Fix Nearly 30 Security Vulnerabilities" first appeared on MacRumors.com

Discuss this article in our forums

In May, Apple agreed to pay $250 million to settle a U.S. class action lawsuit over Siri AI's delayed launch, and eligible iPhone users could receive up to a $95 payout. Apple's settlement received preliminary approval last month, but final approval is not expected until next year, according to a new court document.

The judge presiding over the case last week set the final approval hearing for February 24, 2027, and payments will not begin for several months beyond that date. For now, no action is required from customers, as the settlement website with a claims form has yet to go live. We will continue to provide updates on the case as they become available.
This article, "Siri AI Settlement: Apple Won't Begin Paying Customers Until Next Year" first appeared on MacRumors.com

Discuss this article in our forums

Best Buy is hosting its big 60th Anniversary sale this week, with notable markdowns on Apple devices, TVs, headphones, monitors, and much more. This event is set to last for the rest of this week, and you don't need to be a My Best Buy Plus or Total member to see most of the deals.

Note: MacRumors is an affiliate partner with Best Buy. When you click a link and make a purchase, we may receive a small payment, which helps us keep the site running.

In terms of Apple devices, you can find solid deals on AirPods Pro 3, iPhone Air, Beats accessories, and MacBook Pro. You can get the AirPods Pro 3 for $189.99 ($60 off), as well the AirPods Max 2 for $429.00 ($120 off).



Another notable Apple offer is on the MacBook Neo, which isn't discounted itself, but Best Buy is throwing in a free $25 Starbucks gift card with any MacBook Neo purchase this week. You can also get up to $160 off iPhone Air unlocked models in this event.

Apple

• AirPods 4 - $99.99 ($30 off)


• AirPods Pro 3 - $189.99 ($60 off)


• AirPods Max 2 - $429.00 ($120 off)


• iPad Air - Get $100 off M4 models


• MacBook Neo - Get a free $25 Starbucks gift card


• 16-inch MacBook Pro (M5 Max, 36GB, 2TB) - $3,999.00 ($400 off)


• 16-inch MacBook Pro (M5 Max, 48GB, 2TB) - $4,499.00 ($500 off)

TVs

• 55-inch Toshiba C350 4K Smart Fire TV - $249.99 ($150 off)


• 55-inch Insignia 4K UHD QLED Smart TV - $249.99 ($450 off)


• 65-inch LG UA7050 4K Smart TV - $329.99 ($160 off)


• 98-inch Hisense QLED 4K Smart Google TV - $999.99 ($1,400 off)


• 65-inch Samsung The Frame TV (2025) - $999.99 ($600 off)


• 65-inch LG OLED 4K Smart TV - $1,499.99 ($1,200 off)

Audio

• Beats Pill - $99.99 ($50 off)


• Beats Solo 4 Headphones - $129.99 ($70 off)


• Beats Studio Pro Headphones - $169.99 ($180 off)


• Bose QuietComfort Ultra Headphones - $329.99 ($45 off)

If you're on the hunt for more discounts, be sure to visit our Apple Deals roundup where we recap the best Apple-related bargains of the past week.

---

This article, "Best Buy 60th Anniversary Sale Brings Massive Deals on Apple Products and More" first appeared on MacRumors.com

Discuss this article in our forums

"iPhone Ultra" supply will be very limited when the foldable device is first released later this year, according to Fixed Focus Digital, a known leaker on the Chinese social media platform Weibo.

The account also claimed that the iPhone 18 Pro's A20 Pro chip will be up to 18% faster and up to 30% more power efficient compared to the iPhone 17 Pro's A19 Pro chip. The A20 Pro chip will be the first iPhone chip manufactured with TSMC's 2nm process, rather than the current 3nm process.

Apple's annual iPhone event is likely less than a month away.
This article, "iPhone 18 Pro and iPhone Ultra: New Details Leak as Apple Event Nears" first appeared on MacRumors.com

Discuss this article in our forums

Apple today released iOS 26.6.1, iPadOS 26.6.1, visionOS 26.6.1, and macOS 26.6.2, with all of the updates containing security fixes.


Apple also released iOS 18.7.10 and iPadOS 18.7.10 with security fixes.

All of the iOS and iPadOS updates released today deliver security fixes that were first made available in the iOS 27 and iPadOS 27 betas, according to an Apple support document, which provides more specific details. Likewise, macOS 26.6.2 delivers security fixes that were first made available in the macOS Golden Gate 27 beta.

Apple says visionOS 26.6.1 security fix details are coming soon.

Be aware that iOS 26.6.1, iPadOS 26.6.1, and macOS 26.6.2 have new build numbers compared to the Release Candidate versions that were seeded last week.
This article, "Apple Releases iOS 26.6.1, macOS 26.6.2, and More" first appeared on MacRumors.com

Discuss this article in our forums

Apple today provided developers with the sixth beta of an upcoming visionOS 27 update for testing purposes. The beta comes a week after Apple released the fifth beta.


visionOS 27 can be installed by opening the Settings app, going to Software Updates, and opting into Beta Updates.

visionOS 27 introduces Siri AI, the smarter and more capable version of ‌Siri‌ that's similar in capability to chatbots like ChatGPT and Claude. On the Vision Pro, ‌Siri‌ can answer questions about anything the wearer is looking at, and there's a new ‌Siri‌ orb that can be placed anywhere in wearer's virtual space.

Panorama photos can be turned into spatial environments, and there's a new Icelandic Thórsmörk environment that features dramatic mountains, valleys, and glaciers, along with the northern lights. Web Environment support allows developers to create 360-degree environments in Safari for a more native Vision Pro browsing experience.

App windows are now curved to provide a more immersive workspace, and Control Center has been reorganized to make system controls easier to find. Apple added a smaller widget size, and notifications automatically expand when the wearer looks at them.

More on what's new in visionOS 27 is listed in our Vision Pro roundup.
This article, "Apple Seeds Sixth visionOS 27 Beta to Developers" first appeared on MacRumors.com

Discuss this article in our forums

Apple today seeded the sixth beta of watchOS 27 to developers, with the update coming a week after the launch of the fifth beta.


The beta can be downloaded through the Watch app on the iPhone with a free developer account. The Apple Watch will need to be on the charger, connected to Wi-Fi, and have a battery level of 50 percent or above for new software to be installed. The beta is available for all Apple Watch models compatible with ‌watchOS 27‌ except for the Apple Watch Ultra 3.

‌watchOS 27‌ gains Siri AI, the smarter, more capable version of ‌Siri‌. ‌Siri‌ can hold back-and-forth conversations, plus it has access to general world knowledge and your personal data to answer questions and find information. ‌Siri‌ AI on Apple Watch requires an iPhone that supports Apple Intelligence, including the iPhone 15 Pro and later.

There's a new Dynamic app grid that highlights ‌Siri‌ suggested apps, and more intuitive Smart Stack Suggestions. You can find your parked car, see pinned messages, get noise alerts, and view identity and transit cards.

Liquid Glass has been updated to improve legibility, and Workout Buddy works on the Apple Watch even when an iPhone isn't nearby. Workout Buddy also gains new metrics like progressive increases to distance, pace, or duration. Apple added a new all-in-one Find My app with support for Precision Finding, and there are performance optimizations that improve battery life.

More on what's new in ‌watchOS 27‌ is available in our watchOS 27 roundup.

This article, "Apple Seeds watchOS 27 Beta 6 to Developers" first appeared on MacRumors.com

Discuss this article in our forums

Apple today seeded the sixth beta of tvOS 27 to developers for testing purposes, with the update coming a week after Apple released the fifth beta.


The beta can be downloaded and installed through the Settings app on the Apple TV. A free developer account is required.

tvOS 27 has few new features compared to the other 27 software updates, but it does add a redesigned Podcasts app, options for larger text, and a more responsive Control Center.

AirPlaying to an ‌Apple TV‌ from another Apple device is faster, and apps and animations are smoother. You can also now see AppleCare coverage details in the Settings app.

More on the features in tvOS 27 can be found in our Apple TV roundup.
This article, "Apple Seeds tvOS 27 Beta 6 to Developers" first appeared on MacRumors.com

Discuss this article in our forums

Apple today provided developers with the sixth beta of macOS Golden Gate, with the update coming a week after Apple seeded the fifth beta.


Developers can download ‌macOS Golden Gate‌ by going to System Settings > General > Software Update. Beta Updates will need to be enabled, and a free developer account is required.

‌macOS Golden Gate‌ includes multiple design improvements. Liquid Glass opacity has been improved to increase readability, there's a slider for controlling the level of transparency, and changes to shadowing make it easier to tell when a window is active. Apps now have uniform toolbars, edge-to-edge sidebars, and less rounded corners, plus there are fewer icons in menu bars.

Siri has been transformed into ‌Siri‌ AI, a chatbot-style assistant that combines general world knowledge, your personal data, and onscreen awareness to answer questions about anything and find information for you. ‌Siri‌ lives in Spotlight, and you can ask questions with the new Search or Ask interface.

There's also a ‌Siri‌ app where you can chat with ‌Siri‌ and view past conversations, and on newer Macs, you can set a custom voice for ‌Siri‌ with personalized pace and expressivity. Visual Intelligence is now on the Mac so ‌Siri‌ can answer questions about what's on your screen, and a Write with ‌Siri‌ feature lets ‌Siri‌ generate text or give feedback on your writing.

There are AI photo editing tools in the Photos app, AI tab organization in Safari, an option to use AI to automatically update weak passwords in the Passwords app, and a revamped Image Playground app that can generate photorealistic images.

More on all of the new features in ‌macOS Golden Gate‌ can be found in our macOS Golden Gate roundup.
This article, "Apple Releases macOS Golden Gate Beta 6" first appeared on MacRumors.com

Discuss this article in our forums

Apple today seeded the sixth betas of iOS 27 and iPadOS 27 to developers for testing purposes, with the update coming one week after Apple released the fifth betas.


Registered developers can download the betas from the Settings app on the iPhone or iPad by going to the General section and selecting Software Update.

‌iOS 27‌ introduces Apple's smarter version of Siri, ‌Siri‌ AI. ‌Siri‌ AI is a chatbot similar to ChatGPT, incorporating general world knowledge, personal data from apps like Messages and Mail, and onscreen awareness to answer questions and find information for you.

There are new Apple Intelligence features in apps like Photos, Safari, Shortcuts, Wallet, and Passwords, plus Apple added a standalone ‌Siri‌ app that houses ‌Siri‌ conversations. Write with ‌Siri‌ is available systemwide for generating text or offering feedback on your writing, and Visual Intelligence has been relocated to the Camera app with a new ‌Siri‌ mode.

Apple improved the look of Liquid Glass and added a slider for customizing transparency. There are multiple performance improvements to speed up iOS, so everything feels faster, even on older iPhones. Apps launch quicker, AirDrop transfers are faster, the keyboard pops up more quickly, and devices are better at transitioning between Wi-Fi and Cellular to keep you connected.

For more on what's new in ‌iOS 27‌, we have a dedicated iOS 27 roundup.
This article, "Apple Seeds Sixth iOS 27 and iPadOS 27 Betas to Developers" first appeared on MacRumors.com

Discuss this article in our forums

Apple Sports was updated today with support for additional soccer leagues, including the Austrian Bundesliga, English Women's Super League, Greek Super League, Indian Super League, Saudi Pro League, Spanish Liga F, and Turkish Süper Lig.

Apple Sports already gained support for seven more soccer leagues in July, so the additions now total 14 over the past month. The app remains available on the iPhone only, with version 4.3 rolling out on the App Store now.
This article, "Apple Sports App Updated With More Soccer Leagues" first appeared on MacRumors.com

Discuss this article in our forums

Apple has agreed to make changes to its App Tracking Transparency feature in Germany, according to the country's competition regulator.


Since the release of iOS 14.5 in April 2021, Apple has required apps to ask for permission before tracking a user's activity across other apps and websites for personalized advertising. If a user selects the "Ask App Not to Track" option, the app is unable to access the device's advertising identifier. Apple says the feature is designed to enhance user privacy, but some advertisers have complained that it has significantly impacted their revenue.

In Germany, Apple has agreed to remove "possibly discouraging symbols and wording" from the App Tracking Transparency prompt, the regulator said. Apps will also be "given more scope to explain to users what significance personalized advertising has for their offering and their business model," and the "freedom to combine the consent request required by Apple with the consent requests required under data protection law."

Apple has four months starting on the date it is formally served with the decision to implement the changes in Germany, and it will test them with app developers first, the regulator said. The changes will apply for seven years.

Over the past few years, Apple has faced similar regulatory pressures over the App Tracking Transparency feature in other EU countries, such as France, Italy, and Poland, and from the overarching European Commission.

Apple has maintained that App Tracking Transparency protects user privacy and is compliant with competition law in Germany. Nevertheless, it agreed to make the changes, and the regulator said the proceedings have thus concluded.

Apple issued the following statement regarding the changes:

At Apple, we believe privacy is a fundamental human right, and we introduced App Tracking Transparency to give users a simple way to control whether apps have permission to track their activity across other companies' apps and websites. While we believe the current ATT prompt provides a clear, easy-to-understand and effective way to keep users in control of their data—an opinion shared by the German data protection authorities—we have agreed to make changes to the text and formatting of the prompt at the FCO's request. These commitments ensure we can continue to provide this important privacy tool in Europe and keep users, not ad tech companies and data brokers, in control of their data.

This article, "Apple Agrees to Make 'App Tracking Transparency' Changes in Germany" first appeared on MacRumors.com

Discuss this article in our forums

In select U.S. states, residents can add their driver's license or state ID to the Apple Wallet app on the iPhone and Apple Watch, and then use it to display proof of identity or age at select airports and businesses, and in select apps. According to a new report and evidence within Apple's code, the feature is set to expand to four more states.


A few days ago, North Carolina's DMV announced that it plans to launch a mobile ID program later this year. As reported by WRAL, North Carolina residents will be able to set up a digital ID through a new NC Wallet app starting in December, with Apple Wallet, Google Wallet, and Samsung Wallet support to follow in "early 2027."

To set up the feature, open the Wallet app on the iPhone and tap on the plus sign in the top-right corner. Next, tap on Driver's License and ID Cards, select your state from the list, and follow the on-screen steps to complete the process. Then, you can present your digital ID at participating TSA checkpoints and businesses, without handing over your device.

You can present an Apple Wallet ID where accepted by simply tapping your iPhone or Apple Watch on an identity reader. Then, you will be able to view the specific information being requested by the TSA or business. Only after authorizing with Face ID or Touch ID is the requested identity information released from your device.

As mentioned, you do not need to unlock, show, or hand over your device to present an Apple Wallet ID in person, ensuring user privacy.

Apple Wallet IDs are generally not accepted by law enforcement, so carrying a physical ID is still legally required for traffic stops. In addition, the number of businesses that accept Apple Wallet IDs is still quite small. At least for now, Apple Wallet IDs are designed to be a convenient alternative where they are accepted.

"Your mobile ID is a valid form of identification in North Carolina," the DMV said, in a FAQ on its website. "However, as retailers, restaurants and other businesses transition to mobile IDs, some may not be set up to accept them right away. For now, carrying your physical card gives you a backup when needed."

According to code seen by MacRumors, Apple Wallet IDs are also coming to Oklahoma, Utah, and Virginia, but there is no timeframe for availability.

All in all, Apple Wallet IDs are coming to these four states:

• North Carolina


• Oklahoma


• Utah


• Virginia

The following 14 states already offer Apple Wallet IDs:

• Arizona (since March 2022)


• Maryland (since May 2022)


• Colorado (since November 2022)


• Georgia (since May 2023)


• Ohio (since July 2024)


• Hawaii (since August 2024)


• California (since September 2024)


• Iowa (since October 2024)


• New Mexico (since December 2024)
• Montana (since August 2025)


• North Dakota (since September 2025)


• West Virginia (since October 2025)


• Illinois (since November 2025)


• Arkansas (since May 2026)

The feature is also available in Puerto Rico.

Apple Wallet IDs are accepted at TSA checkpoints in more than 250 airports in the U.S. for domestic travel, and North Carolina's DMV said this will include Charlotte Douglas International Airport and Raleigh-Durham International Airport.

Travelers should refer to TSA signage to confirm availability of the feature.
This article, "Apple Wallet Driver's License Feature to Launch in Four More U.S. States" first appeared on MacRumors.com

Discuss this article in our forums

When iOS 27 arrives next month, you'll be able to reply to a specific green chat bubble (aka an Android message) in a Messages conversation on your iPhone.


All you need to do is press and hold the message, tap Reply, then type your response. It will be received by the recipient as a real threaded reply (i.e. an inline reply), tying it directly to the message in question. It's the same with reactions – react to a shared photo and your contact will see the intended emoji instead of a message saying that you "liked an image."

It's all thanks to Apple's embrace of RCS Universal Profile 3.0, the GSMA standard it helped publish and has been adopting in stages. Universal Profile 2.4 first appeared in iOS 18 in September 2024, but it didn't support inline replies. Come this September, on supporting iPhones, that will finally change.

Bear in mind that the feature also depends on carrier support at both ends. Even before you update to iOS 27, you can see if your device is ready for the change: simply go to Settings ➝ Apps ➝ Messages ➝ RCS Messaging, and check that the RCS Messaging toggle is enabled. If the setting isn't displayed in said menu, your carrier has yet to enable the feature.
This article, "iOS 27 Finally Fixes Replying to Android Texts" first appeared on MacRumors.com

Discuss this article in our forums

• Introduction
• A plea to the undecided voter
• Table
• Notes

Debian LLM GR - Summary of the options

Introduction

LLMs have finally made it to the ultimate stage of Debian’s governance processes, a General Resolution of all the project’s full governing members (DDs).

There are a lot of options on the ballot, and they all have a different structure and approach the question in a different way. It can be hard to see the wood for the trees. I have made a summary table to try to capture the main differences, both in effect, and sentiment.

A plea to the undecided voter

Suspending briefly my attempt to be neutral:

Before voting, I encourage you to read the passionate rationales in options H and A, or at least the summary in my option C.

Few of the LLM defences in the discussion threads, and none of the LLM-positive proposals, provide answers to any of these profound ethical concerns, many of which ought individually to be a deal-breaker. Instead, these crucial questions are simply dismissed or even ignored.

Some will tell you we should “keep politics out of software” but as we can see in the world around us, software is political - now more than ever. Debian’s mission is a highly political one: developing a fully-free operating system, and defending its freeness as we do, is far from neutral!

And of course many of LLMs’ harms affect Debian directly.

Table

	A	G	C	H	F	D	B	E
LLM harms	Robustly discussed	Discussed	Robustly summarised	Robustly discussed; especially re climate	Summarised	Accepted as inevitable	Disregarded [1]	Ignored
Direct contributions of LLM-generated code	Forbidden	Forbidden	Strongly discouraged	Strongly discouraged	Discouraged	Permitted	Permitted	Permitted
Direct use of LLM output in communications (bugs, mailing lists, etc.)	Forbidden	Forbidden	Forbidden (with possible exceptions)	Strongly discouraged	Discouraged	Permitted	Permitted	Permitted
LLM use where LLM output does not end up in the code/message	Forbidden	No position, so permitted	Strongly discouraged	Strongly discouraged	Discouraged	Permitted	Permitted	Permitted
Disclosure of LLM use	LLM use forbidden	LLM use largely forbidden, no further disclosure requirement	Disclosure required	Disclosure encouraged	Disclosure encouraged	Disclosure required	Disclosure required	Undisclosed LLM use is OK
Use of LLMs by upstreams			Condemned			“Not recommended”
Positive statements about LLMs						“Here to stay”	Moderate	Strong

Notes

Ordering

I have tried to present the options in semantic order, with most LLM-negative proposals to the left, and the most LLM-positive to the right.

I have not quoted the one-line titles for the options. These have generally been provided by the proponents of each option, and, unfortunately, some of them are IMO quite misleading.

Note that, unfortunately, the voting software likes to assign numbers to options but also to preferences. Be mindful of this possible confusion when casting your vote. For clarity I quote only the option letters.

Upstream LLM code contributions

Some of the proposals acknowledge the uncertain legal status of LLM output. But all of them implicitly or explicitly assume that LLM output is or can be DFSG free. So none of the proposals forbid upstream projects with LLM-generated contents.

None of the proposals would require us to go back to pre-LLM versions of the upstream projects we use, and attempt to fork and maintain them. I very much think there is room in the world for people to try to do that, but I don’t think the Debian project can be that effort.

Given that the conclusions are the same in each case, whether the matter is discussed does not seem to me to be a significant difference. I have therefore not included a column for it.

Ability of individual teams to set their own rules

My proposal has a specific paragraph (7) explicitly permitting teams to set a “no LLM” policy. The other proposals do not discuss this point specifically. During the discussion, it seemed that most participants agreed that even options which explicitly permit LLM use generally do not prevent a team from setting its own more restrictive LLM policy.

I have therefore not tabulated this aspect.

Exceptions and nuances

Few of the permissive texts are absolute or unconditional. To summarise I have necessarily left out some nuance.

So for example when an entry says “permitted”, that generally means “permitted with conditions which are believed by LLM users to be readily satisfiable” (for example, DFSG-compatibility - see above).

[1] Footnote re proposal B

Proposal B does mention that there are “concerns” about LLM use. But it fails to make an explicit statement about whether these concerns are justified.

It then proceeds exactly as if they are not justified. IMO “disregarded” is a relatively mild term for such a rhetorical technique.

---

Edited 2026-08-18 09:02 UTC to make the proposal letters in the table be links; 2026-08-26 09:11 UTC to fix typos.

comments

Apple's AirPods Max 2 have hit $429.00 on Amazon this week, down from $549.00. This sale is available in two colors on Amazon, while Best Buy has all five models in stock at this low price.

Note: MacRumors is an affiliate partner with some of these vendors. When you click a link and make a purchase, we may receive a small payment, which helps us keep the site running.

Free delivery on Amazon has the AirPods Max 2 arriving around August 22, but Prime members should see same-day delivery options in many locations. This is the best deal on the headphones that we've tracked since June, and it's just about $30 higher when compared to the all-time low price.



If you're on the hunt for more discounts, be sure to visit our Apple Deals roundup where we recap the best Apple-related bargains of the past week.

---

This article, "AirPods Max 2 Discounted by $120 Across Amazon and Best Buy" first appeared on MacRumors.com

Discuss this article in our forums

The screen sharing flaw that Apple rushed out a fix for earlier this month has already been exploited in the wild, according to the Netherlands' National Cyber Security Center (NCSC-NL).


On August 6, Apple released macOS Tahoe 26.6.1, an update to the ‌macOS Tahoe‌ operating system that came out last year. The update came a little over a week after Apple released macOS Tahoe 26.6.

In its security support document, Apple said that the update addressed a vulnerability that could allow an attacker to authenticate to Screen Sharing without valid credentials – in short, a bad actor could view a user's Mac screen and remotely take control of their keyboard and mouse. It appears however that hackers have already been taking advantage of the flaw.

As first reported by ArsTechnica, the NCSC-NL said that it had been notified of abuse of the vulnerability, "observed on multiple systems on which port 5900 was accessible from the internet." The reason is that when screen sharing is enabled, macOS's firewall intentionally exposes this port.

"In all these cases, root had been accessed on the affected system and a Monero crypto miner had been placed," the NCSC-NL added. In other words, a targeted Mac's resources are used to mine cryptocurrency.

When pushing the fix – which was also included in macOS Sonoma 14.8.9 and macOS Sequoia 15.7.9 – Apple said it had addressed the authentication issue with "improved state management." Users who have not updated their Macs should do so as soon as possible. Even for those who have updated, use of a VPN is also recommended when screen sharing is active.

If you're not sure if your macOS version is up-to-date, you can check by going into your Mac's System Settings and selecting General ➝ Software Update.
This article, "Apple's macOS Screen Sharing Flaw Is Being Exploited in the Wild" first appeared on MacRumors.com

Discuss this article in our forums

Apple is hiring a Studio Producer for its Fitness+ service with a background in live production, in what could be a hint at the future of the service.


The job listing was posted last month, detailing an in-person role at Apple's Santa Monica studio. It calls for someone with a "strong foundation in live or live-to-tape multi-camera production and a genuine curiosity about where live content is headed next." Apple says it wants a "creative collaborator" who is "excited to experiment with new formats" and "push the boundaries of what live fitness content can be."

The role's actual list of responsibilities reads like Fitness+ production management rather than anything specific to live content. While Fitness+ is not a live service, many of the skills applicable to live production would likely be transferable to its needs.

Apple Fitness+ launched in 2020 as a library of trainer-led workout and meditation videos available on the iPhone, iPad, and Apple TV, all shot in advance and streamed on demand, with Apple Watch integration for workout metrics. Apple has never offered Peloton-style live classes, real-time leaderboards, or scheduled sessions through the service, so the listing's repeated emphasis on live production skills appears to mark new territory, even if the responsibilities section stops short of describing what that live content would look like.

The job listing arrives as Apple continues to consider Fitness+'s future. Bloomberg's Mark Gurman reported in November that Fitness+ was "under review" amid a broader reorganization, describing it as one of Apple's "weakest digital offerings" due to high churn and low revenue. Apple health vice president Sumbul Desai took over the service as part of that restructuring, with the health division now reporting directly to services chief Eddy Cue.

Gurman said in February that the review was still ongoing, and guessed that Apple would eventually merge Fitness+ with the Health app directly in some form, "perhaps offering it as a combined subscription." He did not mention any plans for live content.

Thanks, Anthony!
This article, "Job Listing Suggests Apple Fitness+ Could Get Live Content" first appeared on MacRumors.com

Discuss this article in our forums

The DistroWatch news feed is brought to you by TUXEDO COMPUTERS. This week in DistroWatch Weekly:
Review: Helwan Linux 5.0
News: Mint develops new kernel manager, NetBSD gets updated Enlightenment port, Redox OS updates system installer, KDE Plasma 6.6 to gain long-term support
Questions and answers: Why distributions mostly use Bash
Released last week: CachyOS 260809, SparkyLinux 8.4, Manjaro Linux 26.1.0, Omarchy....

The DistroWatch news feed is brought to you by TUXEDO COMPUTERS. TUXEDO Computers, a German-based manufacturer of Linux desktop and laptop computers, has announced the release of the initial public beta build of its Debian-based TUXEDO OS. While the past releases of the distribution were based on Ubuntu, the project has recently decided to switch to Debian's "Testing" branch....

The DistroWatch news feed is brought to you by TUXEDO COMPUTERS. PrismLinux, an Arch-based Linux distribution with a custom system installer and support for Cinnamon, GNOME and KDE Plasma desktops, as well as the niri Wayland compositor, has been updated to version 2026.08.15: "After more than two months without a release, PrismLinux Reborn 1.0 is finally here. This release....

Amazon this weekend has introduced a big discount on the AirPods 4 with Active Noise Cancellation, available for $134.99, down from $179.00. This is one of the best prices we've seen on the earbuds all year, and it's accompanied by a solid discount on the AirPods Pro 3.

Note: MacRumors is an affiliate partner with some of these vendors. When you click a link and make a purchase, we may receive a small payment, which helps us keep the site running.

You can also get the AirPods 4 for $99.00, down from $129.00. This is a second-best price on the AirPods 4, which is the base model without Active Noise Cancellation. Amazon provides an August 21 estimated delivery date for free shipping, with faster delivery options for Prime members.




Finally, the AirPods Pro 3 are available for $189.99, down from $249.00. This is the best price we've seen on the AirPods Pro 3 since Prime Day in June, coming in around $10 higher when compared to that all-time low price.



This model of the AirPods Pro launched in September 2025 and has 2x better Active Noise Cancellation than the previous generation, better audio quality, a revised fit that's meant to improve comfort and stability, Live Translation for in-person conversations, and heart rate sensing for workouts.

Head to our full Deals Roundup to get caught up with all of the latest deals and discounts that we've been tracking over the past week.

---

This article, "AirPods 4 ANC Hit $134.99 Low Price on Amazon, Plus Pro 3 for $189.99" first appeared on MacRumors.com

Discuss this article in our forums

It has now been thirty-three years since the Debian project was announced to the world by Ian Murdock, on August 16, 1993. This anniversary is an opportunity to reaffirm the goals, characteristics, and qualities of the Debian project: it’s an association of individuals who have made common cause to create a free operating system. Our distribution is characterized by a commitment to software freedom, as enshrined in the Debian Social Contract and the Debian Free Software Guidelines. It focuses on security and stability. This stability is crucial to Debian position in the free software ecosystem.

With our users as our priority, Debian makes special efforts regarding accessibility with Debian-Accessibility and diversity with our Outreach Programs.

Debian Day is a great opportunity to get together, whether for a local meetup, or simply to grab a coffee with other members of the Debian community. Check out the Debian Day wiki to see if there is a celebration near you. And if there isn't, maybe you can organize it next year!

Today is also an opportunity for you to start or resume your contributions to Debian. For example, you can install the how-can-i-help package and see if there is a bug in any of the software that you use that you can help to fix, contribute small tips on how to install Debian on your machines to our wiki pages, or put a Debian live image in an USB memory and give it to some person near you, who still didn't discover Debian.

Thanks to everybody who has contributed to develop our beloved operating system in these 33 years, and Happy birthday Debian!

I made another minor release with several enhancements: handling non-Debian origin vulnerabilities, improving data caching, and sharing the cache between the debvulns CLI and the exporter. Additionally, there are a few improvements on the dashboard front. Here is a breakdown of what changed.

Not a screenshot of despair. But only because it’s not a screenshot.

Info: German content only, sorry.

I was pondering for the past three years if I should give some sort of TLS basics talk at FrOSCon. I finally stepped up this year and gave that talk today, with the title "TLS, mTLS, SNI, ECH, CAA, HTTPS, PKI, Zertifikate und ein bisschen PQC". I was too optimistic with my 50 slides, and had to drop the Post Quantum Cryptography part at the end. Still got positive feedback from Zugschlus and others - thanks a lot for that <3 - and was asked for the slides. It's not a piece of art, but maybe it helps to release the LibreOffice odp file as well, so others can use it as a base for other events or corp internal talks. So here is the froscon-tls-2026.pdf and froscon-tls-2026.odp, both released under the CC BY-NC license.

The video is also available at media.ccc.de if you want to watch it.

Thanks to everyone who made FrOSCon happen for the 21th time!

Apple is likely winding down work on the initial release of iOS 27 as it prepares to install the operating system on new iPhone models coming next month, but some changes are still being made as we saw with the fifth round of betas this week.


Other news and rumors this week included a look at an alleged battery from the upcoming iPhone 18 Pro Max, third-party accessories revealing some information about the foldable "iPhone Ultra," and more, so read on below for all of the details!

Top Stories

Everything New in iOS 27 Beta 5

We're a little over a month away from the launch of iOS 27, and Apple is continuing to make changes. The fifth beta of ‌iOS 27‌ seeded to developers and public beta testers this week changes the look of some app icons and adjusts Liquid Glass, plus it adds some smaller features that make the iPhone just a little nicer to use.


Check out our full overview of all of the changes in the latest beta.

iPhone 18 Pro Max's Larger Battery Capacity Allegedly Revealed

The upcoming iPhone 18 Pro Max will be equipped with a nearly 12% larger battery compared to the iPhone 17 Pro Max, according to an apparent leak.


An alleged photo of a battery pack for a Chinese model of the iPhone 18 Pro Max with a SIM card tray lists a capacity of 5,391 mAh, up from 4,823 mAh for the equivalent iPhone 17 Pro Max battery.

The iPhone 18 Pro will reportedly start with the same 256GB of storage as the iPhone 17 Pro, but one analyst firm estimates that memory price spikes and other increases will raise Apple's costs to manufacture the new models by approximately 38%.

'iPhone Ultra' Screen Protectors Reveal Asymmetric Corners

The leaker known as "Ice Universe" this week shared images and a hands-on video of screen protectors for Apple's rumored "iPhone Ultra," and the leak appears to confirm a few of the most discussed details about the foldable's front design.


Notably, the leaked accessory has square corners on the side that would sit next to the hinge, and rounded corners on the opposite edge. That asymmetry lines up with months of rumors describing a foldable device with a hinge on one side, and the leak marks one of the clearest looks yet at how the proportions and shape carry over to the cover display itself.

Third-party camera protectors intended for the iPhone Ultra may also point to two expected color options for the device: silver and dark blue.

Apple Watch Rethink Could See Debut of Round Model, Screenless Fitness Tracker, and More

Apple is re-evaluating the Apple Watch lineup and considering a host of radical new designs, according to Bloomberg's Mark Gurman.


In this week's edition of his "Power On" newsletter, Gurman compared plans for the Apple Watch's evolution to the "revolutionary design change" that the foldable iPhone represents. It will be "something that transforms the product for a new era."

Apple's industrial design team has reportedly been "exploring a broader rethink of its smartwatches" for some time, with several directions under evaluation including offering a round display and even some screenless fitness tracker products.

In the nearer term, a ceramic case option for the Apple Watch could return either this year or next. The material has been absent from the Apple Watch lineup since the discontinuation of the Series 5.

New MacBook Pro and Refreshed iMacs Likely Coming in October

Apple is likely to unveil a new M6 MacBook Pro and refreshed iMacs in October, based on its typical release schedule, according to Bloomberg's Mark Gurman.


Writing in the latest edition of his "Power On" newsletter, Gurman reiterated his belief that Apple is readying the launch of a refreshed base-model MacBook Pro with a 14-inch display powered by an M6 chip.

As for iMacs, the new version is likely to be an updated 24-inch model with an M5 chip or M6 chip, replacing the existing M4 model. No major design changes are expected.

iPhone Users Who Pay for Enough iCloud Storage Get New iOS 27 Perks

If you are subscribed to an iCloud+ plan with at least 2TB of storage, you will receive new perks in the Home app on iOS 27, according to Apple.


Starting with iOS 27, Apple said iPhone users who are subscribed to an iCloud+ plan with at least 2TB of storage receive access to three new Apple Intelligence features in the Home app: generated video descriptions for HomeKit Secure Video cameras, the ability to search for camera clips, and automatic surfacing of noteworthy clips.

According to Stephen Robles, the Home app on the fifth developer beta of iOS 27 now indicates how many HomeKit Secure Video cameras are eligible for generated video summaries. Robles told us he had a total of 8TB of iCloud+ storage (6TB plus 2TB from Apple One), and this made him eligible for video summaries for up to 15 cameras.

MacRumors Newsletter

Each week, we publish an email newsletter like this highlighting the top Apple stories, making it a great way to get a bite-sized recap of the week hitting all of the major topics we've covered and tying together related stories for a big-picture view.

So if you want to have top stories like the above recap delivered to your email inbox each week, subscribe to our newsletter!
This article, "Top Stories: iOS 27 Beta 5, iPhone 18 Pro Rumors, and More" first appeared on MacRumors.com

Discuss this article in our forums

What Happened

On 2026/08/10 at 2:11 am Australian eastern standard time (2026/08/09 16:11 UTC) someone created a post titled “Hacked by Chinafans” on my documents blog [1]. The person in question created an account named “67965e42a3c3” on that site with the email address 67965e42a3c3@google.com associated with it (I tried emailing that address and it bounced).

At 04:28:41am Australian eastern standard time (18:28 UTC) I was sent an email titled “Have you been hacked” by a reader of my blogs who subscribed to the RSS feed of my documents blog (a blog that I never expected anyone to read by RSS). Along the lines of “the wisdom of crowds” should we have “the unexpected observation and problem reporting of crowds”? I appreciate the notification, I might not have noticed until the next time I watched an unusually good movie otherwise.

The account in question was apparently created on 2026-07-21 at 16:43:47 (presumably UTC) even though at the time I believe creating accounts was not permitted. As an aside the timestamp of account creation is stored in the user_registered column of the wp_users table in the database, there doesn’t appear to be a way to access this in a standard WordPress installation other than doing a SQL query.

2026-07-24 15:43:17 status triggers-pending wordpress:all 7.0+dfsg1-1
2026-07-24 15:43:19 upgrade wordpress:all 7.0+dfsg1-1 7.0.2+dfsg1-1

Above are the relevant sections of my dpkg log showing the WordPress versions in use. I was running version 7.0+dfsg1-1 at the time the account was apparently created. I am confident in the accuracy of the dpkg logs and believe that they did not compromise the OS, I am not sure whether they ran hostile SQL code to change fields in the MySQL database so had to consider the possibility that the account creation time could have been set to a deliberately misleading value. I checked backups of the MySQL database stored off-site and found that the account in question was not in the 2026-07-21 backup (which was done before 16:43) but in the 2026-07-22 backup.

The WordPress release history [2] has version 7.0.1 released on 2026-07-09 and version 7.0.2 released on 2026-07-17. So presumably the attacker diffed the code on those releases, found an exploitable bug, and used it to create an account on my blog with admin privs. Then they waited a few weeks to see if I would notice and published a blog post when I didn’t notice.

WordPress Deficiencies

1. WordPress doesn’t seem to store the version it’s running at the time of operations. So anyone who doesn’t have a suitable external log of versions deployed (such as the dpkg.log file for a Debian managed installation) won’t know for sure which version was running. It supports automatic updates but you can’t be sure that they happened soon after the release.
2. There is no log of IP addresses used for operations. There are apparently some 3rd party modules to log such things and web pages documenting how to modify the PHP to add it but nothing in the standard distribution.
3. Software should have a standard distribution with some support for logging of security relevant data. The typical situation is that people don’t plan for logging such things until after they have been attacked so the data should be recorded without users going out of their way to log it.
4. A log of security relevant data should be stored in a database table with only insert access (no update, delete, or drop).
5. Ideally a CMS would support different database accounts for different purposes. Someone from an internal network or VPN could talk to an instance of the web server which has a database username and password giving full access. Everyone from outside the trusted range gets an instance of the web server with database access only allowing to read the posts and appearance configuration and to enter comments. If the database didn’t allow the account used for public access to create new admin users or create posts then it would be a lot harder for attackers.
6. Ideally for everything that stores user account data there would be an easy way of getting a list of users in a plain text format to allow running diff. The design of WordPress has two tables, one for users and one for encoded metadata about users of which one will be the access level. The following SQL command will give a list of all users that aren’t subscribers (everyone above the minimum level of access which is typical for new users) along with their encoded password and access level. This could be used in a monitoring system to alert about new privileged users. The TABLE_PREFIX variable is for the prefix for WordPress tables, which is “wp_” by default but can be any legal value.

   select $TABLE_PREFIXusers.user_login, $TABLE_PREFIXusers.user_pass, $TABLE_PREFIXusermeta.meta_value from  $TABLE_PREFIXusers join $TABLE_PREFIXusermeta on $TABLE_PREFIXusers.id = $TABLE_PREFIXusermeta.user_id and meta_key='$TABLE_PREFIXcapabilities' and meta_value != 'a:1:{s:10:"subscriber";b:1;}';

What Next?

The blog post they created had a couple of links to Telegram which could presumably be used to contact them. If anyone involved in computer security wants a copy of the original post to do so then they can contact me by any of the usual methods.

I am interested in communication with the attacker if they wish, Telegram is not a service I use but I presume that anyone capable of doing this sort of attack is also capable of finding other ways of contacting me.

I have idly considered changing to a static site generator, here is a good list of static site generators [3].

I have also idly considered other platforms for blogging such as Lemmy. I don’t know if Lemmy is better than WordPress for security and updates, but there are plenty of free instances running where it wouldn’t be an issue I have to work on.

15 Years

It’s been 15 years since my blog server was cracked by a trojaned ssh client [4]. At least this time it was only one service that was compromised.

• [1] https://doc.coker.com.au/
• [2] https://en-au.wordpress.org/download/releases/
• [3] https://jamstack.org/generators/
• [4] https://etbe.coker.com.au/2011/12/31/server-cracked/

The AMD GPU Problem

For a while I’ve been having issues with AMD GPUs, video locking up periodically. I blogged about this late last year but I first had noticeable problems early last year [1]. The problems hadn’t only concerned my workstation but also my home server which is also used as a workstation. I’ve recently upgraded my machines to Debian/Testing, my home server has been generally OK but my workstation has been crashing a lot. Every second day when on kernel 7.1.6 and then when on 7.1.7 it crashed at least once a day.

The AMD GPUs I have are “[AMD/ATI] Baffin [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X] (rev e5)” in my main desktop workstation, “[AMD/ATI] Lexa [Radeon 540X/550X/630 / RX 640 / E9171 MCM] (rev c1)” in my build server, and “[AMD/ATI] Baffin [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X] (rev cf)” in my home server. They aren’t new GPUs, but also aren’t really old and they all support 4K and better resolution.

Chat GPT Was Useful

When I googled the errors I was seeing I found nothing useful. On the suggestion of a friend I tried asking ChatGPT. Generally I don’t recommend asking LLMs about such things, but it can be a last resort as long as you know what you are doing. ChatGPT asked me to run a number of commands to get information for it to make more informed decisions. I know that the output of lspci and similar commands isn’t a risk, but a novice could be tricked into running commands that expose sensitive data.

ChatGPT did give me some useful information, not a solution but an indication that the problem was due to driver bugs.

Upgrading to Experimental

Debian/Experimental is for packages that are expected to have problems and generally aren’t recommended even for the people who usually use Debian/Unstable. It’s commonly used for packages that are needed to develop other packages, EG new libraries that aren’t fully usable but which are needed to package newer versions of applications.

I upgraded my workstation to the Debian/Experimental kernel 7.2~rc7-1~exp1 after having tried every other convenient option. Generally I wouldn’t recommend that anyone run an Experimental kernel without a really good reason, but crashing more than once a day is a fairly good reason. That kernel has now given me over 4 days of uptime on a system that previously wouldn’t last a day. I installed it on my dual-socket build server that has an old AMD GPU in it for test purposes and that also hasn’t crashed since. I installed it on my ML test machine which has an Intel B580 Battlemage GPU with 16G of VRAM and was repeatedly getting a kernel panic related to the GPU a few seconds after boot and now it also works correctly.

It seems that the 7.1.x kernels have bugs in the AMD video drivers and in some part of the code that affects Intel video drivers and that the bugs in question are fixed in the tree that will become 7.2. I would not recommend anyone who has a 7.1.x kernel working fine for them try 7.2 RC kernels at this time, but anyone who has GPU related problems (particularly Intel and AMD GPUs) should definitely test it out.

I also don’t recommend upgrading any system with an AMD GPU to Debian/Testing or Debian/Unstable at this time unless you are also prepared to install an Experimental kernel if it becomes necessary.

There are a several kernel log dumps related to this after the break (which won’t be in RSS feeds). This is mainly for Google so that other people who have such issues can get more useful results out of Google searches than I got.

Future Support Options

Separate from the issue of whether commercial LLMs like ChatGPT can be useful for solving technical problems there is the issue of whether they are desirable. I think that we really don’t want people solving problems in FOSS systems with closed-source LLMs. This leads to loss of privacy, loss of the control users deserve to have over their own systems, and an implied promotion of non-fee software.

I think that the ideal would be to have a cross distribution effort to generate training data for a support LLM system which can then be further trained by each distribution for a greater emphasis on distribution specific issues.

• [1] https://etbe.coker.com.au/2025/11/09/amd-video-driver-issues/

Errors on AMD GPUs

2026-08-09T23:03:06.004792+10:00 xev kernel: amdgpu 0000:02:00.0: GPU fault detected: 147 0x00024802
2026-08-09T23:03:06.004792+10:00 xev kernel: amdgpu 0000:02:00.0: Process kscreenlocker_g pid 42037 thread kscreenloc:cs0 pid 42044
2026-08-09T23:03:06.004793+10:00 xev kernel: amdgpu 0000:02:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000800
2026-08-09T23:03:06.004794+10:00 xev kernel: amdgpu 0000:02:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0F048002
2026-08-09T23:03:06.004795+10:00 xev kernel: amdgpu 0000:02:00.0: VM fault (0x02, vmid 7, pasid 130) at page 2048, write from 'TC0' (0x54433000) (72)
2026-08-09T23:03:06.008762+10:00 xev kernel: amdgpu 0000:02:00.0: GPU fault detected: 147 0x00004802
2026-08-09T23:03:06.008768+10:00 xev kernel: amdgpu 0000:02:00.0: Process kscreenlocker_g pid 42037 thread kscreenloc:cs0 pid 42044

2026-08-04T01:13:37.505839+10:00 xev kernel: ------------[ cut here ]------------ 
2026-08-04T01:13:37.505859+10:00 xev kernel: amdgpu 0000:02:00.0: [drm] drm_WARN_ON_ONCE(cur_vblank != vblank->last) 
2026-08-04T01:13:37.505862+10:00 xev kernel: WARNING: CPU: 6 PID: 210534 at drivers/gpu/drm/drm_vblank.c:362 drm_update_vblank_count+0x2f1/0x3c0 [drm] 
2026-08-04T01:13:37.505866+10:00 xev kernel: snd_intel_dspcfg wmi_bmof rc_core snd_intel_sdw_acpi drm_ttm_helper uas realtek snd_usbmidi_lib snd_hda_codec ttm mdio_devres snd_hda_core snd_seq_midi drm_kms_helper usb_storage mc snd_hwdep libphy snd_seq_midi_event intel_uncore snd_pcm_oss i2c_algo_bit serio_raw snd_rawmidi pcspkr snd_mixer_oss i2c_i801 video snd_seq snd_pcm i2c_smbus lpc_ich snd_seq_device mei_me e1000e snd_timer mei snd tpm_infineon soundcore joydev bnx2 wmi button nfsd auth_rpcgss nfs_acl lockd grace sunrpc coretemp br_netfilter bridge stp llc sg ghash_clmulni_intel loop msr i2c_dev drm efi_pstore configfs nfnetlink ip_tables x_tables autofs4 btrfs blake2b_generic dm_crypt dm_mod raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx libcrc32c xor raid6_pq raid1 raid0 md_mod ext4 crc16 mbcache jbd2 crc32c_generic virtio_blk evdev hid_generic usbhid hid sd_mod xhci_pci xhci_hcd ahci ehci_pci ehci_hcd libahci crc32c_intel libata usbcore aesni_intel nvme psmouse scsi_mod gf128mul crypto_simd nvme_core cryptd 
2026-08-04T01:13:37.505879+10:00 xev kernel: nvme_auth scsi_common usb_common efivarfs 
2026-08-04T01:13:37.505880+10:00 xev kernel: CPU: 6 UID: 1008 PID: 210534 Comm: sshd-session Tainted: G D 6.12.88+deb13-amd64 #1 Debian 6.12.88-1 
2026-08-04T01:13:37.505881+10:00 xev kernel: Tainted: [D]=DIE 
2026-08-04T01:13:37.505883+10:00 xev kernel: Hardware name: Hewlett-Packard HP Z640 Workstation/212A, BIOS M60 v02.61 03/23/2023 
2026-08-04T01:13:37.505884+10:00 xev kernel: RIP: 0010:drm_update_vblank_count+0x2f1/0x3c0 [drm] 
2026-08-04T01:13:37.505885+10:00 xev kernel: Code: 48 8b 5f 50 48 85 db 75 03 48 8b 1f e8 68 eb 2b cf 48 c7 c1 70 3e cb c0 48 89 da 48 c7 c7 f9 6f cb c0 48 89 c6 e8 af d7 a6 ce <0f> 0b e9 4b fe ff ff 48 8b 4c 24 18 e9 31 fe ff ff 31 f6 48 85 db 
2026-08-04T01:13:37.505887+10:00 xev kernel: RSP: 0000:ffffd3cc8681fca0 EFLAGS: 00010082 
2026-08-04T01:13:37.505888+10:00 xev kernel: RAX: 0000000000000000 RBX: ffff8c6b42b13710 RCX: 0000000000000027 
2026-08-04T01:13:37.505889+10:00 xev kernel: RDX: ffff8c89ef521788 RSI: 0000000000000001 RDI: ffff8c89ef521780 
2026-08-04T01:13:37.505890+10:00 xev kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: ffffd3cc8681fb20 
2026-08-04T01:13:37.505891+10:00 xev kernel: R10: ffff8c8a6fef3628 R11: 0000000000000003 R12: 0000000000000000 
2026-08-04T01:13:37.505892+10:00 xev kernel: R13: ffff8c6c07853828 R14: 0000000000000003 R15: 0000000000000000 
2026-08-04T01:13:37.505893+10:00 xev kernel: FS: 00007ffaf2fd5880(0000) GS:ffff8c89ef500000(0000) knlGS:0000000000000000 
2026-08-04T01:13:37.505895+10:00 xev kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 
2026-08-04T01:13:37.505896+10:00 xev kernel: CR2: 00007fb1718c8000 CR3: 000000074521a004 CR4: 00000000003706f0 
2026-08-04T01:13:37.505897+10:00 xev kernel: Call Trace: 
2026-08-04T01:13:37.505898+10:00 xev kernel:  
2026-08-04T01:13:37.505899+10:00 xev kernel: drm_crtc_accurate_vblank_count+0x41/0xc0 [drm] 
2026-08-04T01:13:37.505900+10:00 xev kernel: dm_pflip_high_irq+0x155/0x330 [amdgpu] 
2026-08-04T01:13:37.505901+10:00 xev kernel: amdgpu_dm_irq_handler+0x85/0x1f0 [amdgpu] 
2026-08-04T01:13:37.505902+10:00 xev kernel: amdgpu_irq_dispatch+0xd2/0x230 [amdgpu] 
2026-08-04T01:13:37.505903+10:00 xev kernel: amdgpu_ih_process+0x84/0x100 [amdgpu] 
2026-08-04T01:13:37.505904+10:00 xev kernel: amdgpu_irq_handler+0x23/0x60 [amdgpu] 
2026-08-04T01:13:37.505905+10:00 xev kernel: __handle_irq_event_percpu+0x4a/0x190
2026-08-04T01:13:37.505907+10:00 xev kernel: handle_irq_event+0x38/0x80 
2026-08-04T01:13:37.505908+10:00 xev kernel: handle_edge_irq+0x8b/0x230 
2026-08-04T01:13:37.505909+10:00 xev kernel: __common_interrupt+0x45/0xe0 
2026-08-04T01:13:37.505910+10:00 xev kernel: common_interrupt+0x42/0xa0 
2026-08-04T01:13:37.505911+10:00 xev kernel: asm_common_interrupt+0x26/0x40 
2026-08-04T01:13:37.505912+10:00 xev kernel: RIP: 0033:0x7ffaf3c5fd7b 
2026-08-04T01:13:37.505913+10:00 xev kernel: Code: 70 c7 00 66 0f 6e f8 c1 ef 02 66 0f 70 f7 e0 83 c7 01 66 0f ef ff 66 0f fa f2 0f 1f 44 00 00 f3 0f 7e 01 66 0f 6f ce 83 c6 01 <48> 83 e9 08 f2 0f 70 c0 1b 66 0f 6f e0 66 0f 6f e8 66 41 0f f9 c0 
2026-08-04T01:13:37.505915+10:00 xev kernel: RSP: 002b:00007fff86a5e0e0 EFLAGS: 00000202 
2026-08-04T01:13:37.505916+10:00 xev kernel: RAX: 0000000000008000 RBX: 0000562614a04050 RCX: 0000562614982ed8 
2026-08-04T01:13:37.505946+10:00 xev kernel: RDX: 0000000000007fe2 RSI: 0000000000000fad RDI: 0000000000002000 
2026-08-04T01:13:37.505948+10:00 xev kernel: RBP: 0000000000000000 R08: 000056261498ac40 R09: 0000000000008000 
2026-08-04T01:13:37.505949+10:00 xev kernel: R10: 0000000000000066 R11: 0000000000007fe1 R12: 0000000000007efa
2026-08-04T01:13:37.505950+10:00 xev kernel: R13: 0000000000008000 R14: 0000000000008000 R15: 000000000000ffe0 
2026-08-04T01:13:37.505951+10:00 xev kernel:  
2026-08-04T01:13:37.505953+10:00 xev kernel: ---[ end trace 0000000000000000 ]--- 
2026-08-04T01:55:40.844110+10:00 xev kernel: pcieport 0000:00:03.3: AER: Multiple Correctable error message received from 0000:00:03.3 
2026-08-04T01:55:40.844130+10:00 xev kernel: pcieport 0000:00:03.3: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Receiver ID) 
2026-08-04T01:55:40.844132+10:00 xev kernel: pcieport 0000:00:03.3: device [8086:6f0b] error status/mask=00000040/00002000 
2026-08-04T01:55:40.844134+10:00 xev kernel: pcieport 0000:00:03.3: [ 6] BadTLP

2026-08-11T09:33:33.473855+10:00 xev kernel: amdgpu 0000:02:00.0: GPU fault detected: 147 0x00024802
2026-08-11T09:33:33.473871+10:00 xev kernel: amdgpu 0000:02:00.0: Process kscreenlocker_g pid 150905 thread kscreenloc:cs0 pid 150912
2026-08-11T09:33:33.473871+10:00 xev kernel: amdgpu 0000:02:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000800
2026-08-11T09:33:33.473873+10:00 xev kernel: amdgpu 0000:02:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0F048002
2026-08-11T09:33:33.473873+10:00 xev kernel: amdgpu 0000:02:00.0: VM fault (0x02, vmid 7, pasid 63) at page 2048, write from 'TC0' (0x54433000) (72)
2026-08-11T09:33:33.473874+10:00 xev kernel: amdgpu 0000:02:00.0: GPU fault detected: 147 0x00004802
2026-08-11T09:33:33.473874+10:00 xev kernel: amdgpu 0000:02:00.0: Process kscreenlocker_g pid 150905 thread kscreenloc:cs0 pid 150912
2026-08-11T09:33:33.473875+10:00 xev kernel: amdgpu 0000:02:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000800
2026-08-11T09:33:33.473876+10:00 xev kernel: amdgpu 0000:02:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0E048002
2026-08-11T09:33:33.473876+10:00 xev kernel: amdgpu 0000:02:00.0: VM fault (0x02, vmid 7, pasid 63) at page 2048, read from 'TC0' (0x54433000) (72)
2026-08-11T09:33:35.481863+10:00 xev kernel: amdgpu 0000:02:00.0: Dumping IP State
2026-08-11T09:33:35.481875+10:00 xev kernel: amdgpu 0000:02:00.0: Dumping IP State Completed
2026-08-11T09:33:35.481875+10:00 xev kernel: amdgpu 0000:02:00.0: [drm] AMDGPU device coredump file has been created
2026-08-11T09:33:35.481876+10:00 xev kernel: amdgpu 0000:02:00.0: [drm] Check your /sys/class/drm/card0/device/devcoredump/data
2026-08-11T09:33:35.481877+10:00 xev kernel: amdgpu 0000:02:00.0: GPU fault detected: 146 0x0110040c
2026-08-11T09:33:35.481877+10:00 xev kernel: amdgpu 0000:02:00.0: Process kscreenlocker_g pid 150905 thread kscreenloc:cs0 pid 150912
2026-08-11T09:33:35.481878+10:00 xev kernel: amdgpu 0000:02:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000022
2026-08-11T09:33:35.481879+10:00 xev kernel: amdgpu 0000:02:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0E00400C
2026-08-11T09:33:35.481879+10:00 xev kernel: amdgpu 0000:02:00.0: VM fault (0x0c, vmid 7, pasid 63) at page 34, read from 'TC3' (0x54433300) (4)
2026-08-11T09:33:35.489845+10:00 xev kernel: amdgpu 0000:02:00.0: ring gfx timeout, signaled seq=5123619, emitted seq=5123621
2026-08-11T09:33:35.489853+10:00 xev kernel: amdgpu 0000:02:00.0: Process kscreenlocker_g pid 150905 thread kscreenloc:cs0 pid 150912
2026-08-11T09:33:35.489854+10:00 xev kernel: amdgpu 0000:02:00.0: GPU reset begin!. Source: 1
2026-08-11T09:33:35.493839+10:00 xev kernel: amdgpu 0000:02:00.0: [drm] ERROR Failed to initialize parser -125!
2026-08-11T09:33:35.737848+10:00 xev kernel: amdgpu: cp is busy, skip halt cp
2026-08-11T09:33:35.897842+10:00 xev kernel: amdgpu: rlc is busy, skip halt rlc
2026-08-11T09:33:35.897852+10:00 xev kernel: amdgpu 0000:02:00.0: BACO reset
2026-08-11T09:33:36.485849+10:00 xev kernel: amdgpu 0000:02:00.0: GPU reset succeeded, trying to resume
2026-08-11T09:33:36.485859+10:00 xev kernel: amdgpu 0000:02:00.0: [drm] PCIE GART of 256M enabled (table at 0x000000F402000000).
2026-08-11T09:33:36.485860+10:00 xev kernel: amdgpu 0000:02:00.0: VRAM is lost due to GPU reset!

Errors on Battlemage

Aug 11 17:01:47 ami kernel: ------------[ cut here ]------------
Aug 11 17:01:47 ami kernel: xe 0000:23:00.0: [drm] DMC 1 mmio[0]/0x5f074 incorrect (expected 0x96fc0, current 0x0)
Aug 11 17:01:47 ami kernel: WARNING: drivers/gpu/drm/i915/display/intel_dmc.c:696 at assert_dmc_loaded+0x275/0x430 [xe], CPU#0: kworker/0:3/215
Aug 11 17:01:47 ami kernel: Modules linked in: intel_rapl_msr intel_rapl_common intel_uncore_frequency intel_uncore_frequency_common xe(+) skx_edac snd_h>
Aug 11 17:01:47 ami kernel:  msr i2c_dev configfs efi_pstore efivarfs autofs4 btrfs libblake2b raid6_pq xor mpt3sas raid_class scsi_transport_sas megarai>
Aug 11 17:01:47 ami kernel: CPU: 0 UID: 0 PID: 215 Comm: kworker/0:3 Not tainted 7.1.7+deb14-amd64 #1 PREEMPT(lazy)  Debian 7.1.7-1 
Aug 11 17:01:47 ami kernel: Hardware name: HP HP Z4 G4 Workstation/81C5, BIOS P61 v03.00 04/15/2026
Aug 11 17:01:47 ami kernel: Workqueue: sync_wq local_pci_probe_callback
Aug 11 17:01:47 ami kernel: RIP: 0010:assert_dmc_loaded+0x291/0x430 [xe]
Aug 11 17:01:47 ami kernel: Code: 24 10 e8 f2 e5 a3 ce 48 8d 3d bb 85 0d 00 8b 54 24 0c 45 89 e9 45 89 e0 48 89 c6 52 8b 4c 24 2c 51 8b 4c 24 30 48 8b 54>
Aug 11 17:01:47 ami kernel: RSP: 0018:ffffd27ac0b87b80 EFLAGS: 00010282
Aug 11 17:01:47 ami kernel: RAX: ffffffffc1743dfd RBX: ffff8c5b80e54000 RCX: 0000000000000001
Aug 11 17:01:47 ami kernel: RDX: ffff8c5b81df5a10 RSI: ffffffffc1743dfd RDI: ffffffffc1605860
Aug 11 17:01:47 ami kernel: RBP: ffff8c5b86955000 R08: 0000000000000000 R09: 000000000005f074
Aug 11 17:01:47 ami kernel: R10: 0000000000000000 R11: 0000000000091050 R12: 0000000000000000
Aug 11 17:01:47 ami kernel: R13: 000000000005f074 R14: 0000000000000001 R15: 0000000000000000
Aug 11 17:01:47 ami kernel: FS:  0000000000000000(0000) GS:ffff8c673e172000(0000) knlGS:0000000000000000
Aug 11 17:01:47 ami kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 11 17:01:47 ami kernel: CR2: 00007ffed1fdcd00 CR3: 0000000ae942a003 CR4: 00000000003706f0
Aug 11 17:01:47 ami kernel: Call Trace:
Aug 11 17:01:47 ami kernel:  
Aug 11 17:01:47 ami kernel:  intel_dmc_enable_pipe+0xe4/0x290 [xe]
Aug 11 17:01:47 ami kernel:  ? drm_crtc_vblank_reset+0x4d/0x120 [drm]
Aug 11 17:01:47 ami kernel:  intel_modeset_setup_hw_state+0xb50/0x1e10 [xe]
Aug 11 17:01:47 ami kernel:  ? intel_display_driver_probe_nogem+0x138/0x1a0 [xe]
Aug 11 17:01:47 ami kernel:  intel_display_driver_probe_nogem+0x138/0x1a0 [xe]
Aug 11 17:01:47 ami kernel:  xe_display_init_early+0xb2/0x140 [xe]
Aug 11 17:01:47 ami kernel:  xe_device_probe+0x3c8/0xb50 [xe]
Aug 11 17:01:47 ami kernel:  ? xe_pm_init_early+0x152/0x160 [xe]
Aug 11 17:01:47 ami kernel:  xe_pci_probe+0xc26/0x1150 [xe]
Aug 11 17:01:47 ami kernel:  local_pci_probe+0x3e/0x90
Aug 11 17:01:47 ami kernel:  local_pci_probe_callback+0x16/0x20
Aug 11 17:01:47 ami kernel:  process_one_work+0x19d/0x3a0
Aug 11 17:01:47 ami kernel:  worker_thread+0x1af/0x320
Aug 11 17:01:47 ami kernel:  ? __pfx_worker_thread+0x10/0x10
Aug 11 17:01:47 ami kernel:  kthread+0xe3/0x120
Aug 11 17:01:47 ami kernel:  ? __pfx_kthread+0x10/0x10
Aug 11 17:01:47 ami kernel:  ret_from_fork+0x2b2/0x340
Aug 11 17:01:47 ami kernel:  ? __pfx_kthread+0x10/0x10
Aug 11 17:01:47 ami kernel:  ret_from_fork_asm+0x1a/0x30
Aug 11 17:01:47 ami kernel:  
Aug 11 17:01:47 ami kernel: ---[ end trace 0000000000000000 ]---

Apple is working on a high-end MacBook Pro that could be called the "MacBook Ultra." The device will have several firsts in a Mac, including an OLED display and a touchscreen.


The "Ultra" name isn't a sure thing, because Apple could also continue to call the device the ‌MacBook Pro‌ and make it a high-end model in the Pro lineup. There are rumors of other "Ultra" devices in the works like AirPods and the foldable iPhone, which could be called the iPhone Ultra.

Design

Apple hasn't redesigned the ‌MacBook Pro‌ since the launch of the M1 Pro and M1 Max models in 2021, so the device is due for a new look. The MacBook Ultra could feature some design changes, including a thinner chassis.

Apple could get rid of the notch on the MacBook Ultra, replacing it with an iPhone-style Dynamic Island. A ‌Dynamic Island‌ could better unify the way Siri AI behaves across the iPhone and the Mac with iOS 27 and macOS Golden Gate.

Size Options

The MacBook Ultra will be available in both 14-inch and 16-inch size options.

Display

Apple's upcoming MacBook will be the first with an OLED display. OLED display technology is already used for the iPhone, Apple Watch, and iPad Pro, but it has taken time for larger-sized OLED screens to come down in price.

OLED will be an upgrade over the current mini-LED display technology in most cases, bringing deeper colors and a higher contrast ratio with true blacks. In an OLED display, individual pixels turn off instead of dimming when not activated, so there's less light leakage. OLED displays tend to have better HDR than mini-LED, but sometimes don't match the mini-LED brightness levels.

Along with OLED technology, the MacBook Ultra is expected to have the first touchscreen display on a Mac. Users will be able to use their fingers to interact with the Mac's display, similar to an iPad.

Touchscreen capabilities will be used alongside the trackpad and keyboard, suggesting Apple sees touch as supplementary rather than a primary control method. Apple is rumored to be adapting ‌macOS Golden Gate‌ for touch input.

Apple plans to add a reinforced hinge to the MacBook Ultra's display so that it doesn't wobble when it's tapped.

MacBook Ultra Hints

There are features in ‌macOS Golden Gate‌ that hint at a future touchscreen Mac. Apple added direct touch input to Sidecar so users can tap and interact with macOS elements when using the ‌iPad‌ as a Mac display.

‌macOS Golden Gate‌ supports an iPhone-style pull-to-refresh option, and it can be used across apps like Safari, Mail, News, Podcasts, and Calendar. A pull-to-refresh option makes the most sense on a touch display.

Chips

The current ‌MacBook Pro‌ models are equipped with M5 Pro and M5 Max chips, and Apple plans to use the same chips for the rumored MacBook Ultra.

Apple is planning to introduce the M6 chip as soon as late 2026, but Bloomberg says Apple isn't going to release any other chips in the M6 series. Apple's chip plans have changed in recent months, and the company is now accelerating the launch of the M7 series. The M7 chips feature major neural processing improvements that will meet increasing demand for machines better able to handle AI tasks.

With no M6 Pro or M6 Max planned, Apple will need to use the M5 Pro and M5 Max so it doesn't have to wait for the M7 series before debuting the MacBook Ultra. A second-generation MacBook Ultra will use the M7 Pro and M7 Max chips, with that machine planned for late 2027 or early 2028.

Pricing

Apple's OLED MacBook is expected to be a premium product, with a price tag higher than current ‌MacBook Pro‌ models. Apple raised the prices of all Macs in June 2026, and so the MacBook Ultra will likely be even more expensive than expected. ‌MacBook Pro‌ pricing went up $300.

The higher-end 14-inch ‌MacBook Pro‌ with M5 Pro chip starts at $2,499 after the price increase, while the 16-inch M5 Pro ‌MacBook Pro‌ starts at $2,999. The OLED MacBook will be priced even higher.

Launch Date

Rumors suggest the MacBook Ultra will launch in late 2026 or early 2027, with mass production to start in late 2026. If the MacBook Ultra comes in 2026, it could be released sometime between October and December, but it won't be introduced at Apple's September iPhone event. If the new MacBook launches in 2027, it could come early in the year at Apple's first 2027 event.

Timing is uncertain because of ongoing memory shortages. Apple will need to be able to secure enough memory chips, and that could affect the company's launch plans.
This article, "MacBook Ultra: Everything We Know About Apple's OLED Touchscreen Mac" first appeared on MacRumors.com

Discuss this article in our forums