[From nobody Fri Sep  4 22:19:05 2026
Received: (at submit) by bugs.debian.org; 2 Jul 2026 21:58:32 +0000
X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02
 (2024-03-25) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-10.9 required=4.0 tests=BAYES_00,FOURLA,
 FROMDEVELOPER,MD5_SHA1_SUM,NO_RELAYS,XMAILER_REPORTBUG autolearn=ham
 autolearn_force=no version=4.0.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 22; hammy, 141; neutral, 40; spammy,
 1. spammytokens:0.941-+--H*r:bugs.debian.org
 hammytokens:0.000-+--H*F:U*carnil, 0.000-+--XDebbugsCc,
 0.000-+--X-Debbugs-Cc, 0.000-+--H*Ad:N*Bug, 0.000-+--H*Ad:N*Tracking
Return-path: &lt;carnil@debian.org&gt;
Received: via submission by buxtehude.debian.org with esmtp (Exim 4.96)
 (envelope-from &lt;carnil@debian.org&gt;) id 1wfPQU-00FgRw-2a
 for submit@bugs.debian.org; Thu, 02 Jul 2026 21:58:32 +0000
Content-Type: text/plain; charset=&quot;us-ascii&quot;
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Salvatore Bonaccorso &lt;carnil@debian.org&gt;
To: Debian Bug Tracking System &lt;submit@bugs.debian.org&gt;
Subject: sssd: CVE-2026-12610: use-after-free during p11_child processing
Message-ID: &lt;178302950844.1709974.1226617281462852774.reportbug@eldamar.lan&gt;
X-Mailer: reportbug 13.2.0+nmu1
Date: Thu, 02 Jul 2026 23:58:28 +0200
Delivered-To: submit@bugs.debian.org

Source: sssd
Version: 2.10.1-2
Severity: important
Tags: security upstream
Forwarded: https://github.com/SSSD/sssd/issues/8796
X-Debbugs-Cc: carnil@debian.org, Debian Security Team &lt;team@security.debian.org&gt;

Hi,

The following vulnerability was published for sssd.

CVE-2026-12610[0]:
| A flaw was found in sssd. When authenticating with a YubiKey, the
| SSSD PAM responder can crash due to a use-after-free vulnerability,
| where a memory pointer is incorrectly handled. A local attacker
| could exploit this flaw by manipulating smartcard or YubiKey
| contents, leading to a denial of service that disrupts
| authentication. This vulnerability also presents a potential for
| privilege escalation, although it is difficult to exploit.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities &amp; Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2026-12610
    https://www.cve.org/CVERecord?id=CVE-2026-12610
[1] https://github.com/SSSD/sssd/issues/8796
[2] https://github.com/SSSD/sssd/commit/fa7a55949a30fed064a28ea6f0c801fc5e8c5ba7 (master)
    https://github.com/SSSD/sssd/commit/f2c69b916f5fe53a930aa39c2078b248b83bc2b4 (sssd-2-13 branch)
    https://github.com/SSSD/sssd/commit/db7ffa3ea6a971bb84bc54558ca7217751724334 (sssd-2-9 branch)   

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
]