dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-24898

MEDIUM · 6.0 CVSS v3.1 Published 2024-04-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/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
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.

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

A resource leak vulnerability in the openEuler Linux kernel's gmjstcm staging driver (drivers/staging/gmjstcm/tcm.c) allows exposure of sensitive information due to improper resource management. The flaw exists in kernel versions from 4.19.90-2109.1.0.0108 through 4.19.90-2403.4.0.0243.

MitigationApply the vendor-supplied kernel update to version 4.19.90-2403.4.0.0244 or later which contains the corrected resource handling in the tcm.c driver.

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

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
Changed
Confidentiality
High
Integrity
None
Availability
None

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

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. Check your running kernel version
    Run `uname -r` or `cat /proc/version` to obtain the kernel version string
    Affected if The version falls within 4.19.90-2109.1.0.0108 through 4.19.90-2403.4.0.0243 inclusive
  2. Verify the gmjstcm staging driver is present
    Check if the driver exists in the kernel by running `ls /lib/modules/$(uname -r)/kernel/drivers/staging/gmjstcm/` or searching for tcm.ko
    Affected if The driver file (tcm.ko or tcm.c) exists in the staging driver directory
  3. Determine if the driver is currently loaded
    Run `lsmod | grep gmjstcm` or check `ls /sys/module/ | grep gmjstcm` to see if the module is loaded
    Affected if The gmjstcm module appears in the list of loaded modules

You are affected if your kernel version is between 4.19.90-2109.1.0.0108 and 4.19.90-2403.4.0.0243 AND the gmjstcm staging driver is present or loaded in your environment.

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 the vendor-supplied kernel update to version 4.19.90-2403.4.0.0244 or later which contains the corrected resource handling in the tcm.c driver.

Recommended fix High confidence

openEuler kernel 4.19.90-2403.4.0.0244 or later

  1. Update the package repository: sudo dnf check-update
  2. Upgrade the kernel package: sudo dnf update kernel
  3. Reboot the system to load the new kernel: sudo reboot
  4. Verify the running kernel version matches or exceeds 4.19.90-2403.4.0.0244: uname -r
Caveat Kernel upgrades may require system reboot and could have compatibility implications with custom kernel modules or specific hardware drivers

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing20.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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