dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-24891

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 unauthorized exposure of sensitive information. The flaw exists in kernel versions 4.19.90-2109.1.0.0108 through 4.19.90-2403.4.0.0243.

MitigationUpgrade the openEuler kernel to version 4.19.90-2403.4.0.0244 or later to patch the resource leak 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 kernel version against affected range
    Run 'uname -r' or 'cat /proc/version' to get the running kernel version. Compare it to the affected range: 4.19.90-2109.1.0.0108 through 4.19.90-2403.4.0.0243
    Affected if The installed kernel version falls within or below the affected version range (4.19.90-2109.1.0.0108 to 4.19.90-2403.4.0.0243)
  2. Locate the gmjstcm driver module
    Run 'find /lib/modules/$(uname -r) -name "*gmjstcm*" 2>/dev/null' or check if the path /lib/modules/$(uname -r)/kernel/drivers/staging/gmjstcm/ exists
    Affected if The gmjstcm driver module or its directory exists in the kernel modules path
  3. Check if gmjstcm driver is loaded
    Run 'lsmod | grep gmjstcm' to see if the driver module is currently loaded, or check /sys/module/gmjstcm/ if the driver is built-in
    Affected if The gmjstcm module appears in lsmod output or the module directory exists in /sys/module/
  4. Verify driver source file presence
    Check for the presence of tcm.c in the staging driver directory: 'find /lib/modules/$(uname -r) -path "*staging/gmjstcm/tcm*" 2>/dev/null' or inspect kernel source at drivers/staging/gmjstcm/tcm.c
    Affected if The vulnerable tcm.c source or compiled driver files exist in the staging gmjstcm directory

You are affected if your openEuler kernel version is 4.19.90-2109.1.0.0108 through 4.19.90-2403.4.0.0243 AND the gmjstcm staging driver is present and loaded (or built-in) 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

Upgrade the openEuler kernel to version 4.19.90-2403.4.0.0244 or later to patch the resource leak in the tcm.c driver.

Recommended fix Moderate confidence

openEuler kernel 4.19.90-2403.4.0.0244 or later

  1. 1. Identify the current running kernel version using 'uname -r' or 'rpm -q kernel'
  2. 2. Schedule a maintenance window for the kernel upgrade (this will require a system reboot)
  3. 3. Update the package repository: 'sudo yum update' or 'sudo dnf update'
  4. 4. Install the updated kernel package: 'sudo yum install kernel' or 'sudo dnf install kernel'
  5. 5. Verify the new kernel version 4.19.90-2403.4.0.0244 or later is installed: 'rpm -q kernel'
  6. 6. Reboot the system to load the fixed kernel
  7. 7. After reboot, verify the running kernel is the fixed version using 'uname -r'
Caveat Kernel upgrades may require driver recompilation or may affect proprietary kernel modules; ensure compatible drivers and kernel modules are available before rebooting

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
21.0 hours of engineering $3,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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