Bug 2348126 (CVE-2022-49187) - CVE-2022-49187 kernel: clk: Fix clk_hw_get_clk() when dev is NULL
Summary: CVE-2022-49187 kernel: clk: Fix clk_hw_get_clk() when dev is NULL
Keywords:
Status: NEW
Alias: CVE-2022-49187
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-02-26 03:18 UTC by OSIDB Bzimport
Modified: 2025-02-26 15:23 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-02-26 03:18:31 UTC
In the Linux kernel, the following vulnerability has been resolved:

clk: Fix clk_hw_get_clk() when dev is NULL

Any registered clk_core structure can have a NULL pointer in its dev
field. While never actually documented, this is evidenced by the wide
usage of clk_register and clk_hw_register with a NULL device pointer,
and the fact that the core of_clk_hw_register() function also passes a
NULL device pointer.

A call to clk_hw_get_clk() on a clk_hw struct whose clk_core is in that
case will result in a NULL pointer derefence when it calls dev_name() on
that NULL device pointer.

Add a test for this case and use NULL as the dev_id if the device
pointer is NULL.

Comment 1 Avinash Hanwate 2025-02-26 10:49:25 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025022615-CVE-2022-49187-e8b4@gregkh/T

Comment 4 Avinash Hanwate 2025-02-26 15:21:56 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025022615-CVE-2022-49187-e8b4@gregkh/T


Note You need to log in before you can comment on or make changes to this bug.