Blame SOURCES/0004-PAM_SSS-close-sss_cli_sd-should-also-be-protected-wi.patch

bd4b98
From 1fd7a5ecb46a02a29ebf42039575b5344307bfbb Mon Sep 17 00:00:00 2001
bd4b98
From: Alexey Tikhonov <atikhono@redhat.com>
bd4b98
Date: Wed, 8 Feb 2023 18:58:37 +0100
bd4b98
Subject: [PATCH 4/4] PAM_SSS: close(sss_cli_sd) should also be protected with
bd4b98
 mutex. Otherwise a thread calling pam_end() can close socket mid pam
bd4b98
 transaction in another thread.
bd4b98
MIME-Version: 1.0
bd4b98
Content-Type: text/plain; charset=UTF-8
bd4b98
Content-Transfer-Encoding: 8bit
bd4b98
bd4b98
Bug only manifested on platforms where "lockfree client"
bd4b98
feature wasn't built.
bd4b98
bd4b98
Reviewed-by: Pavel Březina <pbrezina@redhat.com>
bd4b98
Reviewed-by: Sumit Bose <sbose@redhat.com>
bd4b98
(cherry picked from commit bf3f73ea0ee123fe4e7c4bdd2287ac5a5e6d9082)
bd4b98
---
bd4b98
 src/sss_client/pam_sss.c     | 3 +++
bd4b98
 src/sss_client/pam_sss_gss.c | 2 ++
bd4b98
 2 files changed, 5 insertions(+)
bd4b98
bd4b98
diff --git a/src/sss_client/pam_sss.c b/src/sss_client/pam_sss.c
bd4b98
index afbdef59a..39ad17188 100644
bd4b98
--- a/src/sss_client/pam_sss.c
bd4b98
+++ b/src/sss_client/pam_sss.c
bd4b98
@@ -117,7 +117,10 @@ static void close_fd(pam_handle_t *pamh, void *ptr, int err)
bd4b98
 #endif /* PAM_DATA_REPLACE */
bd4b98
 
bd4b98
     D(("Closing the fd"));
bd4b98
+
bd4b98
+    sss_pam_lock();
bd4b98
     sss_cli_close_socket();
bd4b98
+    sss_pam_unlock();
bd4b98
 }
bd4b98
 
bd4b98
 struct cert_auth_info {
bd4b98
diff --git a/src/sss_client/pam_sss_gss.c b/src/sss_client/pam_sss_gss.c
bd4b98
index 1109ec570..dd578ae5d 100644
bd4b98
--- a/src/sss_client/pam_sss_gss.c
bd4b98
+++ b/src/sss_client/pam_sss_gss.c
bd4b98
@@ -581,7 +581,9 @@ int pam_sm_authenticate(pam_handle_t *pamh,
bd4b98
     }
bd4b98
 
bd4b98
 done:
bd4b98
+    sss_pam_lock();
bd4b98
     sss_cli_close_socket();
bd4b98
+    sss_pam_unlock();
bd4b98
     free(username);
bd4b98
     free(domain);
bd4b98
     free(target);
bd4b98
-- 
bd4b98
2.37.3
bd4b98