AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Low 31 Bitcoin

askrene: fix error path if we fail sanity checks.

Public commit record

What the developer wrote

Authored by Rusty Russell

68/100 · Adequate
askrene: fix error path if we fail sanity checks.

We've already freed the working_ctx, and the fail path does that again.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This commit fixes a programming mistake in Core Lightning's 'askrene' plugin where an error-handling path tried to free memory that had already been freed. Re-freeing the same memory can crash the process or corrupt memory. The fix replaces the shared 'goto fail' path with direct returns so the double-free cannot happen.

Recommended action

Apply the patch. It is a straightforward correctness fix that prevents memory corruption on routing sanity-check failures. No immediate incident response is indicated unless crashes in askrene have already been observed.

Security signals we found

01

Double-free / use-after-free bug in error path

02

Memory corruption / crash potential in routing plugin

03

Fix removes shared cleanup label causing duplicate tal_free

04

No explicit security framing by vendor

Risk score

Why this scored 31/100

Our methodology →
Potential impact 8/30
Exploitability 3/25
Stealth signal 4/15
Affected reach 5/15
Confidence 7/10
Evidence quality 4/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.