Linux Kernel up to 6.0.9 mISDN put_device initialization

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.4$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as problematic, was found in Linux Kernel up to 6.0.9. Impacted is the function put_device of the component mISDN. Such manipulation leads to initialization. This vulnerability is listed as CVE-2022-49818. There is no available exploit. You should upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in Linux Kernel up to 6.0.9. Affected by this issue is the function put_device of the component mISDN. The manipulation with an unknown input leads to a initialization vulnerability. Using CWE to declare the problem leads to CWE-665. The product does not initialize or incorrectly initializes a resource, which might leave the resource in an unexpected state when it is accessed or used. The impact remains unknown. CVE summarizes:

In the Linux kernel, the following vulnerability has been resolved: mISDN: fix misuse of put_device() in mISDN_register_device() We should not release reference by put_device() before calling device_initialize().

The advisory is available at git.kernel.org. This vulnerability is handled as CVE-2022-49818 since 05/01/2025. Technical details are known, but there is no available exploit.

Upgrading to version 4.9.334, 4.14.300, 4.19.267, 5.4.225, 5.10.156, 5.15.80 or 6.0.10 eliminates this vulnerability. Applying the patch 44658d65f6b3118f595a1229d7eed74845a5e2ac/81db4f182744acd004f17d7cc52dde9ea53467e6/d40b35a7922f4df3767ad6fb8ef3dc86e31d7ba3/83672c1b83d107b0d4fe0accf1bf64d8988398e6/709aa1f73d3e9e9ea16e2c4e44f2874c5d2c382c/596230471da3415e92ae6b9d2a4e26f4a81cac5a/87b336aa158201dc30a318431e63e8c5b26c4156/2d25107e111a85c56f601a5470f1780ec054e6ac is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.4

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Initialization
CWE: CWE-665
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Kernel 4.9.334/4.14.300/4.19.267/5.4.225/5.10.156/5.15.80/6.0.10
Patch: 44658d65f6b3118f595a1229d7eed74845a5e2ac/81db4f182744acd004f17d7cc52dde9ea53467e6/d40b35a7922f4df3767ad6fb8ef3dc86e31d7ba3/83672c1b83d107b0d4fe0accf1bf64d8988398e6/709aa1f73d3e9e9ea16e2c4e44f2874c5d2c382c/596230471da3415e92ae6b9d2a4e26f4a81cac5a/87b336aa158201dc30a318431e63e8c5b26c4156/2d25107e111a85c56f601a5470f1780ec054e6ac

Timelineinfo

05/01/2025 🔍
05/01/2025 +0 days 🔍
05/01/2025 +0 days 🔍
11/10/2025 +193 days 🔍

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2022-49818 (🔍)
GCVE (CVE): GCVE-0-2022-49818
GCVE (VulDB): GCVE-100-306938

Entryinfo

Created: 05/01/2025 17:26
Updated: 11/10/2025 23:28
Changes: 05/01/2025 17:26 (58), 11/10/2025 23:28 (11)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you know our Splunk app?

Download it now for free!