glibc: Missing unwind info in __startcontext causes infinite loop in _Unwind_Backtrace
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
Configuration 3 [-]
|
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2016-7250 | The makecontext function in the GNU C Library (aka glibc or libc6) before 2.25 creates execution contexts incompatible with the unwinder on ARM EABI (32-bit) platforms, which might allow context-dependent attackers to cause a denial of service (hang), as demonstrated by applications compiled using gccgo, related to backtrace generation. |
Ubuntu USN |
USN-3239-1 | GNU C Library vulnerabilities |
No CVSS v4.0
No CVSS v3.1
This CVE is not in the KEV list.
Exploit prediction score: 3.9% (3.872% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.