<?xml version="1.0" encoding="UTF-8"?>
<otherdata xmlns="http://linux.duke.edu/metadata/other" packages="7">
<package pkgid="0b9d9b6eac991c3cd747b94f7c16af11743b0d46b6d344b3e2259114914065c4bfc9bf60803c11987816621a832bf97f5f366c675b7cbce9cd0c611d0ece8430" name="openseachest" arch="aarch64">
  <version epoch="0" ver="25.05.3" rel="18.1"/>
  <changelog author="Daniel Wilhelmi &lt;jackdaniels96@gmail.com&gt;" date="1769515200">- Update to 25.05.3
  * Fixed incorrect null pointer check in TRIM function that caused the operation to exit with an error despite valid inputs
  * Fixed incorrect SCSI operation code lookup for pulling SCSI Defect lists
  * Fixed out of bounds access for FARM combined log pull. This wrote a null terminator one byte outside of the allocated memory. This can cause memory corruption, but no known impact otherwise.
  * Changed when the filesystem rescan or reread of the partition table happens to minimize cases where a drive may be disconnected from the OS due to being in an unreadable state. Examples: Sanitize failed state &amp; ATA security locked &amp; sector size change will put the drive into a different state that blocks media access or with different attributes that the OS does not know have changed. Attempting this rescan in this cases causes the drive to disconnect from the system and may have other side affects as well. All cases where this occurs not make sure the drive is in a state that it can complete this operation successfully.
  * Fixed logic in read/write testing (openSeaChest_Generic) for some USB devices that report an ATA passthrough maxlba of 0. Previous versions will always fail on these devices even if they are otherwise working properly.
  * Added tracking of when file locks/unlocks are requested on the device handle to keep things better synchronized between operations.
  * Fixed a crash that occurs in Windows for NVMe devices using an openfabrics NVMe compatible driver.
  * Rewrote logic to select SCSI media access commands with retries for reads, writes, verify, and synchronize cache (10byte vs 16byte versions)
  * Added detecting and selecting a compatible firmware update transfer length to improve compatibility with various devices that have limitations they can report. Default behavior was previously to download in 32k segments, but now it checks if this is compatible and selects a compatible size if limitations are reported. Users can still override this and select a segment size as needed.
  * Removed implied --disableImmediateResponse option when --fastformat x passed during --formatUnit y. This behavior can be selected as needed still, but it is no longer the default. This improves compatibility with some systems.
  * Fixed copyright date in the banner being dynamically set at compile time. This should be constant to when code was written/modified, not when it was compiled.
  * Fixed usage for GNU access attributes which were sometimes applied incorrectly. This can cause warnings or incorrect optimizations, however no known issues have been reported for this.
  * Increased usage of const for tDevice structures to be more clear about when modifications are being done or not. This did find a couple minor code bugs, but no known case of causing incorrect runtime issues.
  * Fixed compatibility with some newer C23 capable compilers
  * Fixed compatibility with msys2 mingw and clang environments. cygwin environment is not currently supported.</changelog>
</package>
<package pkgid="034e51af6a4cd58b309bbc0abd2341d0b56e79bcdaa31bf823adc9db6deea4e55151e3ee1fdf57400b332f43dda5c210b149542d6e89fb36d9580eb519eb0697" name="openseachest" arch="src">
  <version epoch="0" ver="25.05.3" rel="18.1"/>
  <changelog author="Daniel Wilhelmi &lt;jackdaniels96@gmail.com&gt;" date="1769515200">- Update to 25.05.3
  * Fixed incorrect null pointer check in TRIM function that caused the operation to exit with an error despite valid inputs
  * Fixed incorrect SCSI operation code lookup for pulling SCSI Defect lists
  * Fixed out of bounds access for FARM combined log pull. This wrote a null terminator one byte outside of the allocated memory. This can cause memory corruption, but no known impact otherwise.
  * Changed when the filesystem rescan or reread of the partition table happens to minimize cases where a drive may be disconnected from the OS due to being in an unreadable state. Examples: Sanitize failed state &amp; ATA security locked &amp; sector size change will put the drive into a different state that blocks media access or with different attributes that the OS does not know have changed. Attempting this rescan in this cases causes the drive to disconnect from the system and may have other side affects as well. All cases where this occurs not make sure the drive is in a state that it can complete this operation successfully.
  * Fixed logic in read/write testing (openSeaChest_Generic) for some USB devices that report an ATA passthrough maxlba of 0. Previous versions will always fail on these devices even if they are otherwise working properly.
  * Added tracking of when file locks/unlocks are requested on the device handle to keep things better synchronized between operations.
  * Fixed a crash that occurs in Windows for NVMe devices using an openfabrics NVMe compatible driver.
  * Rewrote logic to select SCSI media access commands with retries for reads, writes, verify, and synchronize cache (10byte vs 16byte versions)
  * Added detecting and selecting a compatible firmware update transfer length to improve compatibility with various devices that have limitations they can report. Default behavior was previously to download in 32k segments, but now it checks if this is compatible and selects a compatible size if limitations are reported. Users can still override this and select a segment size as needed.
  * Removed implied --disableImmediateResponse option when --fastformat x passed during --formatUnit y. This behavior can be selected as needed still, but it is no longer the default. This improves compatibility with some systems.
  * Fixed copyright date in the banner being dynamically set at compile time. This should be constant to when code was written/modified, not when it was compiled.
  * Fixed usage for GNU access attributes which were sometimes applied incorrectly. This can cause warnings or incorrect optimizations, however no known issues have been reported for this.
  * Increased usage of const for tDevice structures to be more clear about when modifications are being done or not. This did find a couple minor code bugs, but no known case of causing incorrect runtime issues.
  * Fixed compatibility with some newer C23 capable compilers
  * Fixed compatibility with msys2 mingw and clang environments. cygwin environment is not currently supported.</changelog>
</package>
<package pkgid="e6fa754e0ebefba9055e08564698391c94f080b457d63fe790459728e5fc14073c0c1e9aa37937194890587a17f0cca1eb62bcd1b2d3f0e36c749a8bac1c9034" name="openseachest" arch="src">
  <version epoch="0" ver="25.05.3" rel="7.1"/>
  <changelog author="Daniel Wilhelmi &lt;jackdaniels96@gmail.com&gt;" date="1769515200">- Update to 25.05.3
  * Fixed incorrect null pointer check in TRIM function that caused the operation to exit with an error despite valid inputs
  * Fixed incorrect SCSI operation code lookup for pulling SCSI Defect lists
  * Fixed out of bounds access for FARM combined log pull. This wrote a null terminator one byte outside of the allocated memory. This can cause memory corruption, but no known impact otherwise.
  * Changed when the filesystem rescan or reread of the partition table happens to minimize cases where a drive may be disconnected from the OS due to being in an unreadable state. Examples: Sanitize failed state &amp; ATA security locked &amp; sector size change will put the drive into a different state that blocks media access or with different attributes that the OS does not know have changed. Attempting this rescan in this cases causes the drive to disconnect from the system and may have other side affects as well. All cases where this occurs not make sure the drive is in a state that it can complete this operation successfully.
  * Fixed logic in read/write testing (openSeaChest_Generic) for some USB devices that report an ATA passthrough maxlba of 0. Previous versions will always fail on these devices even if they are otherwise working properly.
  * Added tracking of when file locks/unlocks are requested on the device handle to keep things better synchronized between operations.
  * Fixed a crash that occurs in Windows for NVMe devices using an openfabrics NVMe compatible driver.
  * Rewrote logic to select SCSI media access commands with retries for reads, writes, verify, and synchronize cache (10byte vs 16byte versions)
  * Added detecting and selecting a compatible firmware update transfer length to improve compatibility with various devices that have limitations they can report. Default behavior was previously to download in 32k segments, but now it checks if this is compatible and selects a compatible size if limitations are reported. Users can still override this and select a segment size as needed.
  * Removed implied --disableImmediateResponse option when --fastformat x passed during --formatUnit y. This behavior can be selected as needed still, but it is no longer the default. This improves compatibility with some systems.
  * Fixed copyright date in the banner being dynamically set at compile time. This should be constant to when code was written/modified, not when it was compiled.
  * Fixed usage for GNU access attributes which were sometimes applied incorrectly. This can cause warnings or incorrect optimizations, however no known issues have been reported for this.
  * Increased usage of const for tDevice structures to be more clear about when modifications are being done or not. This did find a couple minor code bugs, but no known case of causing incorrect runtime issues.
  * Fixed compatibility with some newer C23 capable compilers
  * Fixed compatibility with msys2 mingw and clang environments. cygwin environment is not currently supported.</changelog>
</package>
<package pkgid="eb64cba304fcdd25d824e0696536f70a76990040d963266f8655f3a4ddc96caf24fc125c4c10e3f538e577b50b355fa56dbfdc4d42929458c97e40fc7dc64f62" name="openseachest" arch="x86_64">
  <version epoch="0" ver="25.05.3" rel="7.1"/>
  <changelog author="Daniel Wilhelmi &lt;jackdaniels96@gmail.com&gt;" date="1769515200">- Update to 25.05.3
  * Fixed incorrect null pointer check in TRIM function that caused the operation to exit with an error despite valid inputs
  * Fixed incorrect SCSI operation code lookup for pulling SCSI Defect lists
  * Fixed out of bounds access for FARM combined log pull. This wrote a null terminator one byte outside of the allocated memory. This can cause memory corruption, but no known impact otherwise.
  * Changed when the filesystem rescan or reread of the partition table happens to minimize cases where a drive may be disconnected from the OS due to being in an unreadable state. Examples: Sanitize failed state &amp; ATA security locked &amp; sector size change will put the drive into a different state that blocks media access or with different attributes that the OS does not know have changed. Attempting this rescan in this cases causes the drive to disconnect from the system and may have other side affects as well. All cases where this occurs not make sure the drive is in a state that it can complete this operation successfully.
  * Fixed logic in read/write testing (openSeaChest_Generic) for some USB devices that report an ATA passthrough maxlba of 0. Previous versions will always fail on these devices even if they are otherwise working properly.
  * Added tracking of when file locks/unlocks are requested on the device handle to keep things better synchronized between operations.
  * Fixed a crash that occurs in Windows for NVMe devices using an openfabrics NVMe compatible driver.
  * Rewrote logic to select SCSI media access commands with retries for reads, writes, verify, and synchronize cache (10byte vs 16byte versions)
  * Added detecting and selecting a compatible firmware update transfer length to improve compatibility with various devices that have limitations they can report. Default behavior was previously to download in 32k segments, but now it checks if this is compatible and selects a compatible size if limitations are reported. Users can still override this and select a segment size as needed.
  * Removed implied --disableImmediateResponse option when --fastformat x passed during --formatUnit y. This behavior can be selected as needed still, but it is no longer the default. This improves compatibility with some systems.
  * Fixed copyright date in the banner being dynamically set at compile time. This should be constant to when code was written/modified, not when it was compiled.
  * Fixed usage for GNU access attributes which were sometimes applied incorrectly. This can cause warnings or incorrect optimizations, however no known issues have been reported for this.
  * Increased usage of const for tDevice structures to be more clear about when modifications are being done or not. This did find a couple minor code bugs, but no known case of causing incorrect runtime issues.
  * Fixed compatibility with some newer C23 capable compilers
  * Fixed compatibility with msys2 mingw and clang environments. cygwin environment is not currently supported.</changelog>
</package>
<package pkgid="6af24eb9099fb0b8661e8c415502651c5e3ef922a5c32c57fb2d9d32a0b788c5482480e3d463a11596aca6278c9c2dce829f58dfa2168710dcb2c9a1c4ffc8c4" name="openseachest" arch="aarch64">
  <version epoch="0" ver="26.03.2" rel="8.3"/>
  <changelog author="Daniel Wilhelmi &lt;jackdaniels96@gmail.com&gt;" date="1769515200">- Update to 25.05.3
  * Fixed incorrect null pointer check in TRIM function that caused the operation to exit with an error despite valid inputs
  * Fixed incorrect SCSI operation code lookup for pulling SCSI Defect lists
  * Fixed out of bounds access for FARM combined log pull. This wrote a null terminator one byte outside of the allocated memory. This can cause memory corruption, but no known impact otherwise.
  * Changed when the filesystem rescan or reread of the partition table happens to minimize cases where a drive may be disconnected from the OS due to being in an unreadable state. Examples: Sanitize failed state &amp; ATA security locked &amp; sector size change will put the drive into a different state that blocks media access or with different attributes that the OS does not know have changed. Attempting this rescan in this cases causes the drive to disconnect from the system and may have other side affects as well. All cases where this occurs not make sure the drive is in a state that it can complete this operation successfully.
  * Fixed logic in read/write testing (openSeaChest_Generic) for some USB devices that report an ATA passthrough maxlba of 0. Previous versions will always fail on these devices even if they are otherwise working properly.
  * Added tracking of when file locks/unlocks are requested on the device handle to keep things better synchronized between operations.
  * Fixed a crash that occurs in Windows for NVMe devices using an openfabrics NVMe compatible driver.
  * Rewrote logic to select SCSI media access commands with retries for reads, writes, verify, and synchronize cache (10byte vs 16byte versions)
  * Added detecting and selecting a compatible firmware update transfer length to improve compatibility with various devices that have limitations they can report. Default behavior was previously to download in 32k segments, but now it checks if this is compatible and selects a compatible size if limitations are reported. Users can still override this and select a segment size as needed.
  * Removed implied --disableImmediateResponse option when --fastformat x passed during --formatUnit y. This behavior can be selected as needed still, but it is no longer the default. This improves compatibility with some systems.
  * Fixed copyright date in the banner being dynamically set at compile time. This should be constant to when code was written/modified, not when it was compiled.
  * Fixed usage for GNU access attributes which were sometimes applied incorrectly. This can cause warnings or incorrect optimizations, however no known issues have been reported for this.
  * Increased usage of const for tDevice structures to be more clear about when modifications are being done or not. This did find a couple minor code bugs, but no known case of causing incorrect runtime issues.
  * Fixed compatibility with some newer C23 capable compilers
  * Fixed compatibility with msys2 mingw and clang environments. cygwin environment is not currently supported.</changelog>
  <changelog author="Daniel Wilhelmi &lt;jackdaniels96@gmail.com&gt;" date="1782648000">- v26.03.2
  * SCSI defect list bounds check (32-bit) — A previous release fixed an out-of-bounds memory access in SCSI defect list handling on 64-bit builds. This patch extends the same guard to 32-bit builds.
  * Fast-format MBR erase on SATA — Fixed a logic error where fast-format incorrectly assumed ATA Zeros Ext was always available. On hardware that does not support that command, the MBR erase step was silently skipped. If the drive had a valid MBR — including a protective MBR from a GPT-partitioned disk — the drive could become unpartitionable after a sector-size change unless erased with another tool like openSeaChest_Erase after a power cycle to the system was completed.
  * json-c header installation — Fixed an issue where json-c headers were being installed from builds sourced directly from this GitHub repository. (#327)
  * Additional memory safety guards — Several operations that allocate memory based on device-reported values received the same class of fix applied to the SCSI defect list. A maliciously crafted or buggy device could return an abnormally large count that causes the calculated allocation size to wrap around, leading to an undersized buffer and a subsequent out-of-bounds write. None of these conditions are reachable with real, spec-compliant hardware. The affected operations are:
  * Partition info (--showPartitionInfo) — A GPT header reporting ≥ ~31.5 million partition entries (far beyond what the UEFI specification permits) could trigger a heap overflow on 32-bit builds.
  * SAS firmware download info (--showFWDLInfo) — A response to the Report Supported Operation Codes command returning a total length &gt; 0xFFFFFFFC could trigger an out-of-bounds read and write.
  * Set Max LBA model number mapping — A device reporting an abnormally large number of capacity/model-number descriptors (beyond what the ATA or SCSI specifications allow) could trigger a similar overflow.
  * SCSI log and VPD page parser robustness — Added realistic upper-bound checks when iterating over SCSI log pages, subpages, and VPD page lists. A device returning a malformed or oversized page length value could cause a uint16_t loop variable to wrap, which in at least one code path could produce an infinite loop that could never exit. These checks ensure all loops terminate correctly regardless of what the device reports.</changelog>
</package>
<package pkgid="ef31abaeedc861889f8b3cbcd742bff2fb0bc50ffffd19ce90789ddb2bc0a4cb6f1bcc256a24ed99123de693b771ce2669ac6314c0ac3f89329db7adb3ef55ab" name="openseachest" arch="src">
  <version epoch="0" ver="26.03.2" rel="8.3"/>
  <changelog author="Daniel Wilhelmi &lt;jackdaniels96@gmail.com&gt;" date="1769515200">- Update to 25.05.3
  * Fixed incorrect null pointer check in TRIM function that caused the operation to exit with an error despite valid inputs
  * Fixed incorrect SCSI operation code lookup for pulling SCSI Defect lists
  * Fixed out of bounds access for FARM combined log pull. This wrote a null terminator one byte outside of the allocated memory. This can cause memory corruption, but no known impact otherwise.
  * Changed when the filesystem rescan or reread of the partition table happens to minimize cases where a drive may be disconnected from the OS due to being in an unreadable state. Examples: Sanitize failed state &amp; ATA security locked &amp; sector size change will put the drive into a different state that blocks media access or with different attributes that the OS does not know have changed. Attempting this rescan in this cases causes the drive to disconnect from the system and may have other side affects as well. All cases where this occurs not make sure the drive is in a state that it can complete this operation successfully.
  * Fixed logic in read/write testing (openSeaChest_Generic) for some USB devices that report an ATA passthrough maxlba of 0. Previous versions will always fail on these devices even if they are otherwise working properly.
  * Added tracking of when file locks/unlocks are requested on the device handle to keep things better synchronized between operations.
  * Fixed a crash that occurs in Windows for NVMe devices using an openfabrics NVMe compatible driver.
  * Rewrote logic to select SCSI media access commands with retries for reads, writes, verify, and synchronize cache (10byte vs 16byte versions)
  * Added detecting and selecting a compatible firmware update transfer length to improve compatibility with various devices that have limitations they can report. Default behavior was previously to download in 32k segments, but now it checks if this is compatible and selects a compatible size if limitations are reported. Users can still override this and select a segment size as needed.
  * Removed implied --disableImmediateResponse option when --fastformat x passed during --formatUnit y. This behavior can be selected as needed still, but it is no longer the default. This improves compatibility with some systems.
  * Fixed copyright date in the banner being dynamically set at compile time. This should be constant to when code was written/modified, not when it was compiled.
  * Fixed usage for GNU access attributes which were sometimes applied incorrectly. This can cause warnings or incorrect optimizations, however no known issues have been reported for this.
  * Increased usage of const for tDevice structures to be more clear about when modifications are being done or not. This did find a couple minor code bugs, but no known case of causing incorrect runtime issues.
  * Fixed compatibility with some newer C23 capable compilers
  * Fixed compatibility with msys2 mingw and clang environments. cygwin environment is not currently supported.</changelog>
  <changelog author="Daniel Wilhelmi &lt;jackdaniels96@gmail.com&gt;" date="1782648000">- v26.03.2
  * SCSI defect list bounds check (32-bit) — A previous release fixed an out-of-bounds memory access in SCSI defect list handling on 64-bit builds. This patch extends the same guard to 32-bit builds.
  * Fast-format MBR erase on SATA — Fixed a logic error where fast-format incorrectly assumed ATA Zeros Ext was always available. On hardware that does not support that command, the MBR erase step was silently skipped. If the drive had a valid MBR — including a protective MBR from a GPT-partitioned disk — the drive could become unpartitionable after a sector-size change unless erased with another tool like openSeaChest_Erase after a power cycle to the system was completed.
  * json-c header installation — Fixed an issue where json-c headers were being installed from builds sourced directly from this GitHub repository. (#327)
  * Additional memory safety guards — Several operations that allocate memory based on device-reported values received the same class of fix applied to the SCSI defect list. A maliciously crafted or buggy device could return an abnormally large count that causes the calculated allocation size to wrap around, leading to an undersized buffer and a subsequent out-of-bounds write. None of these conditions are reachable with real, spec-compliant hardware. The affected operations are:
  * Partition info (--showPartitionInfo) — A GPT header reporting ≥ ~31.5 million partition entries (far beyond what the UEFI specification permits) could trigger a heap overflow on 32-bit builds.
  * SAS firmware download info (--showFWDLInfo) — A response to the Report Supported Operation Codes command returning a total length &gt; 0xFFFFFFFC could trigger an out-of-bounds read and write.
  * Set Max LBA model number mapping — A device reporting an abnormally large number of capacity/model-number descriptors (beyond what the ATA or SCSI specifications allow) could trigger a similar overflow.
  * SCSI log and VPD page parser robustness — Added realistic upper-bound checks when iterating over SCSI log pages, subpages, and VPD page lists. A device returning a malformed or oversized page length value could cause a uint16_t loop variable to wrap, which in at least one code path could produce an infinite loop that could never exit. These checks ensure all loops terminate correctly regardless of what the device reports.</changelog>
</package>
<package pkgid="c1aa2590c37b29290d1328c2d3f2519a189b7e8bee9676cee91a98c0796a405fe86d975317a3bf703d722278c78465f37c24c0865e2dfd974ba9b371a0cb2c16" name="openseachest" arch="x86_64">
  <version epoch="0" ver="26.03.2" rel="8.3"/>
  <changelog author="Daniel Wilhelmi &lt;jackdaniels96@gmail.com&gt;" date="1769515200">- Update to 25.05.3
  * Fixed incorrect null pointer check in TRIM function that caused the operation to exit with an error despite valid inputs
  * Fixed incorrect SCSI operation code lookup for pulling SCSI Defect lists
  * Fixed out of bounds access for FARM combined log pull. This wrote a null terminator one byte outside of the allocated memory. This can cause memory corruption, but no known impact otherwise.
  * Changed when the filesystem rescan or reread of the partition table happens to minimize cases where a drive may be disconnected from the OS due to being in an unreadable state. Examples: Sanitize failed state &amp; ATA security locked &amp; sector size change will put the drive into a different state that blocks media access or with different attributes that the OS does not know have changed. Attempting this rescan in this cases causes the drive to disconnect from the system and may have other side affects as well. All cases where this occurs not make sure the drive is in a state that it can complete this operation successfully.
  * Fixed logic in read/write testing (openSeaChest_Generic) for some USB devices that report an ATA passthrough maxlba of 0. Previous versions will always fail on these devices even if they are otherwise working properly.
  * Added tracking of when file locks/unlocks are requested on the device handle to keep things better synchronized between operations.
  * Fixed a crash that occurs in Windows for NVMe devices using an openfabrics NVMe compatible driver.
  * Rewrote logic to select SCSI media access commands with retries for reads, writes, verify, and synchronize cache (10byte vs 16byte versions)
  * Added detecting and selecting a compatible firmware update transfer length to improve compatibility with various devices that have limitations they can report. Default behavior was previously to download in 32k segments, but now it checks if this is compatible and selects a compatible size if limitations are reported. Users can still override this and select a segment size as needed.
  * Removed implied --disableImmediateResponse option when --fastformat x passed during --formatUnit y. This behavior can be selected as needed still, but it is no longer the default. This improves compatibility with some systems.
  * Fixed copyright date in the banner being dynamically set at compile time. This should be constant to when code was written/modified, not when it was compiled.
  * Fixed usage for GNU access attributes which were sometimes applied incorrectly. This can cause warnings or incorrect optimizations, however no known issues have been reported for this.
  * Increased usage of const for tDevice structures to be more clear about when modifications are being done or not. This did find a couple minor code bugs, but no known case of causing incorrect runtime issues.
  * Fixed compatibility with some newer C23 capable compilers
  * Fixed compatibility with msys2 mingw and clang environments. cygwin environment is not currently supported.</changelog>
  <changelog author="Daniel Wilhelmi &lt;jackdaniels96@gmail.com&gt;" date="1782648000">- v26.03.2
  * SCSI defect list bounds check (32-bit) — A previous release fixed an out-of-bounds memory access in SCSI defect list handling on 64-bit builds. This patch extends the same guard to 32-bit builds.
  * Fast-format MBR erase on SATA — Fixed a logic error where fast-format incorrectly assumed ATA Zeros Ext was always available. On hardware that does not support that command, the MBR erase step was silently skipped. If the drive had a valid MBR — including a protective MBR from a GPT-partitioned disk — the drive could become unpartitionable after a sector-size change unless erased with another tool like openSeaChest_Erase after a power cycle to the system was completed.
  * json-c header installation — Fixed an issue where json-c headers were being installed from builds sourced directly from this GitHub repository. (#327)
  * Additional memory safety guards — Several operations that allocate memory based on device-reported values received the same class of fix applied to the SCSI defect list. A maliciously crafted or buggy device could return an abnormally large count that causes the calculated allocation size to wrap around, leading to an undersized buffer and a subsequent out-of-bounds write. None of these conditions are reachable with real, spec-compliant hardware. The affected operations are:
  * Partition info (--showPartitionInfo) — A GPT header reporting ≥ ~31.5 million partition entries (far beyond what the UEFI specification permits) could trigger a heap overflow on 32-bit builds.
  * SAS firmware download info (--showFWDLInfo) — A response to the Report Supported Operation Codes command returning a total length &gt; 0xFFFFFFFC could trigger an out-of-bounds read and write.
  * Set Max LBA model number mapping — A device reporting an abnormally large number of capacity/model-number descriptors (beyond what the ATA or SCSI specifications allow) could trigger a similar overflow.
  * SCSI log and VPD page parser robustness — Added realistic upper-bound checks when iterating over SCSI log pages, subpages, and VPD page lists. A device returning a malformed or oversized page length value could cause a uint16_t loop variable to wrap, which in at least one code path could produce an infinite loop that could never exit. These checks ensure all loops terminate correctly regardless of what the device reports.</changelog>
</package>
</otherdata>