Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-49993: loop: Check for overflow while configuring loop

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.25% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 0455bef69028c65065f16bb04635591b2374249b, 18e28817cb516b39de6281f6db9b0618b2cc7b42, 6858933131d0dadac071c4d33335a9ea4b8e76cf.

Low priority for now. Upgrade to Linux Linux 0455bef69028c65065f16bb04635591b2374249b, 18e28817cb516b39de6281f6db9b0618b2cc7b42, 6858933131d0dadac071c4d33335a9ea4b8e76cf or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Jun 18, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 16th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2022-49993

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernelbefore 4.9.327
  • linux linux kernel4.10 and later · before 4.14.292
  • linux linux kernel4.15 and later · before 4.19.312
  • linux linux kernel4.20 and later · before 5.4.274
  • linux linux kernel5.5 and later · before 5.10.140
  • linux linux kernel5.11 and later · before 5.15.64
  • linux linux kernel5.16 and later · before 5.19.6
  • linux linux kernel6.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.12affected
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 18e28817cb516b39de6281f6db9b0618b2cc7b42affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before adf0112d9b8acb03485624220b4934f69bf13369affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before a217715338fd48f72114725aa7a40e484a781ca7affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before b40877b8562c5720d0a7fce20729f56b75a3dedeaffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 6858933131d0dadac071c4d33335a9ea4b8e76cfaffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 0455bef69028c65065f16bb04635591b2374249baffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 9be7fa7ead18a48940df7b59d993bbc8b9055c15affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before c490a0b5a4f36da3918181a8acdc6991d967c5f3affected · git
    • before 2.6.12not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.0.2-16.0.2-1
SUSE:Linux Enterprise Live Patching 12 SP5kernel-defaultbefore 4.12.14-122.269.14.12.14-122.269.1
SUSE:Linux Enterprise Live Patching 12 SP5kgraft-patch-SLE12-SP5_Update_71before 1-8.3.11-8.3.1
SUSE:Linux Enterprise Server 12 SP5-LTSSkernel-sourcebefore 4.12.14-122.269.14.12.14-122.269.1
SUSE:Linux Enterprise Server 12 SP5-LTSSkernel-symsbefore 4.12.14-122.269.14.12.14-122.269.1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2022-49991Jun 18, 2025 · mm/hugetlb: avoid corrupting page->mapping in hugetlb_mcopy_atomic_pte
    22Monitor
  • ← EarlierCVE-2022-49992Jun 18, 2025 · mm/mprotect: only reference swap pfn page if type match
    22Monitor
  • Later →CVE-2022-49994Jun 18, 2025 · bootmem: remove the vmemmap pages from kmemleak in put_page_bootmem
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0455bef69028c65065f16bb04635591b2374249bVendor (CNA)
Linux Linux18e28817cb516b39de6281f6db9b0618b2cc7b42Vendor (CNA)
Linux Linux6858933131d0dadac071c4d33335a9ea4b8e76cfVendor (CNA)
Linux Linux9be7fa7ead18a48940df7b59d993bbc8b9055c15Vendor (CNA)
Linux Linuxa217715338fd48f72114725aa7a40e484a781ca7Vendor (CNA)
Linux Linuxadf0112d9b8acb03485624220b4934f69bf13369Vendor (CNA)
Linux Linuxb40877b8562c5720d0a7fce20729f56b75a3dedeVendor (CNA)
Linux Linuxc490a0b5a4f36da3918181a8acdc6991d967c5f3Vendor (CNA)
debian:linux6.0.2-1 · Debian:12Package registry (OSV)
suse:kernel-default4.12.14-122.269.1 · SUSE:Linux Enterprise Live Patching 12 SP5Package registry (OSV)
suse:kernel-source4.12.14-122.269.1 · SUSE:Linux Enterprise Server 12 SP5-LTSSPackage registry (OSV)
suse:kernel-syms4.12.14-122.269.1 · SUSE:Linux Enterprise Server 12 SP5-LTSSPackage registry (OSV)
suse:kgraft-patch-SLE12-SP5_Update_711-8.3.1 · SUSE:Linux Enterprise Live Patching 12 SP5Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records