Bug 2153059 (CVE-2022-3111) - CVE-2022-3111 kernel: wm8350-power: memory leak in free_charger_irq()
Summary: CVE-2022-3111 kernel: wm8350-power: memory leak in free_charger_irq()
Keywords:
Status: CLOSED NOTABUG
Alias: CVE-2022-3111
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 2153051
TreeView+ depends on / blocked
 
Reported: 2022-12-13 22:00 UTC by Sage McTaggart
Modified: 2023-07-11 18:10 UTC (History)
45 users (show)

Fixed In Version: kernel 5.18-rc1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-06-12 19:29:50 UTC
Embargoed:

Attachments (Terms of Use)

Description Sage McTaggart 2022-12-13 22:00:26 UTC 
[Suggested description]
An issue was discovered in the Linux kernel through 5.16-rc6.
free_charger_irq() in drivers/power/supply/wm8350_power.c lacks free of
WM8350_IRQ_CHG_FAST_RDY, which is registered in wm8350_init_charger().

------------------------------------------

[VulnerabilityType Other]
Missing Release of Resource after Effective Lifetime

------------------------------------------

[Vendor of Product]
the development group

------------------------------------------

[Affected Product Code Base]
Linux kernel - 5.16-rc6

------------------------------------------

[Reference]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.19-rc2&id=6dee930f6f6776d1e5a7edf542c6863b47d9f078

------------------------------------------

[Discoverer]
Jiasheng Jiang
Comment 5 Mauro Matteo Cascella 2023-06-12 08:45:17 UTC 
Upstream commit:
https://github.com/torvalds/linux/commit/6dee930f6f6776d1e5a7edf542c6863b47d9f078
Comment 7 Product Security DevOps Team 2023-06-12 19:29:47 UTC 
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):

https://access.redhat.com/security/cve/cve-2022-3111
Note You need to log in before you can comment on or make changes to this bug.