aboutsummaryrefslogtreecommitdiffstats
path: root/net/unix/sysctl_net_unix.c
diff options
context:
space:
mode:
authorNiklas Cassel <[email protected]>2025-01-27 15:43:04 +0000
committerNiklas Cassel <[email protected]>2025-01-28 10:44:47 +0000
commit6e74e53b34b6dec5a50e1404e2680852ec6768d2 (patch)
treec94189af9e12d3031eefb79b0aef0403e79f6486 /net/unix/sysctl_net_unix.c
parentata: libata-core: Add ATA_QUIRK_NOLPM for Samsung SSD 870 QVO drives (diff)
downloadkernel-6e74e53b34b6dec5a50e1404e2680852ec6768d2.tar.gz
kernel-6e74e53b34b6dec5a50e1404e2680852ec6768d2.zip
ata: libata-sff: Ensure that we cannot write outside the allocated buffer
reveliofuzzing reported that a SCSI_IOCTL_SEND_COMMAND ioctl with out_len set to 0xd42, SCSI command set to ATA_16 PASS-THROUGH, ATA command set to ATA_NOP, and protocol set to ATA_PROT_PIO, can cause ata_pio_sector() to write outside the allocated buffer, overwriting random memory. While a ATA device is supposed to abort a ATA_NOP command, there does seem to be a bug either in libata-sff or QEMU, where either this status is not set, or the status is cleared before read by ata_sff_hsm_move(). Anyway, that is most likely a separate bug. Looking at __atapi_pio_bytes(), it already has a safety check to ensure that __atapi_pio_bytes() cannot write outside the allocated buffer. Add a similar check to ata_pio_sector(), such that also ata_pio_sector() cannot write outside the allocated buffer. Cc: [email protected] Reported-by: reveliofuzzing <[email protected]> Closes: https://lore.kernel.org/linux-ide/CA+-ZZ_jTgxh3bS7m+KX07_EWckSnW3N2adX3KV63y4g7M4CZ2A@mail.gmail.com/ Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Niklas Cassel <[email protected]>
Diffstat (limited to 'net/unix/sysctl_net_unix.c')
0 files changed, 0 insertions, 0 deletions