dbcve.org
Linux KernelOperating system · Linux

CVE-2022-49993

MEDIUM · 5.5 CVSS v3.1 Published 2025-06-18
Fix available
A fix is available. Upgrade to 4.9.327 / 4.14.292 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In the Linux kernel, the following vulnerability has been resolved: loop: Check for overflow while configuring loop The userspace can configure a loop using an ioctl call, wherein a configuration of type loop_config is passed (see lo_ioctl()'s case on line 1550 of drivers/block/loop.c). This proceeds to call loop_configure() which in turn calls loop_set_status_from_info() (see line 1050 of loop.c), passing &config->info which is of type loop_info64*. This function then sets the appropriate values, like the offset. loop_device has lo_offset of type loff_t (see line 52 of loop.c), which is typdef-chained to long long, whereas loop_info64 has lo_offset of type __u64 (see line 56 of include/uapi/linux/loop.h). The function directly copies offset from info to the device as follows (See line 980 of loop.c): lo->lo_offset = info->lo_offset; This results in an overflow, which triggers a warning in iomap_iter() due to a call to iomap_iter_done() which has: WARN_ON_ONCE(iter->iomap.offset > iter->pos); Thus, check for negative value during loop_set_status_from_info(). Bug report: https://syzkaller.appspot.com/bug?id=c620fe14aac810396d3c3edc9ad73848bf69a29e

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:< 4.9.327>= 4.10, < 4.14.292>= 4.15, < 4.19.312>= 4.20, < 5.4.274>= 5.5, < 5.10.140>= 5.11, < 5.15.64>= 5.16, < 5.19.6= 6.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.9.327 / 4.14.292 / 4.19.312 or later
Fixed in 4.9.3274.14.2924.19.312
Vendor patch git.kernel.org →
Recommended fix High confidence

Upgrade to kernel 5.4.274 or later (or the equivalent stable release for your branch: 4.9.327, 4.14.292, or 4.19.312)

  1. 1. Identify the currently running kernel version using `uname -r`
  2. 2. Based on the current kernel version, determine the appropriate upgrade target: For kernel 4.9.x, upgrade to 4.9.327 or later; For kernel 4.10-4.14.x, upgrade to 4.14.292 or later; For kernel 4.15-4.19.x, upgrade to 4.19.312 or later; For kernel 4.20-5.4.x, upgrade to 5.4.274 or later
  3. 3. Update the kernel package using the distribution's package manager (e.g., `apt-get update && apt-get install linux-image` for Debian/Ubuntu, `yum update kernel` for RHEL/CentOS, or `zypper update kernel` for SUSE)
  4. 4. Reboot the system to load the new kernel
  5. 5. Verify the running kernel version with `uname -r` to confirm the fix is applied
Caveat Kernel upgrades may require system reboot and could have compatibility implications with custom modules or specific hardware drivers; test in staging environment first

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-49993 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-49993 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data