CVE-2024-46832: MIPS: cevt-r4k: Don't call get_c0_compare_int if timer irq is installed
First published: Fri Sep 27 2024(Updated: )
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".
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel | <5.10.226 | |
| Linux Kernel | >=5.11<5.15.167 | |
| Linux Kernel | >=5.16<6.1.110 | |
| Linux Kernel | >=6.2<6.6.51 | |
| Linux Kernel | >=6.7<6.10.10 | |
| Linux Kernel | =6.11-rc1 | |
| Linux Kernel | =6.11-rc2 | |
| Linux Kernel | =6.11-rc3 | |
| Linux Kernel | =6.11-rc4 | |
| debian/linux | <=5.10.223-1<=5.10.234-1 | 6.1.129-1 6.1.133-1 6.12.22-1 |
| debian/linux-6.1 | 6.1.129-1~deb11u1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/189d3ed3b25beee26ffe2abed278208bece13f52
- https://git.kernel.org/stable/c/32ee0520159f1e8c2d6597c19690df452c528f30
- https://git.kernel.org/stable/c/50f2b98dc83de7809a5c5bf0ccf9af2e75c37c13
- https://git.kernel.org/stable/c/b1d2051373bfc65371ce4ac8911ed984d0178c98
- https://git.kernel.org/stable/c/d3ff0f98a52f0aafe35aa314d1c442f4318be3db
- https://git.kernel.org/stable/c/e6cd871627abbb459d0ff6521d6bb9cf9d9f7522
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-46832
- https://nvd.nist.gov/vuln/detail/CVE-2024-46832
- https://launchpad.net/bugs/cve/CVE-2024-46832
- https://security-tracker.debian.org/tracker/CVE-2024-46832
- https://ubuntu.com/security/CVE-2024-46832
- https://git.kernel.org/linus/50f2b98dc83de7809a5c5bf0ccf9af2e75c37c13
Frequently Asked Questions
What is the severity of CVE-2024-46832?
CVE-2024-46832 has been classified with medium severity due to its potential impact on system stability.
How do I fix CVE-2024-46832?
To fix CVE-2024-46832, update your Linux kernel to version 6.1.123-1 or later.
Which versions of the Linux kernel are affected by CVE-2024-46832?
CVE-2024-46832 affects Linux kernel versions from 5.10 to 6.11-rc4.
Has CVE-2024-46832 been resolved?
Yes, CVE-2024-46832 has been resolved in subsequent updates to the Linux kernel.
What kind of systems are vulnerable to CVE-2024-46832?
Systems running vulnerable versions of the Linux kernel on MIPS architecture are at risk of CVE-2024-46832.
- agent/title
- agent/type
- agent/first-publish-date
- agent/severity
- agent/remedy
- agent/author
- agent/references
- collector/launchpad-cve
- source/Launchpad
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/trending
- collector/usn-cve
- source/Ubuntu
- agent/event
- agent/description
- agent/source
- collector/nvd-cve
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/nvd-api
- agent/tags
- agent/softwarecombine
- collector/security-tracker-debian
- source/Debian
- vendor/linux
- canonical/linux kernel
- version/linux kernel/5.11
- version/linux kernel/5.16
- version/linux kernel/6.2
- version/linux kernel/6.7
- version/linux kernel/6.11-rc1
- version/linux kernel/6.11-rc2
- version/linux kernel/6.11-rc3
- version/linux kernel/6.11-rc4
- package-manager/debian