CVE-2026-109976 json
Clevis: clevis: integer underflow in pkcs#11 data socket handler crashes daemon on unbound client connection
published 27d ago modified 3d ago also EUVD-2026-98481
- cvss
- 4.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 3%
- public exploits
- 0
- none known
Summary
A flaw was found in the clevis PKCS#11 pin. The clevis-pkcs11-afunix-socket-unlock daemon crashes when an AF_UNIX client connects to the data socket without a bound address, due to an integer underflow in the getpeername result handling. This causes a denial of service, preventing LUKS disk decryption from completing during boot.
Patch / fix
- clevis Debian 14 24-1
debian advisories DEBIAN-CVE-2026-109976
Is CVE-2026-109976 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-109976 updated cvss 4.7
clevis: clevis: integer underflow in PKCS#11 data socket handler crashes daemon on unbound client connection
-
Red Hat Enterprise Linux 9 clevis-luks, clevis-dracut, clevis-systemd, clevis-udisks2, clevis 23-2.el10, clevis-pin-pkcs11 Red Hat Enterprise Linux 10 clevis 23-2.el10affected: workaround, no fix available “No additional end-user mitigation is needed. Under the default systemd configuration, the data socket is only accessible by root, preventing unprivileged users from triggering the crash.”
-
Red Hat Enterprise Linux 7 clevis-luks, clevis-dracut, clevis-systemd, clevis-udisks2, clevis 23-2.el10 Red Hat Enterprise Linux 8 clevis-luks, clevis-dracut, clevis-systemd, clevis-udisks2, clevis 23-2.el10 Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9not affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 26d ago
Exploit prediction
0.14% chance of exploitation in the next 30 days, higher than 3% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- bugzilla.redhat.com https://bugzilla.redhat.com/show_bug.cgi?id=2550375 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.7 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Red Hat Red Hat Enterprise Linux 10
- Red Hat Red Hat Enterprise Linux 7
- Red Hat Red Hat Enterprise Linux 8
- Red Hat Red Hat Enterprise Linux 9
- Red Hat Red Hat OpenShift Container Platform 4
- Red Hat Red Hat OpenShift Container Platform 5
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
-
bugzilla.redhat.com
/show_bug.cgi?id=2550375
issue-tracking, exploit
-
access.redhat.com
/security/cve/CVE-2026-109976
vdb-entry
Sources
- CVE List CVE-2026-109976
- NVD CVE-2026-109976
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.