CVE-2023-53726

CVE-2023-53726 – Linux kernel (arm64): The issue is an out-of-bounds read in the arm64 IP checksum path (arch/arm64/lib/csum.c) caused by negative input lengths. The fix extends the existing early return to reject negative lengths, aligning with the generic code in lib/checksum.c. The vulnerabili...

CVE-2023-53703 HID: amd_sfh: Fix for shift-out-of-bounds

In the Linux kernel, the following vulnerability has been resolved: HID: amdsfh: Fix for shift-out-of-bounds Shift operation of 'exp' and 'shift' variables exceeds the maximum number of shift values in the u32 range leading to UBSAN shift-out-of-bounds. ... 6.120512 UBSAN: shift-out-of-bounds in...

CVE-2023-53703 HID: amd_sfh: Fix for shift-out-of-bounds

In the Linux kernel, the following vulnerability has been resolved: HID: amdsfh: Fix for shift-out-of-bounds Shift operation of 'exp' and 'shift' variables exceeds the maximum number of shift values in the u32 range leading to UBSAN shift-out-of-bounds. ... 6.120512 UBSAN: shift-out-of-bounds in...

CVE-2023-53703

CVE-2023-53703 (Linux kernel) : The issue arises in the HID/amd_sfh code where shifting values in the exp/shift calculation can exceed the 32-bit range, triggering UBSAN shift-out-of-bounds. The described impact is a UBSAN shift-out-of-bounds error in amd_sfh_desc.c (line 149) during the AMD SFH ...

PT-2025-45795

The safe function any as u8 slice can create byte slices that reference uninitialized memory when used with types containing padding bytes. The function uses slice::from raw parts to create a &u8 covering the entire size of a type, including padding bytes. According to Rust's documentation, from...

GHSA-H5J3-CRG5-8JQM orx-pinned-vec has undefined behavior in index_of_ptr with empty slices

The safe function indexofptr causes undefined behavior when called with an empty slice. The issue occurs in the line ptr.addslice.len - 1 which underflows when slice.len is 0, creating a pointer with a massive offset. According to Rust's safety rules, creating such a pointer causes immediate...

Uninitialized memory exposure in any_as_u8_slice

The safe function anyasu8slice can create byte slices that reference uninitialized memory when used with types containing padding bytes. The function uses slice::fromrawparts to create a &u8 covering the entire size of a type, including padding bytes. According to Rust's documentation, fromrawpar...

Undefined behavior in index_of_ptr with empty slices

The safe function indexofptr causes undefined behavior when called with an empty slice. The issue occurs in the line ptr.addslice.len - 1 which underflows when slice.len is 0, creating a pointer with a massive offset. According to Rust's safety rules, creating such a pointer causes immediate...

RUSTSEC-2025-0107 Uninitialized memory exposure in any_as_u8_slice

The safe function anyasu8slice can create byte slices that reference uninitialized memory when used with types containing padding bytes. The function uses slice::fromrawparts to create a &u8 covering the entire size of a type, including padding bytes. According to Rust's documentation, fromrawpar...

RUSTSEC-2025-0106 Undefined behavior in index_of_ptr with empty slices

The safe function indexofptr causes undefined behavior when called with an empty slice. The issue occurs in the line ptr.addslice.len - 1 which underflows when slice.len is 0, creating a pointer with a massive offset. According to Rust's safety rules, creating such a pointer causes immediate...

PT-2025-46132

The safe function any as u8 slice can create byte slices that reference uninitialized memory when used with types containing padding bytes. The function uses slice::from raw parts to create a &u8 covering the entire size of a type, including padding bytes. According to Rust's documentation, from...

PT-2025-45714

The safe function create ring buffer allocates a buffer using Vec::with capacity followed by set len, creating a Box containing uninitialized memory. This leads to undefined behavior when functions like write slices create typed slices e.g., &mut bool over the uninitialized memory, violating Rust...

PT-2025-46130

The safe function create ring buffer allocates a buffer using Vec::with capacity followed by set len, creating a Box containing uninitialized memory. This leads to undefined behavior when functions like write slices create typed slices e.g., &mut bool over the uninitialized memory, violating Rust...

PT-2025-46131

The safe function index of ptr causes undefined behavior when called with an empty slice. The issue occurs in the line ptr.addslice.len - 1 which underflows when slice.len is 0, creating a pointer with a massive offset. According to Rust's safety rules, creating such a pointer causes immediate...

PT-2025-45729

The safe function index of ptr causes undefined behavior when called with an empty slice. The issue occurs in the line ptr.addslice.len - 1 which underflows when slice.len is 0, creating a pointer with a massive offset. According to Rust's safety rules, creating such a pointer causes immediate...

CVE-2025-55085

In NextX Duo before 6.4.4, in the HTTP client module, the network support code for Eclipse Foundation ThreadX, the parsing of HTTP header fields was missing bounds verification. A crafted server response could cause undefined behavior...

CVE-2025-55085 Web http client: Unchecked Server-Side Malicious Packet Issue

In NextX Duo before 6.4.4, in the HTTP client module, the network support code for Eclipse Foundation ThreadX, the parsing of HTTP header fields was missing bounds verification. A crafted server response could cause undefined behavior...

EUVD-2025-34883

In NextX Duo before 6.4.4, in the HTTP client module, the network support code for Eclipse Foundation ThreadX, the parsing of HTTP header fields was missing bounds verification. A crafted server response could cause undefined behavior...

CVE-2025-55085

In NextX Duo prior to 6.4.4, the HTTP client module’s handling of HTTP header fields in the Eclipse Foundation ThreadX network support code lacks bounds verification. This can be triggered by a crafted server response and leads to undefined behavior. Affected product/version: NextX Duo

CVE-2025-55085 Web http client: Unchecked Server-Side Malicious Packet Issue

In NextX Duo before 6.4.4, in the HTTP client module, the network support code for Eclipse Foundation ThreadX, the parsing of HTTP header fields was missing bounds verification. A crafted server response could cause undefined behavior...