Linux Kernel up to 7.1.7 mac80211 ieee80211_process_rx_twt_action length input validation

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.5 | $5k-$25k | 4.03 |
Summary
A vulnerability identified as very critical has been detected in Linux Kernel up to 7.1.7. This affects the function ieee80211_process_rx_twt_action of the component mac80211. Performing a manipulation of the argument length results in input validation.
This vulnerability is reported as CVE-2026-80722. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability classified as very critical has been found in Linux Kernel up to 7.1.7. This affects the function ieee80211_process_rx_twt_action of the component mac80211. The manipulation of the argument length with an unknown input leads to a input validation vulnerability. CWE is classifying the issue as CWE-20. 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: validate individual TWT params before driver setup ieee80211_process_rx_twt_action() only partially validates a received S1G TWT setup frame before queueing it. An individual agreement can therefore reach ieee80211_s1g_rx_twt_setup() with twt->length too short for the full struct ieee80211_twt_params. The individual path passes twt to drv_add_twt_setup(). Both the tracepoint and the driver callback consume the complete parameters block, not merely req_type. Do not pass a short individual agreement to the driver. Broadcast agreements remain unchanged because they are rejected locally after accessing only req_type. [edit commit message to not overclaim lack of validation nor understate driver impact]
The advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2026-80722 since 08/26/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 08/28/2026).
Upgrading to version 5.15.216, 6.1.183, 6.6.151, 6.12.103, 6.18.44 or 7.1.8 eliminates this vulnerability. Applying the patch 92fcd0f30dc8e51f252589b082d46851d295cc1a/09d60d1f72e6598241490eb6c4e97245af895c09/ff558072d199c1d641d1561da622e67f780514de/ade9e2f0f7f4d3089600ac2af8ef0b91746f923b/b558e07708d886acfcf4b0391ed7a8546e81d326/47fb04c3826e1f90271d405523043d6708b9072a/0502d5077e419427d80f4d46ba95d0067f5fb916 is able to eliminate this problem.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-67457). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
- 5.15.215
- 6.1.182
- 6.6.150
- 6.12.102
- 6.18.0
- 6.18.1
- 6.18.2
- 6.18.3
- 6.18.4
- 6.18.5
- 6.18.6
- 6.18.7
- 6.18.8
- 6.18.9
- 6.18.10
- 6.18.11
- 6.18.12
- 6.18.13
- 6.18.14
- 6.18.15
- 6.18.16
- 6.18.17
- 6.18.18
- 6.18.19
- 6.18.20
- 6.18.21
- 6.18.22
- 6.18.23
- 6.18.24
- 6.18.25
- 6.18.26
- 6.18.27
- 6.18.28
- 6.18.29
- 6.18.30
- 6.18.31
- 6.18.32
- 6.18.33
- 6.18.34
- 6.18.35
- 6.18.36
- 6.18.37
- 6.18.38
- 6.18.39
- 6.18.40
- 6.18.41
- 6.18.42
- 6.18.43
- 7.1.0
- 7.1.1
- 7.1.2
- 7.1.3
- 7.1.4
- 7.1.5
- 7.1.6
- 7.1.7
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 10.0VulDB Meta Temp Score: 9.5
VulDB Base Score: 10.0
VulDB Temp Score: 9.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Input validationCWE: CWE-20
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 5.15.216/6.1.183/6.6.151/6.12.103/6.18.44/7.1.8
Patch: 92fcd0f30dc8e51f252589b082d46851d295cc1a/09d60d1f72e6598241490eb6c4e97245af895c09/ff558072d199c1d641d1561da622e67f780514de/ade9e2f0f7f4d3089600ac2af8ef0b91746f923b/b558e07708d886acfcf4b0391ed7a8546e81d326/47fb04c3826e1f90271d405523043d6708b9072a/0502d5077e419427d80f4d46ba95d0067f5fb916
Timeline
08/26/2026 CVE reserved08/28/2026 Advisory disclosed
08/28/2026 VulDB entry created
08/28/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2026-80722 (🔒)
GCVE (CVE): GCVE-0-2026-80722
GCVE (VulDB): GCVE-100-396657
EUVD: 🔒
Entry
Created: 08/28/2026 11:10Updated: 08/28/2026 11:31
Changes: 08/28/2026 11:10 (60), 08/28/2026 11:31 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.