CVE-2026-98189
wifi: wilc1000: fix RX buffer OOB-write in wilc_wlan_handle_isr_ext()
No known exploitation. EPSS puts it in the 7th percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ c5c77ba18ea66aa05441c71e38473efb787705a4, < 3ddb88e237bc1e59fd37b1cf369f3b6c2dedae26Upgrade to: 3ddb88e237bc1e59fd37b1cf369f3b6c2dedae26Affected: ≥ c5c77ba18ea66aa05441c71e38473efb787705a4, < 9f6a276ade936a8803f9f3df217c2368944dc321Upgrade to: 9f6a276ade936a8803f9f3df217c2368944dc321Affected: ≥ c5c77ba18ea66aa05441c71e38473efb787705a4, < aeb44a456d126d89863230eef0187e77e6441995Upgrade to: aeb44a456d126d89863230eef0187e77e6441995Affected: ≥ c5c77ba18ea66aa05441c71e38473efb787705a4, < 612ed9224eae70c53c0c88cb0990e0f9b709280aUpgrade to: 612ed9224eae70c53c0c88cb0990e0f9b709280a + 4 more branchesStated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
In the Linux kernel, the following vulnerability has been resolved: wifi: wilc1000: fix RX buffer OOB-write in wilc_wlan_handle_isr_ext() wilc_wlan_handle_isr_ext() takes the RX transfer size from the device-reported interrupt status register (a 15-bit field shifted left by 2, up to 131068 bytes) and reads that many bytes from the device into rx_buffer, which is only WILC_RX_BUFF_SIZE (96K) large. The wrap check only handles the current offset; the size itself is never compared against the buffer, so a bogus SDIO device can make the driver OOB-write rx_buffer by up to ~32K with data it controls. The oversized transfer also leaves rx_buffer_offset past the end of the buffer, after which the unsigned wrap check stops working and the overflow can repeat. Drop any transfer whose size exceeds the RX buffer, acknowledging the data interrupt and re-arming the RX engine so the bogus frame is discarded and reception can continue. This also restores the rx_buffer_offset <= WILC_RX_BUFF_SIZE invariant the wrap check relies on. This is not expected to change driver behavior in most cases: without this check, an oversized transfer would most likely corrupt neighboring kernel memory instead of completing anyway, and the drop path performs the same interrupt acknowledgment and RX engine re-arming as the normal path, so subsequent transfers are received unaffected. Discovered by Atuin - Automated Vulnerability Discovery Engine.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.2% chance of exploitation activity in the next 30 days, which ranks it in the 7th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
2 events over 0 days, from the signal feeds we watch.
- Publishedrecord updated
Affected products
Sources
References in the record
- git.kernel.org/stable/c/3ddb88e237bc1e59fd37b1cf369f3b6c2dedae26
- git.kernel.org/stable/c/9f6a276ade936a8803f9f3df217c2368944dc321
- git.kernel.org/stable/c/aeb44a456d126d89863230eef0187e77e6441995
And 5 more references. See all after sign-in
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Linux, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI