Menu

Star on GitHub · 3.4k

CVE-2022-49820

5.5 · MEDIUM

In the Linux kernel, the following vulnerability has been resolved: mctp i2c: don't count unused / invalid keys for flow release We're currently hitting the WARN_ON in mctp_i2c_flow_release:…

Published May 1, 2025EPSS 0.17%

Overview

CVE-2022-49820 is a medium-severity vulnerability. It was published on May 1, 2025 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

mctp i2c: don't count unused / invalid keys for flow release

We're currently hitting the WARN_ON in mctp_i2c_flow_release:

if (midev->release_count > midev->i2c_lock_count) {

WARN_ONCE(1, "release count overflow");

This may be hit if we expire a flow before sending the first packet it

contains - as we will not be pairing the increment of release_count

(performed on flow release) with the i2c lock operation (only

performed on actual TX).

To fix this, only release a flow if we've encountered it previously (ie,

dev_flow_state does not indicate NEW), as we will mark the flow as

ACTIVE at the same time as accounting for the i2c lock operation. We

also need to add an INVALID flow state, to indicate when we've done the

release.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2022-49820?

CVE-2022-49820 is a medium-severity vulnerability. It was published on May 1, 2025 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

How severe is CVE-2022-49820?

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2022-49820?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2022-49820?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2022-49820 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2022

View all
Watch the demo →