Linux Kernel up to 5.10.149/5.15.74/5.19.16/6.0.2 Bluetooth percpu_init_rwsem null pointer dereference

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Linux Kernel up to 5.10.149/5.15.74/5.19.16/6.0.2. Affected by this issue is the function percpu_init_rwsem of the component Bluetooth. Performing a manipulation results in null pointer dereference.
This vulnerability is cataloged as CVE-2022-50374. There is no exploit available.
It is suggested to upgrade the affected component.
Details
A vulnerability was found in Linux Kernel up to 5.10.149/5.15.74/5.19.16/6.0.2. It has been classified as critical. This affects the function percpu_init_rwsem of the component Bluetooth. The manipulation with an unknown input leads to a null pointer dereference vulnerability. CWE is classifying the issue as CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. This is going to have an impact on availability. The summary by CVE is:
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_{ldisc,serdev}: check percpu_init_rwsem() failure syzbot is reporting NULL pointer dereference at hci_uart_tty_close() [1], for rcu_sync_enter() is called without rcu_sync_init() due to hci_uart_tty_open() ignoring percpu_init_rwsem() failure. While we are at it, fix that hci_uart_register_device() ignores percpu_init_rwsem() failure and hci_uart_unregister_device() does not call percpu_free_rwsem().
It is possible to read the advisory at git.kernel.org. This vulnerability is uniquely identified as CVE-2022-50374 since 09/17/2025. Technical details of the vulnerability are known, but there is no available exploit.
The vulnerability scanner Nessus provides a plugin with the ID 265620 (Linux Distros Unpatched Vulnerability : CVE-2022-50374), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 5.10.150, 5.15.75, 5.19.17 or 6.0.3 eliminates this vulnerability. Applying the patch d7cc0d51ffcbfd1caaa809fcf9cff05c46d0fb4d/b8917dce2134739b39bc0a5648b18427f2cad569/75b2c71ea581c7bb1303860d89366a42ad0506d2/98ce10f3f345e61fc6c83bff9cd11cda252b05ac/3124d320c22f3f4388d9ac5c8f37eaad0cefd6b1 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 (265620) and CERT Bund (WID-SEC-2025-2087). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Affected
- Amazon Linux 2
- Red Hat Enterprise Linux
- SUSE Linux
- Oracle Linux
- IBM QRadar SIEM
- Open Source Linux Kernel
- RESF Rocky Linux
- Dell Secure Connect Gateway
Product
Type
Vendor
Name
Version
- 5.10.149
- 5.15.0
- 5.15.1
- 5.15.2
- 5.15.3
- 5.15.4
- 5.15.5
- 5.15.6
- 5.15.7
- 5.15.8
- 5.15.9
- 5.15.10
- 5.15.11
- 5.15.12
- 5.15.13
- 5.15.14
- 5.15.15
- 5.15.16
- 5.15.17
- 5.15.18
- 5.15.19
- 5.15.20
- 5.15.21
- 5.15.22
- 5.15.23
- 5.15.24
- 5.15.25
- 5.15.26
- 5.15.27
- 5.15.28
- 5.15.29
- 5.15.30
- 5.15.31
- 5.15.32
- 5.15.33
- 5.15.34
- 5.15.35
- 5.15.36
- 5.15.37
- 5.15.38
- 5.15.39
- 5.15.40
- 5.15.41
- 5.15.42
- 5.15.43
- 5.15.44
- 5.15.45
- 5.15.46
- 5.15.47
- 5.15.48
- 5.15.49
- 5.15.50
- 5.15.51
- 5.15.52
- 5.15.53
- 5.15.54
- 5.15.55
- 5.15.56
- 5.15.57
- 5.15.58
- 5.15.59
- 5.15.60
- 5.15.61
- 5.15.62
- 5.15.63
- 5.15.64
- 5.15.65
- 5.15.66
- 5.15.67
- 5.15.68
- 5.15.69
- 5.15.70
- 5.15.71
- 5.15.72
- 5.15.73
- 5.15.74
- 5.19.0
- 5.19.1
- 5.19.2
- 5.19.3
- 5.19.4
- 5.19.5
- 5.19.6
- 5.19.7
- 5.19.8
- 5.19.9
- 5.19.10
- 5.19.11
- 5.19.12
- 5.19.13
- 5.19.14
- 5.19.15
- 5.19.16
- 6.0.0
- 6.0.1
- 6.0.2
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.6VulDB Meta Temp Score: 5.5
VulDB Base Score: 5.7
VulDB Temp Score: 5.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Null pointer dereferenceCWE: CWE-476 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 265620
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2022-50374
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 5.10.150/5.15.75/5.19.17/6.0.3
Patch: d7cc0d51ffcbfd1caaa809fcf9cff05c46d0fb4d/b8917dce2134739b39bc0a5648b18427f2cad569/75b2c71ea581c7bb1303860d89366a42ad0506d2/98ce10f3f345e61fc6c83bff9cd11cda252b05ac/3124d320c22f3f4388d9ac5c8f37eaad0cefd6b1
Timeline
09/17/2025 Advisory disclosed09/17/2025 CVE reserved
09/17/2025 VulDB entry created
12/27/2025 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2022-50374 (🔒)
GCVE (CVE): GCVE-0-2022-50374
GCVE (VulDB): GCVE-100-324699
CERT Bund: WID-SEC-2025-2087 - Linux Kernel: Mehrere Schwachstellen
Entry
Created: 09/17/2025 17:41Updated: 12/27/2025 02:41
Changes: 09/17/2025 17:41 (59), 09/21/2025 21:02 (2), 12/11/2025 17:06 (10), 12/27/2025 02:41 (7)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.