Kernel tag check fault after wake on Mac17 hardware, Google Chrome Helper, macOS 26.5–27.0.1 — related to r.172793638?

We're seeing a recurring kernel panic across six Mac17-family Macs (Mac17,2 / Mac17,4 / Mac17,8; T8142 and T6050) in a managed fleet. 34 panic logs collected 30 Sept – 9 Oct, all with the same signature:

  • panic(cpu N caller ...): Kernel tag check fault (expected tagged address: 0x...028), esr 0x96000011
  • Faulting address is always at offset 0x28 of the object
  • Same crash PC per build: kernel text exec base + 0x48da38 on 27.0/27.0.1, + 0x46a784 on 26.7, + 0x466ee0 on 26.5
  • Panicked task is "Google Chrome Helper" in all 34 cases, thread Chrome_ChildIOThread (Chrome's IPC/network I/O thread)
  • Always 3–60 s after wake from sleep, usually a dark wake with the lid closed (overnight or after a 3–18 min sleep)
  • No third-party kexts loaded; "Post-boot loaded kexts" lists only Apple drivers

Affected builds: 26.5 (25F71), 26.7 (25G229), 27.0 (26A428), 27.0.1 (26A434). Not a regression from one update: a machine still on 26.5 panics identically.

Only Mac17-family hardware is affected. Older Apple silicon Macs with the same software stack are fine.

Present on every affected machine:

  1. Chrome PWAs (Gmail/Chat/Meet) running in the background, keeping Chrome's network service alive across sleep. On one machine Microsoft Edge is the primary browser and never panics; only Chrome Helper does.
  2. Microsoft Defender for Endpoint with its network filter (content filter) extension, MDM-managed.

This looks related to thread 821372, where DTS described a kernel networking panic on M5-family hardware with a Network Extension present (r.172793638 / FB22401652), fixed in 26.5b2. We appear to be seeing a tag-check-fault variant on 26.5 release and later.

Questions:

  • Is this a known issue, and is it the same root cause as r.172793638?
  • Is there a build where it's fixed?
  • Any recommended mitigation beyond preventing sleep and quitting Chrome?

Feedback Assistant: FB25128015 with panic logs and sysdiagnose. Happy to collect more data or test a build.

Backtrace from a 27.0.1 panic (kernel text exec base 0xfffffe003aa54000), panic PC first:

lr: 0xfffffe003aee1a38
lr: 0xfffffe003aeec580
lr: 0xfffffe003b12cf34
lr: 0xfffffe003b12dc50
lr: 0xfffffe003b07b1f8
lr: 0xfffffe003b07c758
lr: 0xfffffe003b237ff4
lr: 0xfffffe003ac787f0
lr: 0xfffffe003aa576ac
lr: 0x000000018747a57c  (userspace)
Answered by DTS Engineer in 909224022
We’re not developing any of it.

OK.

In that case my advice is that you escalate via Apple Support resources. Usually I’d recommend the Apple Support Community, run by Apple Support, but this sounds like it warrants something more drastic.

Our mission here on the Apple Developer Forums is to help developers create products for Apple platforms. We’re not really set up to help folks with issues like this one.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Are you developing any of the software involved in this issue? Or are you seeing this issue when deploying software developed by others?

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Hey. We’re not developing any of it. The software involved is third-party (Google Chrome, Microsoft Defender for Endpoint) deployed on a managed fleet; we’re seeing the panic as users of the affected Macs. Feedback Assistant FB25128015 has all 34 panic logs.

This is hitting almost every M5 Mac we have, daily, and is causing real disruption. If this has already been identified, could you share what’s known and whether there’s a fix or workaround available?

We’re not developing any of it.

OK.

In that case my advice is that you escalate via Apple Support resources. Usually I’d recommend the Apple Support Community, run by Apple Support, but this sounds like it warrants something more drastic.

Our mission here on the Apple Developer Forums is to help developers create products for Apple platforms. We’re not really set up to help folks with issues like this one.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Same signature here on a Mac17,8 (M5 Pro), macOS 26.7.1 (25G241): Kernel tag check fault about 11 s after a dark wake. The panicked task is not Chrome but a VPN client's networking daemon, so this isn't Chrome-specific. Microsoft Defender's network filter is present here too.

Symbolicated against the 25G241 kernelcache.release.Mac17,6_7_8_9 (UUID 66BEBB57-9A4C-2CA5-BBE9-E361E882DC52, matching the panic):

+0x46a784  cfil_acquire_sockbuf+0xfc   ldrb w8, [x21, #0x28]   ; cfil_info->cfi_flags
+0x46a738  cfil_acquire_sockbuf+0xb0   ; return from sleep, wmesg "cfil_acquire_sockbuf"
+0x475254  cfil_sock_is_closed
+0x6a57d8  soclose_locked
+0x6a6524  soclose
+0x5f8708  fp_close_and_unlock
+0x21057c  sleh_synchronous            ; close() syscall

So close() on a TCP socket with a content filter attached reaches cfil_sock_is_closed, which passes so->so_cfil into cfil_acquire_sockbuf. That sleeps waiting for the send sockbuf, dropping the socket lock, then reads cfi_flags from the cfil_info it was handed without revalidating it. The pointer tag (0xfd) no longer matches the memory tag (0xfc), so the cfil_info was freed while the thread slept and MTE caught the use-after-free (bsd/net/content_filter.c). Your 27.0.1 backtrace has the same frame count and near-identical spacing, so it is very likely the same path.

That fits both patterns in your report: only Mac17 hardware panics because MTE is what catches it, and a content filter is a precondition because without one the socket has no cfil state.

Please let me know if submitting an additional FB would increase priority