# CVE-2024-24898: Information Leakage in kernel

> An attacker can leak sensitive information via a resource leak in the openEuler Linux kernel's staging driver.

- **Severity:** Medium 6.0 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:N/A: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:** 15 Apr 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-744g-wfhc-3v4q, UBUNTU-CVE-2024-24898

## What is CVE-2024-24898?

CVE-2024-24898 is a medium-severity vulnerability in openEuler kernel, published on 15 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Exposure of Sensitive Information to an Unauthorized Actor vulnerability in openEuler kernel on Linux allows Resource Leak Exposure. This vulnerability is associated with program files https://gitee.Com/openeuler/kernel/blob/openEuler-1.0-LTS/drivers/staging/gmjstcm/tcm.C.

This issue affects kernel: from 4.19.90-2109.1.0.0108 before 4.19.90-2403.4.0.0244.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

Apply the vendor's patch.

## Is CVE-2024-24898 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-24898 is a medium-severity vulnerability in openEuler kernel, published on 15 Apr 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-24898 in the wild and no public exploit code.

Affected product: openEuler kernel. 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-24898/ (Markdown: https://insights.sbomify.com/CVE-2024-24898/index.md)
```

## Sources

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

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