CVE-2024-24898

What it actually does

A resource leak in the TCM driver (drivers/staging/gmjstcm/tcm.C) exposes sensitive kernel memory or state to local actors with high privileges.

Why it matters to the business

Elevated local users may obtain kernel-internal data that should remain confidential, increasing risk of further attacks on affected openEuler systems.

How an attack unfolds

An attacker with administrative privileges on a vulnerable openEuler host interacts with the TCM staging driver to trigger the resource leak and read the disclosed sensitive information.

How to fix it

Upgrade the openEuler kernel from versions 4.19.90-2109.1.0.0108 through 4.19.90-2403.4.0.0243 to 4.19.90-2403.4.0.0244 or newer.

How to confirm the fix worked

Confirm the running kernel version meets or exceeds 4.19.90-2403.4.0.0244; attempt to reproduce the resource leak with a local high-privileged test program and verify no sensitive data is disclosed.

Typical attack path

1. Obtain high-privileged (root) shell on the target openEuler system
2. Locate and access the vulnerable TCM driver interface
3. Trigger the resource leak condition to cause sensitive data exposure
4. Read the leaked information from kernel memory or associated structures

How to detect it

Review kernel logs and audit trails for unexpected access or errors involving the TCM driver; look for processes that interact with staging drivers followed by anomalous memory or file reads.

What your security team should do

• Prioritize kernel upgrade on all openEuler hosts within the affected version range
• Restrict local administrative access where possible until patches are applied
• Include the TCM driver path in routine kernel integrity and version checks