Linux Kernel up to 6.18.21/6.19.11 scsi fd_execute_rw_aio ki_write_stream missing initialization

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.6 | $5k-$25k | 0.00 |
Summary
A vulnerability was found in Linux Kernel up to 6.18.21/6.19.11 and classified as critical. Impacted is the function fd_execute_rw_aio of the component scsi. Such manipulation of the argument ki_write_stream leads to missing initialization.
This vulnerability is listed as CVE-2026-43055. There is no available exploit.
It is suggested to upgrade the affected component.
Details
A vulnerability was found in Linux Kernel up to 6.18.21/6.19.11. It has been rated as critical. Affected by this issue is the function fd_execute_rw_aio of the component scsi. The manipulation of the argument ki_write_stream with an unknown input leads to a missing initialization vulnerability. Using CWE to declare the problem leads to CWE-456. The product does not initialize critical variables, which causes the execution environment to use unexpected values. Impacted is confidentiality, integrity, and availability. CVE summarizes:
In the Linux kernel, the following vulnerability has been resolved: scsi: target: file: Use kzalloc_flex for aio_cmd The target_core_file doesn't initialize the aio_cmd->iocb for the ki_write_stream. When a write command fd_execute_rw_aio() is executed, we may get a bogus ki_write_stream value, causing unintended write failure status when checking iocb->ki_write_stream > max_write_streams in the block device. Let's just use kzalloc_flex when allocating the aio_cmd and let ki_write_stream=0 to fix this issue.
The advisory is shared for download at git.kernel.org. This vulnerability is handled as CVE-2026-43055 since 05/01/2026. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 05/01/2026).
Upgrading to version 6.18.22 or 6.19.12 eliminates this vulnerability. Applying the patch ce54802fe6bb78eb0feffc66fed6a45d41ffc3ab/4eaff1728d0e69b95933412241bbccf4f797dba8/01f784fc9d0ab2a6dac45ee443620e517cb2a19b 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.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Vendor
Name
Version
- 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: Missing initializationCWE: CWE-456 / CWE-453
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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 6.18.22/6.19.12
Patch: ce54802fe6bb78eb0feffc66fed6a45d41ffc3ab/4eaff1728d0e69b95933412241bbccf4f797dba8/01f784fc9d0ab2a6dac45ee443620e517cb2a19b
Timeline
05/01/2026 Advisory disclosed05/01/2026 CVE reserved
05/01/2026 VulDB entry created
05/01/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2026-43055 (🔒)
GCVE (CVE): GCVE-0-2026-43055
GCVE (VulDB): GCVE-100-360728
Entry
Created: 05/01/2026 18:17Changes: 05/01/2026 18:17 (60)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.