CVE-2026-23180
Unknown Unknown - Not Provided
Out-of-Bounds Read in Linux dpaa2-switch IRQ Handler

Publication date: 2026-02-14

Last updated on: 2026-04-03

Assigner: kernel.org

Description
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().
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-14
Last Modified
2026-04-03
Generated
2026-05-07
AI Q&A
2026-02-14
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux_kernel linux_kernel *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability exists in the Linux kernel's dpaa2-switch component. The IRQ handler extracts an interface ID (if_id) from the upper 16 bits of a hardware status register and uses this value to index into an array called ethsw->ports[]. However, the if_id value can be any 16-bit number (0-65535), while the ports array only contains a limited number of elements defined by sw_attr.num_ifs. Because there is no validation or bounds check on if_id before accessing the array, this can lead to an out-of-bounds read.

The vulnerability was fixed by adding a bounds check to ensure that if_id is within the valid range before accessing the ports array, preventing potential out-of-bounds memory access.


How can this vulnerability impact me? :

An out-of-bounds read vulnerability like this can potentially lead to information disclosure or system instability. Since the IRQ handler reads memory outside the bounds of the ports array, it might access unintended memory areas, which could expose sensitive data or cause unexpected behavior in the kernel.

However, the exact impact depends on how the system uses the affected component and whether an attacker can exploit this condition to gain useful information or cause a denial of service.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

I don't know


What immediate steps should I take to mitigate this vulnerability?

I don't know


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart