<?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>Fri, 20 Nov 2026 21:05:10 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99473</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99473</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KVM: guest_memfd: Gracefully handle xarray errors when binding a memslot&lt;/p&gt;
&lt;p&gt;If inserting a memslot into a guest_memfd&amp;#39;s bindings xarray fails,
propagate the error back to the caller, i.e. fail memslot creation as well.
Signalling success and continuing on with memslot creation results in
use-after-free, as the guest_memfd instance will remain reachable via the
memslot after the file is freed (kvm_gmem_release() won&amp;#39;t nullify the file
pointer due to lack of a valid binding).&lt;/p&gt;
&lt;p&gt;Opportunistically WARN and reject binding if KVM_MEMSLOT_GMEM_ONLY is
already set, partly to guard against goofs elsewhere, but mostly so that
KVM doesn&amp;#39;t need to worry about clobbering flags when unwinding on failure.&lt;/p&gt;
&lt;p&gt;Regarding the unwind, the slot must be fully prepared before inserting it
into the bindings, at which point the slot becomes reachable.  I.e. waiting
to update the slot in order to avoid the ugly unwind isn&amp;#39;t an option.  And
as part of the unwind, explicitly nullify the relevant bindings, as xarray
can store a subset of entries when populating a range.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KVM: guest_memfd: Gracefully handle xarray errors when binding a memslot&lt;/p&gt;
&lt;p&gt;If inserting a memslot into a guest_memfd&amp;#39;s bindings xarray fails,
propagate the error back to the caller, i.e. fail memslot creation as well.
Signalling success and continuing on with memslot creation results in
use-after-free, as the guest_memfd instance will remain reachable via the
memslot after the file is freed (kvm_gmem_release() won&amp;#39;t nullify the file
pointer due to lack of a valid binding).&lt;/p&gt;
&lt;p&gt;Opportunistically WARN and reject binding if KVM_MEMSLOT_GMEM_ONLY is
already set, partly to guard against goofs elsewhere, but mostly so that
KVM doesn&amp;#39;t need to worry about clobbering flags when unwinding on failure.&lt;/p&gt;
&lt;p&gt;Regarding the unwind, the slot must be fully prepared before inserting it
into the bindings, at which point the slot becomes reachable.  I.e. waiting
to update the slot in order to avoid the ugly unwind isn&amp;#39;t an option.  And
as part of the unwind, explicitly nullify the relevant bindings, as xarray
can store a subset of entries when populating a range.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99473</guid>
    </item>
    <item>
      <title>GHSA-4rww-grmf-xvgg</title>
      <link>https://db.gcve.eu/vuln/ghsa-4rww-grmf-xvgg</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KVM: guest_memfd: Gracefully handle xarray errors when binding a memslot&lt;/p&gt;
&lt;p&gt;If inserting a memslot into a guest_memfd&amp;#39;s bindings xarray fails,
propagate the error back to the caller, i.e. fail memslot creation as well.
Signalling success and continuing on with memslot creation results in
use-after-free, as the guest_memfd instance will remain reachable via the
memslot after the file is freed (kvm_gmem_release() won&amp;#39;t nullify the file
pointer due to lack of a valid binding).&lt;/p&gt;
&lt;p&gt;Opportunistically WARN and reject binding if KVM_MEMSLOT_GMEM_ONLY is
already set, partly to guard against goofs elsewhere, but mostly so that
KVM doesn&amp;#39;t need to worry about clobbering flags when unwinding on failure.&lt;/p&gt;
&lt;p&gt;Regarding the unwind, the slot must be fully prepared before inserting it
into the bindings, at which point the slot becomes reachable.  I.e. waiting
to update the slot in order to avoid the ugly unwind isn&amp;#39;t an option.  And
as part of the unwind, explicitly nullify the relevant bindings, as xarray
can store a subset of entries when populating a range.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KVM: guest_memfd: Gracefully handle xarray errors when binding a memslot&lt;/p&gt;
&lt;p&gt;If inserting a memslot into a guest_memfd&amp;#39;s bindings xarray fails,
propagate the error back to the caller, i.e. fail memslot creation as well.
Signalling success and continuing on with memslot creation results in
use-after-free, as the guest_memfd instance will remain reachable via the
memslot after the file is freed (kvm_gmem_release() won&amp;#39;t nullify the file
pointer due to lack of a valid binding).&lt;/p&gt;
&lt;p&gt;Opportunistically WARN and reject binding if KVM_MEMSLOT_GMEM_ONLY is
already set, partly to guard against goofs elsewhere, but mostly so that
KVM doesn&amp;#39;t need to worry about clobbering flags when unwinding on failure.&lt;/p&gt;
&lt;p&gt;Regarding the unwind, the slot must be fully prepared before inserting it
into the bindings, at which point the slot becomes reachable.  I.e. waiting
to update the slot in order to avoid the ugly unwind isn&amp;#39;t an option.  And
as part of the unwind, explicitly nullify the relevant bindings, as xarray
can store a subset of entries when populating a range.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-4rww-grmf-xvgg</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-99473 — KVM: guest_memfd: Gracefully handle xarray errors when binding a memslot</title>
      <link>https://db.gcve.eu/vuln/msrc_cve-2026-99473</link>
      <description>msrc_CVE-2026-99473</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/msrc_cve-2026-99473</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4695 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4695</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2026-4695</guid>
    </item>
  </channel>
</rss>
