<?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://db.gcve.eu</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>Thu, 19 Nov 2026 18:23:15 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-23411 — apparmor: fix race between freeing data and fs accessing it</title>
      <link>https://db.gcve.eu/vuln/cve-2026-23411</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;apparmor: fix race between freeing data and fs accessing it&lt;/p&gt;
&lt;p&gt;AppArmor was putting the reference to i_private data on its end after
removing the original entry from the file system. However the inode
can aand does live beyond that point and it is possible that some of
the fs call back functions will be invoked after the reference has
been put, which results in a race between freeing the data and
accessing it through the fs.&lt;/p&gt;
&lt;p&gt;While the rawdata/loaddata is the most likely candidate to fail the
race, as it has the fewest references. If properly crafted it might be
possible to trigger a race for the other types stored in i_private.&lt;/p&gt;
&lt;p&gt;Fix this by moving the put of i_private referenced data to the correct
place which is during inode eviction.&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;apparmor: fix race between freeing data and fs accessing it&lt;/p&gt;
&lt;p&gt;AppArmor was putting the reference to i_private data on its end after
removing the original entry from the file system. However the inode
can aand does live beyond that point and it is possible that some of
the fs call back functions will be invoked after the reference has
been put, which results in a race between freeing the data and
accessing it through the fs.&lt;/p&gt;
&lt;p&gt;While the rawdata/loaddata is the most likely candidate to fail the
race, as it has the fewest references. If properly crafted it might be
possible to trigger a race for the other types stored in i_private.&lt;/p&gt;
&lt;p&gt;Fix this by moving the put of i_private referenced data to the correct
place which is during inode eviction.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-23411</guid>
    </item>
    <item>
      <title>USN-8098-10 — linux-raspi, linux-raspi-5.4 vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-8098-10</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:18.04:LTS: linux-raspi-5.4, Ubuntu:Pro:20.04:LTS: linux-raspi&lt;/p&gt;
&lt;p&gt;Qualys discovered that several vulnerabilities existed in the AppArmor
Linux kernel Security Module (LSM). An unprivileged local attacker could
use these issues to load, replace, and remove arbitrary AppArmor profiles
causing denial of service, exposure of sensitive information (kernel
memory), local privilege escalation, or possibly escape a container.
(LP: #2143853)&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:
  - x86 architecture;
  - GPIO subsystem;
  - GPU drivers;
  - BTRFS file system;
  - XFRM subsystem;
  - IPv4 networking;
  - IPv6 networking;
  - MAC80211 subsystem;
  - SMC sockets;
(CVE-2021-47599, CVE-2022-48875, CVE-2022-49072, CVE-2024-49927,
CVE-2024-56640, CVE-2025-21780, CVE-2025-40215)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:18.04:LTS: linux-raspi-5.4, Ubuntu:Pro:20.04:LTS: linux-raspi&lt;/p&gt;
&lt;p&gt;Qualys discovered that several vulnerabilities existed in the AppArmor
Linux kernel Security Module (LSM). An unprivileged local attacker could
use these issues to load, replace, and remove arbitrary AppArmor profiles
causing denial of service, exposure of sensitive information (kernel
memory), local privilege escalation, or possibly escape a container.
(LP: #2143853)&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:
  - x86 architecture;
  - GPIO subsystem;
  - GPU drivers;
  - BTRFS file system;
  - XFRM subsystem;
  - IPv4 networking;
  - IPv6 networking;
  - MAC80211 subsystem;
  - SMC sockets;
(CVE-2021-47599, CVE-2022-48875, CVE-2022-49072, CVE-2024-49927,
CVE-2024-56640, CVE-2025-21780, CVE-2025-40215)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-8098-10</guid>
    </item>
  </channel>
</rss>
