Skip to content
Noroxi
CVE-2025-40176· NVD / CVE Program· CNA Linux

tls: wait for pending async decryptions if tls_strp_msg_hold fails

Noroxi assessment

Priority: Monitor (action score 39/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.46% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: Linux Linux 39dec4ea3daf77f684308576baf483b55ca7f160, 4fc109d0ab196bd943b7451276690fb6bb48c2e0, 9f83fd0c179e0f458e824e417f9d5ad53443f685; azl3 kernel 6.6.112.1-2 on Azure Linux 3.0 6.6.117.1-1.

Low priority for now. Upgrade to Linux Linux 39dec4ea3daf77f684308576baf483b55ca7f160, 4fc109d0ab196bd943b7451276690fb6bb48c2e0, 9f83fd0c179e0f458e824e417f9d5ad53443f685; azl3 kernel 6.6.112.1-2 on Azure Linux 3.0 6.6.117.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: tls: wait for pending async decryptions if tls_strp_msg_hold fails Async decryption calls tls_strp_msg_hold to create a clone of the input skb to hold references to the memory it uses. If we fail to allocate that clone, proceeding with async decryption can lead to various issues (UAF on the skb, writing into userspace memory after the recv() call has returned). In this case, wait for all pending decryption requests.

CriticalCVSS 9.8 · v3.1—No exploit Fix available
Published
Nov 12, 2025
Updated
Oct 15, 2026
EPSS
0.4% · 38th percentile
CWE
—

Report tools

JSON

Action score

39

Monitor

Low priority for now.

CVSS
39 / 40 · 9.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
9.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-40176

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.0affected
    • 84c61fe1a75b4255df1e1e7c054c9e6d048da417 and later · before 9f83fd0c179e0f458e824e417f9d5ad53443f685affected · git
    • 84c61fe1a75b4255df1e1e7c054c9e6d048da417 and later · before c61d4368197d65c4809d9271f3b85325a600586aaffected · git
    • 84c61fe1a75b4255df1e1e7c054c9e6d048da417 and later · before 39dec4ea3daf77f684308576baf483b55ca7f160affected · git
    • 84c61fe1a75b4255df1e1e7c054c9e6d048da417 and later · before 4fc109d0ab196bd943b7451276690fb6bb48c2e0affected · git
    • 84c61fe1a75b4255df1e1e7c054c9e6d048da417 and later · before b8a6ff84abbcbbc445463de58704686011edc8e1affected · git
    • before 6.0not affected · semver
    • 6.1.158 and later · up to and including 6.1.*not affected · semver
    • 6.6.114 and later · up to and including 6.6.*not affected · semver
    • 6.12.55 and later · up to and including 6.12.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-124.27.1.el10_16.12.0-124.27.1.el10_1
AlmaLinux:10kernel-docbefore 6.12.0-124.27.1.el10_16.12.0-124.27.1.el10_1
AlmaLinux:9kernelbefore 5.14.0-611.16.1.el9_75.14.0-611.16.1.el9_7
AlmaLinux:9kernel-64kbefore 5.14.0-611.16.1.el9_75.14.0-611.16.1.el9_7
AlmaLinux:9kernel-64k-corebefore 5.14.0-611.16.1.el9_75.14.0-611.16.1.el9_7
AlmaLinux:9kernel-64k-debugbefore 5.14.0-611.16.1.el9_75.14.0-611.16.1.el9_7
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-611.16.1.el9_75.14.0-611.16.1.el9_7
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-611.16.1.el9_75.14.0-611.16.1.el9_7
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-611.16.1.el9_75.14.0-611.16.1.el9_7
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-611.16.1.el9_75.14.0-611.16.1.el9_7
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-611.16.1.el9_75.14.0-611.16.1.el9_7
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-611.16.1.el9_75.14.0-611.16.1.el9_7
AlmaLinux:9kernel-64k-develbefore 5.14.0-611.16.1.el9_75.14.0-611.16.1.el9_7
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-611.16.1.el9_75.14.0-611.16.1.el9_7
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-611.16.1.el9_75.14.0-611.16.1.el9_7
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-611.16.1.el9_75.14.0-611.16.1.el9_7
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-611.16.1.el9_75.14.0-611.16.1.el9_7
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-611.16.1.el9_75.14.0-611.16.1.el9_7
AlmaLinux:9kernel-corebefore 5.14.0-611.16.1.el9_75.14.0-611.16.1.el9_7
AlmaLinux:9kernel-cross-headersbefore 5.14.0-611.16.1.el9_75.14.0-611.16.1.el9_7
AlmaLinux:9kernel-debugbefore 5.14.0-611.16.1.el9_75.14.0-611.16.1.el9_7
AlmaLinux:9kernel-debug-corebefore 5.14.0-611.16.1.el9_75.14.0-611.16.1.el9_7
AlmaLinux:9kernel-debug-develbefore 5.14.0-611.16.1.el9_75.14.0-611.16.1.el9_7
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-611.16.1.el9_75.14.0-611.16.1.el9_7

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan
  • CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index
    40Plan
  • CVE-2026-72421ipv4: fib: Don't ignore error route in local/main tables.
    40Plan
  • CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler
    40Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux39dec4ea3daf77f684308576baf483b55ca7f160Vendor (CNA)
Linux Linux4fc109d0ab196bd943b7451276690fb6bb48c2e0Vendor (CNA)
Linux Linux9f83fd0c179e0f458e824e417f9d5ad53443f685Vendor (CNA)
Linux Linuxb8a6ff84abbcbbc445463de58704686011edc8e1Vendor (CNA)
Linux Linuxc61d4368197d65c4809d9271f3b85325a600586aVendor (CNA)
azl3 kernel 6.6.112.1-2 on Azure Linux 3.06.6.117.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:kernel5.14.0-611.16.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-611.16.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-611.16.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-611.16.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-611.16.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-611.16.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-611.16.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-611.16.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-611.16.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-611.16.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-611.16.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-611.16.1.el9_7 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.158-1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-611.16.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-611.16.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-611.16.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-611.16.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-611.16.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-611.16.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-611.16.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-611.16.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-611.16.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-611.16.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-611.16.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

+2

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records