CVE-2024-58085
Vulnerability Scoring
Analysis In Progress
CVE-2024-58085 Vulnerability Analysis & Exploit Details
CVE-2024-58085
Attack Complexity Details
-
Attack Complexity:
Attack Complexity Analysis In Progress
-
Attack Vector:
Attack Vector Under Analysis
-
Privileges Required:
None
No authentication is required for exploitation.
-
Scope:
Impact is confined to the initially vulnerable component.
-
User Interaction:
None
No user interaction is necessary for exploitation.
CVE-2024-58085 Details
Status: Awaiting Analysis
Last updated: 🕐 13 Mar 2025, 13:15 UTC
Originally published on: 🕔 06 Mar 2025, 17:15 UTC
Time between publication and last update: 6 days
CVSS Release:
CVE-2024-58085 Vulnerability Summary
CVE-2024-58085: In the Linux kernel, the following vulnerability has been resolved: tomoyo: don't emit warning in tomoyo_write_control() syzbot is reporting too large allocation warning at tomoyo_write_control(), for one can write a very very long line without new line character. To fix this warning, I use __GFP_NOWARN rather than checking for KMALLOC_MAX_SIZE, for practically a valid line should be always shorter than 32KB where the "too small to fail" memory-allocation rule applies. One might try to write a valid line that is longer than 32KB, but such request will likely fail with -ENOMEM. Therefore, I feel that separately returning -EINVAL when a line is longer than KMALLOC_MAX_SIZE is redundant. There is no need to distinguish over-32KB and over-KMALLOC_MAX_SIZE.
Assessing the Risk of CVE-2024-58085
Access Complexity Graph
The exploitability of CVE-2024-58085 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).
Exploitability Analysis for CVE-2024-58085
No exploitability data is available for CVE-2024-58085.
Understanding AC and PR
A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.
Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.
Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.
CVSS Score Breakdown Chart
Above is the CVSS Sub-score Breakdown for CVE-2024-58085, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.
CIA Impact Analysis
Below is the Impact Analysis for CVE-2024-58085, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.
-
Confidentiality:
None
CVE-2024-58085 does not compromise confidentiality.
-
Integrity:
None
CVE-2024-58085 does not impact data integrity.
-
Availability:
None
CVE-2024-58085 does not affect system availability.
Exploit Prediction Scoring System (EPSS)
The EPSS score estimates the probability that this vulnerability will be exploited in the near future.
EPSS Score: 0.044% (probability of exploit)
EPSS Percentile: 15.85%
(lower percentile = lower relative risk)
This vulnerability is less risky than approximately 84.15% of others.
CVE-2024-58085 References
External References
- https://git.kernel.org/stable/c/3df7546fc03b8f004eee0b9e3256369f7d096685
- https://git.kernel.org/stable/c/414705c0303350d139b1dc18f329fe47dfb642dd
- https://git.kernel.org/stable/c/a01c200fa7eb59da4d2dbbb48b61f4a0d196c09f
- https://git.kernel.org/stable/c/b2bd5857a0d6973ebbcb4d9831ddcaebbd257be1
- https://git.kernel.org/stable/c/c67efabddc73171c7771d3ffe4ffa1e503ee533e
- https://git.kernel.org/stable/c/c9382f380e8d09209b8e5c0def0545852168be25
- https://git.kernel.org/stable/c/f6b37b3e12de638753bce79a2858070b9c4a4ad3
- https://git.kernel.org/stable/c/fe1c021eb03dae0dc9dce55e81f77a60e419a27a
CWE Common Weakness Enumeration
Unknown
Protect Your Infrastructure against CVE-2024-58085: Combat Critical CVE Threats
Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.
Other 5 Recently Published CVEs Vulnerabilities
- CVE-2025-2724 – A vulnerability classified as problematic has been found in GNOME libgsf up to 1.14.53. Affected is the function sorting_key_copy. The manipulation...
- CVE-2025-2723 – A vulnerability was found in GNOME libgsf up to 1.14.53. It has been rated as critical. This issue affects the function gsf_property_settings_colle...
- CVE-2025-2722 – A vulnerability was found in GNOME libgsf up to 1.14.53. It has been declared as critical. This vulnerability affects the function gsf_prop_setting...
- CVE-2025-2721 – A vulnerability was found in GNOME libgsf up to 1.14.53. It has been classified as critical. This affects the function gsf_base64_encode_simple. Th...
- CVE-2025-2720 – A vulnerability was found in GNOME libgsf up to 1.14.53 and classified as problematic. Affected by this issue is the function gsf_base64_encode_sim...