CVE-2022-49993
BaseFortify
Publication date: 2025-06-18
Last updated on: 2025-11-14
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.0 |
| linux | linux_kernel | 6.0 |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
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 in the Linux kernel involves an integer overflow when configuring a loop device. Specifically, during the configuration process, a 64-bit unsigned offset value (lo_offset) from the userspace structure loop_info64 is copied directly into a signed long long type in the kernel's loop_device structure without proper checks. This can cause an overflow and trigger warnings in kernel functions like iomap_iter(), potentially leading to unexpected behavior or kernel warnings.
How can this vulnerability impact me? :
The overflow can cause kernel warnings and potentially unstable behavior in the loop device handling. While the description does not explicitly mention exploitation or direct security impact, such overflows can lead to denial of service or other unintended kernel behavior if exploited.