Kernel service interruption via oversized loop offset
Published Jun 18, 2025 · Updated May 11, 2026
Integer overflow in the Linux kernel loop driver allows local users to interrupt service by configuring an oversized loop offset. Directly copying the unsigned loop_info64 lo_offset into the signed loop_device lo_offset lets values above the signed range become negative and trigger a warning in iomap_iter(). Access to a loop device and permission to issue its configuration ioctl are required; the warning affects availability without reported data disclosure or modification.
Summary
What happened
Integer overflow in the Linux kernel loop driver allows local users to interrupt service by configuring an oversized loop offset. Directly copying the unsigned loop_info64 lo_offset into the signed loop_device lo_offset lets values above the signed range become negative and trigger a warning in iomap_iter(). Access to a loop device and permission to issue its configuration ioctl are required; the warning affects availability without reported data disclosure or modification.
The record
- CVE
- CVE-2022-49993
- Published
- Jun 18, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 18, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0455bef69028c65065f16bb04635591b2374249b
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <18e28817cb516b39de6281f6db9b0618b2cc7b42
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6858933131d0dadac071c4d33335a9ea4b8e76cf
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9be7fa7ead18a48940df7b59d993bbc8b9055c15
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a217715338fd48f72114725aa7a40e484a781ca7
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <adf0112d9b8acb03485624220b4934f69bf13369
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b40877b8562c5720d0a7fce20729f56b75a3dede
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c490a0b5a4f36da3918181a8acdc6991d967c5f3
- Affected versionversion=2.6.12
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo