LiveActive security incident?Get immediate response
CVE Record

CVE-2024-46832: MIPS: cevt-r4k: Don't call get_c0_compare_int if timer irq is installed

In the Linux kernel, the following vulnerability has been resolved: MIPS: cevt-r4k: Don't call get_c0_compare_int if timer irq is installed This avoids warning: [ 0.118053] BUG: sleeping function called from invalid context at kernel/locking/mutex.c:283 Caused by get_c0_compare_int on secondary CPU. We also skipped saving IRQ number to struct clock_event_device *cd as it's never used by clockevent core, as per comments it's only meant for "non CPU local devices".

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

Security readout for executives and security teams

Plain-English summary

CVE-2024-46832 is a Linux kernel issue in MIPS timer handling. The sources describe a kernel warning from calling a sleeping function in an invalid context on a secondary CPU. They do not describe remote exploitation, privilege escalation, or data exposure.

Executive priority

Treat this as a targeted kernel maintenance item for MIPS environments. It is not supported by the provided evidence as an emergency internet-wide threat, but affected production platforms should be patched through normal kernel update processes.

Technical view

In MIPS cevt-r4k clock event code, get_c0_compare_int could be called even when the timer IRQ was already installed, causing a mutex-related invalid-context warning. The stable fixes avoid that call path and skip storing an unused IRQ number for CPU-local clock event devices.

Likely exposure

Exposure appears limited to affected Linux kernel builds running on MIPS systems. The bundle does not identify affected user applications, cloud services, x86/ARM systems, or internet-facing attack surface.

Exploitation context

CISA KEV status is false, and the provided sources do not report active exploitation or a public exploit. Evidence points to a kernel correctness and reliability issue rather than a documented attacker workflow.

Researcher notes

The source bundle lacks CVSS, CWE, and exploitability analysis. Analysis should stay close to the kernel commit rationale: invalid-context warning in MIPS cevt-r4k timer IRQ handling, fixed across stable branches and referenced by Debian LTS.

Mitigation direction

  • Identify MIPS Linux systems and appliances in asset inventory.
  • Apply kernel updates containing the referenced stable fixes.
  • For Debian LTS systems, review the Debian advisory and update packages.
  • Use vendor or distribution guidance for backported kernel versions.
  • Prioritize production MIPS platforms where kernel warnings affect availability.

Validation and detection

  • Confirm each system architecture is MIPS before scoping impact.
  • Record running kernel versions and distribution package revisions.
  • Check vendor changelogs for CVE-2024-46832 or referenced stable commits.
  • After updating, reboot and monitor kernel logs for the reported warning.
  • Validate normal timer, CPU startup, and workload behavior after patching.
Prepared
Confidence
medium
Sources
9

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-46832 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
2ADP providers
8Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux38760d40ca61b18b2809e9c28df8b3ff9af8a02b, 38760d40ca61b18b2809e9c28df8b3ff9af8a02b, 38760d40ca61b18b2809e9c28df8b3ff9af8a02b, 38760d40ca61b18b2809e9c28df8b3ff9af8a02b, 38760d40ca61b18b2809e9c28df8b3ff9af8a02b, 38760d40ca61b18b2809e9c28df8b3ff9af8a02bunaffected
LinuxLinux2.6.24, 0, 5.10.226, 5.15.167, 6.1.110, 6.6.51, 6.10.10, 6.11affected
Weakness

CWE details

No CWE listed

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