<?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-10-24T20:31:17.409347+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-98883</id>
    <title>CVE-2026-98883 — serial: 8250_port: recognize UPIO_AU</title>
    <updated>2026-10-24T20:31:17.411823+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>serial: 8250_port: recognize UPIO_AU</p>
<p>My MIPS Alchemy systems generate the following warning during
probe of the 8250 driver:</p>
<p>WARNING: drivers/tty/serial/8250/8250_port.c:462 at set_io_from_upio+0xfc/0x124, CPU#0: swapper/0/1
Unsupported UART type 4
[...]
[&lt;80521d40&gt;] set_io_from_upio+0xfc/0x124
[&lt;80521dfc&gt;] serial8250_set_defaults+0x94/0xe0
[&lt;80520fb4&gt;] serial8250_register_8250_port+0x288/0x51c
[&lt;805214ec&gt;] serial8250_probe+0x160/0x1e8
[&lt;8053b5f0&gt;] platform_probe+0x64/0x90</p>
<p>The least invasive fix is to recognize UPIO_AU (type 4) in set_io_from_upio()
and do nothing, since all parameters have already been set up in
8250_rt288x.c::au_platform_setup().</p>
<p>Run-tested on Alchemy Au1300 platform.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-98883"/>
  </entry>
</feed>
