-
Bug
-
Resolution: Done-Errata
-
Undefined
-
rhel-9.4
-
None
-
libnvme-1.6-1.el9
-
None
-
Important
-
rhel-sst-storage-io
-
ssg_filesystems_storage_and_HA
-
10
-
16
-
None
-
QE ack, Dev ack
-
False
-
-
None
-
Red Hat Enterprise Linux
-
None
-
-
All
-
None
A number of stack smashing issues were reported across several userspace components that use libnvme, on all distros across variety of PCIe NVMe drives.
As explained in https://github.com/linux-nvme/nvme-cli/pull/2051:
The kernel supports since v5.2 direct mapped DMA buffers to userspace.
Up to this point a bounce buffer was involved. Because the buffers are
now directly accessed by the device, the rules of alignment also apply
for the payloads.Furthermore, ensure that the buffer is a multiple of 4k, because there
are devices on the market which will always transfer a multiple of 4k,
even if we ask for less, e.g 512 bytes. This avoid stack smashes.
The work is tracked upstream in https://github.com/linux-nvme/libnvme/issues/684 and https://github.com/linux-nvme/libnvme/issues/728.
The most important fix to backport in 9.4 is https://github.com/linux-nvme/libnvme/pull/727. This one has been tested by the community on affected drives.
There are more related fixes that haven't gone through such extensive testing and may not be as important: https://github.com/linux-nvme/libnvme/pull/731
- blocks
-
RHEL-13127 Backport stack-smashing fixes
- Closed
-
RHEL-8037 dasbus.error.DBusError: No such interface “org.freedesktop.DBus.Properties” on object at path /org/fedoraproject/Anaconda/Modules/Storage/Task/1
- Closed
- links to
-
RHEA-2023:123579 Update libnvme
- mentioned on