Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Nariman-Sayed via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: Nariman-Sayed <code@ffmpeg.org>
Subject: [FFmpeg-devel] [PR] tls_openssl: fix memory leak in cert_from_pem_string (PR #22235)
Date: Fri, 20 Feb 2026 23:25:45 -0000
Message-ID: <177162994646.25.5876070696733864481@29965ddac10e> (raw)

PR #22235 opened by Nariman-Sayed
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/22235
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/22235.patch

tls_openssl: fix memory leak in cert_from_pem_string

When PEM_read_bio_X509 fails, BIO was not freed, causing memory leaks.
Add BIO_free(mem) before returning NULL to prevent resource leak.


>From e75a1348325f9728b2420843d8dee177941f757b Mon Sep 17 00:00:00 2001
From: Nariman-Sayed <narimansayed28@gmail.com>
Date: Sat, 21 Feb 2026 01:19:25 +0200
Subject: [PATCH] tls_openssl: fix memory leak in cert_from_pem_string

---
 libavformat/tls_openssl.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/libavformat/tls_openssl.c b/libavformat/tls_openssl.c
index 0ae0980cc3..b00ce7cc3a 100644
--- a/libavformat/tls_openssl.c
+++ b/libavformat/tls_openssl.c
@@ -407,6 +407,7 @@ static X509 *cert_from_pem_string(const char *pem_str)
     X509 *cert = PEM_read_bio_X509(mem, NULL, NULL, NULL);
     if (!cert) {
         av_log(NULL, AV_LOG_ERROR, "Failed to parse certificate from string\n");
+        BIO_free(mem);
         return NULL;
     }
 
-- 
2.52.0

_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org

                 reply	other threads:[~2026-02-21  0:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=177162994646.25.5876070696733864481@29965ddac10e \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=code@ffmpeg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git