Linux Kernel up to 6.18.52 dpaa2-switch dpaa2_switch_rx memory corruption

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.5 | $5k-$25k | 0.41- |
Summary
A vulnerability was found in Linux Kernel up to 5.15.221/6.1.188/6.6.157/6.12.110/6.18.52. It has been rated as very critical. This vulnerability affects the function dpaa2_switch_rx of the component dpaa2-switch. The manipulation leads to memory corruption.
This vulnerability is uniquely identified as CVE-2026-98911. The attack is possible to be carried out remotely. No exploit exists.
Upgrading the affected component is advised.
Details
A vulnerability, which was classified as very critical, has been found in Linux Kernel up to 5.15.221/6.1.188/6.6.157/6.12.110/6.18.52. This issue affects the function dpaa2_switch_rx of the component dpaa2-switch. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
In the Linux kernel, the following vulnerability has been resolved: dpaa2-switch: fix the error path in dpaa2_switch_rx() In case of an error in dpaa2_switch_rx(), the dpaa2_switch_free_fd() function is called in order to free the FD. This is incorrect since the dpaa2_switch_free_fd() is intended to be used on Tx frame descriptors, meaning that it expects in the software annotation area of the FD data to find a valid skb pointer on which to call dev_kfree_skb(). Fix this by extracting the dma_unmap_page() from dpaa2_switch_build_linear_skb() directly into the dpaa2_switch_rx() function. This allows us to directly use free_pages() in case of an error before an SKB was created and kfree_skb() afterwards.
It is possible to read the advisory at git.kernel.org. The identification of this vulnerability is CVE-2026-98911 since 09/25/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 10/23/2026).
Upgrading to version 5.15.222, 6.1.189, 6.6.158, 6.12.111 or 6.18.53 eliminates this vulnerability. Applying the patch 791068c962469af0090e1a1ee63657fb9eef40db/ee54f8d7e642c44cfcc2dcb390b4c50e145d81b8/259ad6093204b999d41e7e6d0ad90ef9a71a44ab/f4ceb8e3d6d5becb4cda7a7098a8638e18c835a1/fa232b4496cb59503ae5108c756cbe10e59b0bc3/74c1c9f5c0c30bbd0c2cf87b6e3507e7ea46c13d is able to eliminate this problem. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-108867). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
- 5.15.221
- 6.1.188
- 6.6.157
- 6.12.110
- 6.18.0
- 6.18.1
- 6.18.2
- 6.18.3
- 6.18.4
- 6.18.5
- 6.18.6
- 6.18.7
- 6.18.8
- 6.18.9
- 6.18.10
- 6.18.11
- 6.18.12
- 6.18.13
- 6.18.14
- 6.18.15
- 6.18.16
- 6.18.17
- 6.18.18
- 6.18.19
- 6.18.20
- 6.18.21
- 6.18.22
- 6.18.23
- 6.18.24
- 6.18.25
- 6.18.26
- 6.18.27
- 6.18.28
- 6.18.29
- 6.18.30
- 6.18.31
- 6.18.32
- 6.18.33
- 6.18.34
- 6.18.35
- 6.18.36
- 6.18.37
- 6.18.38
- 6.18.39
- 6.18.40
- 6.18.41
- 6.18.42
- 6.18.43
- 6.18.44
- 6.18.45
- 6.18.46
- 6.18.47
- 6.18.48
- 6.18.49
- 6.18.50
- 6.18.51
- 6.18.52
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.9VulDB Meta Temp Score: 9.5
VulDB Base Score: 9.9
VulDB Temp Score: 9.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 5.15.222/6.1.189/6.6.158/6.12.111/6.18.53
Patch: 791068c962469af0090e1a1ee63657fb9eef40db/ee54f8d7e642c44cfcc2dcb390b4c50e145d81b8/259ad6093204b999d41e7e6d0ad90ef9a71a44ab/f4ceb8e3d6d5becb4cda7a7098a8638e18c835a1/fa232b4496cb59503ae5108c756cbe10e59b0bc3/74c1c9f5c0c30bbd0c2cf87b6e3507e7ea46c13d
Timeline
09/25/2026 CVE reserved10/23/2026 Advisory disclosed
10/23/2026 VulDB entry created
10/23/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2026-98911 (🔒)
GCVE (CVE): GCVE-0-2026-98911
GCVE (VulDB): GCVE-100-425747
EUVD: 🔒
Entry
Created: 10/23/2026 14:55Updated: 10/23/2026 15:45
Changes: 10/23/2026 14:55 (59), 10/23/2026 15:45 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.