Linux: Improper Validation of Array Index
CVE-2026-43110 is a high-severity improper validation of array index vulnerability in Linux, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited from the same local network by an unauthenticated attacker, without any action from a user. The record lists versions b329fbcf075949a038045d8e9b86ae3d5bbd8a54, 2ae3ccb78c0a9ef5ee3d80d02ab319ac1d5af734, 9c81bcc2c695e0082012a2a3d36a0eefaa51579c as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.27% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Linux to b329fbcf075949a038045d8e9b86ae3d5bbd8a54 or 2ae3ccb78c0a9ef5ee3d80d02ab319ac1d5af734 or 9c81bcc2c695e0082012a2a3d36a0eefaa51579c or 3ec7437e9d11374105c2c4e47ae671537729d7e6, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.6.136 or 6.12.83 or 6.18.24 or 6.19.14, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 2880b86859967af710c72f7d34fb421a86a71e22 up to, but not including, b329fbcf075949a038045d8e9b86ae3d5bbd8a54; 2880b86859967af710c72f7d34fb421a86a71e22 up to, but not including, 2ae3ccb78c0a9ef5ee3d80d02ab319ac1d5af734; 2880b86859967af710c72f7d34fb421a86a71e22 up to, but not including, 9c81bcc2c695e0082012a2a3d36a0eefaa51579c; 2880b86859967af710c72f7d34fb421a86a71e22 up to, but not including, 3ec7437e9d11374105c2c4e47ae671537729d7e6; 2880b86859967af710c72f7d34fb421a86a71e22 up to, but not including, 9fca68c2512a362cad258e4df12a307bb2ee4b8e; 2880b86859967af710c72f7d34fb421a86a71e22 up to, but not including, 1ae1e1caa428844e481231f6dbe9b4f475f1d52d; 2880b86859967af710c72f7d34fb421a86a71e22 up to, but not including, b427c2b05222db36d32ee141609de6128e9091bb; 2880b86859967af710c72f7d34fb421a86a71e22 up to, but not including, 304950a467d83678bd0b0f46331882e2ac23b12d; and 1 more ranges | b329fbcf075949a038045d8e9b86ae3d5bbd8a54, 2ae3ccb78c0a9ef5ee3d80d02ab319ac1d5af734, 9c81bcc2c695e0082012a2a3d36a0eefaa51579c, 3ec7437e9d11374105c2c4e47ae671537729d7e6, 9fca68c2512a362cad258e4df12a307bb2ee4b8e, 1ae1e1caa428844e481231f6dbe9b4f475f1d52d |
| Siemens | SIMATIC S7-1500 TM MFP - GNU/Linux subsystem | all versions | Not stated |
| Linux | Linux Kernel | 3.9 up to, but not including, 6.6.136; 6.7 up to, but not including, 6.12.83; 6.13 up to, but not including, 6.18.24; 6.19 up to, but not including, 6.19.14; 7.0 | 6.6.136, 6.12.83, 6.18.24, 6.19.14 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- AdjacentThe attacker must be on the same local network segment.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by CNA.
Official description
In the Linux kernel, the following vulnerability has been resolved: wifi: brcmfmac: validate bsscfg indices in IF events brcmf_fweh_handle_if_event() validates the firmware-provided interface index before it touches drvr->iflist[], but it still uses the raw bsscfgidx field as an array index without a matching range check. Reject IF events whose bsscfg index does not fit in drvr->iflist[] before indexing the interface array. [add missing wifi prefix]
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Validation of Array Index
The product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array.
How developers prevent this class of flaw
- Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
- Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, Ada allows the programmer to constrain the values of a variable and languages such as Java and Ruby will allow the programmer to handle exceptions when an out-of-bounds index is accessed.
- Use a CPU and operating system that offers Data Execution Protection (using hardware NX or XD bits) or the equivalent techniques that simulate this feature in software, such as PaX. These techniques ensure that any instruction executed is exclusively at a memory address that is part of the code segment. For more information on these techniques see D3-PSEP (Process Segment Execution Prevention) from D3FEND.
More Improper Validation of Array Index vulnerabilities (CWE-129)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- git.kernel.org/stable/c/1ae1e1caa428844e481231f6dbe9b4f475f1d52d
- git.kernel.org/stable/c/304950a467d83678bd0b0f46331882e2ac23b12d
- git.kernel.org/stable/c/3ec7437e9d11374105c2c4e47ae671537729d7e6
- git.kernel.org/stable/c/9fca68c2512a362cad258e4df12a307bb2ee4b8e
- git.kernel.org/stable/c/b427c2b05222db36d32ee141609de6128e9091bb
Other references
Recent Improper Validation of Array Index vulnerabilities
- 8.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.7 High severity
- 9.8 Critical severity
Spotted an error? Tell us.