A flaw was found in the Linux Kernel. The tun/tap sockets have their socket UID hardcoded to 0 due to a type confusion in their initialization function. While it will be often correct, as tuntap devices require CAP_NET_ADMIN, it may not always be the case, e.g., a non-root user only having that capability. This would make tun/tap sockets being incorrectly treated in filtering/routing decisions, possibly bypassing network filters.
History

Mon, 24 Feb 2025 17:15:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


cve-icon MITRE

Status: PUBLISHED

Assigner: redhat

Published:

Updated: 2025-02-24T17:04:30.565Z

Reserved: 2023-02-27T00:00:00.000Z

Link: CVE-2023-1076

cve-icon Vulnrichment

Updated: 2024-08-02T05:32:46.361Z

cve-icon NVD

Status : Modified

Published: 2023-03-27T21:15:10.423

Modified: 2025-02-24T17:15:12.320

Link: CVE-2023-1076

cve-icon Redhat

Severity : Low

Publid Date: 2023-02-04T00:00:00Z

Links: CVE-2023-1076 - Bugzilla