VulnerabilityPublished 10 Nov 2026Updated 12 Nov 2026

CVE-2026-68305: linux-azure vulnerabilities

Affects Linux kernelSource GCVE Database

Compare

Mentioned vulnerabilities

Authoritative record:CVE-2026-68305· High 7.8

Not known to be exploited · CVSS 7.8 High : upgrade to 7.0.0-1020.21 soon.

Data as of 12 Nov 2026, 18:49 UTC

CVSS 3.1 base score

7.8High

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 7.0.0-1020.21

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 12 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

usn-9019-1

What to do

Upgrade the Ubuntu linux-azure package to 7.0.0-1020.21.

Patches and advisories

ubuntu.com/security/notices/USN-9019-1 (opens in a new tab)

Affected software

Product	Affected	Fixed in
Ubuntu 26.04 LTSlinux-azure`pkg:deb/ubuntu/linux-azure?arch=source&distro=resolute`Other threats	Affected <7.0.0-1020.21	Fixed in 7.0.0-1020.21

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

It was discovered that the io_uring subsystem in the Linux kernel contained a memory leak when handling certain asynchronous commands. A local attacker could possibly use this to cause a denial of service (memory exhaustion). (CVE-2026-80811) It was discovered that the io_uring subsystem in the Linux kernel did not properly validate the size of certain query requests. A local attacker could possibly use this to cause a denial of service (system hang). (CVE-2026-81009) It was discovered that the io_uring subsystem in the Linux kernel did not properly handle canceled task work when processing certain wait operations, leading to the operation being performed in the wrong task context. A local attacker could possibly use this to cause a denial of service (system crash). (CVE-2026-81010) It was discovered that the io_uring subsystem in the Linux kernel did not properly track buffer consumption when receiving truncated network messages. A remote attacker could possibly use this to corrupt the receive buffers of certain applications, resulting in a denial of service or another unspecified impact. (CVE-2026-97618) Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems: - USB Gadget drivers; - Memory management; - Multiple devices driver; - ARM64 architecture; - EROFS file system; - Network file systems library; - Networking core; - eXpress Data Path; - Stream parser; - ARM32 architecture; - M68K architecture; - MIPS architecture; - OpenRISC architecture; - PA-RISC architecture; - PowerPC architecture; - RISC-V architecture; - S390 architecture; - User-Mode Linux (UML); - x86 architecture; - Block layer subsystem; - Cryptographic API; - Compute Acceleration Framework; - Intel NPU Driver; - Speakup Console Speech Driver; - ACPI drivers; - Android drivers; - Serial ATA and Parallel ATA drivers; - Auxiliary display drivers; - Drivers core; - Micron PCIe SSD driver; - Null block device driver; - Ublk userspace block driver; - Compressed RAM block device driver; - Bluetooth drivers; - Bus devices; - AMD CDX bus driver; - Hardware random number generator core; - Character device driver; - TPM device driver; - Clock framework and drivers; - Clocksource drivers; - CPU frequency scaling framework; - CPU idle management framework; - Hardware crypto device drivers; - CXL (Compute Express Link) drivers; - DAX dirext access to differentiated memory framework; - DIBS (Direct Internal Buffer Sharing) drivers; - Buffer Sharing and Synchronization framework; - DMA engine subsystem; - DPLL subsystem; - EDAC drivers; - FireWire subsystem; - ARM SCMI message protocol; - ARM SCPI message protocol; - Google firmware drivers; - Qualcomm firmware drivers; - FPGA Framework; - GPIO subsystem; - GPU drivers; - HID subsystem; - HSI subsystem; - Microsoft Hyper-V drivers; - Hardware monitoring drivers; - CoreSight HW tracing drivers; - I2C subsystem; - I3C subsystem; - IIO subsystem; - IIO ADC drivers; - InfiniBand drivers; - Input Device core drivers; - Input Device (Miscellaneous) drivers; - Input Device (Mouse) drivers; - On-Chip Interconnect management framework; - IOMMU subsystem; - Industry Pack bus drivers; - IRQ chip drivers; - Mailbox framework; - Media drivers; - MemoryStick subsystem; - Multifunction device drivers; - Analog Devices digital potentiometer driver; - Broadcom VK accelerator driver; - Fastrpc Driver; - Amazon Nitro Secure Module driver; - SGI GRU driver; - MMC subsystem; - MTD block device drivers; - Network drivers; - Ethernet bonding driver; - Mellanox network drivers; - Microsoft Azure Network Adapter (MANA) driver; - STMicroelectronics network drivers; - Texas Instruments network drivers; - Ethernet team driver; - MediaTek network drivers; - Near Field Communication (NFC) drivers; - NTB driver; - NVDIMM (Non-Volatile Memory Device) drivers; - NVME drivers; - Device tree and open firmware driver; - Operating Performance Points (OPP) driver; - PA-RISC drivers; - PCI subsystem; - Performance monitor drivers; - PHY drivers; - Pin controllers subsystem; - Chrome hardware platform drivers; - Mellanox platform drivers; - Microsoft Surface platform drivers; - x86 platform drivers; - MediaTek PM domains; - Power sequencing drivers; - Power supply drivers; - Powercap sysfs driver; - PTP clock framework; - PWM drivers; - RapidIO drivers; - Voltage and Current Regulator drivers; - Remote Processor subsystem; - MPAM driver; - RPMSG subsystem; - Real Time Clock drivers; - S/390 drivers; - SCSI subsystem; - ASPEED SoC drivers; - Samsung SoC drivers; - SPI subsystem; - small TFT LCD display modules; - Greybus lights staging drivers; - Media staging dri

References

Community reviews

Loading reviews…