LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48632: i2c: mlxbf: prevent stack overflow in mlxbf_i2c_smbus_start_transaction()

In the Linux kernel, the following vulnerability has been resolved: i2c: mlxbf: prevent stack overflow in mlxbf_i2c_smbus_start_transaction() memcpy() is called in a loop while 'operation->length' upper bound is not checked and 'data_idx' also increments.

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-48632 is a Linux kernel bug in the mlxbf I2C driver. The reported issue is a stack overflow risk caused by copying data in a loop without properly bounding the operation length. Public sources do not provide CVSS, exploitation evidence, or business-impact detail.

Executive priority

Handle through normal kernel vulnerability management unless asset review shows broad mlxbf driver exposure. There is no cited active exploitation or CVSS score in the provided sources, but kernel memory corruption still warrants timely patch validation on relevant systems.

Technical view

The vulnerability is in mlxbf_i2c_smbus_start_transaction(). The CVE description says memcpy() is called in a loop while operation->length lacks an upper-bound check and data_idx increments. Linux stable commit references are provided as the remediation evidence, but the source bundle does not describe exploit prerequisites.

Likely exposure

Exposure is most likely limited to Linux systems running affected kernel versions or backports where the mlxbf I2C driver code is present and reachable. The bundle lists affected Linux versions including 5.10, 5.10.146, 5.15.71, 5.19.12, and 6.0, but packaging impact depends on vendor backports.

Exploitation context

The source bundle does not cite active exploitation, public exploit availability, or inclusion in CISA KEV. Treat exploitation status as unconfirmed. The bug class is memory corruption in kernel driver code, so impact should be assessed against actual driver presence and local hardware/software reachability.

Researcher notes

Evidence is sparse. The public description identifies the flawed bounds handling and linked stable commits, but not attacker position, trigger path, privileges, or confirmed impact. Researchers should focus on affected kernel branches, downstream backports, and whether the mlxbf I2C path is reachable in deployed environments.

Mitigation direction

  • Check Linux vendor advisories for fixed packages or backported patches.
  • Update affected kernels to versions containing the referenced stable fixes.
  • Prioritize systems where the mlxbf I2C driver is enabled or required.
  • If patch timing is constrained, assess whether the driver can be disabled safely.
  • Track vendor kernel backport notes rather than relying only on upstream version numbers.

Validation and detection

  • Inventory running kernel versions across Linux assets.
  • Confirm whether each kernel includes one of the referenced stable fixes.
  • Determine whether the mlxbf I2C driver is built, loaded, or operationally required.
  • Compare distribution package changelogs against CVE-2022-48632.
  • Document any compensating control decisions and patch exceptions.
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-48632 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
LinuxLinuxb5b5b32081cd206baa6e58cca7f112d9723785d6, b5b5b32081cd206baa6e58cca7f112d9723785d6, b5b5b32081cd206baa6e58cca7f112d9723785d6, b5b5b32081cd206baa6e58cca7f112d9723785d6unaffected
LinuxLinux5.10, 0, 5.10.146, 5.15.71, 5.19.12, 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.