# CVE-2026-55297: CVE-2026-55297

Status: published. Published: 2026-11-10. Updated: 2026-11-11.

In handle_chan_msg of tipc_virtio_dev.c, there is a possible way to bypass memory tag access controls via concurrent shared memory modification due to a race condition. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Google / Android: Android kernel (affected). Source: CNA: Google_Devices

## Severity and prioritization

- CVSS 3.1: 6.4 (medium); CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H; source: ADP: CISA-ADP

- CVSS 3.1: 6.4 (medium); CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H; source: NVD: 134c704f-9b21-4f2e-91b3-4a467353bcc0

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: exploitation none; automatable no; technical impact total; source ADP: CISA-ADP

- Weaknesses: CWE-362

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://source.android.com/docs/security/bulletin/pixel/2026/2026-11-01 (CNA: Google_Devices)

- https://source.android.com/docs/security/bulletin/pixel/2026/2026-11-01 (dsap-vuln-management@google.com)

## Provenance

- CNA: Google_Devices: https://www.cve.org/CVERecord?id=CVE-2026-55297; retrieved 2026-11-11; source updated 2026-11-11

- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-55297; retrieved 2026-11-11; source updated 2026-11-11

Revision: 78776fe7287873c2136e5efd74ac9eb6cf6c8a7e2951a1f01e94589bbb327d99

Canonical: https://y2.dev/cve/CVE-2026-55297

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.