LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48714: bpf: Use VM_MAP instead of VM_ALLOC for ringbuf

In the Linux kernel, the following vulnerability has been resolved: bpf: Use VM_MAP instead of VM_ALLOC for ringbuf After commit 2fd3fb0be1d1 ("kasan, vmalloc: unpoison VM_ALLOC pages after mapping"), non-VM_ALLOC mappings will be marked as accessible in __get_vm_area_node() when KASAN is enabled. But now the flag for ringbuf area is VM_ALLOC, so KASAN will complain out-of-bound access after vmap() returns. Because the ringbuf area is created by mapping allocated pages, so use VM_MAP instead. After the change, info in /proc/vmallocinfo also changes from [start]-[end] 24576 ringbuf_map_alloc+0x171/0x290 vmalloc user to [start]-[end] 24576 ringbuf_map_alloc+0x171/0x290 vmap user

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

Security readout for executives and security teams

Plain-English summary

CVE-2022-48714 is a Linux kernel BPF ring buffer memory-mapping fix. The public record describes KASAN detecting out-of-bounds access after a mapping change. No CVSS score, CWE, or active exploitation evidence is provided. Business urgency is mainly to confirm kernel maintenance status, especially for systems running affected upstream kernel ranges.

Executive priority

Handle through normal kernel patch governance unless affected systems are high-value, internet-facing infrastructure, or use custom kernels. There is no sourced evidence of active exploitation, but incomplete severity data means teams should not ignore vendor kernel updates.

Technical view

The BPF ringbuf allocation used VM_ALLOC for an area created by mapping allocated pages. After a KASAN/vmalloc change, that flag combination could trigger KASAN out-of-bounds complaints after vmap(). The kernel fix changes the ringbuf area to VM_MAP. Stable kernel commit references are provided by the CVE record.

Likely exposure

Exposure is limited to Linux kernels in the affected upstream ranges listed by the CVE record, including 5.8-era kernels and stable lines before referenced fixes. Distribution backports may change version-based conclusions, so package-level verification is required.

Exploitation context

The provided sources do not report exploitation, public weaponization, or inclusion in CISA KEV. The described issue is tied to kernel BPF ringbuf mapping behavior and KASAN detection, but the public record does not provide a clear attacker impact statement.

Researcher notes

Evidence is sparse. The CVE text focuses on correcting VM_ALLOC versus VM_MAP for BPF ringbuf mappings and KASAN behavior. No CVSS, CWE, exploit status, or detailed impact assessment is present in the supplied public record.

Mitigation direction

  • Update affected Linux kernels to vendor-supported builds containing the referenced stable fixes.
  • Check Linux distribution advisories for backported fixes before relying on upstream version numbers.
  • Prioritize systems using custom, debug, or nonstandard kernels for verification.

Validation and detection

  • Inventory Linux kernel versions across servers, containers hosts, and appliances.
  • Compare installed kernel packages against vendor advisories for CVE-2022-48714.
  • Confirm whether the referenced upstream stable commits are present or backported.
  • Document exceptions where vendor kernels are marked not affected.
Prepared
Confidence
medium
Sources
6

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-48714 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
5Source 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
LinuxLinux457f44363a8894135c85b7a9afd2bd8196db24ab, 457f44363a8894135c85b7a9afd2bd8196db24ab, 457f44363a8894135c85b7a9afd2bd8196db24ab, 457f44363a8894135c85b7a9afd2bd8196db24abunaffected
LinuxLinux5.8, 0, 5.10.99, 5.15.22, 5.16.8, 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.