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

Published Sep 27, 2024
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

MIPS: cevt-r4k: Don't call getc0compareint 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 getc0compareint on secondary CPU.

We also skipped saving IRQ number to struct clockeventdevice cd as it's never used by clockevent core, as per comments it's only meant for "non CPU local devices".

Other sources

This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.

Launchpad

Affected Software

16 affected componentsFixes available
Linux Linux kernel<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
Linux Linux kernel=6.11-rc2
Linux Linux kernel=6.11-rc3
Linux Linux kernel=6.11-rc4
debian/linux<=5.10.223-1, <=5.10.234-1
6.1.129-16.1.135-16.12.25-16.12.27-1
debian/linux-6.1
6.1.129-1~deb11u1
Microsoft cbl2 kernel 5.15.164.1-1
Microsoft cbl2 kernel 5.15.167.1-1
Microsoft cbl2 kernel 5.15.164.1-1
Microsoft azl3 kernel 6.6.51.1-5
Microsoft azl3 kernel 6.6.47.1-1

Event History

Sep 27, 2024
CVE Published
via MITRE·12:39 PM
Data Sourced
via MITRE·12:39 PM
Description
Data Sourced
via NVD·01:15 PM
RemedyDescriptionSeverityAffected Software
Oct 14, 2024
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
SeverityAffected Software
Updated
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
DescriptionSeverity
Dec 13, 2024
Data Sourced
via Launchpad·03:54 PM
Description
May 3, 2025
Data Sourced
via Ubuntu·06:23 AM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

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.

2

How do I fix CVE-2024-46832?

To fix CVE-2024-46832, update your Linux kernel to version 6.1.123-1 or later.

3

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.

4

Has CVE-2024-46832 been resolved?

Yes, CVE-2024-46832 has been resolved in subsequent updates to the Linux kernel.

5

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203