# CVE-2022-40982: Information disclosure in Intel(R) Processors

> An authenticated local attacker can exploit microarchitectural state to disclose sensitive information on Intel processors.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Aug 2023
- **Updated:** 13 Feb 2025
- **Also known as:** ALPINE-CVE-2022-40982, CLSA-2023-1693410662, CLSA-2023-1693417671, DEBIAN-CVE-2022-40982, DLA-3524-1, UBUNTU-CVE-2022-40982

## What is CVE-2022-40982?

CVE-2022-40982 is a medium-severity vulnerability in Debian Debian Linux, published on 11 Aug 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-203 (Observable Discrepancy), CWE-1342 (Information Exposure through Microarchitectural State after Transient Execution)

## Which versions are affected by CVE-2022-40982?

It affects 534 products.


Products: Debian Debian Linux, Intel Celeron 5205u Firmware, Intel Celeron 5305u Firmware, Intel Celeron G4900 Firmware, Intel Celeron G4900t Firmware, Intel Celeron G4920 Firmware, Intel Celeron G5900 Firmware, Intel Celeron G5900t Firmware, Intel Celeron G5905 Firmware, Intel Celeron G5905t Firmware, Intel Celeron G5920 Firmware, Intel Celeron G5925 Firmware, Intel Core I3-1000g1 Firmware, Intel Core I3-1000g4 Firmware, Intel Core I3-1005g1 Firmware, Intel Core I3-10100 Firmware, Intel Core I3-10100f Firmware, Intel Core I3-10100t Firmware, Intel Core I3-10100y Firmware, Intel Core I3-10105 Firmware and 514 more.

## How do I fix CVE-2022-40982?

Apply the vendor's patch.

## Is CVE-2022-40982 being exploited?

There is no known exploitation of CVE-2022-40982 in the wild and no public exploit code.

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-40982 and fix it if it is affected.

What it is: CVE-2022-40982 is a medium-severity vulnerability in Debian Debian Linux, published on 11 Aug 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-40982 in the wild and no public exploit code.

Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-40982/ (Markdown: https://insights.sbomify.com/CVE-2022-40982/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-40982
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-40982
- OSV: https://osv.dev/vulnerability/CVE-2022-40982

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-40982/
Summaries are generated and may contain mistakes; the official description above is the record.