dpaa2-switch: Fix interrupt storm after receiving bad if_id in IRQ handler
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.15.203, 6.1.167, 6.6.130, 6.12.77, 6.18.17, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: dpaa2-switch: Fix interrupt storm after receiving bad if_id in IRQ handler Commit 31a7a0bbeb00 ("dpaa2-switch: add bounds check for if_id in IRQ handler") introduces a range check for if_id to avoid an out-of-bounds access. If an out-of-bounds if_id is detected, the interrupt status is not cleared. This may result in an interrupt storm. Clear the interrupt status after detecting an out-of-bounds if_id to avoid the problem. Found by an experimental AI code review agent at Google.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 77611cab5bdfff7a070ae574bbfba20a1de99d1b · fixed in 7def51cb9fb8b8d5342443372b8cf28d8fbd7f3d; From 34b56c16efd61325d80bf1d780d0e176be662f59 · fixed in b5bababe7703a7322bc59b803ab1587887a2a5e4; From f89e33c9c37f0001b730e23b3b05ab7b1ecface2 · fixed in c7becfe3e604d138bd53b8ac3111b2b3e8ec6b0e; From 2447edc367800ba914acf7ddd5d250416b45fb31 · fixed in fa4412cdc5178a48799bafcb8af28fd2fbf3d703; From 1b381a638e1851d8cfdfe08ed9cdbec5295b18c9 · fixed in 00f42ace446f1e4bf84988f2281131f52cd32796; From 31a7a0bbeb006bac2d9c81a2874825025214b6d8 · fixed in 28fd8ac1d49389cb230d712116f54e27ebec11b8; From 31a7a0bbeb006bac2d9c81a2874825025214b6d8 · fixed in 74badb9c20b1a9c02a95c735c6d3cd6121679c93; From 5.15.200 · fixed in 5.15.203; From 6.1.163 · fixed in 6.1.167; From 6.6.124 · fixed in 6.6.130; From 6.12.70 · fixed in 6.12.77; From 6.18.10 · fixed in 6.18.17
- Linux Linux
6.19
- KernelLinux
fixed in 5.15.203; From 5.16.0 · fixed in 6.1.167; From 6.2.0 · fixed in 6.6.130; From 6.7.0 · fixed in 6.12.77; From 6.13.0 · fixed in 6.18.17; From 6.19.0 · fixed in 6.19.7
References 7
git.kernel.org
- stable/c/7def51cb9fb8b8d5342443372b8cf28d8fbd7f3d
- stable/c/b5bababe7703a7322bc59b803ab1587887a2a5e4
- stable/c/c7becfe3e604d138bd53b8ac3111b2b3e8ec6b0e
- stable/c/fa4412cdc5178a48799bafcb8af28fd2fbf3d703
- stable/c/00f42ace446f1e4bf84988f2281131f52cd32796
- stable/c/28fd8ac1d49389cb230d712116f54e27ebec11b8
- stable/c/74badb9c20b1a9c02a95c735c6d3cd6121679c93