CVE-2024-50196: Linux kernel · pinctrl: ocelot: fix system hang on level based interrupts
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 5.5 Medium · fixed in 5.4.0-1153.163~18.04.1 : update Linux kernel when convenient.
Data as of 29 Oct 2026, 22:34 UTC
- Patch
- Available – fixed in 5.4.0-1153.163~18.04.1, 5.4.0-1156.163~18.04.1, 5.4.0-1156.165~18.04.1 +84
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 8 Nov 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-7276-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7277-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7288-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7289-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7291-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7288-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7289-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7289-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7305-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7289-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-7308-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7310-1 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-6.11pkg:deb/ubuntu/linux-azure-6.11?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-nvidiapkg:deb/ubuntu/linux-azure-nvidia?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
In the Linux kernel, the following vulnerability has been resolved: pinctrl: ocelot: fix system hang on level based interrupts The current implementation only calls chained_irq_enter() and chained_irq_exit() if it detects pending interrupts. ``` for (i = 0; i < info->stride; i++) { uregmap_read(info->map, id_reg + 4 * i, ®); if (!reg) continue; chained_irq_enter(parent_chip, desc); ``` However, in case of GPIO pin configured in level mode and the parent controller configured in edge mode, GPIO interrupt might be lowered by the hardware. In the result, if the interrupt is short enough, the parent interrupt is still pending while the GPIO interrupt is cleared; chained_irq_enter() never gets called and the system hangs trying to service the parent interrupt. Moving chained_irq_enter() and chained_irq_exit() outside the for loop ensures that they are called even when GPIO interrupt is lowered by the hardware. The similar code with chained_irq_enter() / chained_irq_exit() functions wrapping interrupt checking loop may be found in many other drivers: ``` grep -r -A 10 chained_irq_enter drivers/pinctrl ```
References
- ubuntu.com/security/CVE-2024-50196 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2024-50196 (opens in a new tab)
- git.kernel.org/linus/93b8ddc54507a227087c60a0013ed833b6ae7d3c (opens in a new tab)
- git.kernel.org/stable/c/655f5d4662b958122b260be05aa6dfdf8768efe6 (opens in a new tab)
- git.kernel.org/stable/c/4a81800ef05bea5a9896f199677f7b7f5020776a (opens in a new tab)
- git.kernel.org/stable/c/20728e86289ab463b99b7ab4425515bd26aba417 (opens in a new tab)
- git.kernel.org/stable/c/dcbe9954634807ec54e22bde278b5b269f921381 (opens in a new tab)
- git.kernel.org/stable/c/93b8ddc54507a227087c60a0013ed833b6ae7d3c (opens in a new tab)
- ubuntu.com/security/notices/USN-7276-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7277-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7288-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7289-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7291-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7288-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7289-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7289-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7305-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7289-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-7308-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7310-1 (opens in a new tab)