CVE-2022-49820
Last modified
CVE-2022-49820 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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.. EPSS estimates a 0.14% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 5.18, < 6.0.10 | — |
| Linux | Linux Kernel | 6.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2022-49820?
How severe is CVE-2022-49820?
How do I fix CVE-2022-49820?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2022
- CVE-2022-49815In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49816Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2022-49817In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49818In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49819In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-4982DBLTek GoIP-1 firmware versions up to and including GHSFVT-1…8.7
- CVE-2022-49821In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49822In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49823In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49824In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49825In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49826In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2022-49820?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
