<?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://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-03T14:25:49.348928+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" 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://vulnerability.circl.lu/vuln/certfr-2026-avi-0316</id>
    <title>certfr-2026-avi-0316 — De multiples vulnérabilités ont été découvertes dans les produits VMware. Elles permettent à un attaquant de provoquer…</title>
    <updated>2026-10-03T14:25:50.000163+00:00</updated>
    <content>certfr-2026-avi-0316</content>
    <link href="https://vulnerability.circl.lu/vuln/certfr-2026-avi-0316"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/fkie_cve-2022-50720</id>
    <title>fkie_cve-2022-50720</title>
    <updated>2026-10-03T14:25:50.000335+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>x86/apic: Don't disable x2APIC if locked</p>
<p>The APIC supports two modes, legacy APIC (or xAPIC), and Extended APIC
(or x2APIC).  X2APIC mode is mostly compatible with legacy APIC, but
it disables the memory-mapped APIC interface in favor of one that uses
MSRs.  The APIC mode is controlled by the EXT bit in the APIC MSR.</p>
<p>The MMIO/xAPIC interface has some problems, most notably the APIC LEAK
[1].  This bug allows an attacker to use the APIC MMIO interface to
extract data from the SGX enclave.</p>
<p>Introduce support for a new feature that will allow the BIOS to lock
the APIC in x2APIC mode.  If the APIC is locked in x2APIC mode and the
kernel tries to disable the APIC or revert to legacy APIC mode a GP
fault will occur.</p>
<p>Introduce support for a new MSR (IA32_XAPIC_DISABLE_STATUS) and handle
the new locked mode when the LEGACY_XAPIC_DISABLED bit is set by
preventing the kernel from trying to disable the x2APIC.</p>
<p>On platforms with the IA32_XAPIC_DISABLE_STATUS MSR, if SGX or TDX are
enabled the LEGACY_XAPIC_DISABLED will be set by the BIOS.  If
legacy APIC is required, then it SGX and TDX need to be disabled in the
BIOS.</p>
<p>[1]: https://aepicleak.com/aepicleak.pdf</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2022-50720"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-pc73-7j79-5x2x</id>
    <title>GHSA-pc73-7j79-5x2x</title>
    <updated>2026-10-03T14:25:50.000467+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>x86/apic: Don't disable x2APIC if locked</p>
<p>The APIC supports two modes, legacy APIC (or xAPIC), and Extended APIC
(or x2APIC).  X2APIC mode is mostly compatible with legacy APIC, but
it disables the memory-mapped APIC interface in favor of one that uses
MSRs.  The APIC mode is controlled by the EXT bit in the APIC MSR.</p>
<p>The MMIO/xAPIC interface has some problems, most notably the APIC LEAK
[1].  This bug allows an attacker to use the APIC MMIO interface to
extract data from the SGX enclave.</p>
<p>Introduce support for a new feature that will allow the BIOS to lock
the APIC in x2APIC mode.  If the APIC is locked in x2APIC mode and the
kernel tries to disable the APIC or revert to legacy APIC mode a GP
fault will occur.</p>
<p>Introduce support for a new MSR (IA32_XAPIC_DISABLE_STATUS) and handle
the new locked mode when the LEGACY_XAPIC_DISABLED bit is set by
preventing the kernel from trying to disable the x2APIC.</p>
<p>On platforms with the IA32_XAPIC_DISABLE_STATUS MSR, if SGX or TDX are
enabled the LEGACY_XAPIC_DISABLED will be set by the BIOS.  If
legacy APIC is required, then it SGX and TDX need to be disabled in the
BIOS.</p>
<p>[1]: https://aepicleak.com/aepicleak.pdf</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-pc73-7j79-5x2x"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/rhsa-2024:8613</id>
    <title>RHSA-2024:8613 — Red Hat Security Advisory: kernel security update</title>
    <updated>2026-10-03T14:25:50.000523+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>kernel: hwmon: (w83793) Fix NULL pointer dereference by removing unnecessary structure field kernel: x86/apic: Don't disable x2APIC if locked kernel: ovl: fix use after free in struct ovl_aio_req kernel: mm/sparsemem: fix race in accessing memory_section-&gt;usage hw: cpu: intel: Native Branch History Injection (BHI) kernel: blk-mq: fix IO hang from sbitmap wakeup race kernel: fs/proc: do_task_stat: use sig-&gt;stats_lock to gather the threads/children stats kernel: mptcp: fix data re-injection from stale subflow kernel: mac802154: fix llsec key resources release in mac802154_llsec_key_del kernel: mptcp: ensure snd_nxt is properly initialized on connect kernel: ipv6: prevent possible NULL dereference in rt6_probe() kernel: ext4: fix uninitialized ratelimit_state-&amp;gt;lock access in __ext4_fill_super() kernel: filelock: fix potential use-after-free in posix_lock_inode kernel: mm: prevent derefencing NULL ptr in pfn_section_valid() kernel: powerpc/eeh: avoid possible crash when edev-&amp;gt;pdev changes kernel: nvmet: fix a possible leak when destroy a ctrl during qp establishment</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/rhsa-2024:8613"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ubuntu-cve-2022-50720</id>
    <title>UBUNTU-CVE-2022-50720</title>
    <updated>2026-10-03T14:25:50.000623+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 171 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: x86/apic: Don't disable x2APIC if locked The APIC supports two modes, legacy APIC (or xAPIC), and Extended APIC (or x2APIC).  X2APIC mode is mostly compatible with legacy APIC, but it disables the memory-mapped APIC interface in favor of one that uses MSRs.  The APIC mode is controlled by the EXT bit in the APIC MSR. The MMIO/xAPIC interface has some problems, most notably the APIC LEAK [1].  This bug allows an attacker to use the APIC MMIO interface to extract data from the SGX enclave. Introduce support for a new feature that will allow the BIOS to lock the APIC in x2APIC mode.  If the APIC is locked in x2APIC mode and the kernel tries to disable the APIC or revert to legacy APIC mode a GP fault will occur. Introduce support for a new MSR (IA32_XAPIC_DISABLE_STATUS) and handle the new locked mode when the LEGACY_XAPIC_DISABLED bit is set by preventing the kernel from trying to disable the x2APIC. On platforms with the IA32_XAPIC_DISABLE_STATUS MSR, if SGX or TDX are enabled the LEGACY_XAPIC_DISABLED will be set by the BIOS.  If legacy APIC is required, then it SGX and TDX need to be disabled in the BIOS. [1]: https://aepicleak.com/aepicleak.pdf</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ubuntu-cve-2022-50720"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/wid-sec-w-2025-2929</id>
    <title>WID-SEC-W-2025-2929 — Linux Kernel: Mehrere Schwachstellen</title>
    <updated>2026-10-03T14:25:50.001060+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/wid-sec-w-2025-2929"/>
  </entry>
</feed>
