LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49952: misc: fastrpc: fix memory corruption on probe

In the Linux kernel, the following vulnerability has been resolved: misc: fastrpc: fix memory corruption on probe Add the missing sanity check on the probed-session count to avoid corrupting memory beyond the fixed-size slab-allocated session array when there are more than FASTRPC_MAX_SESSIONS sessions defined in the devicetree.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can corrupt kernel memory during FastRPC driver probing if a device tree defines too many sessions. It appears most relevant to systems using Qualcomm-style FastRPC hardware descriptions. Public sources do not provide a CVSS score, impact rating, or evidence of exploitation.

Executive priority

Treat as targeted platform hygiene unless you operate affected Linux devices with custom firmware or device trees. Prioritize patch validation for embedded, Android-derived, or Qualcomm-based Linux fleets where FastRPC is present.

Technical view

The FastRPC driver lacked a bounds check for the probed session count before writing into a fixed-size slab-allocated session array. If the device tree defines more than FASTRPC_MAX_SESSIONS sessions, probe-time memory corruption can occur. Kernel stable commits add the missing sanity check.

Likely exposure

Exposure is likely limited to Linux kernels with the FastRPC driver enabled and device tree data that can exceed the session limit. The source bundle lists Linux kernel versions and stable commits, but the affected-version details are not fully clear.

Exploitation context

CISA KEV is false in the bundle, and no cited source claims active exploitation. The available description points to malformed or excessive device tree session definitions, not a remote network attack path.

Researcher notes

The public record lacks CVSS, CWE, and detailed exploitability analysis. The key condition is probe-time memory corruption from exceeding FASTRPC_MAX_SESSIONS in device tree-defined sessions. Avoid assuming remote exploitability without platform-specific evidence.

Mitigation direction

  • Update to a vendor kernel containing the referenced FastRPC sanity-check commits.
  • Check Linux distribution, device vendor, or SoC vendor advisories for exact fixed builds.
  • Prioritize systems using FastRPC-capable hardware or custom device trees.
  • Limit untrusted changes to boot images, firmware, and device tree blobs.

Validation and detection

  • Inventory Linux kernel versions and whether the FastRPC driver is built or loaded.
  • Compare deployed kernel sources or packages against the referenced stable commits.
  • Review device tree sources for FastRPC session counts exceeding documented limits.
  • Confirm vendor advisories for affected and fixed versions in your platform.
Prepared
Confidence
medium
Sources
7

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-49952 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
0ADP providers
6Source links

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
LinuxLinuxf6f9279f2bf0e37e2f1fb119d8832b8568536a04, f6f9279f2bf0e37e2f1fb119d8832b8568536a04, f6f9279f2bf0e37e2f1fb119d8832b8568536a04, f6f9279f2bf0e37e2f1fb119d8832b8568536a04, f6f9279f2bf0e37e2f1fb119d8832b8568536a04unaffected
LinuxLinux5.1, 0, 5.4.213, 5.10.142, 5.15.66, 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.