LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49972: xsk: Fix corrupted packets for XDP_SHARED_UMEM

In the Linux kernel, the following vulnerability has been resolved: xsk: Fix corrupted packets for XDP_SHARED_UMEM Fix an issue in XDP_SHARED_UMEM mode together with aligned mode where packets are corrupted for the second and any further sockets bound to the same umem. In other words, this does not affect the first socket bound to the umem. The culprit for this bug is that the initialization of the DMA addresses for the pre-populated xsk buffer pool entries was not performed for any socket but the first one bound to the umem. Only the linear array of DMA addresses was populated. Fix this by populating the DMA addresses in the xsk buffer pool for every socket bound to the same umem.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux networking flaw can corrupt packets when multiple AF_XDP sockets share the same memory region in aligned mode. The first socket works correctly; later sockets may process incorrect DMA addresses. This can undermine data integrity and potentially confidentiality or availability, but exposure is limited to systems using this specialized configuration.

Executive priority

Prioritize systems using high-throughput AF_XDP networking with shared UMEM, especially where corrupted traffic could affect sensitive data or critical services. Routine systems not using this configuration are lower priority. Obtain exact fixed package guidance from the relevant Linux distributor because the supplied version information is incomplete.

Technical view

In XDP_SHARED_UMEM aligned mode, DMA addresses for pre-populated XSK buffer-pool entries were initialized only for the first bound socket. Later sockets received only the linear DMA-address array, causing packet corruption. The referenced kernel changes initialize buffer-pool DMA addresses for every socket sharing the UMEM.

Likely exposure

Likely exposure is limited to affected Linux kernels using AF_XDP with XDP_SHARED_UMEM, aligned mode, and multiple sockets bound to one UMEM. The first socket is unaffected. The supplied affected-version data is ambiguous, so kernel or distribution advisories should determine exact version exposure.

Exploitation context

The CVSS vector describes local, low-privileged access with low complexity and no user interaction. The supplied sources provide no evidence of active exploitation, and the CVE is not listed as KEV. Packet corruption may also occur operationally without malicious activity.

Researcher notes

The failure is configuration-specific and tied to per-socket XSK buffer-pool DMA initialization. Assessment should distinguish the first socket from subsequent sockets sharing one UMEM. The two kernel commits are authoritative fix references, but the bundle does not clearly map each commit to kernel branches or fixed release versions.

Mitigation direction

  • Install a vendor-supported kernel containing the referenced stable fix.
  • Confirm the corrected kernel package and reboot requirements with the Linux distributor.
  • Until patched, avoid binding multiple sockets to one aligned-mode UMEM where operationally feasible.
  • Monitor affected workloads for packet corruption, unexpected data, crashes, or service instability.

Validation and detection

  • Inventory hosts running potentially affected Linux kernel versions.
  • Identify AF_XDP workloads using XDP_SHARED_UMEM with aligned buffers.
  • Determine whether multiple sockets bind to the same UMEM.
  • Verify the running kernel includes either referenced stable fix or an equivalent vendor backport.
  • Test packet integrity specifically through second and subsequent sockets after remediation.
Prepared
Confidence
medium
Sources
4

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-49972 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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.

1CVSS vectors
3Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2022-49972Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux94033cd8e73b8632bab7c8b7bb54caa4f5616db7, 94033cd8e73b8632bab7c8b7bb54caa4f5616db7unaffected
LinuxLinux5.16, 0, 5.19.8, 6.0affected
Weakness

CWE details

No CWE listed

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