CVE Tools

CVE-2022-49044

dm integrity: fix memory corruption when tag_size is less than digest size

No known exploitation. EPSS puts it in the 21st percentile. Fixed versions are out.

Check it yourself

OpenVAS · 14 checks

e.g. OID 1.3.6.1.4.1.25623.1.1.11.2022.5249

Run the check

Published Updated Sources: CVE.org, NVD, BDU

What to do

Find your product and version, then upgrade to the build on the right.

  • LinuxAffected: ≥ a3fcf7253139609bf9ff901fbf955fba047e75dd, < 6a95d91c0b315c965198f6ab7dec7c94129e17e0Upgrade to: 6a95d91c0b315c965198f6ab7dec7c94129e17e0Affected: ≥ a3fcf7253139609bf9ff901fbf955fba047e75dd, < 7f84c937222944c03f4615ca4742df6bed0e5adfUpgrade to: 7f84c937222944c03f4615ca4742df6bed0e5adfAffected: ≥ a3fcf7253139609bf9ff901fbf955fba047e75dd, < cd02b2687d66f0a8e716384de4b9a0671331f1dcUpgrade to: cd02b2687d66f0a8e716384de4b9a0671331f1dcAffected: ≥ a3fcf7253139609bf9ff901fbf955fba047e75dd, < 6b4bf97587ef6c1927a78934b700204920655123Upgrade to: 6b4bf97587ef6c1927a78934b700204920655123 + 2 more branchesStated by: CVE record
  • Canonical Ltd. UbuntuAffected: 16.04 LTSUpgrade to: not statedStated by: BDU
  • Red Hat Inc. Red Hat Enterprise LinuxAffected: 8Upgrade to: not statedStated by: BDU
  • Red Hat Inc. Red Hat VirtualizationAffected: 4 for RHEL 8Upgrade to: not statedStated by: BDU
  • Сообщество свободного программного обеспечения Debian GNU/LinuxAffected: 11Upgrade to: not statedStated by: BDU

Versions as the sources state them. 1 more product has version data. Full version matrix after sign-in

What it is

From the CVE record

In the Linux kernel, the following vulnerability has been resolved: dm integrity: fix memory corruption when tag_size is less than digest size It is possible to set up dm-integrity in such a way that the "tag_size" parameter is less than the actual digest size. In this situation, a part of the digest beyond tag_size is ignored. In this case, dm-integrity would write beyond the end of the ic->recalc_tags array and corrupt memory. The corruption happened in integrity_recalc->integrity_sector_checksum->crypto_shash_final. Fix this corruption by increasing the tags array so that it has enough padding at the end to accomodate the loop in integrity_recalc() being able to write a full digest size for the last member of the tags array.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS21st
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.3% chance of exploitation activity in the next 30 days, which ranks it in the 21st percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

8 events over 533 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. OpenVAS check added
  3. Patch availablerecord updated
  4. Publishedweakness classified, att&ck mapped

Affected products

Technical detail

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

Scored 7.8 by NVD.

How it is reached

  • Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required LowRequires basic user-level privileges
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Red Hat Enterprise Linux, not every advisory.