<?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-20T21:03:42.458211+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/fkie_cve-2026-99487</id>
    <title>fkie_cve-2026-99487</title>
    <updated>2026-11-20T21:03:42.462117+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>rust: bug: pass TAINT_WARN to warn_slowpath_fmt() on UML</p>
<p>On UML, `warn_flags!` calls `warn_slowpath_fmt()` directly. Its third
argument is a taint number, but `warn_on!` passes its bug flags there.</p>
<p>As a result, `add_taint()` gets 2304 instead of 9 (`TAINT_WARN`). The
warning is not recorded: `/proc/sys/kernel/tainted` stays 0 after
`warn_on!` fires, where it should be 512. It also causes an
out-of-bounds write in `add_taint()`.</p>
<p>Pass `TAINT_WARN` directly, as C does on UML.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-99487"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-3xfj-g4c3-8vqx</id>
    <title>GHSA-3xfj-g4c3-8vqx</title>
    <updated>2026-11-20T21:03:42.462235+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>rust: bug: pass TAINT_WARN to warn_slowpath_fmt() on UML</p>
<p>On UML, `warn_flags!` calls `warn_slowpath_fmt()` directly. Its third
argument is a taint number, but `warn_on!` passes its bug flags there.</p>
<p>As a result, `add_taint()` gets 2304 instead of 9 (`TAINT_WARN`). The
warning is not recorded: `/proc/sys/kernel/tainted` stays 0 after
`warn_on!` fires, where it should be 512. It also causes an
out-of-bounds write in `add_taint()`.</p>
<p>Pass `TAINT_WARN` directly, as C does on UML.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-3xfj-g4c3-8vqx"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/msrc_cve-2026-99487</id>
    <title>msrc_CVE-2026-99487 — rust: bug: pass TAINT_WARN to warn_slowpath_fmt() on UML</title>
    <updated>2026-11-20T21:03:42.462278+00:00</updated>
    <content>msrc_CVE-2026-99487</content>
    <link href="https://db.gcve.eu/vuln/msrc_cve-2026-99487"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/wid-sec-w-2026-4695</id>
    <title>WID-SEC-W-2026-4695 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
    <updated>2026-11-20T21:03:42.462309+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 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</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/wid-sec-w-2026-4695"/>
  </entry>
</feed>
