Executive Summary

Informations
Name CVE-2022-49187 First vendor Publication 2025-02-26
Vendor Cve Last vendor Modification 2025-03-14

Security-Database Scoring CVSS v3

Cvss vector : CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Overall CVSS Score 5.5
Base Score 5.5 Environmental Score 5.5
impact SubScore 3.6 Temporal Score 5.5
Exploitabality Sub Score 1.8
 
Attack Vector Local Attack Complexity Low
Privileges Required Low User Interaction None
Scope Unchanged Confidentiality Impact None
Integrity Impact None Availability Impact High
Calculate full CVSS 3.0 Vectors scores

Security-Database Scoring CVSS v2

Cvss vector :
Cvss Base Score N/A Attack Range N/A
Cvss Impact Score N/A Attack Complexity N/A
Cvss Expoit Score N/A Authentication N/A
Calculate full CVSS 2.0 Vectors scores

Detail

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.

Original Source

Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-49187

CWE : Common Weakness Enumeration

% Id Name
100 % CWE-476 NULL Pointer Dereference

CPE : Common Platform Enumeration

TypeDescriptionCount
Application 7
Os 3527

Sources (Detail)

https://git.kernel.org/stable/c/0c1b56df451716ba207bbf59f303473643eee4fd
https://git.kernel.org/stable/c/23f89fe005b105f0dcc55034c13eb89f9b570fac
https://git.kernel.org/stable/c/4be3e4c05d8dd1b83b75652cad88c9e752ec7054
https://git.kernel.org/stable/c/d183f20cf5a7b546d4108e796b98210ceb317579
Source Url

Alert History

If you want to see full details history, please login or register.
0
1
2
3
4
5
6
7
8
9
10
Date Informations
2025-06-26 02:09:20
  • Multiple Updates
2025-06-25 12:22:11
  • Multiple Updates
2025-06-24 02:13:56
  • Multiple Updates
2025-05-27 02:09:31
  • Multiple Updates
2025-03-29 03:14:22
  • Multiple Updates
2025-03-28 13:34:44
  • Multiple Updates
2025-03-28 02:56:49
  • Multiple Updates
2025-03-19 00:21:24
  • Multiple Updates
2025-03-18 00:21:13
  • Multiple Updates
2025-03-15 00:20:56
  • Multiple Updates
2025-02-26 17:20:33
  • First insertion