It is more likely a severe communication issue happened. A related fix was committed by Google on June 15th [0] and was apparently assigned CVE-2026-58882. GrapheneOS [1] was able to ship the fix through the security preview channel as early as July, but it will otherwise be in the upcoming November security bulletin.
[0] https://android.googlesource.com/platform/frameworks/opt/tel...
[1] https://x.com/GrapheneOS/status/2115848460578762757