Fedora Account System
Red Hat Associate
Red Hat Customer
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process. When authenticating with a YubiKey, the SSSD PAM responder crashes inside sss_certmap_match_cert because the sss_certmap_ctx pointer passed to it has already been freed and reused for string data from the p11_child response. The pointer value 0x6e65687475412056 decodes to ASCII "V Auth en" which is part from the certificate label "X.509 Certificate for PIV Authentication" returned by p11_child. This confirms that the freed sss_certmap_ctx memory was reused during response parsing. Root cause: sss_certmap_ctx is owned by the PAM request state. If the request is cancelled or completes while the asynchronous p11_child process is still running, the request state (and the context) is freed. When the child eventually returns and p11_child_done / parse_p11_child_response run, they call sss_certmap_match_cert with a dangling pointer. The certificate data (token name, label, or certificate contents) then occupies the freed memory. Impact: Denial of service: The PAM responder crashes, breaking authentication in some cases. Potential privilege escalation: Because an attacker controls the smartcard/YubiKey contents, they can influence the data that replaces the freed sss_certmap_ctx structure, turning this into a controlled use-after-free in a privileged, long-running process (although this looks hard to exploit).
*** Bug 2494800 has been marked as a duplicate of this bug. ***
Upstream ticket: https://github.com/SSSD/sssd/issues/8796 Upstream PR: https://github.com/SSSD/sssd/pull/8861
Fixed as of https://github.com/SSSD/sssd/commit/fa7a55949a30fed064a28ea6f0c801fc5e8c5ba7
sssd-2-13 branch: https://github.com/SSSD/sssd/commit/f2c69b916f5fe53a930aa39c2078b248b83bc2b4
FEDORA-2026-5acfb0243b (CVE-2026-12610 CVE-2026-14474 CVE-2026-14476) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2026-5acfb0243b
FEDORA-2026-9ab663dcd4 (CVE-2026-12610 CVE-2026-14474 CVE-2026-14476) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2026-9ab663dcd4
FEDORA-2026-5acfb0243b has been pushed to the Fedora 44 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-5acfb0243b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-5acfb0243b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-9ab663dcd4 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-9ab663dcd4` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-9ab663dcd4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-8fad0036a5 (sssd-2.13.1-3.fc45) has been submitted as an update to Fedora 45. https://bodhi.fedoraproject.org/updates/FEDORA-2026-8fad0036a5
FEDORA-2026-8fad0036a5 (sssd-2.13.1-3.fc45) has been pushed to the Fedora 45 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-5acfb0243b (CVE-2026-12610 CVE-2026-14474 CVE-2026-14476) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-9ab663dcd4 (CVE-2026-12610 CVE-2026-14474 CVE-2026-14476) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.