Cyber Resilience

CVE-2024-1048

Redhat Enterprise Linux 8.0 … 9.0

Published
06 February 2024
Modified
17 June 2026
Patch / advisory
CVSS Score v3.1 3.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
EPSS Score 0.0027 19th percentile
Risk Priority 29 floored blend · peak EPSS

Summary

CVE-2024-1048 is a low-severity Incomplete Cleanup (CWE-459) vulnerability in Redhat Enterprise Linux. Its CVSS base score is 3.3 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked at the 19th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-14 (Non-persistence) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

A flaw was found in the grub2-set-bootflag utility of grub2. After the fix of CVE-2019-14865, grub2-set-bootflag will create a temporary file with the new grubenv content and rename it to the original grubenv file. If the program is killed before…

more

the rename operation, the temporary file will not be removed and may fill the filesystem when invoked multiple times, resulting in a filesystem out of free inodes or blocks.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
T1552 Unsecured Credentials Credential Access
Adversaries may search compromised systems to find and obtain insecurely stored credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-4001Same product: Fedoraproject Fedora
CVE-2024-23672Same product: Fedoraproject Fedora
CVE-2023-4156Same product: Fedoraproject Fedora
CVE-2024-0553Same product: Fedoraproject Fedora
CVE-2023-4692Same product: Gnu Grub2
CVE-2023-4693Same product: Gnu Grub2
CVE-2025-37908Shared CWE-459
CVE-2025-20293Shared CWE-459
CVE-2023-41835Shared CWE-459
CVE-2024-53869Shared CWE-459

Affected Assets

gnu
grub2
all versions
redhat
enterprise linux
8.0, 9.0
fedoraproject
fedora
40

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V6.4.1

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover incomplete cleanup through dynamic analysis or resource-leak testing.

Non-persistence mechanisms explicitly initiate resources in a known state and terminate them, directly enforcing cleanup.

Session termination forces explicit release of session-related temporary resources.

Preventing unintended information transfer through shared resources requires complete cleanup of those resources.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure-development practices and coding standards normally require proper resource release and cleanup.

ID.AM-08 partial match
prevents

Life-cycle management encompasses disposal of temporary resources but does not specifically target runtime cleanup bugs.

PR.DS-10 partial match
prevents

Explicitly calls for removing sensitive data after use, directly addressing one class of incomplete cleanup.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

degrades

Explicitly requires secure deletion of temporary or residual data, directly addressing incomplete cleanup.

prevents

SDLC practices include cleanup steps, yet the weakness can still occur if those steps are omitted.

prevents

Secure-coding rules can mandate explicit cleanup of temporary resources, but do not guarantee it.

finds

Change-management processes may require cleanup verification, but the control itself does not address the weakness.

References