<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-19T16:56:07.325012+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/cve-2026-23409</id>
    <title>CVE-2026-23409 — apparmor: fix differential encoding verification</title>
    <updated>2026-11-19T16:56:07.334357+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>apparmor: fix differential encoding verification</p>
<p>Differential encoding allows loops to be created if it is abused. To
prevent this the unpack should verify that a diff-encode chain
terminates.</p>
<p>Unfortunately the differential encode verification had two bugs.</p>
<p>1. it conflated states that had gone through check and already been
   marked, with states that were currently being checked and marked.
   This means that loops in the current chain being verified are treated
   as a chain that has already been verified.</p>
<p>2. the order bailout on already checked states compared current chain
   check iterators j,k instead of using the outer loop iterator i.
   Meaning a step backwards in states in the current chain verification
   was being mistaken for moving to an already verified state.</p>
<p>Move to a double mark scheme where already verified states get a
different mark, than the current chain being kept. This enables us
to also drop the backwards verification check that was the cause of
the second error as any already verified state is already marked.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-23409"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/usn-8098-10</id>
    <title>USN-8098-10 — linux-raspi, linux-raspi-5.4 vulnerabilities</title>
    <updated>2026-11-19T16:56:07.334471+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:18.04:LTS: linux-raspi-5.4, Ubuntu:Pro:20.04:LTS: linux-raspi</p>
<p>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)</p>
<p>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)</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/usn-8098-10"/>
  </entry>
</feed>
