CVE-2026-23180: dpaa2-switch: add bounds check for if_id in IRQ handler
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.14% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: Linux Linux 1b381a638e1851d8cfdfe08ed9cdbec5295b18c9, 2447edc367800ba914acf7ddd5d250416b45fb31, 31a7a0bbeb006bac2d9c81a2874825025214b6d8.
Low priority for now. Upgrade to Linux Linux 1b381a638e1851d8cfdfe08ed9cdbec5295b18c9, 2447edc367800ba914acf7ddd5d250416b45fb31, 31a7a0bbeb006bac2d9c81a2874825025214b6d8 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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().
- Published
- Feb 14, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 3th percentile
- CWE
- CWE-125
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.0
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.15affected
- 24ab724f8a4661b2dc8e696b41df93bdc108f7a1 and later · before 77611cab5bdfff7a070ae574bbfba20a1de99d1baffected · git
- 24ab724f8a4661b2dc8e696b41df93bdc108f7a1 and later · before 34b56c16efd61325d80bf1d780d0e176be662f59affected · git
- 24ab724f8a4661b2dc8e696b41df93bdc108f7a1 and later · before f89e33c9c37f0001b730e23b3b05ab7b1ecface2affected · git
- 24ab724f8a4661b2dc8e696b41df93bdc108f7a1 and later · before 2447edc367800ba914acf7ddd5d250416b45fb31affected · git
- 24ab724f8a4661b2dc8e696b41df93bdc108f7a1 and later · before 1b381a638e1851d8cfdfe08ed9cdbec5295b18c9affected · git
- 24ab724f8a4661b2dc8e696b41df93bdc108f7a1 and later · before 31a7a0bbeb006bac2d9c81a2874825025214b6d8affected · git
- before 5.15not affected · semver
- 5.15.200 and later · up to and including 5.15.*not affected · semver
- 6.1.163 and later · up to and including 6.1.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.164-1 | 6.1.164-1 |
| Debian:13 | linux | before 6.12.73-1 | 6.12.73-1 |
| Debian:14 | linux | before 6.18.10-1 | 6.18.10-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-23176Feb 14, 2026 · platform/x86: toshiba_haps: Fix memory leaks in add/remove routines0Monitor
- ← EarlierCVE-2026-23178Feb 14, 2026 · HID: i2c-hid: fix potential buffer overflow in i2c_hid_get_report()31Monitor
- Later →CVE-2026-23182Feb 14, 2026 · spi: tegra: Fix a memory leak in tegra_slink_probe()0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1b381a638e1851d8cfdfe08ed9cdbec5295b18c9 | Vendor (CNA) |
| Linux Linux | 2447edc367800ba914acf7ddd5d250416b45fb31 | Vendor (CNA) |
| Linux Linux | 31a7a0bbeb006bac2d9c81a2874825025214b6d8 | Vendor (CNA) |
| Linux Linux | 34b56c16efd61325d80bf1d780d0e176be662f59 | Vendor (CNA) |
| Linux Linux | 77611cab5bdfff7a070ae574bbfba20a1de99d1b | Vendor (CNA) |
| Linux Linux | f89e33c9c37f0001b730e23b3b05ab7b1ecface2 | Vendor (CNA) |
| debian:linux | 6.1.164-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-68082175 days apartlibceph: fix two unsafe bare decodes in decode_lockers()39Monitor
- CVE-2026-68160177 days apartceph: fix pre-auth out-of-bounds read on snaptrace in ceph_handle_caps()39Monitor
- CVE-2026-68388177 days apartsmb/client: handle overlapping allocated ranges in fallocate39Monitor
- CVE-2026-72084182 days apartscsi: target: Bound PR-OUT TransportID parsing to the received buffer39Monitor
- CVE-2026-64551163 days apartsctp: validate STALE_COOKIE cause length before reading staleness36Monitor
- CVE-2026-68343177 days apartsmb: client: validate DFS referral PathConsumed36Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/2447edc367800ba914acf7ddd5d250416b45fb31
- git.kernel.org/stable/c/31a7a0bbeb006bac2d9c81a2874825025214b6d8
- git.kernel.org/stable/c/34b56c16efd61325d80bf1d780d0e176be662f59
- git.kernel.org/stable/c/77611cab5bdfff7a070ae574bbfba20a1de99d1b
- git.kernel.org/stable/c/f89e33c9c37f0001b730e23b3b05ab7b1ecface2
Vendor advisories and official records. Exploit/PoC links are deliberately left out.