Security readout for executives and security teams
Plain-English summary
This is a Linux kernel driver flaw in the ISMT SMBus/I2C path. A local user with access to the relevant I2C interface could trigger an out-of-bounds read, potentially exposing kernel memory or crashing the system. It is high severity, but the supplied evidence does not show remote exploitation or active exploitation.
Executive priority
Patch in the normal high-severity kernel maintenance window, faster for multi-user systems or hosts exposing I2C device access to workloads. There is meaningful confidentiality and availability risk, but no supplied evidence of active exploitation.
Technical view
The ismt_access() function did not validate data->block[0] before using it as a block size during I2C_SMBUS_BLOCK_DATA handling. The supplied KASAN trace shows an out-of-bounds read through memcpy after an i2cdev ioctl path. The fix is described as checking the block size first.
Likely exposure
Exposure is likely limited to Linux systems running affected kernels with the ismt_smbus/I2C path reachable by a local, low-privileged user. Package-level exposure depends on distribution backports, which are not mapped in the supplied sources.
Exploitation context
The CVSS vector is local, low complexity, low privileges, and no user interaction. The source bundle marks KEV as false and provides no cited evidence of active exploitation. Treat this as local privilege-bound kernel exposure, not an internet-facing remote bug.
Researcher notes
The affected-version data in the bundle is not enough to map every distribution package. Focus validation on the ISMT SMBus driver path, i2cdev ioctl reachability, and whether the stable fix for checking data->block[0] is present.
Mitigation direction
- Apply a vendor or distribution kernel update containing the referenced stable fixes.
- Prioritize systems where local users can access I2C device interfaces.
- Restrict unnecessary access to I2C device nodes until patched.
- Confirm kernel vendor guidance for exact fixed package versions.
Validation and detection
- Inventory Linux kernel versions and distribution package build numbers.
- Check whether ismt_smbus and I2C device access are present on affected hosts.
- Verify installed kernels include the relevant stable fix commits or vendor backports.
- Review local user and service access to I2C device interfaces.
Public sources used
- CVE Program
- CVE List V5
- Linux stable commit 4a7bb1d93add
- Linux stable commit 03b7ef7a6c5c
- Linux stable commit bfe41d966c86
- Linux stable commit cdcbae2c5003
- Linux stable commit 9ac541a0898e
- Linux stable commit 96c12fd0ec74
- Linux stable commit a642469d464b
- Linux stable commit 233348a04bec
- Linux stable commit 39244cc75482
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CWE-125: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-50394 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H1.85.2Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.1HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/4a7bb1d93addb2f67e36fed00a53cb7f270d7b7aCVE reference
- https://git.kernel.org/stable/c/03b7ef7a6c5ca1ff553470166b4919db88b810f6CVE reference
- https://git.kernel.org/stable/c/bfe41d966c860a8ad4c735639d616da270c92735CVE reference
- https://git.kernel.org/stable/c/cdcbae2c5003747ddfd14e29db9c1d5d7e7c44ddCVE reference
- https://git.kernel.org/stable/c/9ac541a0898e8ec187a3fa7024b9701cffae6bf2CVE reference
- https://git.kernel.org/stable/c/96c12fd0ec74641295e1c3c34dea3dce1b6c3422CVE reference
- https://git.kernel.org/stable/c/a642469d464b2780a25a49b51ae56623c65eac34CVE reference
- https://git.kernel.org/stable/c/233348a04becf133283f0076e20b317302de21d9CVE reference
- https://git.kernel.org/stable/c/39244cc754829bf707dccd12e2ce37510f5b1f8dCVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.