Patch Forecast
Amber warning
Patch this week.

CVE-2026-64541

Canonical Ubuntu Linux: use-after-free

Risk score
79/100
CVSS
9.8 v3.1
Published
27 Jul 2026

Open in the live forecast Today's forecast

What to know

What it is
A critical vulnerability in the Linux kernel allows an attacker to potentially gain control of the system, access sensitive information, and disrupt the system's integrity. An attacker could exploit this vulnerability remotely without requiring user interaction.
Affected
{'product': 'Ubuntu Linux', 'vendor': 'Canonical'}
Fix
Check the linked advisory for the fix, as no specific version is given.
Exploitation
No known exploitation

Story map

Story map: Canonical Ubuntu LinuxTHE FLAWSTHE FIXCVE-2026-64541Use-after-freeCVSS 9.8CVE-2026-93479Heap buffer overflow can leadto remote code executionCVSS 8.1 · EPSS 1%CVE-2026-15176Heap buffer overflow can leadto remote code executionCVSS 8.1 · EPSS 1%CVE-2026-97205NGINX Plus and NGINX OpenSource have a vulnerability inthe ngx_http_core_module…CVSS 8.1 · EPSS 1%FixCheck the linked advisory forthe concrete fix.Who is exposed{'products': ['NGINX Plus','NGINX Open Source'],'packages': [], 'versions': []}RED · ACT TODAYCanonical UbuntuLinuxA vulnerability exists in NGINXPlus and NGINX Open Sourcewhen a map directive uses regexmatching and the root directiveor access log format referencesthe map's regex capturevariables before referencing…Where it standsNo known exploitationHOW IT UNFOLDEDOfficial record on the left, the press on the right, oldest first.26 Oct · Ubuntu security noticesUSN-8955-1: nginx vulnerabilities5 Nov · Ubuntu security noticesUSN-8955-2: nginx vulnerabilities6 Nov · Ubuntu security noticesUSN-9003-1: Linux kernel (NVIDIA) vulnerabilitiesCONNECTS TOSame weaknessUse-after-free (CWE-416)400 other warnings in 30 days →Same productEarlier Canonical Ubuntu Linux warnings163 in the last 90 days →
Story map: the flaws, the fix, how it unfolded and what it connects to. Boxes link to the record or article.

At a glance

Canonical Ubuntu Linux: Red, act today. A vulnerability exists in NGINX Plus and NGINX Open Source when a map directive uses regex matching and the root directive or access log format references the map's regex capture variables before referencing the map output variable. An unauthenticated attacker can exploit this vulnerability by sending crafted HTTP requests, causing a heap buffer overflow in the NGINX worker process leading to a restart, or potential…

The flaws

  • CVE-2026-64541: Use-after-free (CVSS 9.8)
  • CVE-2026-93479: Heap buffer overflow can lead to remote code execution (CVSS 8.1 · EPSS 1%)
  • CVE-2026-15176: Heap buffer overflow can lead to remote code execution (CVSS 8.1 · EPSS 1%)
  • CVE-2026-97205: NGINX Plus and NGINX Open Source have a vulnerability in the ngx_http_core_module module (CVSS 8.1 · EPSS 1%)

The fix

Fix: Check the linked advisory for the concrete fix.

Who is exposed: {'products': ['NGINX Plus', 'NGINX Open Source'], 'packages': [], 'versions': []}

Where it stands

  • No known exploitation

How it unfolded

  1. 26 Oct, Ubuntu security notices (official): USN-8955-1: nginx vulnerabilities
  2. 5 Nov, Ubuntu security notices (official): USN-8955-2: nginx vulnerabilities
  3. 6 Nov, Ubuntu security notices (official): USN-9003-1: Linux kernel (NVIDIA) vulnerabilities

Connects to

Why it is Amber

  • CVSS 9.8 critical
  • Remotely exploitable without logging in
  • On your watchlist: linux kernel
  • Named in a government or vendor bulletin

Government and vendor bulletins

References

Original description

In the Linux kernel, the following vulnerability has been resolved: net/smc: fix UAF in smc_cdc_rx_handler() by pinning the socket smc_cdc_rx_handler() looks up the connection by token under the link group's conns_lock, drops the lock, and then dereferences conn and the smc_sock derived from it, ending in sock_hold(&smc->sk) inside smc_cdc_msg_recv(). No reference is held across the lock release. The only reference pinning the socket while the connection is discoverable in the link group is taken in smc_lgr_register_conn() (sock_hold) and dropped in __smc_lgr_unregister_conn() (sock_put), both under conns_lock. Once the handler drops conns_lock, a concurrent close() -> smc_release() -> smc_conn_free() -> smc_lgr_unregister_conn() can drop that reference and free the smc_sock, so the handler's later sock_hold() runs on freed memory: WARNING: lib/refcount.c:25 at refcount_warn_saturate Workqueue: rxe_wq do_work refcount_warn_saturate (lib/refcount.c:25) smc_cdc_msg_recv (net/smc/smc_cdc.c:430) smc_cdc_rx_handler (net/smc/smc_cdc.c:502) smc_wr_rx_tasklet_fn (net/smc/smc_wr.c:445) tasklet_action_common (kernel/softirq.c:938) handle_softirqs (kernel/softirq.c:622) Kernel panic - not syncing: panic_on_warn set Only SMC-R is affected. The SMC-D receive tasklet is stopped by tasklet_kill(&conn->rx_tsklet) in smc_conn_free() before the connection is unregistered, so it cannot run concurrently with the free. Take the socket reference while still holding conns_lock, so the registration reference can no longer be the last one, and drop it once the handler is done.

Last activity 6 Nov 2026. Patch Forecast updates every hour.