CVE-2022-50299
BaseFortify
Publication date: 2025-09-15
Last updated on: 2025-12-04
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 4.10 (inc) to 4.14.296 (exc) |
| linux | linux_kernel | From 4.15 (inc) to 4.19.262 (exc) |
| linux | linux_kernel | From 4.20 (inc) to 5.4.220 (exc) |
| linux | linux_kernel | From 5.5 (inc) to 5.10.150 (exc) |
| linux | linux_kernel | From 5.11 (inc) to 5.15.75 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 5.19.17 (exc) |
| linux | linux_kernel | From 6.0 (inc) to 6.0.3 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-NVD-CWE-noinfo |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs in the Linux kernel's md (multiple device) component where the use of snprintf() can cause a warning or error when the total length of block device names plus slashes exceeds 200 characters. snprintf() returns the number of characters that would have been written, which can cause an integer wraparound in the expression "200 - len" leading to unexpected behavior. The fix replaces snprintf() with scnprintf(), which returns the actual number of characters written, preventing this wraparound and the associated warning.
How can this vulnerability impact me? :
This vulnerability can cause warnings or errors in the Linux kernel when handling device names longer than expected, potentially leading to instability or unexpected behavior in the md subsystem. This could affect system reliability or cause issues in managing RAID devices, but it does not directly indicate a security breach or data compromise.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring system logs for specific kernel warnings related to snprintf usage in the md (multiple device) subsystem. Look for kernel log messages similar to the warning shown in the description, such as messages containing 'WARNING: CPU' and references to vsnprintf or snprintf in the mdadm context. You can use commands like 'dmesg | grep -i snprintf' or 'journalctl -k | grep -i snprintf' to search for these warnings in kernel logs.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where this issue is fixed, specifically where snprintf calls in the md subsystem are replaced with scnprintf to prevent buffer overflow warnings. Until an update is applied, monitor system logs for the warning and avoid configurations that cause the total characters in block device names plus slashes to exceed 200, which triggers the issue.