CVE-2022-50246
What it is
In the Linux kernel, the following vulnerability has been resolved: usb: typec: tcpci: fix of node refcount leak in tcpci_register_port() I got the following report while doing device(mt6370-tcpc) load test with CONFIG_OF_UNITTEST and CONFIG_OF_DYNAMIC enabled: OF: ERROR: memory leak, expected refcount 1 instead of 2, of_node_get()/of_node_put() unbalanced - destroy cset entry: attach overlay node /i2c/pmic@34/tcpc/connector The 'fwnode' set in tcpci_parse_config() which is called in tcpci_register_port(), its node refcount is increased in device_get_named_child_node(). It needs be put while exiting, so call fwnode_handle_put() in the error path of tcpci_register_port() and in tcpci_unregister_port() to avoid leak.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Record status
- Analyzed
Affected
- Linux Kernel < 5.4.229
- Linux Kernel < 5.10.163
- Linux Kernel < 5.15.86
- Linux Kernel < 6.0.16
- Linux Kernel < 6.1.2
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2022-50246.md and follow it. Check whether this project is affected by CVE-2022-50246. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/0384e87e3fec735e47f1c133c796f32ef7a72a9b
- https://git.kernel.org/stable/c/4f257e2eba419ab4cd880c822346450e4e7b2af3
- https://git.kernel.org/stable/c/5f125507d2270035dfcf83fbff6cff5a143e200c
- https://git.kernel.org/stable/c/ba75be6f0d9d028d20852564206565a4c03e3288
- https://git.kernel.org/stable/c/d3b6c28a71f111a6c67ddc3238aab95910fd86cf
- https://git.kernel.org/stable/c/e75a324409715bd71348f79a49aa61b69dbeb676
References
- https://git.kernel.org/stable/c/0384e87e3fec735e47f1c133c796f32ef7a72a9b
- https://git.kernel.org/stable/c/4f257e2eba419ab4cd880c822346450e4e7b2af3
- https://git.kernel.org/stable/c/5f125507d2270035dfcf83fbff6cff5a143e200c
- https://git.kernel.org/stable/c/ba75be6f0d9d028d20852564206565a4c03e3288
- https://git.kernel.org/stable/c/d3b6c28a71f111a6c67ddc3238aab95910fd86cf
- https://git.kernel.org/stable/c/e75a324409715bd71348f79a49aa61b69dbeb676