mctp i2c: don't count unused / invalid keys for flow release
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s MCTP I2C flow-release logic can count a release without a matching I2C lock operation if a flow expires before its first packet is sent. This can trigger a release-count overflow warning; the input does not specify whether an attacker can trigger it or what access would be required.
Engineers running Linux kernels with MCTP I2C support should check their deployments; affected versions are not specified.