# CVE-2025-24511: Information disclosure in Intel(R) I350 Series Ethernet

> An authenticated user can exploit improper initialization in Intel I350 Ethernet drivers to expose sensitive information.

- **Severity:** Low 2.0 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA: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:** No
- **Published:** 12 Aug 2025
- **Updated:** 13 Aug 2025
- **Also known as:** GHSA-47hw-p9qv-5wqq

## What is CVE-2025-24511?

CVE-2025-24511 is a low-severity vulnerability in Intel(R) I350 Series Ethernet, published on 12 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper initialization in the Linux kernel-mode driver for some Intel(R) I350 Series Ethernet before version 5.19.2 may allow an authenticated user to potentially enable Information disclosure via data exposure.

Weakness: CWE-665 (Improper Initialization)

## Which versions are affected by CVE-2025-24511?


## How do I fix CVE-2025-24511?

No fix has been published for CVE-2025-24511 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-24511 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-24511 and fix it if it is affected.

What it is: CVE-2025-24511 is a low-severity vulnerability in Intel(R) I350 Series Ethernet, published on 12 Aug 2025. 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-2025-24511 in the wild and no public exploit code.

Affected product: Intel(R) I350 Series Ethernet. 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-2025-24511/ (Markdown: https://insights.sbomify.com/CVE-2025-24511/index.md)
```

## Sources

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

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