Skip to content
Noroxi
CVE.org (no NVD analysis yet)· CNA Linux

CVE-2026-98189: wifi: wilc1000: fix RX buffer OOB-write in wilc_wlan_handle_isr_ext()

Noroxi assessment

Priority: Monitor (action score 0/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.17% (FIRST EPSS).
  • Fixed version: Linux Linux 14dcf4c3d74c878175b19d3da5986f83f26b1dd5, 304a5d72a04a3979a6434088c8d9c5172c2a908e, 3ddb88e237bc1e59fd37b1cf369f3b6c2dedae26; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1.

Low priority for now. Upgrade to Linux Linux 14dcf4c3d74c878175b19d3da5986f83f26b1dd5, 304a5d72a04a3979a6434088c8d9c5172c2a908e, 3ddb88e237bc1e59fd37b1cf369f3b6c2dedae26; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1 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: 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.

—No exploit Fix available
Published
Oct 6, 2026
Updated
Oct 19, 2026
EPSS
0.1% · 7th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

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.

Follow CVE-2026-98189

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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

    • 4.2affected
    • c5c77ba18ea66aa05441c71e38473efb787705a4 and later · before 3ddb88e237bc1e59fd37b1cf369f3b6c2dedae26affected · git
    • c5c77ba18ea66aa05441c71e38473efb787705a4 and later · before 9f6a276ade936a8803f9f3df217c2368944dc321affected · git
    • c5c77ba18ea66aa05441c71e38473efb787705a4 and later · before aeb44a456d126d89863230eef0187e77e6441995affected · git
    • c5c77ba18ea66aa05441c71e38473efb787705a4 and later · before 612ed9224eae70c53c0c88cb0990e0f9b709280aaffected · git
    • c5c77ba18ea66aa05441c71e38473efb787705a4 and later · before 304a5d72a04a3979a6434088c8d9c5172c2a908eaffected · git
    • c5c77ba18ea66aa05441c71e38473efb787705a4 and later · before 4f86fb6f9dce04f697da85806ad96a932fc2f079affected · git
    • c5c77ba18ea66aa05441c71e38473efb787705a4 and later · before 14dcf4c3d74c878175b19d3da5986f83f26b1dd5affected · git
    • c5c77ba18ea66aa05441c71e38473efb787705a4 and later · before c1ba7f7f18465e259cf1b4d9c73fc73853d7f790affected · git
    • before 4.2not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.190-16.1.190-1
Debian:12linux-6.12before 6.12.113-1~deb12u16.12.113-1~deb12u1
Debian:13linuxbefore 6.12.113-16.12.113-1
Debian:14linuxbefore 7.2.8-17.2.8-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-98187Oct 6, 2026 · wifi: p54: require a full exp_if record in PDR_INTERFACE_LIST
    0Monitor
  • ← EarlierCVE-2026-98188Oct 6, 2026 · wifi: p54: validate curve data length in the calibration curve converters
    0Monitor
  • Later →CVE-2026-98190Oct 6, 2026 · wifi: wilc1000: fix out-of-bounds read in P2P public action frames
    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 / packageFixed versionSource
Linux Linux14dcf4c3d74c878175b19d3da5986f83f26b1dd5Vendor (CNA)
Linux Linux304a5d72a04a3979a6434088c8d9c5172c2a908eVendor (CNA)
Linux Linux3ddb88e237bc1e59fd37b1cf369f3b6c2dedae26Vendor (CNA)
Linux Linux4f86fb6f9dce04f697da85806ad96a932fc2f079Vendor (CNA)
Linux Linux612ed9224eae70c53c0c88cb0990e0f9b709280aVendor (CNA)
Linux Linux9f6a276ade936a8803f9f3df217c2368944dc321Vendor (CNA)
Linux Linuxaeb44a456d126d89863230eef0187e77e6441995Vendor (CNA)
Linux Linuxc1ba7f7f18465e259cf1b4d9c73fc73853d7f790Vendor (CNA)
azl3 kernel 6.6.157.1-1 on Azure Linux 3.06.6.158.1-1 · Release NotesMicrosoft (MSRC)
debian:linux6.1.190-1 · Debian:12Package registry (OSV)
debian:linux6.12.113-1 · Debian:13Package registry (OSV)
debian:linux7.2.8-1 · Debian:14Package registry (OSV)
debian:linux-6.126.12.113-1~deb12u1 · Debian:12Package 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.

  1. Published
  2. Fix recordedsame day
  3. TodayNov 4, 2026+29 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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 researchers

Finders, 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

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

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

  1. Exploit maturity— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records