CVE-2026-56923
Analyzed Analyzed - Analysis Complete

Memory Corruption in Linux Kernel TIPC Protocol

Vulnerability report for CVE-2026-56923, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-15

Last updated on: 2026-09-21

Assigner: Google Devices

Description

In handle_unmap_req of tipc_virtio_dev.c, there is a possible memory corruption due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-15
Last Modified
2026-09-21
Generated
2026-10-06
AI Q&A
2026-09-16
EPSS Evaluated
2026-10-04
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
google android *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-362 The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a race condition in the TIPC VirtIO device driver code (tipc_virtio_dev.c). It occurs during the handling of an unmapping request, leading to potential memory corruption. This flaw could allow a local attacker to escalate their privileges on the system without needing additional execution rights or user interaction.

Detection Guidance

This vulnerability involves a race condition in the TIPC virtio device driver (tipc_virtio_dev.c) that could lead to memory corruption and privilege escalation. Detection requires inspecting kernel logs for TIPC-related errors or crashes, particularly during memory unmapping operations. Check for kernel oops messages or segmentation faults linked to tipc_virtio_dev. Use commands like dmesg | grep -i tipc or journalctl -k | grep -i tipc to search for relevant logs. If TIPC is not actively used, consider disabling the module with modprobe -r tipc to prevent potential exploitation.

Impact Analysis

If exploited, this vulnerability could let an attacker gain higher privileges on your system, potentially allowing them to take control of it or access sensitive data. Since it requires local access but no user interaction, systems running affected TIPC VirtIO drivers are at risk.

Compliance Impact

This vulnerability could lead to local privilege escalation, which may result in unauthorized access to sensitive data. This could potentially violate compliance requirements under GDPR (data protection) and HIPAA (health information privacy) if exploited.

Mitigation Strategies

Apply vendor patches or updates for the affected TIPC VirtIO driver component. Monitor official security advisories for updates. Restrict access to vulnerable systems until patched. Review logs for unusual activity related to memory corruption or privilege escalation.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-56923. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart