Access of Resource Using Incompatible Type ('Type Confusion') Affecting kernel-libbpf-static package, versions <0:6.1.19-30.43.amzn2023


Severity

Recommended
high

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.05% (19th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Access of Resource Using Incompatible Type ('Type Confusion') vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-AMZN2023-KERNELLIBBPFSTATIC-5960994
  • published12 Oct 2023
  • disclosed27 Mar 2023

Introduced: 27 Mar 2023

CVE-2023-1076  (opens in a new tab)
CWE-843  (opens in a new tab)
First added by Snyk

How to fix?

Upgrade Amazon-Linux:2023 kernel-libbpf-static to version 0:6.1.19-30.43.amzn2023 or higher.
This issue was patched in ALAS2023-2023-138.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-libbpf-static package and not the kernel-libbpf-static package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2023 relevant fixed versions and status.

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.

CVSS Scores

version 3.1