Bug 2464418 (CVE-2026-43055) - CVE-2026-43055 kernel: scsi: target: file: Use kzalloc_flex for aio_cmd
Summary: CVE-2026-43055 kernel: scsi: target: file: Use kzalloc_flex for aio_cmd
Keywords:
Status: NEW
Alias: CVE-2026-43055
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-05-01 15:05 UTC by OSIDB Bzimport
Modified: 2026-05-01 18:59 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-05-01 15:05:45 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.