Skip to content
Systems

CVE-2026-64444

8.1
High
EPSS 0.28%Patch availableJul 27, 2026

OOB read in rtl8723bs kernel Wi‑Fi driver lets a malicious AP crash or leak kernel memory.

common questions

Is CVE-2026-64444 being exploited?

Not confirmed. CVE-2026-64444 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.28% probability of exploitation in the next 30 days.

How severe is CVE-2026-64444?

CVE-2026-64444 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-64444?

Yes. A fix has been recorded for CVE-2026-64444. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-64444 affect?

CVE-2026-64444 affects Linux kernel (staging/rtl8723bs driver), Devices with Realtek RTL8723BS Wi‑Fi chipset, Embedded systems and laptops using rtl8723bs. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-64444?

Update to a patched kernel or apply vendor rtl8723bs fix immediately

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (staging/rtl8723bs driver)Devices with Realtek RTL8723BS Wi‑Fi chipsetEmbedded systems and laptops using rtl8723bs
impact

Malicious Wi‑Fi AP can trigger an out‑of‑bounds read during AssocResponse parsing, causing kernel memory disclosure or crash (DoS); may enable further exploitation.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= 554c0a3abf216c991c5ebddcdb2c08689ecd290b and < 889ca6000ac7fa73457b041848fcb08e0d51b809
  • affected>= 554c0a3abf216c991c5ebddcdb2c08689ecd290b and < 1a52a05471494546f955a58e8c170c0c796c52d5
  • affected>= 554c0a3abf216c991c5ebddcdb2c08689ecd290b and < 0406d746574e875d8778552eb674fcfbf5330bfb
  • affected>= 554c0a3abf216c991c5ebddcdb2c08689ecd290b and < 0970dd47726a57e52013594e9fbf667586eb3673
  • affected>= 554c0a3abf216c991c5ebddcdb2c08689ecd290b and < 04f612dc03427e0b1ac80a2611b5ac0ba93ac446
  • affected>= 554c0a3abf216c991c5ebddcdb2c08689ecd290b and < 7e7741c8315e4160aead00a60cdd6f81ab880717
  • affected>= 554c0a3abf216c991c5ebddcdb2c08689ecd290b and < f9654207e92283e0acac5d64fe5f8835383b5a23
  • affected4.12
vendor says fixed in< 4.12, >= 5.15.212 and <= 5.15.*, >= 6.1.178 and <= 6.1.*, >= 6.6.145 and <= 6.6.*, >= 6.12.96 and <= 6.12.*, >= 6.18.39 and <= 6.18.*, >= 7.1.4 and <= 7.1.*, >= 7.2 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free