CVE-2025-14831

Published Feb 9, 2026

Last updated 23 days ago

Overview

Description
A flaw was found in GnuTLS. This vulnerability allows a denial of service (DoS) by excessive CPU (Central Processing Unit) and memory consumption via specially crafted malicious certificates containing a large number of name constraints and subject alternative names (SANs).
Source
secalert@redhat.com
NVD status
Deferred

Risk scores

CVSS 3.1

Type
Secondary
Base score
5.3
Impact score
1.4
Exploitability score
3.9
Vector string
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Severity
MEDIUM

Weaknesses

secalert@redhat.com
CWE-407

Social media

Hype score
Not currently trending
  1. BREAKING: SUSE Linux Micro 6.2 releases gnutls update patching CVE-2025-14831 DoS and CVE-2025-9820 buffer overflow, admins urged to apply via YaST or zypper immediately. https://t.co/lcMx8nOZi7

    @threatcluster

    8 Apr 2026

    170 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  2. #Mageia 2026-0045 addresses a high-severity GnuTLS flaw (CVE-2025-14831). This isn't just a patch; it's a compliance and operational necessity. Read more: 👉 https://t.co/BgZ0aVmCFY #Security https://t.co/ICq0mxgtJ2

    @Cezar_H_Linux

    21 Feb 2026

    60 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  3. Heads up, #Debian community! 🐧 A significant DoS vulnerability (CVE-2025-14831) in the #GnuTLS library has been patched. Read more: 👉 https://t.co/99oEmHPzRW #Security https://t.co/s0NgAZrKGy

    @Cezar_H_Linux

    18 Feb 2026

    47 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  4. GNUTLS-SA-2026-02-09-1、CVE-2026-1584 Severity High; invalid pointer access GNUTLS-SA-2026-02-09-2、CVE-2025-14831 Severity Medium; denial of service The GnuTLS Transport Layer Security Library https://t.co/KkxVAntDe6

    @autumn_good_35

    10 Feb 2026

    128 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  5. GnuTLS 3.8.12 fixes 2 CVEs https://t.co/9rzV3GhTDn CVE-2026-1584: NULL pointer dereference in PSK binder verification (TLS 1.3 resumption attempt with an invalid PSK binder value in ClientHello could lead to DoS) CVE-2025-14831: Name constraint processing performance issue

    @oss_security

    10 Feb 2026

    663 Impressions

    2 Retweets

    5 Likes

    1 Bookmark

    1 Reply

    0 Quotes

  6. CVE-2025-14831 Denial of Service Vulnerability in GnuTLS via Malicious C... https://t.co/Uqf1i9lcLH Don't wait vulnerability scanning results: https://t.co/oh1APvMMnd

    @VulmonFeeds

    9 Feb 2026

    48 Impressions

    0 Retweets

    0 Likes

    1 Bookmark

    0 Replies

    0 Quotes

  7. CVE-2025-14831 A flaw was found in GnuTLS. This vulnerability allows a denial of service (DoS) by excessive CPU (Central Processing Unit) and memory consumption via specially crafte… https://t.co/TayL7snrFO

    @CVEnew

    9 Feb 2026

    260 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  1. In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Fix shadow paging use-after-free due to unexpected role Commit 0cb2af2ea66ad ("KVM: x86: Fix shadow paging use-after-free due to unexpected GFN") fixed a shadow paging mismatch between stored and computed GFNs; the bug could be triggered by changing a PDE mapping from outside the guest, and then deleting a memslot. The rmap_remove() call would miss entries created after the PDE change because the GFN of the leaf SPTE does not match the GFN of the struct kvm_mmu_page. A similar hole however remains if the modified PDE points to a non-leaf page. In this case the gfn can be made to match, but the role does not match: the original large 2MB page creates a kvm_mmu_page with direct=1, while the new 4KB needs a kvm_mmu_page with direct=0. However, kvm_mmu_get_child_sp() does not compare the role, and therefore reuses the page. The next step is installing a leaf (4KB) SPTE on the new path which records an rmap entry under the gfn resolved by the walk. But when that child is zapped its parent kvm_mmu_page has direct=1 and kvm_mmu_page_get_gfn() computes the gfn for the 4KB page as sp->gfn + index instead of using sp->shadowed_translation[] (or sp->gfns[] in older kernels). It therefore fails to remove the recorded entry. When the memslot is dropped the shadow page is freed but the rmap entry survives, as in the scenario that was already fixed. Code that later walks that gfn (dirty logging, MMU notifier invalidation, and so on) dereferences an sptep that lies in the freed page, causing the use-after-free.CVE-2026-53359