Skip to content
Systems

CVE-2026-64441

8.8
High
EPSS 0.26%Patch availableJul 27, 2026

OOB reads in rtl8723bs Wi‑Fi driver IE parsing allowing remote crash or memory disclosure

common questions

Is CVE-2026-64441 being exploited?

Not confirmed. CVE-2026-64441 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.26% probability of exploitation in the next 30 days.

How severe is CVE-2026-64441?

CVE-2026-64441 is rated High with a CVSS score of 8.8. 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-64441?

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

What does CVE-2026-64441 affect?

CVE-2026-64441 affects Linux kernel (staging/rtl8723bs driver), Devices using Realtek RTL8723BS on Linux. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-64441?

Apply the Linux kernel update that fixes rtl8723bs; restrict untrusted Wi‑Fi; reboot affected hosts.

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 using Realtek RTL8723BS on Linux
impact

Crafted Wi‑Fi IEs can trigger kernel out-of-bounds reads, enabling remote kernel crash (DoS) and potential kernel memory disclosure; may aid privilege escalation.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= 554c0a3abf216c991c5ebddcdb2c08689ecd290b and < efa27d487abcdec79669a60a6d94d5d6eceb7c1d
  • affected>= 554c0a3abf216c991c5ebddcdb2c08689ecd290b and < 2ea1ce30ead61589214240e8d33d96310fd613e5
  • affected>= 554c0a3abf216c991c5ebddcdb2c08689ecd290b and < b27ecba3196f6c14e3809595ebd69c0c2392512a
  • affected>= 554c0a3abf216c991c5ebddcdb2c08689ecd290b and < 6ab1161e539fb7a1c8b35ff5a6ced4702e855b9c
  • affected>= 554c0a3abf216c991c5ebddcdb2c08689ecd290b and < 4b51ee8a40fe47864197d73cc02b191de7a6b072
  • affected>= 554c0a3abf216c991c5ebddcdb2c08689ecd290b and < 729c4e72563bda0f1725db1db9ea08df06f41d9b
  • affected>= 554c0a3abf216c991c5ebddcdb2c08689ecd290b and < 1463ca3ec6601cbb097d8d87dbf5dcf1cb86a344
  • 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.97 and <= 6.12.*, >= 6.18.40 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