Linux Kernel up to 5.10.162/5.15.85/6.0.15/6.1.1 drivers/base/driver.c vimc_init assertion

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.
4.9$0-$5k0.00

Summaryinfo

A vulnerability has been found in Linux Kernel up to 5.10.162/5.15.85/6.0.15/6.1.1 and classified as critical. Affected by this issue is the function vimc_init of the file drivers/base/driver.c. This manipulation causes an unknown weakness. This vulnerability appears as CVE-2022-50340. There is no available exploit. The affected component should be upgraded.

Detailsinfo

A vulnerability classified as critical was found in Linux Kernel up to 5.10.162/5.15.85/6.0.15/6.1.1. Affected by this vulnerability is the function vimc_init of the file drivers/base/driver.c. The CWE definition for the vulnerability is CWE-617. The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary. The impact remains unknown. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: media: vimc: Fix wrong function called when vimc_init() fails In vimc_init(), when platform_driver_register(&vimc_pdrv) fails, platform_driver_unregister(&vimc_pdrv) is wrongly called rather than platform_device_unregister(&vimc_pdev), which causes kernel warning: Unexpected driver unregister! WARNING: CPU: 1 PID: 14517 at drivers/base/driver.c:270 driver_unregister+0x8f/0xb0 RIP: 0010:driver_unregister+0x8f/0xb0 Call Trace: <TASK> vimc_init+0x7d/0x1000 [vimc] do_one_initcall+0xd0/0x4e0 do_init_module+0x1cf/0x6b0 load_module+0x65c2/0x7820

It is possible to read the advisory at git.kernel.org. This vulnerability is known as CVE-2022-50340 since 09/16/2025. The exploitation appears to be difficult. Technical details of the vulnerability are known, but there is no available exploit.

The vulnerability scanner Nessus provides a plugin with the ID 265659 (Linux Distros Unpatched Vulnerability : CVE-2022-50340), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 5.10.163, 5.15.86, 6.0.16 or 6.1.2 eliminates this vulnerability. Applying the patch 14d85b600bb1f6f8ef61fa8fc1907e2e623d8350/9c9ff35d68691aaea85b2e93763772e23930b3a3/681ac2902039d9b497b3ae18fdc204314979e61e/f38df8984ef1b45ba23888d0e232cc21a95bd04b/f74d3f326d1d5b8951ce263c59a121ecfa65e7c0 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.

The vulnerability is also documented in the databases at Tenable (265659) and CERT Bund (WID-SEC-2025-2077). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Affected

  • Debian Linux
  • Amazon Linux 2
  • Red Hat Enterprise Linux
  • Ubuntu Linux
  • SUSE Linux
  • Oracle Linux
  • IBM QRadar SIEM
  • SUSE openSUSE
  • Open Source Linux Kernel
  • RESF Rocky Linux
  • Dell Secure Connect Gateway
  • Dell NetWorker

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.0
VulDB Meta Temp Score: 4.9

VulDB Base Score: 4.6
VulDB Temp Score: 4.4
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: Assertion
CWE: CWE-617
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

Nessus ID: 265659
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2022-50340

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.163/5.15.86/6.0.16/6.1.2
Patch: 14d85b600bb1f6f8ef61fa8fc1907e2e623d8350/9c9ff35d68691aaea85b2e93763772e23930b3a3/681ac2902039d9b497b3ae18fdc204314979e61e/f38df8984ef1b45ba23888d0e232cc21a95bd04b/f74d3f326d1d5b8951ce263c59a121ecfa65e7c0

Timelineinfo

09/16/2025 Advisory disclosed
09/16/2025 +0 days CVE reserved
09/16/2025 +0 days VulDB entry created
02/23/2026 +160 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2022-50340 (🔒)
GCVE (CVE): GCVE-0-2022-50340
GCVE (VulDB): GCVE-100-324523
CERT Bund: WID-SEC-2025-2077 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 09/16/2025 20:37
Updated: 02/23/2026 10:49
Changes: 09/16/2025 20:37 (58), 09/21/2025 05:16 (2), 10/20/2025 23:52 (7), 12/01/2025 23:50 (13), 12/27/2025 07:41 (1), 02/23/2026 10:49 (1)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Interested in the pricing of exploits?

See the underground prices here!