Canonical Ubuntu Linux Linux Operating System
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in Canonical Ubuntu Linux.
Recent Canonical Ubuntu Linux Security Advisories
| Advisory | Title | Published |
|---|---|---|
| USN-8098-9 | USN-8098-9: Linux kernel (IBM) vulnerabilities | March 27, 2026 |
| USN-8128-1 | USN-8128-1: CryptX vulnerabilities | March 26, 2026 |
| USN-8126-1 | USN-8126-1: Linux kernel (Azure) vulnerabilities | March 25, 2026 |
| USN-8125-1 | USN-8125-1: Linux kernel (Azure) vulnerabilities | March 25, 2026 |
| USN-8094-4 | USN-8094-4: Linux kernel (Azure) vulnerabilities | March 25, 2026 |
| USN-8124-1 | USN-8124-1: Bind vulnerabilities | March 25, 2026 |
| USN-8123-1 | USN-8123-1: Mbed TLS vulnerabilities | March 25, 2026 |
| USN-8098-8 | USN-8098-8: Linux kernel (Azure FIPS) vulnerabilities | March 25, 2026 |
| USN-8098-7 | USN-8098-7: Linux kernel (Azure) vulnerabilities | March 25, 2026 |
| USN-8122-1 | USN-8122-1: PJSIP vulnerabilities | March 24, 2026 |
By the Year
In 2026 there have been 244 vulnerabilities in Canonical Ubuntu Linux with an average score of 6.1 out of ten. Last year, in 2025 Ubuntu Linux had 2851 security vulnerabilities published. Right now, Ubuntu Linux is on track to have less security vulnerabilities in 2026 than it did last year. Last year, the average CVE base score was greater by 0.23
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2026 | 244 | 6.06 |
| 2025 | 2851 | 6.29 |
| 2024 | 3542 | 6.32 |
| 2023 | 1069 | 6.88 |
| 2022 | 1201 | 6.99 |
| 2021 | 738 | 6.85 |
| 2020 | 744 | 6.25 |
| 2019 | 788 | 6.99 |
| 2018 | 921 | 7.12 |
It may take a day or so for new Ubuntu Linux vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Canonical Ubuntu Linux Security Vulnerabilities
libssh Denial of Service via Arbitrary File Access during Config Parsing
CVE-2026-0965
- March 26, 2026
A flaw was found in libssh where it can attempt to open arbitrary files during configuration parsing. A local attacker can exploit this by providing a malicious configuration file or when the system is misconfigured. This vulnerability could lead to a Denial of Service (DoS) by causing the system to try and access dangerous files, such as block devices or large system files, which can disrupt normal operations.
External Control of File Name or Path
Libssh DoS via regex backtracking in match_pattern with crafted hostnames
CVE-2026-0967
- March 26, 2026
A flaw was found in libssh. A remote attacker, by controlling client configuration files or known_hosts files, could craft specific hostnames that when processed by the `match_pattern()` function can lead to inefficient regular expression backtracking. This can cause timeouts and resource exhaustion, resulting in a Denial of Service (DoS) for the client.
ReDoS
libssh SFTP longname NullCheck: Heap OverRead -> DoS
CVE-2026-0968
- March 26, 2026
A flaw was found in libssh in which a malicious SFTP (SSH File Transfer Protocol) server can exploit this by sending a malformed 'longname' field within an `SSH_FXP_NAME` message during a file listing operation. This missing null check can lead to reading beyond allocated memory on the heap. This can cause unexpected behavior or lead to a denial of service (DoS) due to application crashes.
NULL Pointer Dereference
SCP Client Path Traversal Allowing Local File Overwrite (CVE-2026-0964)
CVE-2026-0964
- March 26, 2026
A malicious SCP server can send unexpected paths that could make the client application override local files outside of working directory. This could be misused to create malicious executable or configuration files and make the user execute them under specific consequences. This is the same issue as in OpenSSH, tracked as CVE-2019-6111.
Directory traversal
OpenSSH ssh_get_hexa Zero-Length Leak Self-DoS via GSSAPI
CVE-2026-0966
- March 26, 2026
The API function `ssh_get_hexa()` is vulnerable, when 0-lenght input is provided to this function. This function is used internally in `ssh_get_fingerprint_hash()` and `ssh_print_hexa()` (deprecated), which is vulnerable to the same input (length is provided by the calling application). The function is also used internally in the gssapi code for logging the OIDs received by the server during GSSAPI authentication. This could be triggered remotely, when the server allows GSSAPI authentication and logging verbosity is set at least to SSH_LOG_PACKET (3). This could cause self-DoS of the per-connection daemon process.
buffer underrun
Use-After-Return in ISC BIND 9 named for SIG(0) (9.20.020, 9.21.019, 9.20.9S120)
CVE-2026-3591
5.4 - Medium
- March 25, 2026
A use-after-return vulnerability exists in the `named` server when handling DNS queries signed with SIG(0). Using a specially-crafted DNS request, an attacker may be able to cause an ACL to improperly (mis)match an IP address. In a default-allow ACL (denying only specific IP addresses), this may lead to unauthorized access. Default-deny ACLs should fail-secure. This issue affects BIND 9 versions 9.20.0 through 9.20.20, 9.21.0 through 9.21.19, and 9.20.9-S1 through 9.20.20-S1. BIND 9 versions 9.18.0 through 9.18.46 and 9.18.11-S1 through 9.18.46-S1 are NOT affected.
Return of Stack Variable Address
BIND 9 Crash via Signed TSIG TKEY Query (9.20.0 9.21.19)
CVE-2026-3119
6.5 - Medium
- March 25, 2026
Under certain conditions, `named` may crash when processing a correctly signed query containing a TKEY record. The affected code can only be reached if an incoming request has a valid transaction signature (TSIG) from a key declared in the `named` configuration. This issue affects BIND 9 versions 9.20.0 through 9.20.20, 9.21.0 through 9.21.19, and 9.20.9-S1 through 9.20.20-S1. BIND 9 versions 9.18.0 through 9.18.46 and 9.18.11-S1 through 9.18.46-S1 are NOT affected.
assertion failure
ISC BIND 9 9.20.09.20.20 Memory Leak via Crafted Domain
CVE-2026-3104
7.5 - High
- March 25, 2026
A specially crafted domain can be used to cause a memory leak in a BIND resolver simply by querying this domain. This issue affects BIND 9 versions 9.20.0 through 9.20.20, 9.21.0 through 9.21.19, and 9.20.9-S1 through 9.20.20-S1. BIND 9 versions 9.18.0 through 9.18.46 and 9.18.11-S1 through 9.18.46-S1 are NOT affected.
Missing Release of Resource after Effective Lifetime
BIND 9 DNSSEC Zone Crafting CPU Exhaustion (9.11-9.21)
CVE-2026-1519
7.5 - High
- March 25, 2026
If a BIND resolver is performing DNSSEC validation and encounters a maliciously crafted zone, the resolver may consume excessive CPU. Authoritative-only servers are generally unaffected, although there are circumstances where authoritative servers may make recursive queries (see: https://kb.isc.org/docs/why-does-my-authoritative-server-make-recursive-queries). This issue affects BIND 9 versions 9.11.0 through 9.16.50, 9.18.0 through 9.18.46, 9.20.0 through 9.20.20, 9.21.0 through 9.21.19, 9.11.3-S1 through 9.16.50-S1, 9.18.11-S1 through 9.18.46-S1, and 9.20.9-S1 through 9.20.20-S1.
Unchecked Input for Loop Condition
systemd IPC API Assert Freeze v239-<257.11 (v258-<258.5, v259-<259.2)
CVE-2026-29111
5.5 - Medium
- March 23, 2026
systemd, a system and service manager, (as PID 1) hits an assert and freezes execution when an unprivileged IPC API call is made with spurious data. On version v249 and older the effect is not an assert, but stack overwriting, with the attacker controlled content. From version v250 and newer this is not possible as the safety check causes an assert instead. This IPC call was added in v239, so versions older than that are not affected. Versions 260-rc1, 259.2, 258.5, and 257.11 contain patches. No known workarounds are available.
Improper Privilege Management
pyOpenSSL CVE-2026-27459: Buffer Overflow via cookie callback (22.0.0-26.0.0)
CVE-2026-27459
- March 17, 2026
pyOpenSSL is a Python wrapper around the OpenSSL library. Starting in version 22.0.0 and prior to version 26.0.0, if a user provided callback to `set_cookie_generate_callback` returned a cookie value greater than 256 bytes, pyOpenSSL would overflow an OpenSSL provided buffer. Starting in version 26.0.0, cookie values that are too long are now rejected.
Classic Buffer Overflow
pyOpenSSL 0.14.0-<26.0.0 TLS ServerName CB Exception Bypass
CVE-2026-27448
- March 17, 2026
pyOpenSSL is a Python wrapper around the OpenSSL library. Starting in version 0.14.0 and prior to version 26.0.0, if a user provided callback to `set_tlsext_servername_callback` raised an unhandled exception, this would result in a connection being accepted. If a user was relying on this callback for any security-sensitive behavior, this could allow bypassing it. Starting in version 26.0.0, unhandled exceptions now result in rejecting the connection.
Failing Open
OpenSSH GSSAPI: Uninitialized Variables via sshpkt_disconnect
CVE-2026-3497
- March 12, 2026
Vulnerability in the OpenSSH GSSAPI delta included in various Linux distributions. This vulnerability affects the GSSAPI patches added by various Linux distributions and does not affect the OpenSSH upstream project itself. The usage of sshpkt_disconnect() on an error, which does not terminate the process, allows an attacker to send an unexpected GSSAPI message type during the GSSAPI key exchange to the server, which will call the underlying function and continue the execution of the program without setting the related connection variables. As the variables are not initialized to NULL the code later accesses those uninitialized variables, accessing random memory, which could lead to undefined behavior. The recommended workaround is to use ssh_packet_disconnect() instead, which does terminate the process. The impact of the vulnerability depends heavily on the compiler flag hardening configuration.
Use of Uninitialized Resource
curl SMB UAF: freed memory used on repeated request
CVE-2026-3805
7.5 - High
- March 11, 2026
When doing a second SMB request to the same host again, curl would wrongly use a data pointer pointing into already freed memory.
Dangling pointer
CURL: Improper HTTP Proxy Connection Reuse with Different Credentials
CVE-2026-3784
6.5 - Medium
- March 11, 2026
curl would wrongly reuse an existing HTTP proxy connection doing CONNECT to a server, even if the new request uses different credentials for the HTTP proxy. The proper behavior is to create or use a separate connection.
Authentication Bypass by Primary Weakness
curl HTTP Redirect Leaks OAuth2 Bearer Token
CVE-2026-3783
5.3 - Medium
- March 11, 2026
When an OAuth2 bearer token is used for an HTTP(S) transfer, and that transfer performs a redirect to a second URL, curl could leak that token to the second hostname under some circumstances. If the hostname that the first request is redirected to has information in the used .netrc file, with either of the `machine` or `default` keywords, curl would pass on the bearer token set for the first host also to the second one.
Insufficiently Protected Credentials
libcurl Negotiate Auth Reuse Vulnerability: Wrong Credential Leak
CVE-2026-1965
6.5 - Medium
- March 11, 2026
libcurl can in some circumstances reuse the wrong connection when asked to do an Negotiate-authenticated HTTP or HTTPS request. libcurl features a pool of recent connections so that subsequent requests can reuse an existing connection to avoid overhead. When reusing a connection a range of criterion must first be met. Due to a logical error in the code, a request that was issued by an application could wrongfully reuse an existing connection to the same server that was authenticated using different credentials. One underlying reason being that Negotiate sometimes authenticates *connections* and not *requests*, contrary to how HTTP is designed to work. An application that allows Negotiate authentication to a server (that responds wanting Negotiate) with `user1:password1` and then does another operation to the same server also using Negotiate but with `user2:password2` (while the previous connection is still alive) - the second request wrongly reused the same connection and since it then sees that the Negotiate negotiation is already made, it just sends the request over that connection thinking it uses the user2 credentials when it is in fact still using the connection authenticated for user1... The set of authentication methods to use is set with `CURLOPT_HTTPAUTH`. Applications can disable libcurl's reuse of connections and thus mitigate this problem, by using one of the following libcurl options to alter how connections are or are not reused: `CURLOPT_FRESH_CONNECT`, `CURLOPT_MAXCONNECTS` and `CURLMOPT_MAX_HOST_CONNECTIONS` (if using the curl_multi API).
Authentication Bypass by Primary Weakness
Mar 2026: ASP.NET Core Denial of Service Vulnerability
CVE-2026-26130
7.5 - High
- March 10, 2026
Allocation of resources without limits or throttling in ASP.NET Core allows an unauthorized attacker to deny service over a network.
Allocation of Resources Without Limits or Throttling
Mar 2026: .NET Denial of Service Vulnerability
CVE-2026-26127
7.5 - High
- March 10, 2026
Out-of-bounds read in .NET allows an unauthorized attacker to deny service over a network.
Out-of-bounds Read
Ubuntu 6.8 Kernel: AF_UNIX UAF in legacy GC LPE
CVE-2025-13350
- March 05, 2026
Ubuntu Linux 6.8 GA retains the legacy AF_UNIX garbage collector but backports upstream commit 8594d9b85c07 ("af_unix: Dont call skb_get() for OOB skb"). When orphaned MSG_OOB sockets hit unix_gc(), the garbage collector still calls kfree_skb() as if OOB SKBs held two references; on Ubuntu Linux 6.8 (Noble Numbat) kernel tree, they have only the queue reference, so the buffer is freed while still reachable and subsequent queue walks dereference freed memory, yielding a reliable local privilege escalation (LPE) caused by a use-after-free (UAF). Ubuntu builds that have already taken the new GC stack from commit 4090fa373f0e, and mainline Linux kernels shipping that infrastructure are unaffected because they no longer execute the legacy collector path. This issue affects Ubuntu Linux from 6.8.0-56.58 before 6.8.0-84.84.
Dangling pointer
Exiv2 OOB Read in CRW Parser (<=0.28.7), Fixed in 0.28.8
CVE-2026-25884
- March 02, 2026
Exiv2 is a C++ library and a command-line utility to read, write, delete and modify Exif, IPTC, XMP and ICC image metadata. Prior to version 0.28.8, an out-of-bounds read was found. The vulnerability is in the CRW image parser. This issue has been patched in version 0.28.8.
Out-of-bounds Read
Exiv2 OOB Read in Preview (-pp) fixed in 0.28.8
CVE-2026-27596
- March 02, 2026
Exiv2 is a C++ library and a command-line utility to read, write, delete and modify Exif, IPTC, XMP and ICC image metadata. Prior to version 0.28.8, an out-of-bounds read was found in Exiv2. The vulnerability is in the preview component, which is only triggered when running Exiv2 with an extra command line argument, like -pp. The out-of-bounds read is at a 4GB offset, which usually causes Exiv2 to crash. This issue has been patched in version 0.28.8.
Out-of-bounds Read
Exiv2 C++ Preview Component Integer Overflow CVE202627631 (Fixed in 0.28.8)
CVE-2026-27631
- March 02, 2026
Exiv2 is a C++ library and a command-line utility to read, write, delete and modify Exif, IPTC, XMP and ICC image metadata. Prior to version 0.28.8, an uncaught exception was found in Exiv2. The vulnerability is in the preview component, which is only triggered when running Exiv2 with an extra command line argument, like -pp. Due to an integer overflow, the code attempts to create a huge std::vector, which causes Exiv2 to crash with an uncaught exception. This issue has been patched in version 0.28.8.
Uncaught Exception
Vim <9.2.0078: stack-buffer-overflow in statusline rendering
CVE-2026-28422
2.2 - Low
- February 27, 2026
Vim is an open source, command line text editor. Prior to version 9.2.0078, a stack-buffer-overflow occurs in `build_stl_str_hl()` when rendering a statusline with a multi-byte fill character on a very wide terminal. Version 9.2.0078 patches the issue.
Stack Overflow
Vim <9.2.0077: Heap Buffer Overflow in Swap Recovery
CVE-2026-28421
5.3 - Medium
- February 27, 2026
Vim is an open source, command line text editor. Versions prior to 9.2.0077 have a heap-buffer-overflow and a segmentation fault (SEGV) exist in Vim's swap file recovery logic. Both are caused by unvalidated fields read from crafted pointer blocks within a swap file. Version 9.2.0077 fixes the issue.
Improper Input Validation
Vim <9.2.0076 Heap OOB Buf Read/Write via Max Unicode Combining
CVE-2026-28420
4.4 - Medium
- February 27, 2026
Vim is an open source, command line text editor. Prior to version 9.2.0076, a heap-based buffer overflow WRITE and an out-of-bounds READ exist in Vim's terminal emulator when processing maximum combining characters from Unicode supplementary planes. Version 9.2.0076 fixes the issue.
Heap-based Buffer Overflow
Vim 9.2.0075: Heap Buffer Underflow in Emacs-Style Tags Parsing
CVE-2026-28419
5.3 - Medium
- February 27, 2026
Vim is an open source, command line text editor. Prior to version 9.2.0075, a heap-based buffer underflow exists in Vim's Emacs-style tags file parsing logic. When processing a malformed tags file where a delimiter appears at the start of a line, Vim attempts to read memory immediately preceding the allocated buffer. Version 9.2.0075 fixes the issue.
buffer underrun
Vim<9.2.0074 Heap Buffer Overflow via Emacs-Style Tags Parsing
CVE-2026-28418
4.4 - Medium
- February 27, 2026
Vim is an open source, command line text editor. Prior to version 9.2.0074, a heap-based buffer overflow out-of-bounds read exists in Vim's Emacs-style tags file parsing logic. When processing a malformed tags file, Vim can be tricked into reading up to 7 bytes beyond the allocated memory boundary. Version 9.2.0074 fixes the issue.
Heap-based Buffer Overflow
Vim 9.2.0072 netrw CMD-INJ via scp://
CVE-2026-28417
4.4 - Medium
- February 27, 2026
Vim is an open source, command line text editor. Prior to version 9.2.0073, an OS command injection vulnerability exists in the `netrw` standard plugin bundled with Vim. By inducing a user to open a crafted URL (e.g., using the `scp://` protocol handler), an attacker can execute arbitrary shell commands with the privileges of the Vim process. Version 9.2.0073 fixes the issue.
Improper Neutralization of Invalid Characters in Identifiers in Web Pages
GVfs FTP Backend IP/Port Spoofing Allows Client Port Scanning
CVE-2026-28295
4.3 - Medium
- February 26, 2026
A flaw was found in the FTP GVfs backend. A malicious FTP server can exploit this vulnerability by providing an arbitrary IP address and port in its passive mode (PASV) response. The client unconditionally trusts this information and attempts to connect to the specified endpoint, allowing the malicious server to probe for open ports accessible from the client's network.
SSRF
ImageMagick PCD Huffman OOB Read Fixed in 7.1.2-15/6.9.13-40
CVE-2026-26284
6.5 - Medium
- February 24, 2026
ImageMagick is free and open-source software used for editing and manipulating digital images. Prior to versions 7.1.2-15 and 6.9.13-40, ImageMagick lacks proper boundary checking when processing Huffman-coded data from PCD (Photo CD) files. The decoder contains an function that has an incorrect initialization that could cause an out of bounds read. Versions 7.1.2-15 and 6.9.13-40 contain a patch.
Heap-based Buffer Overflow
ImageMagick MAP Decoder Heap Buffer Over-read (CVE-2026-25987) before 7.1.2-15
CVE-2026-25987
5.3 - Medium
- February 24, 2026
ImageMagick is free and open-source software used for editing and manipulating digital images. Prior to versions 7.1.2-15 and 6.9.13-40, a heap buffer over-read vulnerability exists in the MAP image decoder when processing crafted MAP files, potentially leading to crashes or unintended memory disclosure during image decoding. Versions 7.1.2-15 and 6.9.13-40 contain a patch.
Out-of-bounds Read
ImageMagick 7.1.2-14 heap overflow in ReadYUVImage() YUV 4:2:2
CVE-2026-25986
5.3 - Medium
- February 24, 2026
ImageMagick is free and open-source software used for editing and manipulating digital images. Prior to versions 7.1.2-15 and 6.9.13-40, a heap buffer overflow write vulnerability exists in ReadYUVImage() (coders/yuv.c) when processing malicious YUV 4:2:2 (NoInterlace) images. The pixel-pair loop writes one pixel beyond the allocated row buffer. Versions 7.1.2-15 and 6.9.13-40 contain a patch.
Memory Corruption
ImageMagick <7.1.2-15 heap UAF via crafted MSL script
CVE-2026-25983
5.3 - Medium
- February 24, 2026
ImageMagick is free and open-source software used for editing and manipulating digital images. Prior to versions 7.1.2-15 and 6.9.13-40, a crafted MSL script triggers a heap-use-after-free. The operation element handler replaces and frees the image while the parser continues reading from it, leading to a UAF in ReadBlobString during further parsing. Versions 7.1.2-15 and 6.9.13-40 contain a patch.
Dangling pointer
ImageMagick stack buffer overflow (msl.c) before 7.1.2-15/6.9.13-40
CVE-2026-25968
7.4 - High
- February 24, 2026
ImageMagick is free and open-source software used for editing and manipulating digital images. Prior to versions 7.1.2-15 and 6.9.13-40, a stack buffer overflow occurs when processing the an attribute in msl.c. A long value overflows a fixed-size stack buffer, leading to memory corruption. Versions 7.1.2-15 and 6.9.13-40 contain a patch.
Stack Overflow
ImageMagick 7.1.2-15/6.9.13-40 UI/XPM Index Overflow Crash
CVE-2026-25898
6.5 - Medium
- February 24, 2026
ImageMagick is free and open-source software used for editing and manipulating digital images. Prior to versions 7.1.2-15 and 6.9.13-40, the UIL and XPM image encoder do not validate the pixel index value returned by `GetPixelIndex()` before using it as an array subscript. In HDRI builds, `Quantum` is a floating-point type, so pixel index values can be negative. An attacker can craft an image with negative pixel index values to trigger a global buffer overflow read during conversion, leading to information disclosure or a process crash. Versions 7.1.2-15 and 6.9.13-40 contain a patch.
Out-of-bounds Read
ImageMagick Integer Overflow in sun decoder pre7.1.215/6.9.1340
CVE-2026-25897
6.5 - Medium
- February 24, 2026
ImageMagick is free and open-source software used for editing and manipulating digital images. Prior to versions 7.1.2-15 and 6.9.13-40, an Integer Overflow vulnerability exists in the sun decoder. On 32-bit systems/builds, a carefully crafted image can lead to an out of bounds heap write. Versions 7.1.2-15 and 6.9.13-40 contain a patch.
Heap-based Buffer Overflow
Valkey <=9.0.2 Clusterbus OOB Read Crash
CVE-2026-21863
7.5 - High
- February 23, 2026
Valkey is a distributed key-value database. Prior to versions 9.0.2, 8.1.6, 8.0.7, and 7.2.12, a malicious actor with access to the Valkey clusterbus port can send an invalid packet that may cause an out bound read, which might result in the system crashing. The Valkey clusterbus packet processing code does not validate that a clusterbus ping extension packet is located within buffer of the clusterbus packet before attempting to read it. Versions 9.0.2, 8.1.6, 8.0.7, and 7.2.12 fix the issue. As an additional mitigation, don't expose the cluster bus connection directly to end users, and protect the connection with its own network ACLs.
Out-of-bounds Read
Valkey Lua Script Null Byte Injection CVE-2025-67733 - Fixed 9.0.2, 8.1.6, 8.0.7
CVE-2025-67733
8.5 - High
- February 23, 2026
Valkey is a distributed key-value database. Prior to versions 9.0.2, 8.1.6, 8.0.7, and 7.2.12, a malicious user can use scripting commands to inject arbitrary information into the response stream for the given client, potentially corrupting or returning tampered data to other users on the same connection. The error handling code for lua scripts does not properly handle null characters. Versions 9.0.2, 8.1.6, 8.0.7, and 7.2.12 fix the issue.
Injection
QEMU KVM Xen Guest Off-By-One heap OOB access in Xen physdev
CVE-2026-0665
6.5 - Medium
- February 18, 2026
An off-by-one error was found in QEMU's KVM Xen guest support. A malicious guest could use this flaw to trigger out-of-bounds heap accesses in the QEMU process via the emulated Xen physdev hypercall interface, leading to a denial of service or potential memory corruption.
Memory Corruption
QEMU virtio-crypto AKCIPHER DoS via unchecked memory allocation
CVE-2025-14876
5.5 - Medium
- February 18, 2026
A flaw was found in the virtio-crypto device of QEMU. A malicious guest operating system can exploit a missing length limit in the AKCIPHER path, leading to uncontrolled memory allocation. This can result in a denial of service (DoS) on the host system by causing the QEMU process to terminate unexpectedly.
Allocation of Resources Without Limits or Throttling
FFmpeg Firequalizer NULL Pointer Deref Leading to DoS
CVE-2025-10256
5.3 - Medium
- February 18, 2026
A NULL pointer dereference vulnerability exists in FFmpegs Firequalizer filter (libavfilter/af_firequalizer.c) due to a missing check on the return value of av_malloc_array() in the config_input() function. An attacker could exploit this by tricking a victim into processing a crafted media file with the Firequalizer filter enabled, causing the application to dereference a NULL pointer and crash, leading to denial of service.
NULL Pointer Dereference
Rack 2.2.22 / 3.1.20 / 3.2.5 Fixed XSS in Directory Index via javascript: links
CVE-2026-25500
5.4 - Medium
- February 18, 2026
Rack is a modular Ruby web server interface. Prior to versions 2.2.22, 3.1.20, and 3.2.5, `Rack::Directory` generates an HTML directory index where each file entry is rendered as a clickable link. If a file exists on disk whose basename starts with the `javascript:` scheme (e.g. `javascript:alert(1)`), the generated index contains an anchor whose `href` is exactly `javascript:alert(1)`. Clicking the entry executes JavaScript in the browser (demonstrated with `alert(1)`). Versions 2.2.22, 3.1.20, and 3.2.5 fix the issue.
XSS
Rack::Directory Path Escape Prior to 2.2.22/3.1.20/3.2.5
CVE-2026-22860
7.5 - High
- February 18, 2026
Rack is a modular Ruby web server interface. Prior to versions 2.2.22, 3.1.20, and 3.2.5, `Rack::Directory`s path check used a string prefix match on the expanded path. A request like `/../root_example/` can escape the configured root if the target path starts with the root string, allowing directory listing outside the intended root. Versions 2.2.22, 3.1.20, and 3.2.5 fix the issue.
Directory traversal
Linux Kernel TEGRA210 QSPI curr_xfer race causes NULL deref
CVE-2026-23207
- February 14, 2026
In the Linux kernel, the following vulnerability has been resolved: spi: tegra210-quad: Protect curr_xfer check in IRQ handler Now that all other accesses to curr_xfer are done under the lock, protect the curr_xfer NULL check in tegra_qspi_isr_thread() with the spinlock. Without this protection, the following race can occur: CPU0 (ISR thread) CPU1 (timeout path) ---------------- ------------------- if (!tqspi->curr_xfer) // sees non-NULL spin_lock() tqspi->curr_xfer = NULL spin_unlock() handle_*_xfer() spin_lock() t = tqspi->curr_xfer // NULL! ... t->len ... // NULL dereference! With this patch, all curr_xfer accesses are now properly synchronized. Although all accesses to curr_xfer are done under the lock, in tegra_qspi_isr_thread() it checks for NULL, releases the lock and reacquires it later in handle_cpu_based_xfer()/handle_dma_based_xfer(). There is a potential for an update in between, which could cause a NULL pointer dereference. To handle this, add a NULL check inside the handlers after acquiring the lock. This ensures that if the timeout path has already cleared curr_xfer, the handler will safely return without dereferencing the NULL pointer.
Linux Kernel SPI tegra210-Quad curr_xfer Race Leading to Null Deref
CVE-2026-23202
- February 14, 2026
In the Linux kernel, the following vulnerability has been resolved: spi: tegra210-quad: Protect curr_xfer in tegra_qspi_combined_seq_xfer The curr_xfer field is read by the IRQ handler without holding the lock to check if a transfer is in progress. When clearing curr_xfer in the combined sequence transfer loop, protect it with the spinlock to prevent a race with the interrupt handler. Protect the curr_xfer clearing at the exit path of tegra_qspi_combined_seq_xfer() with the spinlock to prevent a race with the interrupt handler that reads this field. Without this protection, the IRQ handler could read a partially updated curr_xfer value, leading to NULL pointer dereference or use-after-free.
Vim <9.1.2148: NetBeans specialKeys Stack Buffer Overflow
CVE-2026-26269
5.4 - Medium
- February 13, 2026
Vim is an open source, command line text editor. Prior to 9.1.2148, a stack buffer overflow vulnerability exists in Vim's NetBeans integration when processing the specialKeys command, affecting Vim builds that enable and use the NetBeans feature. The Stack buffer overflow exists in special_keys() (in src/netbeans.c). The while (*tok) loop writes two bytes per iteration into a 64-byte stack buffer (keybuf) with no bounds check. A malicious NetBeans server can overflow keybuf with a single specialKeys command. The issue has been fixed as of Vim patch v9.1.2148.
Stack Overflow
PostgreSQL Buffer Overrun via Char Valid. (18.2/17.8/16.12/15.16/14.21)
CVE-2026-2006
8.8 - High
- February 12, 2026
Missing validation of multibyte character length in PostgreSQL text manipulation allows a database user to issue crafted queries that achieve a buffer overrun. That suffices to execute arbitrary code as the operating system user running the database. Versions before PostgreSQL 18.2, 17.8, 16.12, 15.16, and 14.21 are affected.
out-of-bounds array index
Heap Buffer Overflow in PostgreSQL pgcrypto (pre 18.2/17.8/16.12/15.16/14.21) OS Exploit
CVE-2026-2005
8.8 - High
- February 12, 2026
Heap buffer overflow in PostgreSQL pgcrypto allows a ciphertext provider to execute arbitrary code as the operating system user running the database. Versions before PostgreSQL 18.2, 17.8, 16.12, 15.16, and 14.21 are affected.
Heap-based Buffer Overflow
PostgreSQL intarray RCE before 18.2/17.8/16.12/15.16/14.21
CVE-2026-2004
8.8 - High
- February 12, 2026
Missing validation of type of input in PostgreSQL intarray extension selectivity estimator function allows an object creator to execute arbitrary code as the operating system user running the database. Versions before PostgreSQL 18.2, 17.8, 16.12, 15.16, and 14.21 are affected.
Improper Validation of Specified Type of Input
Stay on top of Security Vulnerabilities
Want an email whenever new vulnerabilities are published for Canonical Ubuntu Linux or by Canonical? Click the Watch button to subscribe.