CVE-2022-48757: net: fix information leakage in /proc/net/ptype
In the Linux kernel, the following vulnerability has been resolved:
net: fix information leakage in /proc/net/ptype
In one net namespace, after creating a packet socket without binding it to a device, users in other net namespaces can observe the new packettype added by this packet socket by reading /proc/net/ptype file. This is minor information leakage as packet socket is namespace aware.
Add a net pointer in packettype to keep the net namespace of of corresponding packet socket. In ptypeseqshow, this net pointer must be checked when it is not NULL.
Other sources
In the Linux kernel, the following vulnerability has been resolved:
net: fix information leakage in /proc/net/ptype
The Linux kernel CVE team has assigned CVE-2022-48757 to this issue.
Upstream advisory: https://lore.kernel.org/linux-cve-announce/2024062007-CVE-2022-48757-c816@gregkh/T
— Red Hat
Linux Kernel could allow a remote authenticated attacker to obtain sensitive information, caused by incorrect default permissions in netdevice.h. By sending a specially crafted request, a remote attacker could exploit this vulnerability to obtain sensitive information and use this information to launch further attacks against the affected system.
— IBM
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2022-48757?
CVE-2022-48757 is classified as a low severity vulnerability due to information leakage in net namespaces.
How do I fix CVE-2022-48757?
To mitigate CVE-2022-48757, you should update to the latest kernel versions specified such as 4.4.302, 4.9.300, 4.14.265, 4.19.228, 5.4.176, 5.10.96, 5.15.19, 5.16.5, or 5.17.
What systems are affected by CVE-2022-48757?
CVE-2022-48757 affects specific versions of the Linux kernel in various distributions, including Red Hat versions listed in the vulnerability details.
What impact does CVE-2022-48757 have on system security?
The impact of CVE-2022-48757 allows users in one net namespace to observe packet types from another net namespace, potentially leading to unintended information disclosure.
Is there a known exploit for CVE-2022-48757?
As of now, there are no publicly known exploits specifically targeting CVE-2022-48757.