<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 30 Sep 2026 10:47:14 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-72279 — KVM: arm64: nv: Respect read-only PFN when mapping L1 VNCR</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-72279</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KVM: arm64: nv: Respect read-only PFN when mapping L1 VNCR&lt;/p&gt;
&lt;p&gt;KVM currently maps the L1 VNCR into the host stage-1 by relying entirely
on the permissions of the guest stage-1. At the same time, it is
entirely possible that the backing PFN is read-only (e.g. RO memslot),
meaning that the L1 VNCR should use at most a read-only mapping.&lt;/p&gt;
&lt;p&gt;Cache the writability of the PFN in the VNCR TLB and use it to constrain
the resulting fixmap permissions. Promote VNCR permission faults to an
SEA in the case where the guest attempts to write to a read-only
endpoint. Conveniently, this also plugs a page leak found by Sashiko [*]
resulting from the early return for a read-only PFN.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KVM: arm64: nv: Respect read-only PFN when mapping L1 VNCR&lt;/p&gt;
&lt;p&gt;KVM currently maps the L1 VNCR into the host stage-1 by relying entirely
on the permissions of the guest stage-1. At the same time, it is
entirely possible that the backing PFN is read-only (e.g. RO memslot),
meaning that the L1 VNCR should use at most a read-only mapping.&lt;/p&gt;
&lt;p&gt;Cache the writability of the PFN in the VNCR TLB and use it to constrain
the resulting fixmap permissions. Promote VNCR permission faults to an
SEA in the case where the guest attempts to write to a read-only
endpoint. Conveniently, this also plugs a page leak found by Sashiko [*]
resulting from the early return for a read-only PFN.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-72279</guid>
    </item>
    <item>
      <title>USN-8816-1 — linux, linux-aws, linux-aws-7.0, linux-hwe-7.0, linux-ibm, linux-oracle, linux-raspi, linux-realtime vulnerabilities</title>
      <link>https://vulnerability.circl.lu/vuln/usn-8816-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-aws-7.0, Ubuntu:24.04:LTS: linux-hwe-7.0, Ubuntu:26.04:LTS: linux, Ubuntu:26.04:LTS: linux-aws, Ubuntu:26.04:LTS: linux-ibm, Ubuntu:26.04:LTS: linux-oracle, Ubuntu:26.04:LTS: linux-raspi, Ubuntu:26.04:LTS: linux-realtime&lt;/p&gt;
&lt;p&gt;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:
  - ARM64 architecture;
  - S390 architecture;
  - x86 architecture;
  - DRBD Distributed Replicated Block Device drivers;
  - InfiniBand drivers;
  - IOMMU subsystem;
  - Multiple devices driver;
  - Network drivers;
  - Microsoft Azure Network Adapter (MANA) driver;
  - NVME drivers;
  - TCM subsystem;
  - Virtio Host (VHOST) subsystem;
  - Xen hypervisor drivers;
  - AFS file system;
  - File systems infrastructure;
  - Network file systems library;
  - Network file system (NFS) client;
  - NTFS3 file system;
  - OCFS2 file system;
  - OrangeFS file system;
  - SMB network file system;
  - IPv4 networking;
  - Sun RPC protocol;
  - IPv6 networking;
  - IP tunnels definitions;
  - Netfilter;
  - TCP network protocol;
  - Locking primitives;
  - 9P file system network protocol;
  - B.A.T.M.A.N. meshing protocol;
  - Networking core;
  - IFE protocol;
  - RxRPC session sockets;
  - Network traffic control;
  - SCTP protocol;
  - SMC sockets;
  - TIPC protocol;
  - XFRM subsystem;
(CVE-2026-64530, CVE-2026-64534, CVE-2026-64535, CVE-2026-64541,
CVE-2026-64551, CVE-2026-68083, CVE-2026-68457, CVE-2026-68476,
CVE-2026-68477, CVE-2026-72014, CVE-2026-72020, CVE-2026-72033,
CVE-2026-72041, CVE-2026-72046, CVE-2026-72064, CVE-2026-72065,
CVE-2026-72069, CVE-2026-72083, CVE-2026-72084, CVE-2026-72085,
CVE…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-aws-7.0, Ubuntu:24.04:LTS: linux-hwe-7.0, Ubuntu:26.04:LTS: linux, Ubuntu:26.04:LTS: linux-aws, Ubuntu:26.04:LTS: linux-ibm, Ubuntu:26.04:LTS: linux-oracle, Ubuntu:26.04:LTS: linux-raspi, Ubuntu:26.04:LTS: linux-realtime&lt;/p&gt;
&lt;p&gt;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:
  - ARM64 architecture;
  - S390 architecture;
  - x86 architecture;
  - DRBD Distributed Replicated Block Device drivers;
  - InfiniBand drivers;
  - IOMMU subsystem;
  - Multiple devices driver;
  - Network drivers;
  - Microsoft Azure Network Adapter (MANA) driver;
  - NVME drivers;
  - TCM subsystem;
  - Virtio Host (VHOST) subsystem;
  - Xen hypervisor drivers;
  - AFS file system;
  - File systems infrastructure;
  - Network file systems library;
  - Network file system (NFS) client;
  - NTFS3 file system;
  - OCFS2 file system;
  - OrangeFS file system;
  - SMB network file system;
  - IPv4 networking;
  - Sun RPC protocol;
  - IPv6 networking;
  - IP tunnels definitions;
  - Netfilter;
  - TCP network protocol;
  - Locking primitives;
  - 9P file system network protocol;
  - B.A.T.M.A.N. meshing protocol;
  - Networking core;
  - IFE protocol;
  - RxRPC session sockets;
  - Network traffic control;
  - SCTP protocol;
  - SMC sockets;
  - TIPC protocol;
  - XFRM subsystem;
(CVE-2026-64530, CVE-2026-64534, CVE-2026-64535, CVE-2026-64541,
CVE-2026-64551, CVE-2026-68083, CVE-2026-68457, CVE-2026-68476,
CVE-2026-68477, CVE-2026-72014, CVE-2026-72020, CVE-2026-72033,
CVE-2026-72041, CVE-2026-72046, CVE-2026-72064, CVE-2026-72065,
CVE-2026-72069, CVE-2026-72083, CVE-2026-72084, CVE-2026-72085,
CVE…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/usn-8816-1</guid>
    </item>
  </channel>
</rss>
