# CVE-2024-23984: Information disclosure in Intel(R) Processors

> A privileged local attacker can exploit an observable discrepancy in the RAPL interface to disclose sensitive information.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:H/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Sep 2024
- **Updated:** 3 Nov 2025
- **Also known as:** ALPINE-CVE-2024-23984, BELL-CVE-2024-23984, DEBIAN-CVE-2024-23984, GHSA-m5wh-wcvg-3f5f, UBUNTU-CVE-2024-23984

## What is CVE-2024-23984?

CVE-2024-23984 is a medium-severity vulnerability in Intel(R) Processors, published on 16 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Observable discrepancy in RAPL interface for some Intel(R) Processors may allow a privileged user to potentially enable information disclosure via local access.

Weakness: CWE-203 (Observable Discrepancy)

## Which versions are affected by CVE-2024-23984?


## How do I fix CVE-2024-23984?

Apply the vendor's patch.

## Is CVE-2024-23984 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-23984 and fix it if it is affected.

What it is: CVE-2024-23984 is a medium-severity vulnerability in Intel(R) Processors, published on 16 Sep 2024. 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-2024-23984 in the wild and no public exploit code.

Affected product: Intel(R) Processors. 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-2024-23984/ (Markdown: https://insights.sbomify.com/CVE-2024-23984/index.md)
```

## Sources

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

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