dbcve.org
Enterprise LinuxOperating system · Redhat

CVE-2022-40982

MEDIUM · 6.5 CVSS v3.1 Published 2023-08-11
Fix available
A fix is available. Upgrade to 20230808 or later.
See remediation →
67/100
Remediation priority · Elevated
Public exploit Zero-click

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
Information exposure through microarchitectural state after transient execution in certain vector execution units for some Intel(R) Processors may allow an authenticated user to potentially enable information disclosure via local access.

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
Enterprise LinuxOperating system
Affected:= 6.0= 7.0= 8.0= 9.0
Debian LinuxOperating system
Affected:= 10.0= 11.0= 12.0
XenOperating system
Affected:all versions
MicrocodeOperating system
Affected:< 20230808
Xeon E 2314 FirmwareOperating system
Affected:all versions
Xeon E 2324g FirmwareOperating system
Affected:all versions
Xeon E 2334 FirmwareOperating system
Affected:all versions
Xeon E 2374g FirmwareOperating 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
Changed
Confidentiality
High
Integrity
None
Availability
None

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

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 20230808 or later
Fixed in 20230808
Recommended fix High confidence

CPU microcode version >= 20230808 (intel-microcode package), Xen hypervisor with Downfall mitigation

  1. Check current microcode version: on Linux, run 'dmesg | grep microcode' or 'cat /proc/cpuinfo' for CPU details
  2. For Enterprise Linux (RHEL/CentOS): Update microcode via 'yum update microcode_ctl' or 'dnf update microcode_ctl', then reboot the system
  3. For Debian Linux: Update via 'apt update && apt install intel-microcode' or 'apt upgrade', then reboot
  4. For Xen hypervisor: Ensure hypervisor is updated to version with fixed microcode, may require host system update and VM restart
  5. Verify microcode version is >= 20230808 after update: 'dmesg | grep microcode' should show version 20230808 or later
  6. For cloud environments (AWS, etc.): Stop and restart instance to ensure new host hypervisor/microcode is loaded
Caveat Reboot required to load updated microcode; cloud instances must be stopped and restarted; potential for rare compatibility issues with very old CPU models

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-40982 — 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-40982 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