Lucene search
+L

5975 matches found

OSV
OSV
•added 2026/09/16 11:17 a.m.•13 views

DEBIAN-CVE-2026-89981

In the Linux kernel, the following vulnerability has been resolved: arm64: Don't read GMIDEL1 when MTE is disabled cpuinfostorecpu gates the GMIDEL1 read on the raw IDAA64PFR1EL1, so it reads the register even when the kernel has disabled MTE CONFIGARM64MTE=n or arm64.nomte. KVM sets HCREL2.TID5 ...

5.9AI score0.00198EPSS
SaveExploits0References1
OSV
OSV
•added 2026/09/16 11:17 a.m.•19 views

DEBIAN-CVE-2026-89913

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: vgic-v3: take an LPI reference in vgicv3savependingtables vgicv3savependingtables iterates dist-lpixa using xaforeach and dereferences the returned struct vgicirq in the loop body without holding a reference on the LP...

8.8CVSS5.9AI score0.00196EPSS
SaveExploits0References1
OSV
OSV
•added 2026/09/16 11:17 a.m.•12 views

AZL-101282 CVE-2026-89913 affecting package kernel 6.6.157.1-1

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: vgic-v3: take an LPI reference in vgicv3savependingtables vgicv3savependingtables iterates dist-lpixa using xaforeach and dereferences the returned struct vgicirq in the loop body without holding a reference on the LP...

8.8CVSS5.8AI score0.00196EPSS
SaveExploits0References1
NVD
NVD
•added 2026/09/16 11:17 a.m.•15 views

CVE-2026-89913

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: vgic-v3: take an LPI reference in vgicv3savependingtables vgicv3savependingtables iterates dist-lpixa using xaforeach and dereferences the returned struct vgicirq in the loop body without holding a reference on the LP...

8.8CVSS0.00196EPSS
SaveExploits0References3
NVD
NVD
•added 2026/09/16 11:17 a.m.•23 views

CVE-2026-89916

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Make VNCR invalidation participate in MMU invalidation retry A VNCR TLB invalidation can occur on one vcpu while another vcpu is faulting in this same page. Without correctly handling this, we can end up with the...

9.3CVSS0.00194EPSS
SaveExploits0References3
NVD
NVD
•added 2026/09/16 11:17 a.m.•12 views

CVE-2026-89917

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Handle VNCR TLB invalidation race with vcpuput VNCR unmapping While VNCR TLB invalidation always occurs under the MMU lock, vcpuput doesn't, while it unmaps the VNCR page. The problem is that the invalidation evaluate...

0.00206EPSS
SaveExploits0References3
NVD
NVD
•added 2026/09/16 11:17 a.m.•16 views

CVE-2026-89911

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Correctly cap TLBI Range to the architural limit TLB Invalidation by Range has a fairly powerful way of encoding pretty large ranges in a small number of bits. This range can be based on an arbitrary VA, which means i...

7.9CVSS0.00159EPSS
SaveExploits0References3
NVD
NVD
•added 2026/09/16 11:17 a.m.•17 views

CVE-2026-89914

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Sign-extend VA for range-based TLBI invalidation When the decoderangetlbi helper was moved to be used for S1 TLBIs, the required sign extension was omitted. Add it. As a result, special care must be taken to not...

9.3CVSS0.00194EPSS
SaveExploits0References3
NVD
NVD
•added 2026/09/16 11:17 a.m.•14 views

CVE-2026-89918

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Correctly handle end of VA space TLBI invalidation Our TLB invalidation by VA code is based on comparing two ranges, one defined by the TLB, and one defined by the TLBI instruction. Each range is defined by a start an...

9.3CVSS0.00194EPSS
SaveExploits0References3
NVD
NVD
•added 2026/09/16 11:17 a.m.•17 views

CVE-2026-89915

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Remove VM-wide VNCR mapping counter The global VNCR mapping counter is used to decide whether an L1 provided VNCR page is mapped in L0 on any CPU at the point of dealing with a TLB invalidation. It is incremented when...

9.3CVSS0.00194EPSS
SaveExploits0References3
OSV
OSV
•added 2026/09/16 11:17 a.m.•11 views

DEBIAN-CVE-2026-89918

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Correctly handle end of VA space TLBI invalidation Our TLB invalidation by VA code is based on comparing two ranges, one defined by the TLB, and one defined by the TLBI instruction. Each range is defined by a start an...

9.3CVSS5.9AI score0.00194EPSS
SaveExploits0References1
OSV
OSV
•added 2026/09/16 11:17 a.m.•15 views

DEBIAN-CVE-2026-89911

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Correctly cap TLBI Range to the architural limit TLB Invalidation by Range has a fairly powerful way of encoding pretty large ranges in a small number of bits. This range can be based on an arbitrary VA, which means i...

7.9CVSS6.1AI score0.00159EPSS
SaveExploits0References1
OSV
OSV
•added 2026/09/16 11:17 a.m.•14 views

DEBIAN-CVE-2026-89915

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Remove VM-wide VNCR mapping counter The global VNCR mapping counter is used to decide whether an L1 provided VNCR page is mapped in L0 on any CPU at the point of dealing with a TLB invalidation. It is incremented when...

9.3CVSS5.9AI score0.00194EPSS
SaveExploits0References1
OSV
OSV
•added 2026/09/16 11:17 a.m.•14 views

DEBIAN-CVE-2026-89914

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Sign-extend VA for range-based TLBI invalidation When the decoderangetlbi helper was moved to be used for S1 TLBIs, the required sign extension was omitted. Add it. As a result, special care must be taken to not...

9.3CVSS5.9AI score0.00194EPSS
SaveExploits0References1
OSV
OSV
•added 2026/09/16 11:17 a.m.•10 views

DEBIAN-CVE-2026-89917

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Handle VNCR TLB invalidation race with vcpuput VNCR unmapping While VNCR TLB invalidation always occurs under the MMU lock, vcpuput doesn't, while it unmaps the VNCR page. The problem is that the invalidation evaluate...

5.8AI score0.00206EPSS
SaveExploits0References1
OSV
OSV
•added 2026/09/16 11:17 a.m.•14 views

DEBIAN-CVE-2026-89916

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Make VNCR invalidation participate in MMU invalidation retry A VNCR TLB invalidation can occur on one vcpu while another vcpu is faulting in this same page. Without correctly handling this, we can end up with the...

9.3CVSS5.8AI score0.00194EPSS
SaveExploits0References1
OSV
OSV
•added 2026/09/16 10:32 a.m.•13 views

CVE-2026-89981 arm64: Don't read GMID_EL1 when MTE is disabled

In the Linux kernel, the following vulnerability has been resolved: arm64: Don't read GMIDEL1 when MTE is disabled cpuinfostorecpu gates the GMIDEL1 read on the raw IDAA64PFR1EL1, so it reads the register even when the kernel has disabled MTE CONFIGARM64MTE=n or arm64.nomte. KVM sets HCREL2.TID5 ...

5.8AI score
SaveExploits0References5
CVE
CVE
•added 2026/09/16 10:32 a.m.•22 views

CVE-2026-89981

CVE-2026-89981 affects the Linux kernel on arm64 platforms. The __cpuinfo_store_cpu() function reads the GMID_EL1 register based on the raw ID_AA64PFR1_EL1 value, even when the kernel has MTE disabled (CONFIG_ARM64_MTE=n or arm64.nomte). In a pKVM (protected KVM) environment, KVM sets HCR_EL2.TID...

5.8AI score0.00198EPSS
SaveExploits0References2
Cvelist
Cvelist
•added 2026/09/16 10:32 a.m.•37 views

CVE-2026-89981 arm64: Don't read GMID_EL1 when MTE is disabled

In the Linux kernel, the following vulnerability has been resolved: arm64: Don't read GMIDEL1 when MTE is disabled cpuinfostorecpu gates the GMIDEL1 read on the raw IDAA64PFR1EL1, so it reads the register even when the kernel has disabled MTE CONFIGARM64MTE=n or arm64.nomte. KVM sets HCREL2.TID5 ...

0.00198EPSS
SaveExploits0References2
CVE
CVE
•added 2026/09/16 10:32 a.m.•21 views

CVE-2026-89918

CVE-2026-89918 affects the Linux kernel KVM arm64 subsystem. The root cause is a flaw in the TLB invalidation (TLBI) by virtual address range: when the TLBI instruction's range reaches the end of the TTBR1 VA space , the expression base + size wraps around to 0, causing the range comparison to fa...

9.3CVSS5.8AI score0.00194EPSS
SaveExploits0References3
Rows per page
Query Builder