LiveActive security incident?Get immediate response
CVE Record

CVE-2024-58078: misc: misc_minor_alloc to use ida for all dynamic/misc dynamic minors

In the Linux kernel, the following vulnerability has been resolved: misc: misc_minor_alloc to use ida for all dynamic/misc dynamic minors misc_minor_alloc was allocating id using ida for minor only in case of MISC_DYNAMIC_MINOR but misc_minor_free was always freeing ids using ida_free causing a mismatch and following warn: > > WARNING: CPU: 0 PID: 159 at lib/idr.c:525 ida_free+0x3e0/0x41f > > ida_free called for id=127 which is not allocated. > > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< ... > > [<60941eb4>] ida_free+0x3e0/0x41f > > [<605ac993>] misc_minor_free+0x3e/0xbc > > [<605acb82>] misc_deregister+0x171/0x1b3 misc_minor_alloc is changed to allocate id from ida for all minors falling in the range of dynamic/ misc dynamic minors

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue is a minor-number bookkeeping bug in the misc device subsystem. The public record shows a kernel warning when a device is deregistered, caused by freeing an ID that was not allocated through the same allocator path. No source provided confirms data theft, privilege escalation, or active exploitation.

Executive priority

Treat this as a monitored kernel maintenance item unless vendor advisories raise severity. It does not currently justify emergency response from the provided evidence, but affected kernels should be patched through normal kernel update processes.

Technical view

misc_minor_alloc used ida allocation only for MISC_DYNAMIC_MINOR, while misc_minor_free always used ida_free for dynamic and misc-dynamic minor ranges. That mismatch could trigger an ida_free warning during misc_deregister. The fix aligns allocation behavior by using ida for all minors in those ranges.

Likely exposure

Exposure is limited to Linux kernels containing the affected misc device minor allocation logic, including the version ranges listed in the CVE bundle. Systems using vendor kernels may be affected if the vulnerable code was backported or not yet patched.

Exploitation context

The sources do not describe an exploit path, attacker requirements, or active exploitation. CISA KEV status is false in the provided bundle. The observable issue is a kernel warning during misc device deregistration, so operational stability impact is clearer than security impact.

Researcher notes

The CVE lacks CVSS, CWE, exploitability details, and named impacted distributions. Analysis should focus on kernel lineage, stable-branch fix presence, and whether local driver activity can reach misc_deregister paths that expose the allocator mismatch.

Mitigation direction

  • Apply a Linux stable or vendor kernel containing the referenced fix.
  • Check distribution advisories for backported patches matching CVE-2024-58078.
  • Prioritize systems loading misc device drivers or out-of-tree kernel modules.
  • If patch timing is unclear, follow vendor guidance before changing kernel behavior.

Validation and detection

  • Inventory Linux kernel versions and vendor patch levels across affected assets.
  • Confirm whether vendor kernels include one of the referenced stable fixes or an equivalent backport.
  • Review kernel logs for ida_free warnings during misc device deregistration.
  • Track the CVE record for any later CVSS, CWE, or exploitation updates.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-58078 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
5Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxab760791c0cfbb1d7a668f46a135264f56c8f018, ab760791c0cfbb1d7a668f46a135264f56c8f018, ab760791c0cfbb1d7a668f46a135264f56c8f018, ab760791c0cfbb1d7a668f46a135264f56c8f018unaffected
LinuxLinux6.2, 0, 6.6.78, 6.12.14, 6.13.3, 6.14affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.