CVE-2024-46791
Last modified
CVE-2024-46791 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: can: mcp251x: fix deadlock if an interrupt occurs during mcp251x_open The mcp251x_hw_wake() function is called with the mpc_lock mutex held and disables the interrupt handler so that no interrupts can be processed while waking the device. If an interrupt has already occurred then waiting for the interrupt handler to complete will deadlock because it will be trying to acquire the same mutex. CPU0 CPU1 ---- ---- mcp251x_open() mutex_lock(&priv->mcp_lock) request_threaded_irq() <interrupt> mcp251x_can_ist() mutex_lock(&priv->mcp_lock) mcp251x_hw_wake() disable_irq() <-- deadlock Use disable_irq_nosync() instead because the interrupt handler does everything while holding the mutex so it doesn't matter if it's still running.. EPSS estimates a 0.16% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: can: mcp251x: fix deadlock if an interrupt occurs during mcp251x_open The mcp251x_hw_wake() function is called with the mpc_lock mutex held and disables the interrupt handler so that no interrupts can be processed while waking the device. If an interrupt has already occurred then waiting for the interrupt handler to complete will deadlock because it will be trying to acquire the same mutex. CPU0 CPU1 ---- ---- mcp251x_open() mutex_lock(&priv->mcp_lock) request_threaded_irq() <interrupt> mcp251x_can_ist() mutex_lock(&priv->mcp_lock) mcp251x_hw_wake() disable_irq() <-- deadlock Use disable_irq_nosync() instead because the interrupt handler does everything while holding the mutex so it doesn't matter if it's still running.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 5.5, < 5.10.226 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.167 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.110 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.51 | — |
| Linux | Linux Kernel | >= 6.7, < 6.10.10 | — |
| Linux | Linux Kernel | 6.11 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2024-46791?
How severe is CVE-2024-46791?
How do I fix CVE-2024-46791?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2024
- CVE-2024-46786In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-46787In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2024-46788In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-46789In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-4679Incorrect Default Permissions vulnerability in Hitachi JP1/E…7.8
- CVE-2024-46790In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-46792In the Linux kernel, the following vulnerability has been re…3.3
- CVE-2024-46793In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-46794In the Linux kernel, the following vulnerability has been re…3.3
- CVE-2024-46795In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-46796In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-46797In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2024-46791?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
