LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48966: net: mvneta: Prevent out of bounds read in mvneta_config_rss()

In the Linux kernel, the following vulnerability has been resolved: net: mvneta: Prevent out of bounds read in mvneta_config_rss() The pp->indir[0] value comes from the user. It is passed to: if (cpu_online(pp->rxq_def)) inside the mvneta_percpu_elect() function. It needs bounds checkeding to ensure that it is not beyond the end of the cpu bitmap.

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel bug in the mvneta network driver. A user-supplied RSS configuration value could be used without proper bounds checking, causing an out-of-bounds read against the CPU bitmap. Business risk is currently hard to rank because the sources provide no CVSS score, exploit evidence, or impact details beyond the memory safety issue.

Executive priority

Set priority after asset scoping. This should not outrank actively exploited vulnerabilities based on current evidence, but it should be remediated during kernel maintenance for systems using the affected driver.

Technical view

mvneta_config_rss() accepted pp->indir[0] from user input and later passed the derived rxq_def value into cpu_online() through mvneta_percpu_elect(). The fix adds bounds checking so the value cannot address beyond the CPU bitmap. The CVE record lists Linux kernel affected versions and multiple stable kernel fix commits.

Likely exposure

Exposure is most likely limited to Linux systems running affected kernels with the mvneta driver in use. The provided sources do not establish remote exploitability, required privileges, default reachability, or affected distributions. Treat embedded, appliance, and infrastructure Linux builds using this network driver as the primary inventory target.

Exploitation context

The CVE is not marked in KEV, and the supplied sources do not claim active exploitation or public exploit availability. The known issue is user-controlled input reaching a kernel CPU bitmap check without sufficient bounds validation. Any stronger exploitation claim would exceed the provided evidence.

Researcher notes

Key unknowns are impact severity, privilege boundary, distribution-specific affected ranges, and whether the code path is reachable in common configurations. The source description supports an out-of-bounds read in kernel driver logic, but not a confirmed confidentiality, availability, or escalation outcome.

Mitigation direction

  • Update affected Linux kernels to a release containing the referenced stable fixes.
  • Check distribution or appliance vendor advisories for backported kernel fixes.
  • Prioritize systems where the mvneta driver is enabled or required.
  • If patch timing is unclear, ask the vendor for affected-kernel mapping.

Validation and detection

  • Inventory Linux kernel versions across appliances, servers, and embedded deployments.
  • Identify systems where the mvneta driver is present or active.
  • Map deployed kernels to the CVE record and referenced stable commits.
  • Confirm vendor kernels include the bounds-checking fix or a backport.
Prepared
Confidence
medium
Sources
10

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-48966 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
1ADP providers
9Source 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

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxcad5d847a093077b499a8b0bbfe6804b9226c03e, cad5d847a093077b499a8b0bbfe6804b9226c03e, cad5d847a093077b499a8b0bbfe6804b9226c03e, cad5d847a093077b499a8b0bbfe6804b9226c03e, cad5d847a093077b499a8b0bbfe6804b9226c03e, cad5d847a093077b499a8b0bbfe6804b9226c03e, cad5d847a093077b499a8b0bbfe6804b9226c03e, cad5d847a093077b499a8b0bbfe6804b9226c03eunaffected
LinuxLinux4.5, 0, 4.9.336, 4.14.302, 4.19.269, 5.4.227, 5.10.159, 5.15.83, 6.0.13, 6.1affected
Weakness

CWE details

No CWE listed

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