VulnerabilityPublished 22 Sep 2026Updated 27 Oct 2026

CVE-2025-10263: linux-azure, linux-oracle vulnerabilities

Affects Linux kernelSource GCVE Database

Authoritative record:CVE-2025-10263· Critical 9.1

Not known to be exploited · CVSS 9.1 Critical · fixed in 7.0.0-1014.14 : patch Linux kernel as a priority.

Data as of 28 Oct 2026, 05:11 UTC

CVSS 3.1 base score

9.1Critical

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

EPSS: 0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 7.0.0-1014.14, 7.0.0-1011.11

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

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

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
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: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, 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-8726-4

What to do

Upgrade the Ubuntu to 7.0.0-1014.14 (linux-azure package) or 7.0.0-1011.11 (linux-oracle package).

Patches and advisories

ubuntu.com/security/notices/USN-8726-4 (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-1014.14	Fixed in 7.0.0-1014.14
Ubuntu 26.04 LTSlinux-oracle`pkg:deb/ubuntu/linux-oracle?arch=source&distro=resolute`Other threats	Affected <7.0.0-1011.11	Fixed in 7.0.0-1011.11

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

AI-suggested

A patch is available and should be applied promptly. The vendor advisory (Ubuntu USN-8726-4) provides updated linux-azure and linux-oracle kernel package versions that fix these vulnerabilities. After applying the update, a system reboot is required to activate the fixes. Note that due to an ABI change, third-party kernel modules must be recompiled and reinstalled. Users should update to linux-image versions 7.0.0-1014.14 (azure) and 7.0.0-1011.11 (oracle) or later as specified in the advisory.

Description

Multiple security vulnerabilities were discovered in the Linux kernel affecting numerous subsystems and architectures, including ARM64, ARM32, RISC-V, x86, and others. One notable issue (CVE-2025-10263) involves some ARM processors completing a broadcast TLB invalidation before memory writes through the invalidated translation are globally observed, potentially allowing a local attacker to write to memory after permission revocation, bypassing protections or escalating privileges. These flaws could allow attackers to compromise affected systems. Updates correcting these issues are available for linux-azure and linux-oracle kernels.

Impact

A local attacker could exploit the ARM TLB invalidation flaw to write to memory after permissions have been revoked, potentially bypassing memory protections or escalating privileges. The other identified vulnerabilities across numerous kernel subsystems could also be leveraged to compromise system integrity or security. The overall impact is the potential for local privilege escalation and system compromise if unpatched.

References

Community reviews

Loading reviews…