LiveActive security incident?Get immediate response
CVE Record

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 `packet_type` 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 `packet_type` to keep the net namespace of of corresponding packet socket. In `ptype_seq_show`, this net pointer must be checked when it is not NULL.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue leaks minor networking metadata between network namespaces. A local user in one namespace may observe packet socket registration details created in another namespace through /proc/net/ptype. The source describes it as minor information leakage, not code execution or privilege escalation.

Executive priority

Treat this as a low-severity isolation hygiene issue. It matters most for shared Linux platforms and container hosts, but the available evidence does not support emergency action. Fold remediation into normal kernel patch cycles unless tenant isolation risk is unusually high.

Technical view

The kernel packet socket path added packet_type entries without retaining the owning network namespace. ptype_seq_show could expose those entries to readers in other namespaces via /proc/net/ptype. The fix adds a net namespace pointer to packet_type and checks it during display.

Likely exposure

Exposure is most relevant on Linux systems using network namespaces, containers, or multi-tenant local workloads where untrusted users can read /proc/net/ptype. The bundle lists affected Linux versions and stable-branch fixes, but exact distribution package impact depends on vendor backports.

Exploitation context

The provided sources do not show active exploitation, KEV listing, public exploit use, or a CVSS score. Abuse appears to require local read access to /proc/net/ptype and a namespace boundary where packet socket metadata should remain isolated.

Researcher notes

Focus review on net namespace isolation around packet_type visibility in /proc/net/ptype. The key fix behavior is namespace association and filtering in display logic. Evidence is limited to the CVE record and Linux stable commit references; no exploitability analysis is provided.

Mitigation direction

  • Update to a Linux kernel containing the referenced stable fixes.
  • Check your distribution advisory for the exact fixed kernel package.
  • Reduce untrusted local access to container hosts where feasible.
  • Review container namespace and procfs exposure policies.
  • Prioritize routine patching unless local multi-tenant isolation is critical.

Validation and detection

  • Inventory Linux kernel versions across hosts and container platforms.
  • Map running kernels to vendor-fixed packages or referenced stable commits.
  • Confirm whether untrusted users can read /proc/net/ptype.
  • Assess use of network namespaces or packet sockets on exposed systems.
  • Document compensating controls if patching is delayed.
Prepared
Confidence
medium
Sources
11

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-48757 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
10Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux2feb27dbe00cbb4f7d31f90acf6bd0d751dd0a50, 2feb27dbe00cbb4f7d31f90acf6bd0d751dd0a50, 2feb27dbe00cbb4f7d31f90acf6bd0d751dd0a50, 2feb27dbe00cbb4f7d31f90acf6bd0d751dd0a50, 2feb27dbe00cbb4f7d31f90acf6bd0d751dd0a50, 2feb27dbe00cbb4f7d31f90acf6bd0d751dd0a50, 2feb27dbe00cbb4f7d31f90acf6bd0d751dd0a50, 2feb27dbe00cbb4f7d31f90acf6bd0d751dd0a50, 2feb27dbe00cbb4f7d31f90acf6bd0d751dd0a50unaffected
LinuxLinux2.6.26, 0, 4.4.302, 4.9.300, 4.14.265, 4.19.228, 5.4.176, 5.10.96, 5.15.19, 5.16.5, 5.17affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.