dpaa2-switch: add bounds check for 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.200, 6.1.163, 6.6.124, 6.12.70, 6.18.10
- 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
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: dpaa2-switch: add bounds check for if_id in IRQ handler The IRQ handler extracts if_id from the upper 16 bits of the hardware status register and uses it to index into ethsw->ports[] without validation. Since if_id can be any 16-bit value (0-65535) but the ports array is only allocated with sw_attr.num_ifs elements, this can lead to an out-of-bounds read potentially. Add a bounds check before accessing the array, consistent with the existing validation in dpaa2_switch_rx().
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 24ab724f8a4661b2dc8e696b41df93bdc108f7a1 · fixed in 77611cab5bdfff7a070ae574bbfba20a1de99d1b; From 24ab724f8a4661b2dc8e696b41df93bdc108f7a1 · fixed in 34b56c16efd61325d80bf1d780d0e176be662f59; From 24ab724f8a4661b2dc8e696b41df93bdc108f7a1 · fixed in f89e33c9c37f0001b730e23b3b05ab7b1ecface2; From 24ab724f8a4661b2dc8e696b41df93bdc108f7a1 · fixed in 2447edc367800ba914acf7ddd5d250416b45fb31; From 24ab724f8a4661b2dc8e696b41df93bdc108f7a1 · fixed in 1b381a638e1851d8cfdfe08ed9cdbec5295b18c9; From 24ab724f8a4661b2dc8e696b41df93bdc108f7a1 · fixed in 31a7a0bbeb006bac2d9c81a2874825025214b6d8
- Linux Linux
5.15
- KernelLinux
From 5.15.0 · fixed in 5.15.200; From 5.16.0 · fixed in 6.1.163; From 6.2.0 · fixed in 6.6.124; From 6.7.0 · fixed in 6.12.70; From 6.13.0 · fixed in 6.18.10