Cross-namespace packet-socket disclosure via unfiltered proc output
Published Jun 20, 2024 · Updated May 11, 2026
Information disclosure in the Linux kernel allows local users to observe packet-socket registrations across network namespaces. The ptype_seq_show function renders packet_type entries in /proc/net/ptype without filtering them by their owning network namespace. A local user who can read the proc file can learn that another namespace created an unbound packet socket, but the disclosed entry does not expose packet contents.
Summary
What happened
Information disclosure in the Linux kernel allows local users to observe packet-socket registrations across network namespaces. The ptype_seq_show function renders packet_type entries in /proc/net/ptype without filtering them by their owning network namespace. A local user who can read the proc file can learn that another namespace created an unbound packet socket, but the disclosed entry does not expose packet contents.
The record
- CVE
- CVE-2022-48757
- Published
- Jun 20, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-668, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 20, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.6.26
- Affected versionversion=2feb27dbe00cbb4f7d31f90acf6bd0d751dd0a50 <47934e06b65637c88a762d9c98329ae6e3238888
- Affected versionversion=2feb27dbe00cbb4f7d31f90acf6bd0d751dd0a50 <839ec7039513a4f84bfbaff953a9393471176bee
- Affected versionversion=2feb27dbe00cbb4f7d31f90acf6bd0d751dd0a50 <8f88c78d24f6f346919007cd459fd7e51a8c7779
- Affected versionversion=2feb27dbe00cbb4f7d31f90acf6bd0d751dd0a50 <b67ad6170c0ea87391bb253f35d1f78857736e54
- Affected versionversion=2feb27dbe00cbb4f7d31f90acf6bd0d751dd0a50 <be1ca30331c7923c6f376610c1bd6059be9b1908
- Affected versionversion=2feb27dbe00cbb4f7d31f90acf6bd0d751dd0a50 <c38023032a598ec6263e008d62c7f02def72d5c7
- Affected versionversion=2feb27dbe00cbb4f7d31f90acf6bd0d751dd0a50 <db044d97460ea792110eb8b971e82569ded536c6
- Affected versionversion=2feb27dbe00cbb4f7d31f90acf6bd0d751dd0a50 <e372ecd455b6ebc7720f52bf4b5f5d44d02f2092
- Affected versionversion=2feb27dbe00cbb4f7d31f90acf6bd0d751dd0a50 <e43669c77cb3a742b7d84ecdc7c68c4167a7709b
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo