Lucene search
+L

7 matches found

Positive Technologies
Positive Technologies
•added 2026/05/29 12:00 a.m.•34 views

PT-2026-45016

Content removed...

5.8CVSS5.7AI score0.0013EPSS
SaveExploits1References5
RustSec
RustSec
•added 2025/04/24 12:00 p.m.•24 views

`hugepage_rs::dealloc` may allow invalid memory deallocation from safe code

hugepagers::dealloc was a publicly accessible safe function. It accepted an arbitrary raw pointer and Layout, then forwarded them to the hugepage allocator's GlobalAlloc::dealloc implementation. GlobalAlloc::dealloc requires callers to ensure that the pointer denotes a block of memory currently...

5.5AI score
SaveExploits0Affected Software1
Mend
Mend
•added 2025/02/13 10:07 a.m.•8 views

WS-2022-0414

Unsound API in secp256k1 allows use-after-free and invalid deallocation from safe code, because of incorrect bounds on method Secp256k1::preallocatedgennew...

9.8CVSS6.1AI score
SaveExploits0References6
osv_ghsa
osv_ghsa
•added 2022/12/08 4:00 p.m.•13 views

GHSA-969W-Q74Q-9J8V Unsound API in `secp256k1` allows use-after-free and invalid deallocation from safe code

Because of incorrect bounds on method Secp256k1::preallocatedgennew it was possible to cause use-after-free from safe consumer code. It was also possible to "free" memory not allocated by the appropriate allocator. The method takes a place for storing the context as a mutable reference and return...

7.3AI score
SaveExploits0References3
Github Security Blog
Github Security Blog
•added 2022/12/08 4:00 p.m.•39 views

Unsound API in `secp256k1` allows use-after-free and invalid deallocation from safe code

Because of incorrect bounds on method Secp256k1::preallocatedgennew it was possible to cause use-after-free from safe consumer code. It was also possible to "free" memory not allocated by the appropriate allocator. The method takes a place for storing the context as a mutable reference and return...

0.3AI score
SaveExploits0References3Affected Software1
osv_rustsec
osv_rustsec
•added 2022/11/30 12:00 p.m.•47 views

RUSTSEC-2022-0070 Unsound API in `secp256k1` allows use-after-free and invalid deallocation from safe code

Because of incorrect bounds on method Secp256k1::preallocatedgennew it was possible to cause use-after-free from safe consumer code. It was also possible to "free" memory not allocated by the appropriate allocator. The method takes a place for storing the context as a mutable reference and return...

7.3AI score
SaveExploits0References4
RustSec
RustSec
•added 2022/11/30 12:00 p.m.•37 views

Unsound API in `secp256k1` allows use-after-free and invalid deallocation from safe code

Because of incorrect bounds on method Secp256k1::preallocatedgennew it was possible to cause use-after-free from safe consumer code. It was also possible to "free" memory not allocated by the appropriate allocator. The method takes a place for storing the context as a mutable reference and return...

0.2AI score
SaveExploits0Affected Software1
Rows per page
Query Builder