CVE-2022-49820

Source
https://nvd.nist.gov/vuln/detail/CVE-2022-49820
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-49820.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2022-49820
Related
Published
2025-05-01T15:16:05Z
Modified
2025-05-02T13:53:20Z
Summary
[none]
Details

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 WARNON in mctpi2cflowrelease:

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, devflowstate 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.

References

Affected packages

Debian:12 / linux

Package

Name
linux
Purl
pkg:deb/debian/linux?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
6.0.10-1

Ecosystem specific

{
    "urgency": "not yet assigned"
}

Debian:13 / linux

Package

Name
linux
Purl
pkg:deb/debian/linux?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
6.0.10-1

Ecosystem specific

{
    "urgency": "not yet assigned"
}