dbcve.org
FedoraOperating system · Fedoraproject

CVE-2022-33742

HIGH · 7.1 CVSS v3.1 Published 2022-07-05
Fix available
A fix is available. Upgrade to 4.9.322 / 4.14.287 or later.
See remediation →
73/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
Linux disk/nic frontends data leaks T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Linux Block and Network PV device frontends don't zero memory regions before sharing them with the backend (CVE-2022-26365, CVE-2022-33740). Additionally the granularity of the grant table doesn't allow sharing less than a 4K page, leading to unrelated data residing in the same 4K page as data shared with a backend being accessible by such backend (CVE-2022-33741, CVE-2022-33742).

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
How this class of weakness works · CWE-200

The application discloses data — error detail, internal paths, tokens, or other users' records — to someone who shouldn't see it. On its own it can look minor, but it hands attackers the map they need for a larger attack. Remediation is about minimising what's returned and enforcing authorization on every piece of data.

General guidance for the information exposure class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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
FedoraOperating system
Affected:= 35= 36
Debian LinuxOperating system
Affected:= 10.0= 11.0
Linux KernelOperating system
Affected:>= 2.6.13, < 4.9.322>= 4.14, < 4.14.287>= 4.19, < 4.19.251>= 5.4, < 5.4.204>= 5.10, < 5.10.129>= 5.15, < 5.15.53>= 5.18, < 5.18.10= 2.6.12= 5.19
XenOperating system
Affected:all versions

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
High
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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.322 / 4.14.287 / 4.19.251 or later
Fixed in 4.9.3224.14.2874.19.251
Vendor patch www.openwall.com →
Recommended fix High confidence

Linux kernel 4.9.322+, 4.14.287+, 4.19.251+, 5.4.204+, or latest stable kernel (5.10+, 5.15+, 6.1+)

  1. 1. Identify the running Linux kernel version with `uname -r`
  2. 2. For Fedora 35/36 systems: Run `dnf update kernel` to fetch the latest patched kernel
  3. 3. For Debian 10/11 systems: Run `apt-get update && apt-get install linux-image` to get the patched kernel
  4. 4. For other Linux distributions: Update to a kernel version >= 4.9.322 (if using 4.9.x), >= 4.14.287 (if using 4.14.x), >= 4.19.251 (if using 4.19.x), >= 5.4.204 (if using 5.4.x), or preferably a newer stable kernel
  5. 5. Reboot the system to load the patched kernel
  6. 6. Verify the new kernel version is running with `uname -r`
Caveat Kernel updates may require reboot and could have compatibility implications with custom drivers or modules; ensure critical workloads are tested on the new kernel before production deployment

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,250. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-33742 — 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-33742 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