Linux Kernel up to 6.19.11 Bluetooth enc_size stack-based overflow

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Linux Kernel up to 6.19.11 and classified as critical. This impacts an unknown function of the component Bluetooth. Such manipulation of the argument enc_size leads to stack-based overflow. This vulnerability is traded as CVE-2026-43020. There is no exploit available. It is suggested to upgrade the affected component.
Details
A vulnerability was found in Linux Kernel up to 6.19.11 and classified as critical. Affected by this issue is an unknown code of the component Bluetooth. The manipulation of the argument enc_size with an unknown input leads to a stack-based overflow vulnerability. Using CWE to declare the problem leads to CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). Impacted is confidentiality, integrity, and availability. CVE summarizes:
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: MGMT: validate LTK enc_size on load Load Long Term Keys stores the user-provided enc_size and later uses it to size fixed-size stack operations when replying to LE LTK requests. An enc_size larger than the 16-byte key buffer can therefore overflow the reply stack buffer. Reject oversized enc_size values while validating the management LTK record so invalid keys never reach the stored key state.
The advisory is shared for download at git.kernel.org. This vulnerability is handled as CVE-2026-43020 since 05/01/2026. The exploitation is known to be easy. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 05/31/2026).
The vulnerability scanner Nessus provides a plugin with the ID 318033 (RockyLinux 9 : kernel (RLSA-2026:21556)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 5.10.253, 5.15.203, 6.1.168, 6.6.134, 6.12.81, 6.18.22 or 6.19.12 eliminates this vulnerability. Applying the patch 0f37d1e65c6d71ad94ccfb5c602163c525db789d/257cdb960d8ff6d60bb6461b03c814b6cf0c9e64/c34577f517b556fb6ca173d45bf7e766ae2564ce/f71695e81f4cb428f3c7e2138eae88199005b52c/82f342b3b006ca1d65f4890c05f2ec32fcb808b6/50fb64defa72a3fecd0af1ca7c6b47b5c5c2b257/40ba329e8b4cd2fb11b0caf5e6a543ceaebb6009/b8dbe9648d69059cfe3a28917bfbf7e61efd7f15 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at Tenable (318033). Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
- 5.10.252
- 5.15.202
- 6.1.167
- 6.6.133
- 6.12.0
- 6.12.1
- 6.12.2
- 6.12.3
- 6.12.4
- 6.12.5
- 6.12.6
- 6.12.7
- 6.12.8
- 6.12.9
- 6.12.10
- 6.12.11
- 6.12.12
- 6.12.13
- 6.12.14
- 6.12.15
- 6.12.16
- 6.12.17
- 6.12.18
- 6.12.19
- 6.12.20
- 6.12.21
- 6.12.22
- 6.12.23
- 6.12.24
- 6.12.25
- 6.12.26
- 6.12.27
- 6.12.28
- 6.12.29
- 6.12.30
- 6.12.31
- 6.12.32
- 6.12.33
- 6.12.34
- 6.12.35
- 6.12.36
- 6.12.37
- 6.12.38
- 6.12.39
- 6.12.40
- 6.12.41
- 6.12.42
- 6.12.43
- 6.12.44
- 6.12.45
- 6.12.46
- 6.12.47
- 6.12.48
- 6.12.49
- 6.12.50
- 6.12.51
- 6.12.52
- 6.12.53
- 6.12.54
- 6.12.55
- 6.12.56
- 6.12.57
- 6.12.58
- 6.12.59
- 6.12.60
- 6.12.61
- 6.12.62
- 6.12.63
- 6.12.64
- 6.12.65
- 6.12.66
- 6.12.67
- 6.12.68
- 6.12.69
- 6.12.70
- 6.12.71
- 6.12.72
- 6.12.73
- 6.12.74
- 6.12.75
- 6.12.76
- 6.12.77
- 6.12.78
- 6.12.79
- 6.12.80
- 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.19.0
- 6.19.1
- 6.19.2
- 6.19.3
- 6.19.4
- 6.19.5
- 6.19.6
- 6.19.7
- 6.19.8
- 6.19.9
- 6.19.10
- 6.19.11
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.0VulDB Meta Temp Score: 7.6
VulDB Base Score: 8.0
VulDB Temp Score: 7.6
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: Stack-based overflowCWE: CWE-121 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 318033
Nessus Name: RockyLinux 9 : kernel (RLSA-2026:21556)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 5.10.253/5.15.203/6.1.168/6.6.134/6.12.81/6.18.22/6.19.12
Patch: 0f37d1e65c6d71ad94ccfb5c602163c525db789d/257cdb960d8ff6d60bb6461b03c814b6cf0c9e64/c34577f517b556fb6ca173d45bf7e766ae2564ce/f71695e81f4cb428f3c7e2138eae88199005b52c/82f342b3b006ca1d65f4890c05f2ec32fcb808b6/50fb64defa72a3fecd0af1ca7c6b47b5c5c2b257/40ba329e8b4cd2fb11b0caf5e6a543ceaebb6009/b8dbe9648d69059cfe3a28917bfbf7e61efd7f15
Timeline
05/01/2026 Advisory disclosed05/01/2026 CVE reserved
05/01/2026 VulDB entry created
05/31/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2026-43020 (🔒)
GCVE (CVE): GCVE-0-2026-43020
GCVE (VulDB): GCVE-100-360644
Entry
Created: 05/01/2026 17:43Updated: 05/31/2026 08:30
Changes: 05/01/2026 17:43 (59), 05/31/2026 08:30 (2)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.