dbcve.org
Debian LinuxOperating system · Debian

CVE-2022-41804

MEDIUM · 6.7 CVSS v3.1 Published 2023-08-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
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
Unauthorized error injection in Intel(R) SGX or Intel(R) TDX for some Intel(R) Xeon(R) Processors may allow a privileged user to potentially enable escalation of privilege 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 · moderate confidence

Unauthorized error injection vulnerability in Intel SGX (Software Guard Extensions) or Intel TDX (Trust Domain Extensions) on certain Xeon processors allows a privileged local user to potentially escalate privileges by injecting errors into these hardware security technologies.

MitigationApply Intel firmware/microcode updates for affected Xeon processors when available, or disable SGX/TDX if these security features are not required in the environment.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Debian LinuxOperating system
Affected:= 11.0= 12.0
FedoraOperating system
Affected:= 38
Xeon Gold 5315y FirmwareOperating system
Affected:all versions
Xeon Gold 5317 FirmwareOperating system
Affected:all versions
Xeon Gold 5318n FirmwareOperating system
Affected:all versions
Xeon Gold 5318s FirmwareOperating system
Affected:all versions
Xeon Gold 5318y FirmwareOperating system
Affected:all versions
Xeon Gold 5320 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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the processor model
    Run `lscpu | grep 'Model name'` or `cat /proc/cpuinfo | grep 'model name' | head -1` to see the CPU model
    Affected if The CPU model matches any of these: Intel Xeon Gold 5315Y, 5317, 5318N, 5318S, 5318Y, or 5320
  2. Check if SGX is enabled in the system
    Check /proc/cpuinfo for 'sgx' in the flags section, or run `rdmsr 0x12a 2>/dev/null` to read the SGX capability MSR (value non-zero means SGX is available)
    Affected if SGX is present and enabled (the system supports and has activated SGX)
  3. Check if TDX is enabled in the system
    Check dmesg output for TDX-related messages (`dmesg | grep -i tdx`), or look for 'tdx' in /proc/cpuinfo flags
    Affected if TDX is present and enabled (the system supports and has activated TDX)
  4. Verify firmware version (if accessible)
    Check system firmware/bios version via `dmidecode -s bios-version` or through vendor-specific tools, though firmware version info for Xeon processors may require out-of-band management access
    Affected if The firmware version cannot be updated to the patched version (all versions of the listed Xeon Gold models are affected per the advisory)

You are affected if your system uses an Intel Xeon Gold 5315Y, 5317, 5318N, 5318S, 5318Y, or 5320 processor AND has either SGX or TDX enabled and cannot apply firmware updates.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Intel firmware/microcode updates for affected Xeon processors when available, or disable SGX/TDX if these security features are not required in the environment.

Recommended fix High confidence

Intel CPU microcode update (contact OEM for platform-specific firmware containing the fix)

  1. Check current CPU microcode version: `dmesg | grep -i microcode` or `cat /proc/cpuinfo | grep -i microcode`
  2. For Debian: Install microcode updates via `apt-get update && apt-get install intel-microcode`
  3. For Fedora: Install microcode updates via `dnf install microcode_ctl`
  4. Reboot the system after applying microcode updates to load the new firmware
  5. Alternatively, contact your server/system manufacturer for BIOS/firmware updates that include the Intel fix
Caveat Microcode updates may require system reboot; some updates may have compatibility considerations with specific workloads

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

Fix this in Debian Linux Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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