CyberSecBulletin
CVE-2026-43176NVD status: Modified

In the Linux kernel, the following vulnerability has been resolved: wifi: rtw89: pci: validate…

Published Updated By the CyberSecBulletin desk

CVE-2026-43176 is a high-severity improper input validation vulnerability in Linux, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited from the same local network by an unauthenticated attacker, without any action from a user. The record lists versions ebeaa3b24ba568ff8505165f954dba15cc53e4b3, 3e8a88b5e8b3506d9c5e031a65ba65ce9a0683a3, 5f93d611b33a05bd03d6843c8efe8cb6a1992620 as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.24% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Linux to ebeaa3b24ba568ff8505165f954dba15cc53e4b3 or 3e8a88b5e8b3506d9c5e031a65ba65ce9a0683a3 or 5f93d611b33a05bd03d6843c8efe8cb6a1992620, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 6.18.16 or 6.19.6, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux110f3c11f440d78ef8a181f75456e24e428f69e4 up to, but not including, ebeaa3b24ba568ff8505165f954dba15cc53e4b3; 110f3c11f440d78ef8a181f75456e24e428f69e4 up to, but not including, 3e8a88b5e8b3506d9c5e031a65ba65ce9a0683a3; 110f3c11f440d78ef8a181f75456e24e428f69e4 up to, but not including, 5f93d611b33a05bd03d6843c8efe8cb6a1992620; 6.18ebeaa3b24ba568ff8505165f954dba15cc53e4b3, 3e8a88b5e8b3506d9c5e031a65ba65ce9a0683a3, 5f93d611b33a05bd03d6843c8efe8cb6a1992620
LinuxLinux Kernel6.18 up to, but not including, 6.18.16; 6.19 up to, but not including, 6.19.66.18.16, 6.19.6

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
AdjacentThe attacker must be on the same local network segment.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by CNA.

Official description

In the Linux kernel, the following vulnerability has been resolved: wifi: rtw89: pci: validate release report content before using for RTL8922DE The commit 957eda596c76 ("wifi: rtw89: pci: validate sequence number of TX release report") does validation on existing chips, which somehow a release report of SKB becomes malformed. As no clear cause found, add rules ahead for RTL8922DE to avoid crash if it happens.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Input Validation

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How developers prevent this class of flaw

  • Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build recognizers for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of allowing parser code to be scattered throughout the program, where it could be subject to errors or inconsistencies that create weaknesses.
  • Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
  • Understand all the potential areas where untrusted inputs can enter the product, including but not limited to: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.

More Improper Input Validation vulnerabilities (CWE-20)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Improper Input Validation vulnerabilities

Spotted an error? Tell us.