CVE-2026-43113: wifi: wl1251: validate packet IDs before indexing tx_frames
Noroxi assessment
Priority: Monitor (action score 35/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.24% (FIRST EPSS).
- Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0fd56fad9c56356e7fa7a7c52e7ecbf807a44eb0, 26ee518695c484f75e3606d631278e84bd24ae02, 6509dbece7339dbc8980c706b9d623119a6de105.
Low priority for now. Upgrade to Linux Linux 0fd56fad9c56356e7fa7a7c52e7ecbf807a44eb0, 26ee518695c484f75e3606d631278e84bd24ae02, 6509dbece7339dbc8980c706b9d623119a6de105 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: wifi: wl1251: validate packet IDs before indexing tx_frames wl1251_tx_packet_cb() uses the firmware completion ID directly to index the fixed 16-entry wl->tx_frames[] array. The ID is a raw u8 from the completion block, and the callback does not currently verify that it fits the array before dereferencing it. Reject completion IDs that fall outside wl->tx_frames[] and keep the existing NULL check in the same guard. This keeps the fix local to the trust boundary and avoids touching the rest of the completion flow.
- Published
- May 6, 2026
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- CWE-476
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.8
- 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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel2.6.31 and later · before 6.6.136
- linux linux kernel6.7 and later · before 6.12.83
- linux linux kernel6.13 and later · before 6.18.24
- linux linux kernel6.19 and later · before 6.19.14
- linux linux kernel7.0
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
- 2.6.31affected
- 2f01a1f58889fbfeb68b1bc1b52e4197f3333490 and later · before 6509dbece7339dbc8980c706b9d623119a6de105affected · git
- 2f01a1f58889fbfeb68b1bc1b52e4197f3333490 and later · before a8a11a876f0a97061ee5d9e61d0f5a0df7e241c7affected · git
- 2f01a1f58889fbfeb68b1bc1b52e4197f3333490 and later · before e0dc1ad870d6788b049bfe1511ac75b2333a7550affected · git
- 2f01a1f58889fbfeb68b1bc1b52e4197f3333490 and later · before b6ba1eacf276063ebeefbbae8056043c24f2efafaffected · git
- 2f01a1f58889fbfeb68b1bc1b52e4197f3333490 and later · before df15adc692a802636dd3f258fc7cca8bf7a0ed9aaffected · git
- 2f01a1f58889fbfeb68b1bc1b52e4197f3333490 and later · before 8d7465be5163a923ee5d7459719ef5a021c1584aaffected · git
- 2f01a1f58889fbfeb68b1bc1b52e4197f3333490 and later · before 26ee518695c484f75e3606d631278e84bd24ae02affected · git
- 2f01a1f58889fbfeb68b1bc1b52e4197f3333490 and later · before 0fd56fad9c56356e7fa7a7c52e7ecbf807a44eb0affected · git
- before 2.6.31not 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.176-1 | 6.1.176-1 |
| Debian:13 | linux | before 6.12.85-1 | 6.12.85-1 |
| Debian:14 | linux | before 6.19.14-1 | 6.19.14-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-43106May 6, 2026 · cachefiles: fix incorrect dentry refcount in cachefiles_cull()31Monitor
- ← EarlierCVE-2026-43108May 6, 2026 · soc: qcom: pd-mapper: Fix element length in servreg_loc_pfr_req_ei22Monitor
- Later →CVE-2026-43121May 6, 2026 · io_uring/zcrx: fix user_ref race between scrub and refill paths18Monitor
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 | 0fd56fad9c56356e7fa7a7c52e7ecbf807a44eb0 | Vendor (CNA) |
| Linux Linux | 26ee518695c484f75e3606d631278e84bd24ae02 | Vendor (CNA) |
| Linux Linux | 6509dbece7339dbc8980c706b9d623119a6de105 | Vendor (CNA) |
| Linux Linux | 8d7465be5163a923ee5d7459719ef5a021c1584a | Vendor (CNA) |
| Linux Linux | a8a11a876f0a97061ee5d9e61d0f5a0df7e241c7 | Vendor (CNA) |
| Linux Linux | b6ba1eacf276063ebeefbbae8056043c24f2efaf | Vendor (CNA) |
| Linux Linux | df15adc692a802636dd3f258fc7cca8bf7a0ed9a | Vendor (CNA) |
| Linux Linux | e0dc1ad870d6788b049bfe1511ac75b2333a7550 | Vendor (CNA) |
| debian:linux | 6.1.176-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.
No nightly-computed relations.
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 on the same network segment can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
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
- Adjacent
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-476 · NULL Pointer DereferenceCVSS vector
CVSS:3.1/AV:A/AC:L/PR:N/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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/26ee518695c484f75e3606d631278e84bd24ae02
- git.kernel.org/stable/c/6509dbece7339dbc8980c706b9d623119a6de105
- git.kernel.org/stable/c/8d7465be5163a923ee5d7459719ef5a021c1584a
- git.kernel.org/stable/c/a8a11a876f0a97061ee5d9e61d0f5a0df7e241c7
- git.kernel.org/stable/c/b6ba1eacf276063ebeefbbae8056043c24f2efaf
- git.kernel.org/stable/c/df15adc692a802636dd3f258fc7cca8bf7a0ed9a
- git.kernel.org/stable/c/e0dc1ad870d6788b049bfe1511ac75b2333a7550
Vendor advisories and official records. Exploit/PoC links are deliberately left out.